Discussions

This code, in your Fighter_Kogel class, should be removed if you want the instances to move and get removed at edges like a Kogel instance is programmed to do. As an alternative, you could change it to: <Code Omitted>

I do not know what more can be said about accessibility. However, to get "around it", you could add a new method in the class of the actor to call the method and return its results: <Code Omitted>Then call this method from the world subclass.

Ohhhh ok that makes sense. Thank you so much!

The Light class in the scenario (in the Player class) was modified to allow changing the range of illumination (strength of light). Also, the Scroller class was fitted to support non-scrolling areas along right and bottom edges of the world (a crop method was added).

Not tested, but I believe if you just add the three color parts together and divide by 3, then use that value for all three parts should be close to what you want: <Code Omitted>

thanks bruv

You do not have to initialize the player again (only initialized in the starting world). That is, your line 5 is not needed to put a player in a different world. The line I provide previously will move the player from one world to the next. The new world does not have to create another instance of a PurpleGuy object. If it would make things easier, you could add a method to the different worlds to help move the player into each world:

I do not believe greenfoot allows access to its Component objects; which means you cannot do anything about the cursor being used. You could create an Actor subclass whose behavior is to follow the mouse and whose instances have the crosshair image. You may want to increase the scenario speed a bit to help in delayed movement of the actor. There may not be a suitable mix of speed and performace for

Thank you.

The java.util.List class is abstract, which means you cannot directly create a List object from that class. You can create a List object via a non-abstract class that extends the List class, such as the ArrayList class): <Code Omitted>You could import the two packages: <Code Omitted>to simplify the line to: <Code Omitted>

Thanks for the help! Can't believe I missed that!

First, get a reference to the actor it wants to follow; then, turn toward it and move toward it. Depending on your scenario, you may need to reset the rotation of the follower back to zero to complete the steps involved. If the follower moves at a slow rate (certainly, if less than 5 pixels per move), you might consider using a smooth mover support class to eliminate any inaccuracies in moving direction.

Thanks!

Replace lines 31 thru 34 in your MyWorld class above with: <Code Omitted> Then, add the following to the MyWorld

If I knew what it was, I would have said so. Since I do not, there is nothing to say currently. It could be anything from too many actors in the world to loading music files frequently to who knows what.