Discussions

Probably depends on the order you placed the wombats into the world.

You could add the following as the first line in the foundLeaf method, to prevent "seeing" the leaf when count is 2: <Code Omitted>

You would probably need to use the getNeighbours method, determine if the list returned was empty or not and, if not, (randomly?) remove (eat) one that is in the list.

You could vertically mirror the image of the one on the right: <Code Omitted>However, this will probably redden the image and the mirroring would need done every time the wombat faces the opposite direction. Better would be to have two GreenfootImage fields in the class to hold a right-facing and a left-facing wombat. On any turn to 0 or 180 degrees, set the appropriate image.

Make line 40: <Code Omitted>

Remove line 18.

They are probably on top of each other (one hidden behind another).

You could make it any value you want; but it would help to make it a reasonable one. An initial value of zero is always a fair option.

Many ways. It would depend on how many wombats you want to be eaters (at one time); whether (and when) their eating status could change (among other things.

Just add the condition along with the thrust key being down that the speed is less than whatever max value you are setting. For example: <Code Omitted>

I guess you could make the leaf image somewhat transparent. That way, when two are together, it resultant image will appear darker than the rest.

What happens when the wombat gets to the edge of the world (which way does it turn)? which way does it then move? what about when it reaches the next edge?

Just how the code currently works. Change it if you want.

Gotta' leave something for you to build your programming skills on.

Increase the value of the argument in the move command.