Discussions

Collision checking should come AFTER any change in position (or rotation) -- that is, any change not dictated by collision to begin with. There are two actions that should be performed when a collision occurs: moving (or rotating) off the object collided with and turning. The first of these is often missed by young coders.

In act method of Space class, you can use: <Code Omitted> Thank you Dan, that was the code I was missing. I should also mention, my professor also said that we were not allowed to modify the act method, so I replaced line 100 of the Asteroid class with the if statement you posted. It looks like this:

You will need to have the Instructions object retain the message for later use (add a String field and assign message to it) and then add a setColor method to the class that acquires a color (via parameter argument) and creates and sets an appropriately colored new image.

To stop a sound, you need a reference to it. After you changed to the new world in line 34 of the Title_Screen class, you won’t have any further chance to get a reference to the sound object from the newly created world, so it will run forever. A few alternatives you could go for: 1) stop the sound before changing the world 2) pass a reference when you create the new world 3) make the sound a class variable (static) instead of an object variable to access it from anywhere more easily

<Code Omitted>

int timeOut = ((MyWorld)getWorld()).TimeOut();

If not in the world, then a reference to those actors must be maintained -- preferably, in a list (or a set of lists).

yes

Please refer to my Jump and Run Demo w/Moving Platform scenario. Run and click on Who button for code used.

The direction field is not required and only complicates things. Just negate the speed value to turn around. You will only need one setLocaton line that way, also. <Code Omitted> Remove count++; from act.

This appears to be an assignment. Maybe you should refer to the java tutorials for help on this, particularly the section on arguments.

Insert the following after line 133 in Projectile class: <Code Omitted>

Please refer to the Greefoot tutorials.

Those kind of errors are usually caused by having information blocks embedded in the files. Try re-saving the files w/o the information.

Uh sorri, I found out myself xd It's literally just <Code Omitted> well still thank you, and if this helped someone else, that's just better :p