TIMER TICKER FOR JMC For JMC version 3.26 with VBScript (c) Rashnak 2004 (Special thanks to Björn for testing this) VERSION HISTORY: 2004-08-12 The script appeared to behave badly when local time changes from 23:59:59 to 00:00:00 at midnight. This is fixed. 2004-08-08 "Session" timer will no longer flash in status box. 2004-08-08 New addition contains records of dawn and dusk hours for each month and an improved trigger for displaying them together with Time timer: #action {/^(.+), the (\d{1,2})(st|nd|rd|th) of (.*), Year (\d{1,4}) of the (.+) Age.$/} {#script timeAction "", "", "%1", "%2", "%3", "%4", "%5"} #action {/^(\d{1,2})(am|pm) on (.+), the (\d{1,2})(st|nd|rd|th) of (.*), Year (\d{1,4}) of the (.+) Age.$/} {#script timeAction "%0", "%1", "%2", "%3", "%5", "%6", "%7"} #action {/^According to the (Dúnadan|Sindarin) calendar, it is:$/} {#showme Time on Arda is $timerTime. Dawn: $timeMonthDawn Dusk: $timeMonthDusk} You have to check time on MUME once to capture the current month name, before the above action starts to work properly. 2004-08-07 In the script the difference between two times is calculated by taking the 'seconds' field of two time values and substracting them. For example, if T1 = 18:00.9 and T2 = 18:01.0, the script would calculate the difference as one whole second, when in fact it is only about 0.1 of a second. This and future versions contain another timer mechanism to measure times at resolution of 0.1 second "ticks". The actual length of these ticks may not be exactly 0.1 seconds, but at 0 - 5 second range the difference should be minimal. The same command interface can be used for these timers, like this: timer Test 1.5 - #showme Moi! Sets a countdown timer of 1.5 seconds (instead of 1:05 you must use 1.5 format). To start from zero, use 0.0. 2004-08-07 When a countdown timer reaches zero, any commands it is set to execute will execute once, after which the commands are now cleared from the timer. Unless one of these commands was to delete the timer, the timer itself will continue to run on the negative side though. This was a quick hack to prevent a possible problem that sometimes made the script miss timer reaching zero value. 2004-08-06 Bug in 2004-08-05 version that caused error message with the following command syntax was fixed: timer