Discussions

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

So then you just need two images, one showing the closed door and the other one the opened one. Then to open the door you just have to set the other image.

Once it gets a reference to the player (either by passing it to the follower or by a getObject... type method), just turn toward the player's location coordinates.

That is the exact one I am using (USB version). Have not tried newer.

Oh you're right I forgot about this, it works now ! Thanks !

What (exactly) was the error? What is the coding around which the error occurred. This class is intended to be a parent class of your game worlds. It contains 3 constructors (beginning on lines 3, 8 and 13) and a method (to be overridden in som

Thanks ! That worked !

Are you sure? Check again.

Alright: <Code Omitted> I believe you mean: <Code Omitted>

You should probably run your scenario at normal speed (60fps ~ 50speed) and just change the image every 30 frames. For most scenarios, using frames makes for more consistent behavior. Any lag could throw timing of interplay of actors off when using system time.

Thank you very much, finally I found the solution

oooh thanks appreciate your help!!

Thanks, works perfectly.