--- a/LuaLibraries.wiki	Sun Jan 17 12:39:33 2016 +0000
+++ b/LuaLibraries.wiki	Sun Jan 17 12:43:07 2016 +0000
@@ -1,6 +1,8 @@
 #summary Libraries for writing Lua scripts in Hedgewars.
 
-= Introduction =
+= Lua libraries documentation =
+
+== Introduction ==
 
 Libraries in scripts in Hedgewars are lua files that are used by many scripts to add a common function, as an example the Locale library that allows scripts to translate text. The variables in these files are not exposed to the script using it but all the functions can be called.
 
@@ -12,35 +14,35 @@
 <code language="lua">loadfile(GetDataPath() .. "Scripts/<Library Name>.lua")()</code>
 This does not work with new Hedgewars versions anymore and causes the script to break. You have to replace it with `HedgewarsScriptLoad`. *Calls to `loadfile` are one of the most common reasons why old scripts do not work in recent Hedgewars versions.*
 
-= Table of Contents =
+== Table of Contents ==
 
 <wiki:toc max_depth="2" />
-= Locale =
+== Locale ==
 
 This library allows you to translate string and should be used whenever a script has text. It loads the appropriate locale file and check automatically.
 
-=== `loc(text)` ===
+==== `loc(text)` ====
 
 Returns the localised string of `text` or, if it is not found, it returns `text`.
 
 
 
-= Utils =
+== Utils ==
 
 This library includes miscellaneous functions to use, they are all independent of each other and can be used everywhere.
 
-=== `gearIsInBox(gear, x, y, w, h)` ===
+==== `gearIsInBox(gear, x, y, w, h)` ====
 
 Returns whether the gear is inside (centre point of the gear) a box with x and y as the top left corner and having the width and height of w and h respectively.
 
 
-=== `gearIsInCircle(gear, x, y, r, useRadius)` ===
+==== `gearIsInCircle(gear, x, y, r, useRadius)` ====
 
 Returns whether the gear is inside a circle with x and y being the centre point and r being the radius of the circle. The boolean useRadius determine whether only the centre point of the gear will be used or the radius of the gear will be checked too.
 
 
 
-= Tracker =
+== Tracker ==
 
 This library is intended to be used if you need to keep track of gears. It can also keep track of teams and clans and as an extra functionality it can also store variables for a gear, team or clan.
 
@@ -61,61 +63,61 @@
 To see a commented example of the tracker in use by a script you can look at
 [http://hg.hedgewars.org/hedgewars/file/default/share/hedgewars/Data/Scripts/Multiplayer/Random_Weapon.lua Random Weapons].
 
-== Tracking functions ==
+=== Tracking functions ===
 
-=== `trackGear(gear)` ===
+==== `trackGear(gear)` ====
 
 Will keep track of the gear.
 
 
-=== `trackDeletion(gear)` ===
+==== `trackDeletion(gear)` ====
 
 Will stop keeping track of the gear (gears not tracked will be ignored).
 
 
-=== `trackTeams()` ===
+==== `trackTeams()` ====
 
 Will start the tracking of teams, clans and hedgehogs (hogs can be tracked without this).
 
 
-== “`runOn`” functions ==
+=== “`runOn`” functions ===
 
-=== `runOnGears(func)` ===
+==== `runOnGears(func)` ====
 
 Runs the function `func` on all gears.
 
 
-=== `runOnHogs(func)` ===
+==== `runOnHogs(func)` ====
 
 Runs the function `func` on all hedgehogs.
 
 
-=== `runOnHogsInTeam(func, team)` ===
+==== `runOnHogsInTeam(func, team)` ====
 
 Runs the function `func` on all hedgehogs in the specified team.
 
 
-=== runOnHogsInOtherTeams(func, team) ===
+==== runOnHogsInOtherTeams(func, team) ====
 
 Runs the function `func` on all hedgehogs but those in the specified team.
 
 
-=== `runOnHogsInClan(func, clan)` ===
+==== `runOnHogsInClan(func, clan)` ====
 
 Runs the function `func` on all hedgehogs in the specified clan.
 
 
-=== `runOnHogsInOtherClans(func, clan)` ===
+==== `runOnHogsInOtherClans(func, clan)` ====
 
 Runs the function `func` on all hedgehogs but those in the specified clan.
 
 
-== Variable functions ==
+=== Variable functions ===
 
 _To be continued …_
 
 
-= Animate =
+== Animate ==
 
 This library provides functions that aid cinematic/cut-scene creation and functions for handling events. 
 
@@ -133,12 +135,12 @@
 Also, `AnimInit()` needs to be called in `onGameInit()`.
 Each of these functions will be explained below.
 
-== Cinematic Handling ==
+=== Cinematic handling ===
 
-=== `ShowAnimation()` ===
+==== `ShowAnimation()` ====
 Performs the current action in the cinematic and returns `true` if finished, otherwise `false`. It needs to be used in `onGameTick`. Cut-scenes need to be added with `AddAnim(steps)`.
 
-=== `AddAnim(steps)` ===
+==== `AddAnim(steps)` ====
 Adds `steps` to the array of animations, where `steps` is a table with numbers as keys and elements of the following form. Each step is a table having the following keys: `func`, `args`, `swh`.
 
   * `func` is the function to be executed. It can be any function that returns false when it needs to be called again in following game ticks (e.g. `AnimMove`). It can be one of the cinematic functions. 
@@ -154,7 +156,7 @@
     }
 AddAnim(cinem)</code>
 
