 |
charneus
Wizard
Joined: 19 Jun 2005
Posts: 1876
Location: California
|
 Posted: Mon Dec 10, 2007 6:59 am
What's wrong with this script?
|
I've been messing around with idle triggers - mainly because of my newborn son. Basically, what I'm doing is setting up a trigger to make me go afk after a certain amount of time. Here's what I have...
| Code: |
| #ONINPUT {*} {#UNTRIGGER "Idle";#IF (@idle) {idle=0;#SAY IdleScript was activated!} {#ALARM "Idle" +600 {idle=1;away I am away, but forgot to put up my script.;#IF (!@offduty) {offduty;helper I'm away from the keyboard for a bit.}}}} |
However, after being away for a half hour, I came back, and the script didn't activate. As far as I know, #ONINPUT is only based off something being entered into the command line, right? Or does it also include scripts? I have several ingame scripts that will fire whether I'm there or not (such as every hour, it'll report my experience, or it'll recast a spell), but I wouldn't think that'd interfere with the script. Am I wrong?
Charneus |
|
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Mon Dec 10, 2007 12:01 pm
|
Any command sent to the MUD will activate an oninput trigger, including scripted commands. To avoid this, use #send.
|
|
|
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
