Discussions

Greenfoot should not crash regardless of auto-compilation. Can you please contact support as per instructions on our support page. There are no plans to allow disabling auto-compile.

Let me guess: you're using a Mac? It sounds like the problem described here. Try the solution there, or try using Greenfoot 3.5.0.

You need to be more specific and show some attempted code. What do you mean by "float"? Would it be moving at all and, if so, how? (in detail)

The World instance method getBackground returns a GreenfootImage object that contains the array you are trying to create. You can then use the GreenfootImage instance method setPixelAt to change a screen pixel by setting a color to any pixel of that image. You can acquire the Color object assigned to a pixel by using the getColorAt method on a GreenfootImage instance.

I was just trying to point out that the root directory is different when as an executable jar file. The root is does not include the jar folder and therefore it would need to be included in your code if you were to have the txt file inside the jar folder. Whereas, when opened in greenfoot, the root in

You will use basically the same format for jumping as for firing a bullet, tracking the state of the jumping key. You will also need to retain the horizontal direction that the jump is initiated at:

You will never fire a bullet with the current code because you are guaranteed to use getKey method previously in either the if (!onGround) or its else part. Each time the method is called, it will return a new key or, if no key remains in the keyboard buffer, null. Also, with Greenfoot, the buffer is loaded at the beginning of each act cycle while the scenario is running, meaning that if you use the getKey method multiple times, only the one first acted on will be guaranteed to get any key. For player controlling, better is to use the isKeyDown

Please refer to my Scrolling Tutorial scenario.

If your code above is in the Wombat class, then use this instead of Wombat.

thank you :-)

As is, your else part will execute regardless of the state of the D key (since else is linked only to the A key part). Move line 12 to the beginning of the method and then instead of else, just ask if it is still false at line 11.

The same can be said for the Good component field. That is, the line: <Code Omitted>would need to read <Code Omitted>for the field to obtain a value and for the getGood method to return that object (and not null).