Exult Forum

IgnitusDragon, that is nothing like what the problem was.

-Colourless Dragon

It was a jokingly generalization, but I sense your disagreeing with me just to spite.
If the game remembered to move him down, he'd go-wouldn't he?
I'm not saying the game physically forgot, of course the programming is still there, from what I understand, the command to go down wasn't ran because something didn't look for something. Can you explain in laymans terms Colourless?

Forget is the wrong word to say, the engine didn't forget anything. It's not like the engine generated the path and was then unable to move the avatar along it. It was just unable to create the path at all. Saying "didn't know how" or "couldn't work out how to" would be better. The engine didn't know how to move the avatar down the stairs so (s)he got stuck at the top.

Explaining pathfiniding in laymans terms (especially the A* algorithm that Exult uses) can be reasonably difficult. Anyway, In an attempt to explain the bug, when creating the path, the engine thought it had already gone to a specific spot, when it infact hadn't actually gone there yet. Because of that, the engine didn't attempt to continue the path from the spot.

I think you did well in explaining Colourless, sort of like:

A = (training area of the list field)
B = (steps going to the doors, leading to list field)

Then the point from A to B isn't set because it already thought you were at point A?
Something like that maybe.
Thanks for your explanation I'm sure alot of people will be set at ease knowing this bug was fixed.

I had this exact same problem on XP. I was using the RC2 Release. Once I upgraded to the newer stable snapshot, the problem disappeared. I have posted a new problem if someone could have a look. Thanks!