Discussions

Hmm, you're right. I mis-read that code (as 250 - 350). However, the 'n must be positive' error nearly always comes from mis-use of the Greenfoot.getRandomNumber method, in my experience (and it certainly doesn't come from addObject). Pe1per, perhaps you can point out which line actually causes the error rather than forcing us to guess?

Are only enemies moving? I think I didn't really get the way the game works right now. You get points for every click on an enemy and you have to place them back until one reaches the right side? Could it be that the seeLocation method (which I don't really understand why it is made like this) is quite useless? It is only called when it was dragged to a different position and if it is on a target position, it shouldn't move. How is this supposed to be? You could do it like that:

For continuous: <Code Omitted>

<Code Omitted>or <Code Omitted>

Use the code tags to post code please. What I would suggest first, because this code is a mess (and it isn't easy to get an overview of what is important and what not), have the images in arrays. Then you can code that in a few lines and don't have to do something like what you did there.

Firstly thanks for the reply . Could you possibly give me a suggestion of what the code in line 3 and 6 needs to be?

thanks its works now, you've been a great help to my game.

In your second Demo, can you explain to me how the tail knows how to follow the head? I would post the code that covers things like direction and spawning the tail is almost the entire snake class.

thank you guys its now working

You should be able to use code similar to the code of the act method except that you will reverse the direction of the turns and look for walls instead of looking for where walls are not. This should be done once, when the actor is added into the world (use the 'addedToWorld' method).

How is the variable declared? and what is the name of the class it is declared in?

Maybe you should look at my Super Level Support Class scenario. It would facilitate in both retaining field values between worlds as well as changing from world to world. Although that scenario creates new worlds instead of returning to previous world, it can still be used. Create a static map (or array of levels) with static fields to track the world currently in and add a static method to change worlds using changes in location within the array:

ok thank you all you really helped me :) Now it works fine!