Dragon Fogel
Level: Smitemaster
Rank Points: 2584
Registered: 06-21-2014
IP: Logged

Sometimes, when you tell a character to move or turn, that command doesn't get immediately executed and is instead queued up for the next turn. This tends to take priority over other script commands.

I don't know exactly why this happens, but it would be nice to be able to override it. There are a lot of times when the script is more important than the movement.

hyperme
Level: Smitemaster

Rank Points: 1261
Registered: 06-23-2006
IP: Logged

Character moves don't get "queued", so I don't think this works. What's actually happening is that because move commands can take multiple turns, the character won't advance to the next command until the move is finished. This wired pretty strongly into how the movement commands work, so changing that would be very risky.

____________________________
[Insert witty comment here]
Qzvlkx?

Dragon Fogel
Level: Smitemaster
Rank Points: 2584
Registered: 06-21-2014
IP: Logged

Okay, then here's my new thought. Two commands. One stops the character from doing any movement on the current turn, but stores a "next move" if a move command comes up. The other cancels the previous command and causes the stored next move to happen immediately.

I don't know if there's anything this would enable which is currently impossible, but it would make it more convenient to adjust scripts for moving NPCs that do other things.

hyperme
Level: Smitemaster

Rank Points: 1261
Registered: 06-23-2006
IP: Logged

It may be possible to add a behaviour that makes it so single-step moves don't become blocking if they can't be done.

The "stored move" thing seems kind of complicated from a user perspective.

____________________________
[Insert witty comment here]
Qzvlkx?

Dragon Fogel
Level: Smitemaster
Rank Points: 2584
Registered: 06-21-2014
IP: Logged

The idea is that it would be more of a tool so that, if the move is happening at the wrong point in the turn but the script is complicated enough that copying the code which actually sets up the move is nontrivial (because it has weird conditions or something), you can just use these commands.

Someone Else
Level: Smitemaster

Rank Points: 2358
Registered: 06-14-2005
IP: Logged

Probably the best way to accomplish your goal is to store the bit to calculate the next move in a subroutine and call that. If you need to calculate something at a different point, use local (_ prefixed) variables at that different point.