Zugg Software :: View topic

Sorcerer Joined: 13 Jan 2006 Posts: 715

Do temporary triggers not exist in CMUD?
I've always used temporary triggers for my practice script.
Once a skill/spell reaches its max a temp trigger fires and sets the practice variable to the next one to work on.
However manually deleting each trigger in CMUD since I can't find the setting for temporary triggers.
Yes I know they can be created from the command line using #TEMP, but where is the check box for it in the settings editor?
I prefer to create these in the settings editor for a variety of reasons, and this checkbox missing is a major hassle for me.

Posted: Sat Dec 01, 2007 10:12 pm

I believe this is an omission. Surprised it wasn't noticed before. Maybe it's something easy for Zugg to fix.

Confirmed as a bug.

Posted: Mon Dec 03, 2007 5:47 pm

Unfortunately, for this upcoming public version, you can only use the #TEMP command to create a temporary trigger, sorry. Temporary triggers are not stored in the package database, and the package editor is only a database editor, so that is why the package editor can't manipulate temporary triggers. It's not a simple "fix".

Posted: Mon Dec 03, 2007 6:49 pm

That makes a lot of sense. Zugg I probably wouldn't both with implementing it then. I believe the spirit of temp triggers is create them programmatically. Ralgith I know it's annoying but maybe you can create a generic temp trigger then update it's pattern and value in the editor.

Sorcerer Joined: 13 Jan 2006 Posts: 715

Or make I guess I could make an alias that I pass the params and it makes the temp for me, would be quicker than typing the FULL trigger every time on command line.

Posted: Mon Dec 03, 2007 11:04 pm

How much less hassle is

temp "(*) something something %w %d %s %d" "#say hah"

compared to

#temp {(*) something something %w %d %s %d} {#say hah}

?

Sorcerer Joined: 13 Jan 2006 Posts: 715

I meant more along the lines of only passing the parameter that changes, which is only a single portion of a larger phrase :D
Then the alias puts in the generic part for me and makes the temp trigger.
However, I'd like to see temporary triggers saved over reopening the client.
That was one very annoying thing in zMUD, all my autopractice temporary triggers (sometimes as many as 50) going bye bye if I closed zMUD and restarted it.
Something I'd prefer not to also experience with CMUD.

Though I suppose I could use #UNTRIG to have it delete itself once it fires. So, on that idea... is #UNTRIG in zmud? :D

Posted: Tue Dec 04, 2007 12:09 am

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

From the way you are using your temporary triggers it almost sounds like you would be better off using #T- #T+ to enable and disable triggers...

Sorcerer Joined: 13 Jan 2006 Posts: 715

I don't want them to be disabled. Once a spell is maxed out the trigger is NEVER needed again. So why only disable it?
I'll do the #UNTRIG.