Discussions

You will either have to upload your scenario to this site with publish source code checkbox checked or show all your class codes here (using 'code' tags).

First thing is to decide how long the delay between two bullets should be, e.g. "2 seconds". Since Greenfoot regularly calls the act method, the unit for the delay should be "number of calls to the act method" (/"cycles"). On normal speed, Greenfoot calls the act method approximately 60 times a second. 1. So, let's define a constant for the duration until the next bullet can be fired: <Code Omitted> 2. Next, an attribute is needed that stores the current state of the cooldown, e.g. storing the remaining time (in cycle

I'm not sure but this might help you. You can always define methods in the World class that are callable via right click on the scenario screen. So in your case you might want to add a method "showTutorialText()" or "switchSound()" that is defined in your World class (needs to be public i guess) and is callable via right click (a drop down with all methods should be shown). This only works if you don't need to run your scenario as an app but it will work if the scenario is paused in greenfoot!

Good catch! :)

The other problem is that, because Greenfoot does not restart the JVM every time you press "Reset", threads will remain running until you restart Greenfoot. To fix this, we have to keep track of the actors that were created and stop threads of actors that are not on the active world. Putting it all together:

ok

Thanks, it worked.

Seems like you have everything in order. Maybe your file operations are not what javascript would allow.

Thanks it works.

Ok, thank you all.

You can check out this one for a start: https://www.greenfoot.org/scenarios/13501

Oh, right. I forgot about that. Thanks

Passt schon habe es mit <Code Omitted>gelößt.

Show codes of "block" class.

You don’t even need to remove the ball, instead put it back to the default position and reset the velocity.