Discussions

Your Soldier class has one constructor. The one with a bunch of parameters. The subclasses should have a constructor which exists in the super class. So you could either create a constructor in the Soldier class without parameters. And/or the subclasses constructors should match. So the constructor of your Heavy class could look like this.

Apparently, rand is alternating between 0 and 1 inside the do loop, making x add and subtract; add and subtract. You need to be very careful with loops and make sure that they will eventually, at some point, be broken out of. Unfortunately, your coding is (1) undocumented; (2) bulky, and not easily readable; and (3) unfactored; -- making it virtually impossible to see what is going on (especially for an outsider). All I can say at this point is that you need better control of the flow within the loop. A visited cell should not be re-visited.

Thank you so much!!!!

Thank you, this prepare method at the bottom has become a habit for me. I really should bring it up to the top!

Ways to reverse it yourself might include: <Code Omitted>or <Code Omitted>("resu" is "user" backwards, if you were wondering)

Sorry, I no longer need to address this problem. This post took a long time to get approved, so I had to find my own way around it.

When your MyWorld object (or, your world) is created, the initial value of friendClicked is set to zero by line 107 (fields are created and set to their initial values before the constructor is executed). Since a constructor is only executed once per object created, the condition on line 31 will always be true and the else part of that if-else structure will never execute. Anything done after initial creation of an object cannot feasibly be coded in the constructor. Sometimes, some finalizing set-up is required once an actor is added to a world or when a world is

Change ‘world’ in line 20 to ‘getWorld()’. You might want to change ‘projectile’ to ‘new Projectile()’ as well.

Ok works fine now, thank you guys!

Okay. Possible solutions are (1) you could just remove the car collided with; or (2) you could create another class to take the image of collided car and replace the car with it.

Please refer to my Scrolling Tutorial scenario.

*ahem*, really?

That was little confusing -- as what would be the "original world". At any rate, let me explain this way. When you extend a class, what you are doing is creating a union of classes to describe the same type object as the class being extended creates. The extending class can add new possible states (fields) for the object or add, modify and/or remove behaviors that the object can do (by adding