Discussions

I am sorry to hear about the circumstances and hope that at least my answer is helpful: There are two ways that I see likely to be successful: 1. Download an old version of Greenfoot (the version with which the scenarios had been created 10 years ago) and run the scenario in this old version. or 2. Adjusting the scenarios to the current version. Details: 1) === Download old version === If you click on the "Download" button above, you get to the Download section. There, on the bottom, there are links to the "version history" and "old versions of Greenfoot". "version history" will

Rotations pivot at the middle of the image. Make the center of rotation the middle of the image of the flipper.

Decreasing "world.interval" would cause stars to spawn more quickly.

In Mikey class fall method, you set velocity to zero prematurely (at line 38). The value is needed (at least, the sign of the value is) to determine if bumping head or landing on platform as well as in setting the location the actor should be relocated at if a collision does occur. Also, using didBumpHead and isOnSolidPlatform after moving vertically won't work as the platform could be anywhere with respect to the actor. I see no use for didBUmpHead at all. On the other had, isOnSolidPlatform is useful as far as a condition to jump provided

I guess the problem is that BOTH if blocks are executed if the player collides with the wall from the left. Let's have a detailed look at that scenario (colliding with a wall with velocityX > 0):

ohh sorry dint see this <Code Omitted>

Thanks Danpost! I ended up changing it up while I was waiting for a response but I have a new question now, for which I'll post as a new discussion. Please check it out whenever you can! :)

Another way is to place multiple bricks at the same location (to act as "one brick" with multiple hit capability) -- one actual brick for each time the "one brick" is to be hit. Then, simply (in Ball class): <Code Omitted>The first line is to "reduce the health"; the second line is to rebound off a still existing brick (though, just not the same one). The code for bouncing off a brick is to be put in the new method, bounceOffBrick. This will actually require nothing but

There are two ways to make your actor stay in the air longer. One is just to make it jump higher. The other is to lower the effect of gravity while maintaining it as a positive value. Here, you will have to decrease the jump force to compensate for the change in height achieved. Since you cannot keep gravity positive by decreasing the integer value of one, you will need to start using partial pixel values. This is done by tracking and using the location coordinates of the actor as ei

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