Manual:Timer Engine - Revision history

Dt192 at 08:42, 16 February 2026

2026-02-16T08:42:27Z

Dt192: /* Time remaining */

2026-02-16T00:15:43Z

Time remaining

Zooka: ordering

2024-05-13T13:59:10Z

ordering

Dt192 at 06:47, 18 January 2024

2024-01-18T06:47:25Z

Mediares: This page didn't mention remainingTime()!

2023-12-27T23:48:20Z

This page didn't mention remainingTime()!

Zooka: Stopwatch manual added

2023-12-08T05:48:58Z

Stopwatch manual added

Gesslar: correcting grammar

2023-01-17T01:30:43Z

correcting grammar

Kebap: add description text for page

2021-01-05T10:24:12Z

add description text for page

Kitchen: /* Using variables */

2020-05-05T18:33:40Z

Using variables

Vadi: /* Using variables */

2020-03-18T20:55:42Z

Using variables

@@ Line 60: / Line 60: @@
 === Time remaining ===
-You can use [[Manual:Mudlet Object Functions#remainingTime|remainingTime()]] to check how much time remains on a provided Timer.<syntaxhighlight lang="lua">
+You can use [[Manual:Mudlet Object Functions#remainingTime|remainingTime()]] to check how much time remains on a provided Timer.
 tid = tempTimer(600, [[echo("\nYour ten minutes are up.\n")]])
 echo("\nYou have " .. remainingTime(tid) .. " seconds left, use it wisely... \n")

@@ Line 66: / Line 66: @@
 -- Will produce something like:
-You have 599.923 seconds left, use it wisely...
+--> You have 599.923 seconds left, use it wisely...
 -- Then ten minutes time later:
-Your ten minutes are up.
+--> Your ten minutes are up.
 </syntaxhighlight>
 ===Using variables===
 To embed a value of a variable in tempTimer code, you might try using this given what you've learnt:

@@ Line 132: / Line 132: @@
 [[File:Offset timers.png|center]]
 == Stopwatches ==
@@ Line 225: / Line 248: @@
 -->

@@ Line 6: / Line 6: @@
 Mudlet supports four different sorts of timers:
-#  Regular GUI Timers
+#  [[#Regular GUI Timers|Regular GUI Timers]]
-#  Temporary Timers
+#  [[#Temporary Timers|Temporary Timers]]
-#  Offset Timers
+#  [[#Offset Timers|Offset Timers]]
-#  Stopwatches
+#  [[#Stopwatches|Stopwatches]]
 The first can be configured by clicking and will start some code in regular intervals. The others can be used in other scripts you code. All of them are described in more detail below.

@@ Line 59: / Line 59: @@
 </syntaxhighlight>
 ===Using variables===
 To embed a value of a variable in tempTimer code, you might try using this given what you've learnt:

@@ Line 4: / Line 4: @@
 =Timer Engine=
-Mudlet supports 3 different sorts of timers:
+Mudlet supports four different sorts of timers:
 #  Regular GUI Timers
 #  Temporary Timers
 #  Offset Timers
-The first can be configured by clicking and will start some code in regular intervals. The second and third can be used in other scripts you code. All of them are described in more detail below.
+The first can be configured by clicking and will start some code in regular intervals. The others can be used in other scripts you code. All of them are described in more detail below.
 ==Regular GUI Timers==
@@ Line 117: / Line 118: @@
 [[File:Offset timers.png|center]]
 <!-- Not implemented yet!

@@ Line 102: / Line 102: @@
 ===Closures===
-Last but not least, you can also use [http://www.lua.org/pil/6.1.html closures] with tempTimer - using a slightly different syntax that has advantages. For example, you have access variables in it's scope, when it goes off:
+Last but not least, you can also use [http://www.lua.org/pil/6.1.html closures] with tempTimer - using a slightly different syntax that has advantages. For example, you have access variables in its scope, when it goes off:
 <syntaxhighlight lang="lua">
@@ Line 114: / Line 114: @@
 ==Offset Timers==
-<span style="color:#0000FF">'''Offset Timers'''</span> are child timers of a parent timer and fire a single shot after a specified timeout after their parent fired its respective timeout. This interval is an offset to the interval of its parent timer. To make them, add a regular GUI timer (see above), then create another timer and '''drag it onto the timer'''. This will make the timer that is "inside" the timer (the child inside the parent) go off at a certain time after it's parent goes off. Offset timers differ visually from regular timers and are represented with a + icon for offset. Offset timers can be turned on and off by the user just like any other timer. For example - a  parent timer fires every 30 seconds and by doing so kicks off 3 offset timers with an offset of 5 seconds each. Consequently, the 3 children fire 5 seconds after each time the parent timer fired. To make this happen, make the parent timer tic every 30 seconds, drag 3 timers into it with an offset of 5s on each:
+<span style="color:#0000FF">'''Offset Timers'''</span> are child timers of a parent timer and fire a single shot after a specified timeout after their parent fired its respective timeout. This interval is an offset to the interval of its parent timer. To make them, add a regular GUI timer (see above), then create another timer and '''drag it onto the timer'''. This will make the timer that is "inside" the timer (the child inside the parent) go off at a certain time after its parent goes off. Offset timers differ visually from regular timers and are represented with a + icon for offset. Offset timers can be turned on and off by the user just like any other timer. For example - a  parent timer fires every 30 seconds and by doing so kicks off 3 offset timers with an offset of 5 seconds each. Consequently, the 3 children fire 5 seconds after each time the parent timer fired. To make this happen, make the parent timer tic every 30 seconds, drag 3 timers into it with an offset of 5s on each:
 [[File:Offset timers.png|center]]

← Older revision		Revision as of 10:24, 5 January 2021
Line 1:		Line 1:
	{{TOC right}}		{{TOC right}}
		+	{{#description2:Manual on handling timers via GUI or Lua code, starting, stopping, nesting, etc.}}

	=Timer Engine=		=Timer Engine=

@@ Line 70: / Line 70: @@
 -- or with less brackets:
-tempTimer(1.4, function() echo("hello, "..matches[2]..!\n") end)
+tempTimer(1.4, function() echo("hello, "..matches[2].."!\n") end)
 </syntaxhighlight>