-=== `RemoveAnim(steps)` ===
+==== `RemoveAnim(steps)` ====
 Removes `steps` from the animations array.
 
 === `AddSkipFunction(anim, func, args)` ===
@@ -162,10 +164,10 @@
 Example:
 <code language="lua">AddSkipFunc(cinem, SkipCinem, {})</code>
 
-=== `RemoveSkipFunction(anim)` ===
+==== `RemoveSkipFunction(anim)` ====
 Removes the skip function associated with `anim`.
 
-=== `SetAnimSkip(bool)` ===
+==== `SetAnimSkip(bool)` ====
 Sets the state of animation skipping to `bool`. It is useful in case the player is allowed to skip the animation.
 
 Example:
@@ -175,36 +177,36 @@
     end
 end</code>
 
-=== `AnimInProgress()` ===
+==== `AnimInProgress()` ====
 Returns `true` if a cinematic is currently taking place, `false` otherwise.
 
-=== `ExecuteAfterAnimations()` ===
+==== `ExecuteAfterAnimations()` ====
 Calls the functions (added with `AddFunction`) that need to be executed after the cinematic. The best location for this function call is in `onGameTick`.
 
-=== `AddFunction(element)` ===
+==== `AddFunction(element)` ====
 Adds `element` to the functions array that are to be called after the cinematic. `element` is a table with the keys: `func`, `args`.
 
 Example:
 <code language="lua">AddFunction({func = AfterCinem, args = {2}})</code>
 
-=== `RemoveFunction()` ===
+==== `RemoveFunction()` ====
 Removes the first function from the aforementioned list.
 
-=== `AnimInit()` ===
+==== `AnimInit()` ====
 Initializes variables used by the other functions. Needs to be called in `onGameInit`.
 
-=== !AnimUnWait() ===
+==== !AnimUnWait() ====
 Decreases the wait time used by cinematics. It is best called in `onGameTick`.
 
-== Cinematic Functions ==
+=== Cinematic functions ===
 
-=== `AnimSwitchHog(gear)` ===
+==== `AnimSwitchHog(gear)` ====
 Switches to `gear` and follows it.
 
-=== `AnimWait(gear, time)` ===
+==== `AnimWait(gear, time)` ====
 Increases the wait time by `time`. `gear` is just for compatibility with `ShowAnimation`.
 
-=== `AnimSay(gear, text, manner, time` ===
+==== `AnimSay(gear, text, manner, time` ====
 Calls `HogSay` with the first three arguments and increses the wait time by `time`.
 
 Example:
@@ -213,37 +215,37 @@
     {func = AnimSay, args = {gear2, "No, I'm not!", SAY_SAY, 2000}}
    }</code>
 
-=== `AnimSound(gear, sound, time)` ===
+==== `AnimSound(gear, sound, time)` ====
 Plays the sound `sound` and increases the wait time by `time`.
 
-=== `AnimTurn(hog, dir)` ===
+==== `AnimTurn(hog, dir)` ====
 Makes `hog` face in direction `dir`, where `dir` equals either `"Right"` or `"Left"`.
 
-=== `AnimMove(hog, dir, x, y)` ===
+==== `AnimMove(hog, dir, x, y)` ====
 Makes `hog` move in direction `dir` until either his horizontal coordinate is `x` or his vertical coordinate is `y`.
 
-=== `AnimJump(hog, jumpType)` ===
+==== `AnimJump(hog, jumpType)` ====
 Makes `hog` perform a jump of type `jumpType`, where `jumpType` equals either `"long"`, `"high"` or `"back"`.
 
-=== `AnimSetGearPosition(gear, x, y, fall)` ===
+==== `AnimSetGearPosition(gear, x, y, fall)` ====
 Sets the position of `gear` to (`x`, `y`). If the optional argument `fall` does not equal `false` then the gear is given a small falling velocity in order to get around exact positioning.
 
-=== `AnimDisappear(gear, x, y)` ===
+==== `AnimDisappear(gear, x, y)` ====
 Teleports the gear to (`x`, `y`), adding some effects at the previous position and sounds. Doesn’t follow the gear.
 
-=== `AnimOutOfNowhere(gear, x, y)` ===
+==== `AnimOutOfNowhere(gear, x, y)` ====
 Teleports the gear to (`x`, `y`), adding effects and sounds at the final position. Follows gear.
 
-=== `AnimTeleportGear(gear, x, y)` ===
+==== `AnimTeleportGear(gear, x, y)` ====
 Teleports the gear to (`x`, `y`), adding effects and sounds both at the starting position and the final position. Follows gear.
 
