Discussions

Line 15 in the Nyawa class will only set the value of 'nyawa' to '1' when the project is compiled (because you have made it a ''static' (or class) field. As such, you need to set its value either during the construction of the world or during the construction of the Nyawa object..

Thanks, Danpost! Your're a life saver! Thanks!! I really appreciate your help!!

Oh, I see. This makes things a lot easier and more flexible, I understand where I went wrong. Thanks Dan,

Thanks but we got it sort of fixed already. Appreciate the feedback!

I cannot see how you are getting that error on that line, especially considering the condition before it (line 4) and that no action is taken between that and the next previous line (line 3) where you assign 'x' its value. However, an improvement that will probably solve the issue is that you really do not need that particular condition on line 4. You can just use this: <Code Omitted>

No. But you can make your world smaller to fit the monitor size and scroll the background image using program code.

Did you review this page?

There are a couple of ways (at least) to improve the direction of movement. Probably the best one is to track the location and rotation of the actor using finer units of measure (rather than units of whole pixels and whole degrees). The SmoothMover class provided with greenfoot provides a finer coordinate system, but does not provide finer rotation. My QActor support class, however, provides both. It can be found in my Asteroids w/Improved QActor class scenario.

Thank you!

Problem fixed! As I thought, the problem was with working on distant sessions at school. We tried other ways, and it appears that the problem is fixed by working on a local session, or even on an USB key. Thanks for your answer!

XD Thank you^^, i didn't see that. Thank you too^^, that gave me a good idea on something :3

The ScoreBoard class is for when the game has ended and the Bullet class only shows that 'hit' is called on a hit asteroid. Nowhere is a running score shown or changed. What code do you have in the Asteroid class and World subclass (called MyWorld, possibly)?

Not unless you program one to use. Neither java nor greenfoot come with a 'penDown' method in any of their classes.

You should note that all other sounds are triggered by objects that are immediately being removed from the world. With the last one, the Bts object is not being removed -- nor is a different world being set active. This means that the act method of this object is repeatedly finding itself intersecting the Bts object and repeatedly creating new GreenfootSound objects to play, one on top of another. Hence, the impression of all your sounds playing at the same time. One way to "fix" the issue would be to remove the intersecting Bts object from the world. However, if you are to keep it in th