Discussions

Get a reference to the eaten leaf. Next, get a random x and a random y. Then, set a new location (x, y) for the referenced leaf.

Thank you for the guidance, i figured it out, sorry I forgot to say thank you before.

There is no reason why it cannot be done in greenfoot.

thanks again so much dude

It doesn' just work like that - there's a lot more to Greenfoot than the "greenfoot" package. I have made a tutorial how to run Greenfoot scenarios in IntelliJ, a widely used Java editor. Maybe that helps you, it will at least give you an idea about how much there is to do. If you are still interested, there are probably ways to run Greenfoot in BlueJ, but it would be quite complicated for sure. Also, Greenfoot actually IS BlueJ under the hood and has the exact same editor, so I don't know what you are trying to achieve here. I

Newer versions of greenfoot auto-compile. At the bottom of your class editor, you should see a message. "No syntax errors" will should if the class appears fine to the compiler; otherwise, "Errors found." will display and the location of each will be flagged with a red line number and a squiggle line under problem text (or near it). Hovering the mouse of the squiggle line will pop up a message on the particular error found there. Also, any classes with errors with be diagonally striped in the classes window frame. If a

Make sure your platform images do not have any excess transparencies in them. The player is considered "on" a platform if it touches any part of the image of the platform, including any transparent part of the image. Neither should the image of the player have any excess transparencies.

Copy the folder onto your local disk and extract it if it is a zip.

Your for loops are set to iterate twice the length of the array. Meaning, you are creating more Track objects than the array can hold. That is, your array length is 68880 and you try to place 137760 Track objects in that array. It can't be done. Hence the error once your loop counter reaches 68880, since the last element is indexed at 68879.

Thank you @danpost, its working better now. :)

Thanks man, you carry this site

Thanks so much, I used 1 health for each player and used a switch and it cleaned up my code (and performance) by sooo much

Actually, never mind I managed to fix it, thanks alot for your help @danpost

Try to remove the brick from the ball class and remove all code inside the brick class. It’s never good to have intersection checks in the classes of both objects which intersect with each other.

thank you @danpost, that makes sense. Thank you for your help :)