Discussions

No -- the UserInfo class of greenfoot does that for you. You only need to call the 'store' method on a modified (or un-modified) UserInfo object returned from 'UserInfo.getMyInfo()'. As the documentation states, however, you must first make sure that the user is logged in and storage server is available with 'if (UserInfo.isStorageAvailable())'.

NVM, got it!

thanks

Have the dummy actor set (or finalize) its image in an 'addedToWorld' method. Please refer to the Actor class API documentation for information on this method.

@Gevater_Tod4711 Oh... good to know.

You need to post your error message (copy/paste it) and show the Sun class (if that is indeed where the error is occurring).

You need to make a higher level component that is top-down containing two lower level components -- one with the cards that is left to right and one with the control panel which is left to right.

No. The scrolling is something that should be done in your subclass of world (your ScrollingWorld class) -- even determining if scrolling should be done. The player should be programmed as normal (without respect to scrolling at all). Your code:

It's just one error. At line 16 of your PlayerPink class, you are dereferencing a null reference. That is, you have obtained a null value and are trying to call a method on it (or access a variable with it). java.lang.NullPointerException - is the type of the error at PlayerPink.act(PlayerPink.java:16) - tells you where it happened The rest: at greenfoot.core.Simulation.actActor(Simulation.java:568) at greenfoot.core.Simulation.runOneLoop(Simulation.java:526) at greenfoot.core.Simulation.runContent(Simulation.java:215) at greenfoot.core.Simulati

Alright,thank you

That actually worked. My loop had a wrong value in it. Thank you for the help!

Your null pointer was probably due the 'getWorld' not being able to get the World object that the actor was in after it was removed from the world. Get a reference to the world before removing the actor: <Code Omitted>

If you use 'static' fields and methods in your Main class for the scores and names, you will be able to change them directly from the Plane class using 'Main.staticMethodName()' or 'Main.staticFieldName'. My Pushy Woman scenario has an example of how that works in the Maze class (I think that is where the 'static' fields for best scores are located).

It works wonders. It beats deleting then having to replace the button by a long shot. Thanks a lot.

One thing, first. In the act method, you are using both 'move' and 'setLocation'. You need to use one or the other, but not both; and, the preceding code should be geared toward that end. You should get the movement right for the head of the snake before moving on to trying to move an entire 'multiple section' snake. Since you are using only NORTH, SOUTH, EAST and WEST directions, using 'setLocation' with 'dx' and 'dy' would be the way to go.