-=== `AnimVisualGear(gear, x, y, vgType, state, critical, follow)` ===
+==== `AnimVisualGear(gear, x, y, vgType, state, critical, follow)` ====
 Calls `AddVisualGear` with arguments second to sixth. If the optional argument `follow` equals `true` then the gear is followed. `gear` is for compatibility only.
 
-=== `AnimCaption(gear, text, time)` ===
+==== `AnimCaption(gear, text, time)` ====
 Adds `text` as caption and increases wait time by `time`.
 
-=== `AnimCustomFunction(gear, func, args)` ===
+==== `AnimCustomFunction(gear, func, args)` ====
 Calls the function `func` with `args` as arguments. This function is useful, for instance, when the cinematic uses the position of a gear at the moment of execution. If `func` needs to be called in following game ticks then it should return false.
 
 Example:
@@ -259,7 +261,7 @@
 
 cinem = {{func = AnimCustomFunction, args = {hog1, NeedToTurn, {hog1, hg2}}}}</code>
 
-=== `AnimInsertStepNext(step)` ===
+==== `AnimInsertStepNext(step)` ====
 Inserts `step` after the current step (read: action) in the cinematic array. Useful when an action depends on variables (e.g. positoins). It can be used mostly with `AnimCustomFunction`. Note: In case of multiple consecutive calls, steps need to be added in reverse order.
 
 Example:
@@ -277,11 +279,11 @@
 end
 cinem = {{func = AnimCustomFunction, args = {liveHog, BlowHog, {deadHog}}}}</code>
 
-== Event Handling ==
+=== Event handling ===
 
 Events are pairs of functions that are used to check for various conditions. One of them is for verification and, if it returns `true`, the second function is called.
 
-=== `AddEvent(condFunc, condArgs, doFunc, doArgs, evType)` ===
+==== `AddEvent(condFunc, condArgs, doFunc, doArgs, evType)` ====
 Adds the functions `condFunc` and `doFunc` to the events list. They get called with the respective args (`condArgs` and `doArgs`). `condFunc` will get called in every game tick until it returns `true` or is removed. Once it returns `true`, `doFunc` is called and they are or are not removed from the list, depending on `evType` (`0` for removal, `1` for keeping). An `evType` of `1` is useful for repeating actions (e.g. every time a hog gets damaged, do something).
 
 Example:
@@ -300,10 +302,10 @@
 AddEvent(CheckPos, {}, DoPos, {}, 0) -- Add event that gets removed on completion
 AddEvent(CheckAmmo, {}, DoAmmo, {}, 1) -- Add repeating event</code>
 
-=== `AddNewEvent(condFunc, condArgs, doFunc, doArgs, evType)` ===
+==== `AddNewEvent(condFunc, condArgs, doFunc, doArgs, evType)` ====
 Does the same as `AddEvent`, but first checks if the event is already in the list so that it isn’t added twice.
 
-=== `RemoveEventFunc(cFunc, cArgs)` ===
+==== `RemoveEventFunc(cFunc, cArgs)` ====
 Removes the event or events that have `cFunc` as the condition checking function. If `cArgs` does not equal `nil` then only those events get removed that have `cArgs` as arguments for `cFunc`, too.
 
 Example:
@@ -315,11 +317,11 @@
 RemoveEventFunc(condFunc1) --Removes all three events that have condFunc1
 RemoveEventFunc(condFunc2, condArgs1) --Removes a single event</code>
 
-=== `CheckEvents` ===
+==== `CheckEvents` ====
 Verifies all the condition functions in the events list and calls the respective ‘action’ functions if the conditions are met. If the `evType` of a completed event equals `0` then it is removed from the list. This function is best placed in `onGameTick`.
 
 
-= Params =
+== Params ==
 The Params library is a small library introduced in 0.9.21. It provides a function to parse the parameter string `ScriptParam` and it is intended to simplify using this string.
 
 This library requires the parameter string to be in a certain format. It must be a comma-seperated list of kev-value pairs in the `key=value` format. Examples:
@@ -330,10 +332,10 @@
 
 Using this library is by no means neccessary, you could use practically whatever syntax you wish if you write your own code for parsing.
 
-=== `parseParams()` ===
+==== `parseParams()` ====
 Parses `ScriptParam` and writes the result into the global table `params`. The table will follow the `key=value` pattern. Both keys and pairs are stored as string.
 
-==== Example  ====
+===== Example  =====
 <code language="lua">
 function onParameters()
     parseParams()
@@ -350,7 +352,7 @@
 
 
 
-= !TargetPractice =
+== !TargetPractice ==
 Starting with 0.9.21, this library provides a function to create an entire target practice mission which follows some basic properties.
 
 Here is a brief description of the generated missions:
@@ -433,7 +435,7 @@
 
 TargetPracticeMission(params)</code>
 
-= !SpeedShoppa =
+== !SpeedShoppa ==
 Starting with 0.9.22, this library provides a function to create a simple shoppa-style mission.
 
 In !SpeedShoppa missions, the player starts with infinite ropes and has to collect all crates as fast as possible and compete for the fastest time.