MUDgate wrote:Okay so this is what I've turned it into:
if step1 then killTrigger(step1) end
step1 = tempTrigger("The corridors in the lower caves are unrefined and narrow.", [[send("north") resetFormat()]])
I got it to stop adding "north' commands, it just does the one. But i couldn't get it to turn off. Even if i deleted the trigger it would still trigger a "north" command off that one substring.
Deleting the trigger that created the trigger won't do anything to the trigger that it made, because it lives on its own. To delete it, you would do:
if step1 then killTrigger(step1) end
MUDgate wrote:The only thing that seems to prevent this ghost trigger from firing is resetProfile(). It seemed to work, no more ghost trigger.
Yeah, because that (same as a Mudlet restart) clears all temporary triggers.
MUDgate wrote:
So i remade the trigger and tried using resetProfile() in an alias thinking that I can use it to stop my walking loop when i run into an orc.
But the trigger wont fire!
resetProfile() seems to not just shut down the tempTrigger() but prevent it from reestablishing it's self and firing again.
Using resetProfile() as part of your actual process is a bad idea. It also doesn't prevent reestablishing triggers, you must have had something else going on.
MUDgate wrote:
Ideally I'd like to fill a script with these tempTrigger room descriptions and use them in an event with raiseEvent() to re-initiate my walking loop after i kill an orc. I thought that using disalbeKey() would give me blanket control of my tempTriggers since i plan on having them all in one script. But after testing, and my experience with resetProfile, it doesn't seem like disableKey will stop the tempTriggers once they've been created.
disableKey() is for keys combinations. I think you mean disableTrigger(). disableKey() indeed won't do anything to a trigger.
MUDgate wrote:
It feels like I'd have to disableTrigger() each specific trigger depending on what room I'm in in order to keep from being walked passed any orcs.
Any ideas\advice on how I can get the kind of general control of my tempTriggers I want?
I'd just create triggers in the editor, not using temporary triggers, in a group and enableTrigger()/disableTrigger() on that entire group to turn things on and off. Far simpler setup.