Discussions

First, you have a reference to the ninja in this 'levelOne' world. There is no need to have the ninja pass its x and y to the world -- 'ninja.getX()' and 'ninja.getY()' can be used straight away (getting the most current position of the actor). You can eliminate the 'ninjaX' and 'ninjaY' fields from the class as well as the 'updateNinjaPosition' method. You may be able to do similar with the 'ninjaDirection' field (depending on exactly what it refers to). What you could use is a method in the world class to pass the ninja actor itself:

Thanks! It worked, to some extent. I managed to sort out the rest of the problems.

Yea that is what I should have done That's a cool way to reduce the class

@Super_Hippo, the page change got me there (along with the separate posting of the two methods). I concur with your rearrangement of the code. However, either line 5 should be removed (as 'gold' is not being used in the method) or line 6 should be changed to the following: <Code Omitted>making good use of the reference to the object.

took longer than expected but its done :). Many thanks danpost and Super_Hippo

I might try that. That would normally be how I would do it following the OO design but I really hate how greenfoot doesn't allow packages. All the code goes in one huge place so I'm trying to keep it semi-neat and tidy. Though doing it that way I can remove the XML since it will be all in code. Currently the way spells work is that I have a Spell class that holds all the characteristics of the spells and all the spells are in a list. When a player casts a spell, it creates a SpellObject and it inherits the spell characteristics. Then the SpellObject has an act method that handles eve

You would be better off not to use the System time as the regulating system. Counting act cycles is preferred because it avoids differences in system speed and lagging. In other words, the number of act cycles for any run of the game will not be consistent if using the system time. When using system time, the maximum amount of progress in the game would vary. When counting act cycles, you can still display a stop-watch like counter. I have uploaded Timer Support Class (simple) with source.

See above.

I think Super_Hippo was thinking that if you start with 3 lives and lose a life every act, then you would be dead after three act cycles (about 1/20 seconds). You only need to update the lives counter and image when a life is lost; not every act cycle.

This is what I said should go in the Player class. Well, the bullet has movement behavior, but the Rifle does not. I was suggesting an if statement in the Weapon class to qualify when a shot can be fired.

The scoreboard which you can import will sort every user who played your game in descending order of their 'score'. For every user, you can store a 'score', 10 ints and 5 strings. If you double click on 'World' and click on 'PREV CLASS' in the top left corner, you get to the 'UserInfo' help. As a standard way to store a score, it is written like this:

Thanks the long way works great

Oh! I misunderstood the method! Okay thanks