Discussions

problem fixed, now on to debugging issues with firing cannons -___-

thanks! only issue with that is that jumpCounter remains at 20 even after the key is released, so a second keyDown check such as the following is needed to reset the count so that the actor could jump later if(!(Greenfoot.isKeyDown("w"))) jumpCount=0;

Ok thanks.

Um, I'm not too sure about what you're trying to do, but wouldn't it be better to create an abstract class "Piece" with declared GreenfootImage blackImage and whiteImage, and then in the constructor have a blackImage and a whiteImage parameter, this way with superclass constructor chaining you can ensure every Piece will have pictures? Then, whenever the piece is moved, check the color of the square it is moving it to (again, with a superclass method somewhat like this...

Thanks!

Ok - the proper name for that is "0-based indexing" (as Java arrays use), though in this case the x/y values aren't really meant to be so much indexes as they are distances from the top left cell. Regardless we could say that the co-ordinates are "0-based". Yes, I meant bounded, sorry.

Oh my god. Of course nothing happens because i didnt set stepsizex and stepsizey stepsizex = xway/steps; stepsizey = yway/steps;

Np, there are also some other resources dotted about greenfoot.org for both beginners and advanced users.

Yes, a very big difference. By saying <Code Omitted> you are saying "Get the world! do nothing with it. And then try to removeObjects" But only the world is able to remove objects, so you need to do this: <Code Omitted> which says "Get the world, and then *use* the world to remove this object" which is what you want

Oh... Thanks This exactlly what I need

@kwill1429 Yes, I could... But then i would need 500 or more Wombat-Pictures... And I think, thats too mutch... @mik Thank you very much! :D

Nevermind! I found my problem, and have since fixed it.

Oh thanks! i did not know that greenfoot draws everything again every act! that's helpfull! thanks again, Mattan.