To be honest, returning to game design hasn't been going all that well, so recently, I thought I could distract myself by looking over an old Roodylib "to do" list to see if there was anything I still wanted to add.
The first thing that sounded appealing was trying to come up with a solution to Hugo's default handling of >FOLLOW, as a game seems kind of dumb when you have just seen a character leave a room and >FOLLOW responds with "Which way did he go?"
I wrote a system that relies on using CharMove to move your NPCs. The code takes note of the direction the NPC left in, and unless the NPC returns at some point, >FOLLOW will result in going in the same direction. There was no ultra-clean method that didn't involve replacing some routines, but this was the most elegant solution that I could come up with. Beyond including this code, authors would just need to remember to give their roaming NPCs the "last_dir" property that I have defined.
After writing this, I wanted to test it out in a game. I first tried "Guilty Bastards" because I incorrectly remembered being able to follow someone at some point (although it definitely has a character following you). I then tried "Spur," which I was reminded was actually the game that inspired this whole better-following thing in the first place, but I couldn't even use my code with it as it completely substitutes another character script routine for CharMove. I mean, sure, I could have rewritten it all so my code would still have worked, but in my sandbox version of "Spur", I had already written a >FOLLOW SO-AND-SO workaround anyway.
So I just had to test it with my own code, and hey, everything seems to be working fine. I'll probably just throw it in the "extensions" folder in my Roodylib distribution at some point.