Discussions

From within your subclass of World, you can use the getObjectsAt(int x, int y, Class clss) method. This will return a list of actors of given type at that location. If you don't need the actor itself, just checking if the list is empty is enough: <Code Omitted>otherwise:

Thanks. (sorry for the late reply)

Thank you very much! it worked great and had a better effect than I thought

The code you are showing is only executed when that particular world is created. It does not run when you click on the "Step" or "Run" buttons. The code (lines 3 through 6) needs to be in the act method or a method

After copying all codes into classes in greenfoot, it compiled for me. I did remove some codes, however -- only those related to sounds and images (because I did not have the required files for them. Classes with syntax errors should show with diagonal red stripes through the class icon and lines containing errors should be marked by red at the beginning of the lines. Also, the error within the line may be underlined, however, some syntax errors have these underlines show at places not exactly where the error actually is.

One simple way to handle it is by creating a new type of Actor for the dead ones:

Since it was part of the assignment, you will need to include the field: (see line 6):

Look at this https://github.com/LeoTuet/greenfoot-maven-starter

By keeping a reference to that actor in your World subclass, you can easily use something like the following: <Code Omitted>Line 1 assigns an object of type Player to the field named "player". Actually, a memory address of the "player"'s information is stored and held by the fi

Good evening danpost, thank you very much, I looked at your code example today, this week I will continue the game project. If I have any questions I will ask you.

The (same) problem is with lines 47, 49 and 54. They do not retain the objects in the fields provided on line 8. The values for those fields remains null and the checks for clicks will fail on these, or, at least, not work as you intended. To retain the buttons in the fields, you must not create a new variable (which those lines do). Look back at what I gave to see how they get retained. Also, note that the field names I gave are not (at least case-wise) the same as the class name. This helps for readability of your code (letting you know it is a variable name, not a class name).

It worked!!!!! Thank you soooooo much

Thanks that worked!

When a collision occurs between the moving pla