|
Tigger Novice
Joined: 07 Oct 2002 Posts: 46 Location: USA
|
Posted: Sat Nov 02, 2002 12:53 am
configureing the tick timer |
I fell lost I have read all the tick times help files but I am still not too sure so I am asking here.
The mud I play let's you see the tick, is there any easy way to set the ticktimer using triggers with this knoldge
Pattern = -- TICK!
Also how do you referance the tick time I want to do something just before the tick...how would I do this?
thanks for the help. |
|
|
|
LightBulb MASTER
Joined: 28 Nov 2000 Posts: 4817 Location: USA
|
Posted: Sat Nov 02, 2002 4:10 am |
You can use #TS to set the timer.
#TR {^-- TICK!} {#TS}
To do something just before the tick, trigger on the timer message.
#TR {TICK IN 5 SECONDS} {action}
You can change the warning time using #TIMER or the Tick Timer preferences.
LightBulb
Senior Member |
|
|
|
Antacus Newbie
Joined: 05 Aug 2002 Posts: 3
|
Posted: Sun Nov 03, 2002 4:36 am |
I use the below as my timeout cmd and notice that the tic countdown halts from 10 down to 0 unless I hit esc. If I do that then it does not do the #cr. Any ideas of a workaround?
#SAY Tick in 10;#WAIT 11000;#CR |
|
|
|
LightBulb MASTER
Joined: 28 Nov 2000 Posts: 4817 Location: USA
|
Posted: Sun Nov 03, 2002 5:27 am |
You don't need a timeout command. Just set the timeout margin to 10, the warning message is automatic. To set this at the command line use:
#TIMER {on} {} {1} {10}
If you would rather use Preferences, it's:
Display tick message: checked
Timer Interval: leave alone
Timeout Margin: 10
Timeout Command: blank
Oh, it's the #WAIT that's causing your problem of course.
LightBulb
Senior Member |
|
|
|
Tigger Novice
Joined: 07 Oct 2002 Posts: 46 Location: USA
|
Posted: Mon Nov 04, 2002 1:10 am |
hummm I tried the set trigger but all I get every tick is
"Timer now at 60 secs."
is that correct?
and should I remove the trigger now? |
|
|
|
LightBulb MASTER
Joined: 28 Nov 2000 Posts: 4817 Location: USA
|
Posted: Mon Nov 04, 2002 6:58 am |
At the tick (when your MUD sends --TICK!) the trigger I wrote does a #TS to update the timer. When it does, you get zMUD's estimate of when the next tick will be. This is the "Timer now at 60 secs" message. If your MUD is using 60 second ticks, all is well. If not, zMUD will make corrections and should be pretty well synced in within 5 to 10 ticks.
With the timer command "#TIMER {on} {} {1} {10}" you should also get a message 10 seconds before the timer expires that says "TICK IN 10 SECONDS". If the next tick arrives more than 10 seconds early (at 45 seconds for instance) you naturally won't see this. But as I said, zMUD will adjust and the message will start showing up once zMUD gets reasonably close to the actual MUD tick.
LightBulb
Senior Member |
|
|
|
|
|