Zugg Software :: View topic

Posted: Sat Feb 11, 2006 12:17 am

Hi there,

Ok I have a trigger, I'll simplify it to this so it's easier for me to explain...

#TRIGGER {^(*) looks at you.$} {flex;say hello %1}

Now, if someone wants to act the monkey and spam the "look" command at me, I've obviously run into a problem here. What I need, if someone could be so helpful Wink

is something to make it so after the trigger fires, it will be unable to do so again until perhaps a tick or two has elapsed, thus preventing someone from abusing my obvious lack of talents with triggers Smile

... if that makes any sense you're a better person than me heehee!!

Thanks again!

P.S. If you could show me what the completed trigger would look like so I can enter it in the command prompt, I would be most greatful Very Happy

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

#variable AlreadyGreeted {} {} "leave blank to put it in the NONE folder or type the full folder name and path (ie, System|Automapper)"
#if (%ismember(%1,@AlreadyGreeted)) {} {flex;say hello %1;#additem AlreadyGreeted %1}

EDIT: the above will prevent you from flex-greeting the same person more than once per connected session.

Wanderer Joined: 26 May 2004 Posts: 68

or you could use
#t- (your greeting trigger class)
#wa and put in
#t+ (same as above)
that turns it off for however many seconds you choose after you greet anyone. minor thing is it prevents it from working whenever one person does it.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

never use #WAIT in a trigger. All your triggers and maybe your aliases and everything else actually stop working, not just the one with the #WAIT in it.

Apprentice Joined: 29 Jun 2001 Posts: 198 Location: USA

You can also try this:

Wanderer Joined: 26 May 2004 Posts: 68

Enchanter Joined: 10 Oct 2000 Posts: 698

Wanderer Joined: 26 May 2004 Posts: 68

wow. heh. i guess i dont keep up much cause im busy mudding! that said.. now im intrigued why mine works fine.

Novice Joined: 11 Feb 2005 Posts: 39

#TRIGGER {^(*) looks at you.$} {flex;say hello %1;look %1;#ALARM +60 {#T+ LookedatTrigger};#T- LookedatTrigger} LookedatTrigger

best to make the trigger turn itself off and create an alarm to turn it back on after about a min or so. as if someone wants to kill you they just have to 10look you 10look you 10look you and your client well start to work overtime as your trigger well be fireing all the time even though its not sending any commands as the if in the trigger matches but none the less you computer is working overtime makeing the decision wether not todo something or not. hense best to turn the trigger off and save your cpu for otherthings. these triggers are realy just for fun anyway so if it dosent fire for everyone no big deal right? but sometimes the people looking at you arnt so much fun to play with so lets not give them a tool to help them kill you imho anyway.

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

I would just use a simple two state trigger with a wait second for the second one. It's more reliable than alarms and easy enough to code.

Posted: Tue Feb 14, 2006 5:12 pm

Hello again and thanks very much for all the help ... but Embarassed

As I explained initially, I had problems with childish individuals spamming 'look' at me, thus firing off my trigger, which proved to be a nuisance. I thought that showing a simple trigger would help me explain better what I needed and it has to an extent. However, not realising that the #WAIT command creates problems of its own, I left that part out. My trigger basically looked like this when I first created it...

Adept Joined: 21 Sep 2005 Posts: 250 Location: Austin, TX

It looks like you've switched the order of your emotes between examples (the wink comes LAST, right?). Regardless, something like the following should work for ANY series of time-delayed emotes. Just create a separate (temporary) alarm for each message, with staggered delays:

Posted: Tue Feb 14, 2006 6:31 pm

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

Follow Larkins example of a multistate trigger. Its clean, simple, and won't be fired repeatedly

#TRIGGER {^(*) looks at you.$} {flex;say hello %1}
#COND {} {emote does something} {wait|param=2000}
#COND {} {emote does something else} {wait|param=2000}
#COND {} {emote another something} {wait|param=2000}
#COND {} {emote crys.} {wait|param=2000}
#COND {} {#NOOP 30 minute wait} {wait|param=1800000}

Posted: Tue Feb 14, 2006 10:56 pm

Heya guys 'n gals,

I got my trigger sorted and it looks like this...

Adept Joined: 21 Sep 2005 Posts: 250 Location: Austin, TX

Haven't tested this, but try your CONDs using %t1 in place of %1, and it should work. The %t<n> variables let you refer to the <n>th pattern matching variable captured by ANY state of a multi-state trigger.