LuaGuide: better paragraphicing of gametick funcs
authorWuzzy
Thu, 09 Jun 2016 14:15:15 +0100
changeset 898 159bbbd0ab0a
parent 897 c3ce54152c05
child 899 011ca6031678
LuaGuide: better paragraphicing of gametick funcs
LuaGuide.wiki
--- a/LuaGuide.wiki	Thu Jun 09 14:13:15 2016 +0100
+++ b/LuaGuide.wiki	Thu Jun 09 14:15:15 2016 +0100
@@ -104,7 +104,10 @@
 
 == Other important event handlers ==
 
-The last very important event handlers are `onGameTick` and `onGameTick20`. `onGameTick` is called every game tick, that is every millisecond which is a thousand times a second. `onGameTick20` is called every 20 game ticks, that is, every 20 milliseconds. These functions are very important for specifying actions which need to happen regularily. It is important to know when to use `onGameTick`, and when to use `onGameTick20`. You can usually get away with just using `onGameTick` but must make sure any code inserted here must be efficient and fast, as this function is called very often. Complex code which takes more time to execute should go into `onGameTick20` instead.
+The last important event handlers are `onGameTick` and `onGameTick20`. `onGameTick` is called every game tick, that is every millisecond which is a thousand times a second. `onGameTick20` is called every 20 game ticks, that is, every 20 milliseconds.
+
+These functions are very important for specifying actions which need to happen regularily. It is important to know when to use `onGameTick`, and when to use `onGameTick20`. You can usually get away with just using `onGameTick` but must make sure any code inserted here must be efficient and fast, as this function is called very often. Complex code which takes more time to execute should go into `onGameTick20` instead.
+
 If you need a different interval other than 1 or 20 milliseconds, you can use modulo on the `GameTicks` variable which holds the total number of game ticks since the beginning of the game.
 
 == Getting started … for real ==