Discussions

Minor quibble but: <Code Omitted> "Lose" is spelled as "lose". "loose" is how you describe a nut that needs tightening.

I believe your issue is due to the fact that 'questionTime' will only be called while the 'space' key is down (see condition of 'if' on line 60). In other words if you hold down the 'space' key and select an answer, you might find you made progress. Then, again, you may not. On lines 110, 121 and 132, you are comparing different String object to see if they are the same. They may contain the same internal character array, but the String objects are not the same. That is, the String objects created and assigned to the fields on lines 30 through 32 are not the same String objects created an

You did not act like a total noob -- you did use code tags around your code (or used the 'code' link below the reply box to insert the code into the post). (good job!) <Code Omitted>I used the blue 'if', and the condition is 'when it exceeds 35 degrees'. There is an Actor class method to get how many degrees the actor is turned and you know what you want to compare it to (or, at least, should be able to figure it out).

Phew, thanks again.

Hey! Sorry for the late response, I was trying to fix some other stuff in my code before i was able to implement this one. But it did work, thank you. So, for anyone who needs this i'll let my implementation using danpost idea here:

Check out this scenario.

I was going to suggest doing that, but I was not sure if it would work (I had noticed that 160 is 2 to the 7th power, or 128, more than 32, where 32 is the character number for a space).

You need to put the code for what you want to do when both tanks are destroyed at line 51 of the Game_World_Level_2 class.

So what do you want to do? Did you lose your code? Do you want to make a Mario game? I'm not sure what you are trying to ask.

thanks man :D

If you follow the logic of the code, you will realize where the problem is coming from. The act method starts with this: <Code Omitted>Now, assume the "w" key is pressed -- this is what happens: The first 'if' condition becomes true and the actor is rotated to 270 degrees and move up one cell. Then the second 'if' condition becomes false and the actor

The Actor class has several collision checking methods available that perform in different ways. Maybe you should check out the Actor class API documentation to see what is available because 'getOneObjectAtOffset' may not be the best one to use in this case.

It's finally fixed! Thank you very much for the fast reply and for the correcting my errors, danpost. :D