computer games forum

Ok I guess I need to put a walkthrough... you can beat that boss fight but you need to find the right strategy:

I preordered, and yes, I want to see it and I'll be glad to help test it. I'd offer to help program it, but I don't have any skills for that sadly.

Hm well at this point I think I might just make it public, since everyone who preordered seems eager to play
Will make another thread!
About helping don't worry, playtesting is already enough. Is not good to be so "disgusted" (only because I played it TOO MUCH) about a game, so even if I fix a bug I need to test it again

Tried like in walkthrough, still dead end.Example how i did:

Sorry, the right sequence is:

Update: I'm planning everything on paper first, but I think I have an idea so I can reuse 90% of the existing script, but made it in a more linear way that will avoid all those problems.
Ideally this time when will put the game on testing, you'd find max 1-2 plot bugs but nothing more I think in 2 weeks I should be able to finish, maybe sooner!

Jack,
I appreciate you. I'm glad you want to release a bug-free product.
Very respectfully,
fleet

jack1974 wrote:Update: I'm planning everything on paper first, but I think I have an idea so I can reuse 90% of the existing script, but made it in a more linear way that will avoid all those problems.
Ideally this time when will put the game on testing, you'd find max 1-2 plot bugs but nothing more I think in 2 weeks I should be able to finish, maybe sooner!

Why not split it separately, one BH2: Earth and BH2: Mars? so you don't have to lose 10%?

Well what I'm going to try now is to keep the same scenes list, but have a central script that calls each one, so all the game logic is concentrated in 30-40 lines of code. Before there were jumps all around the script, which was making debugging it a nightmare (you would have to scroll pages of text to find the jump commands). Perhaps this system will work already, so nothing will be lost

jack1974 wrote:Well what I'm going to try now is to keep the same scenes list, but have a central script that calls each one, so all the game logic is concentrated in 30-40 lines of code. Before there were jumps all around the script, which was making debugging it a nightmare (you would have to scroll pages of text to find the jump commands). Perhaps this system will work already, so nothing will be lost

Uggh...there should be a law against spaghetti code. The more complex code gets, the better organized it needs to be. Otherwise we end up with a debugging nightmare like the one you've been facing. My condolences. In the future you may want to consider asking your writers to check in their code regularly so you can see if it's getting out of hand much earlier in the development process.