ZAPing to an undefined step breaks NPC

[jrbudda]

I accidentally left a ZAP in the last step (step 2) of a script. Afterwards the NPC would not work at all even if I removed him and recreated him, reloaded the server, etc.
Finally found the Current Step line in the saves.yml. It was set to 3, only by deleting this line and reloading was I able to make him work again.

Would it be possible for ZAP only to work if the specified step is defined?

[aufdemrand]

Yes, absolutely. The new build I'm working on breaks commands down into little 'modules' (requirements are next), so that things like error handling can be implemented nicely. You'll see a lot better handling of errors in newer builds, or at least an attempt to put that in place. I haven't specifically checked for that, but I will. That's a good idea, and fits in with the behavior of the error checking that's being put into place: 'If your script is wrong, error out with information.' I think it will be better in the long run. The alternative was, 'If your script is wrong, do the command with as much information as possible, even with an error.' My fear is that would cause potentially running unintended commands, which could be bad (and confusing).

[jrbudda]

Oh awesome. Haha a simple 'I'm working on it" would have sufficed. :)

But yea that sounds great, kludging the YAML now does make for a messy, messy stack trace.

[aufdemrand]

:)

[aufdemrand]

Nice little warning now in debug mode if you attempt this. Decided not to completely disable since it could be used to an advantage in special circumstances.