RPG207 Ghost no longer ghosts... what happened?

In this latest build, ghost is imediate, and no longer floats you from point to point? Why?

no sooner do I say this than it works... almost like it works sometimes but not others.

Hmmm ... it depends.

IT should have a "timeout" based on level ... if memory serves, somewhere between 8 and 12 seconds (I'd have to look at the code to check the equation).

So if it takes longer than 8 seconds to get where you're going, and you have Ghost 3, at the end of the 8 seconds you're teleported to the destination.

If you're ghosting when the wave ticks over, instead of being dropped "where you are", you're supposed to be teleported to your destination.

If you are farther away from your destination than you were last tick, you're teleported to your destination (IE, if you've passed your destination, you get teleported back to it).

If there's any "instantaneous" ghosting going on (you die and then teleport), that's a problem.

Hmmm I *think* I know what this is (a ">" that should be ">=" because of when "tick" actually happens and PrevDist is set) but my IP has apparently changed and I can't update my CVS copy to get an accurate copy of it to change and update.

This should be fixed in CVS. Sorry about that. GiveTo and Tick being called close together (before the subject is moved) could cause this without the fix.

Szlat didn't understand the issue ...

One of the enhancements I added to ghost was a check to ensure that your distance to your destination was always decreasing (or now, decreasing or equal to). The only time the distance to your destination should increase is if there's a bug somewhere (either in the map or ghost). It's done by saving the Previous Distance to Destination in a variable for checking during the next Tick; it's initialized during the GiveTo function. Thing is, I didn't account for the fact that an individual might not move during the period between the GiveTo call and the "first" Tick of Ghosting. Since the individual didn't move, the distance to destination was equal between the initialization during GiveTo and Tick.

Ghost would then do what it was told to: move the person to their destination (another enhancement mainly for those end of wave ghostings, or if someone *had* passed their destination) and end Ghost. Oops.

So I changed > to >=.

Strangely enough, it was one of those things that never happened during testing, even in a dedicated server environment.