Discussions

Thanks!

cool thanks danpost it works

For consistency, use frame counting. At normal scenario speed, every 6 frames would be about 1/10 of a second. So, add to score every 6th frame.

<Code Omitted>

@danpost thank you very much for helping me out. It is working now as expected <Code Omitted> I learned that I have to use getWorld() as shown bel

I'm doing the latter

Are you trying to copy the original behavior?

I tried it and still, whether I spawn him right on the ground or make him fall a few pixels, the effect is the same. Let's continue our conversation here, please, if you are still willing to help: https://www.greenfoot.org/topics/64038/0#post_142560

Example: <Code Omitted>

It is "supposed" to make an actor move more precisely; but fails, as accuracy is lost by the roundings.

Alright, thank you that helps to clean up the mess a bit... As a java beginner I thought that at least one instance of a class had to be active at any moment to use the functions in that class, that's why I defined the music in every world separately.

The canSee and hit , which is equivalent to eat, methods are obsolete. They have been replaced by the Actor class methods, isTouching and removeTouching: <Code Omitted>

I am not a fan of the approach you have chosen to code the behavior of FigurEng objects. The many different collision checks make it quite complicated. On top of that, having them actually touching a stone when "on" one (see line 62) actually complicates things even more. I prefer maintaining separation from all objects and, after moving, using the direction of movement to dictate where contact was made with a colliding object. That is, if FallSpeed is negative, then any object would be above it and if it is positive, then below ("on ground" state can be determined here, as

thank you well seen, I did not watch out