Discussions

Yes - there are probably better methods, but I use the following (I haven't got any uploaded scenarios with multiple levels, but I've made a few) method: Once you're moving on to the next level (with the setWorld(new NextWorldName()) method), pass the objects to the next world in its constructor. In other words, you'd have it like this: setWorld(new NextWorldName(getObjects(null))) and then in the NextWorldName class, you'd obviously have to modify its code so that its constructor takes a java.util.List as a parameter, and then store it. Then, when you want to go back to the first world, you

Maybe because of what I said?

Haha yeah, that's what I've been doing with it x]

AIFF is Apples version of WAV

You can either use the java.util.Date class or as suggested above use the System.currentTimeMillis() approach. Both are effectively same. Java Classpath in Windows

Okay, thanks.

You need to be a bit more specific. Where is your counter? How is it declared? Are you trying to get the score TO the scoreboard? Usually, the score is kept within the scoreboard class, and a reference to the scoreboard is kept in the world class. That way, methods such as getScore(), bumpCounter(int), and other counter related methods can be placed there and the act method will update the scoreboard image (if the score is in view the whole game-set).

You're probably running the JRE rather than the JDK - the former won't work. Head over here and grab the latest JDK - make sure to click on the button under JDK not JRE!

I'd advise against running Greenfoot as administrator; you simply don't need to. If you get the warning about the scenario being read-only when you don't actually have a scenario open, there's nothing to worry about, you can ignore the warning. If you do have a scenario open (one of the examples included with Greenfoot) it just means you need to save the scenario somewhere else (and then open it from the new location) before you can work with it.

The reason the explode object does not remove is because you are removing 'this' from the world first. Now there is no 'world' referenced. Switch the last two lines of code and the explode should remove. As far as fraction of objects, the only ways I can think of are (1) if you build the object in parts, or (2) if you change the image to reflect the remo val at given points.

We'd need to see your code for certain - but the above advice is a common cause! If you have declared a populate() method then check it's the same case (Java is case sensitive) and check your curly brackets are all in the right place which can also sometimes cause that error.

Also check out the Greenfoot videos (especially the ones on shooting).