Discussions

Thanks alot! Works perfect! How can I + your rep?

Come to think of it, isn't that exactly what you suggested?

Excellent!!! Thanks for teaching me how to do that!

If you do not want the object to be removed from the world, change the 3-line code above to: <Code Omitted>

What you essentially want in a collision detection method is the ability to prevent the player from going into walls at all. This can be done by alligning the actor agenst the object if it touches it. It would also be better if you detect for actors at every cell in the area the actor is about to move into. This way, you can detect the actor first, and then move the player agenst the actor instead of letting the player move normally which could cause the player to move into it (if he's going fast enough) and glitch like you described. I made a completed scenario with good hit detection that us

I thing u have to do it again and do it other way :)

As far as laser v bullet shooting: laser shooting happens when a bullet is created every act method while bullet shooting will skip several act methods between each bullet creation. This is usually done by adding a shot timer that increments every act. When the timer reaches a certain value, create a new bullet and reset the timer. You can add a boolean field to your actor to allow creation of the pop-up; however you will also need two dual conditional 'if' statements to run accomplish what you want. If 'atLocation' is a method (or condition) that determines whether the actor is on the s

By placing the 'setLocation' statement with the 'getRandomNumber' call in the 'act' method, the object will erratically jump vertically until a new world is set due to the 'getX()<=20' or the 'getX()>=getWorld().getWidth()-1' checks. The initial location should be set when the object is added into the world.

Have two field in your world, one for the current time and one for total combined time. Call them 'time' and 'totalTime'; and make them 'public' fields. Then when one level is ended and you need to move on to the next, use something like this: <Code Omitted>

To check whether there are no more objects from a class you can use this code: <Code Omitted>If you add this code in a World subclass leave out the getWorld(). To set the world to a new world you can use the method Greenfoot.setWorld(World) e.g. like this: <Code Omitted>

All this does is create another object (just not a world or actor object) that is referenced in the first world.

You would use both lines of code. The initial line in question to create the object followed by the statement to add it into the world. Review the code that is put into the 'prepare' method when you 'Save the world'.

Thank you!

Is there a way arond this?