OK, I have been trying to figure out a way to get the player-controlled character to move one tile at a time (vertically or horizontally; basically the way it worked in V2) without hiijacking the entire movement system.

My first idea was to make the "player" character an ordinary NPC and have it moved around through movescripts. I bound the directional keys to functions that assigned a one-tile movescript to the entity if the current movecode was 0 -- for example, if movecode is 0, the "PressDown" function changes the pseudo-player's movescript to "D1." This works nicely enough, but you have to press the button again every tile -- you can't just hold it down and keep moving in that direction. Then I tried HookTimering a function that checked what directional buttons you were using, but my HookTimered "if (key[SCAN_DOWN] == TRUE)" (and others) always returned false for some reason. So that's a no go. Can anyone think of another way for me to do this? I'd really like to avoid just taking control of the entity processing entirely.

Maybe tell them to walk 20 steps. Then stop them at the next availiable tile boundry when the button gets released.

And loading movecodes into strings (to then pass to ents) for walking, etc is easier than it seems.

Hope that helps.
El

Obstruction-checking is easy; I already have it in. Checking for obstructiony entities will be a touch more work, but nothing traumatic.

As for the moving 20 steps, it seems like that system might have problems with stopping at the right time, but I suppose it's worth a look. I tried setting it to moving one step and repeating the movestring (R1B for right, and so on), but this actually causes the stuttery walk also, which surprised me. Vecna, any way to avoid that?

Got it.