Discussions

You will need to show some attempted codes on having, or trying to have, it function as you want. Best is to show th

I believe the class tree is built, or rebuilt, during compilation based on how the dependencies are found in the code during compilation. I doubt it would be very easy to control the order of class positions precisely.

A 270 rotation is straight up. That is not part of a "pyramid" shape. With the rotation set to any odd multiple of 45, the code should work and all movement will remain at odd multiples of 45.

Nice to see that these are actually some people active ö behind the scenes

Typo here!? Should be eat(Rocket.class); I guess..

This will work during a single session, but will not work when going from one session to the next (scenario is closed and reopened -- or recompiled). For that, you will have to use a file or database to store the progress. A file is sufficient provided you do not upload the scenario onto a website. To work on a webpage, Greenfoot provides the UserInfo class to allow variables to have their changing values stored in a database.

I have already finished it. Thanks a million. I really appreciate it.

Oops -- line 24 above should be: <Code Omitted>(missed the closing square bracket for the index of the array)

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! :)