"always" doesn't seem to always cut it.

[Skeets]

I am using the property always to put a collision marker below the guy, but when he moves too quickly, the collision marker falls behind quickly. This doesn't make much sense, because this is what I did:

Always->set position at -20, 10 from object.

[Nifflas]

That happens if the parent object changes it's X and Y position after the 'Always' event in the main event loop. If you are using a pre-defined movement, I honestly don't know how you can fix this, but if you have programmed your own custom movement within the event editor, make sure that the parent object's X and Y positions are set to your desired values before you start to make the childs following it.

The events are always performed from the top to the bottom of the event list.

[DavidN]

If this event comes further up in the event list than an event that moves your character, the character will move after the marker is set to his position, giving this "dragging" effect. To get rid of it, make sure that "Always" event is the last in your event list, or at least happens after any events that move your character.

This also used to happen with built-in movements, but was corrected in build 246 or so.