Discussions

The removal was probably from something executed just prior to this code.

Solved it myself - I forgot to put a delay into it. Still leaving this here for education purposes haha

Thank you.

The Greenfoot package has a Color class (Greenfoot.Color) which you import when importing greenfoot.*. If you import java.awt.Color, you use this Color class instead. The GreenfootImage constructor requires the Greenfoot.Color class. This was changed to make conversions to HTML5 possible for exported scenarios.

Thanks a lot!

Sounds like you have a recursion issue. Cannot help you without seeing what codes you are using. Start with class of 100+ objects; then, class where those objects are being created from (whether from world or from another actor).

thank you :D.

It would make things easier if you also use english words for your variables instead of german words

also you reference other world classes and other things here please post all the classes and the entirety of them. I did my best based on the info you gave but the code I gave you very likely wont work because there are parts of your code that I cant see

Agreed! Danpost has helped me countless times. This community does not deserve all he does for us and all he teaches. I certainly agree that Danpost is epic. Happy Easter everyone.

ohhh I see now, thanks it works now.

Okay. Thank you for your reply!

That helped, the program doesn't stops itself anymore. It don't want to do what I want it does, but I think I can manage it myself ;-) (p.s. Nccb your idea shouldn't matter in my case beacause situationRemove() shouldn't be executed…)

When you remove the apple from the world, you reset appleflip. Similarly, when you remove the letter, you reset letterAflip. So whichever one gets removed first will prevent the other seeing the state where both are flipped. You should probably make one class responsible for removing both the items rather than making them only remove themselves. (Greenfoot.delay delays the whole simulation not just that actor, so it won't make a difference to the behaviour.)

I think you are using turn in places where you should be using setRotation (line 57 and 81). You are turning -90 degrees (making a left face) when hitting a side edge along the bottom. That will make the actor face in opposite directions (one up and one down) depending on the side hit.