Discussions

Thank you very much for your help!

No. More like this: <Code Omitted>

Thank you for all of your help! It seems that i have found my own way of solving the problem, though probably a round-about way of doing so. Once again thank you for you continuous help.

You could create an unbounded world by adding a 'false' parameter in the super call to the World class: public World(int width, int height, int cellsize, boolean bounded) The above line is the signature of an alternate constructor for the World class which allows you to state whether the world is bounded (prevents actors from leaving the world window) or unbounded (allowing actors to go beyond the limits of the window). So, for example: <Code Omitted>

Thanks. Running new VicWorld() did help. The Inspect said it did know that it was a VicWorld object.

Thank you so much my game works now

What the error is saying is that after you hit an asteroid and the bullet is removed from the world, you cannot then try to find an intersecting Enemy1 object. You cannot look for any intersecting object to an object that is not in the world (the bullet was removed). Change line 12 to this: <Code Omitted>This will ensure that the bullet is still in the world when checking for an intersecting Enemy1 object.

Ah sorry for the late reply, its working. Thank you alot Dan! :D

First, I'm not entirely sure about this: <Code Omitted>I don't know how you've defined the getDirection method, but simply using cannonbarrel.getRotation() might be easier. If that doesn't fix it, I suspect it's a problem with the precision in movement. Try to use the SmoothMover class to track the position and such (you can import that class into your project from Greenfoot).

Just because a project compiles, it does not mean that you will not get any errors. Compiling will catch syntax error (spelling, punctuation and use of symbols) as well as things like accessibility of methods and fields and proper type-casting of elements within the code. But there are some errors that the compiler cannot predict on. These are called run-time errors. In java, these are called "exceptions". Anytime an exception is thrown, it is either caught (by code created specifically designed to detect the error) or it is not caught and the scenario is terminated and a message will be

I was not suggesting that you not use any of those methods -- I was suggesting that you use one of those methods (most probably the 'getObjectsInRange' method); but only after re-locating the auto to potential future locations. After performing the check, you would move the auto back to where it was moved from, if a collision was found to occur. So, for example, a method to change lane

Guys, you should have seen the following above:By not following this you may get an IndexOutOfBoundsException run-time error.

Thank you very much! You have been a great help.

No. You would use it exactly as is. The GifImage class contains a private GreenfootImage array with the name 'images' that holds the individual images of the gif. That is what is being referred to here.