Editing Mod Hooks
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
− | + | WarLight will call into a [[Mods|mod's]] lua code using what are called '''hooks'''. | |
For example, it will call a hook named Server_StartGame when a game is beginning and give your mod an opportunity to change things about how the map is set up. | For example, it will call a hook named Server_StartGame when a game is beginning and give your mod an opportunity to change things about how the map is set up. | ||
Line 7: | Line 7: | ||
== Server Hooks == | == Server Hooks == | ||
− | + | Server_Created (Server_Created.lua) | |
** Called in every game when the game is first created. In multi-player, this means it's called before players even accept or join the request for the game. This is the only place that game settings can be changed. | ** Called in every game when the game is first created. In multi-player, this means it's called before players even accept or join the request for the game. This is the only place that game settings can be changed. | ||
** Return value: None. | ** Return value: None. | ||
Line 33: | Line 33: | ||
* Server_AdvanceTurn_Start (Server_AdvanceTurn.lua) | * Server_AdvanceTurn_Start (Server_AdvanceTurn.lua) | ||
− | ** Called whenever the server begins processing a normal turn (not territory picking). This gives mods an opportunity to insert orders at the start of a turn, before any player's orders are added. All of the Server_AdvanceTurn_* | + | ** Called whenever the server begins processing a normal turn (not territory picking). This gives mods an opportunity to insert orders at the start of a turn, before any player's orders are added. All of the Server_AdvanceTurn_* turns share global state within a single turn, so global variables can be read and written reliably by mods. |
** Arguments: | ** Arguments: | ||
# [[Mod API Reference:Game|Game]]: Provides read-only information about the game. | # [[Mod API Reference:Game|Game]]: Provides read-only information about the game. | ||
− | # addNewOrder: A function that you can call to add a [[Mod API Reference:GameOrder|GameOrder]] to the start of the turn | + | # addNewOrder: A function that you can call to add a [[Mod API Reference:GameOrder|GameOrder]] to the start of the turn. Pass a single GameOrder as the only argument to this function. You may call this function multiple times if you wish. |
− | + | ||
− | + | ||
− | + | ||
Line 52: | Line 49: | ||
## WL.ModOrderControl.Skip: Indicates this order should be skipped. It won't appear in the orders list at all and it will be as if the order never existed. A [[Mod API Reference:GameOrderEvent|GameOrderEvent]] will be written into the orders list to tell the player who entered this order that their order was skipped. | ## WL.ModOrderControl.Skip: Indicates this order should be skipped. It won't appear in the orders list at all and it will be as if the order never existed. A [[Mod API Reference:GameOrderEvent|GameOrderEvent]] will be written into the orders list to tell the player who entered this order that their order was skipped. | ||
## WL.ModOrderControl.SkipAndSupressSkippedMessage: Same as Skip, except that the GameOrderEvent is not written. This should be used with care, as players will want to know why their order didn't appear in the orders list. This should only be used if you use some other mechanism to explain to the player why their order was not present, or if this is an order that your mod inserted and therefore no players were expecting it. | ## WL.ModOrderControl.SkipAndSupressSkippedMessage: Same as Skip, except that the GameOrderEvent is not written. This should be used with care, as players will want to know why their order didn't appear in the orders list. This should only be used if you use some other mechanism to explain to the player why their order was not present, or if this is an order that your mod inserted and therefore no players were expecting it. | ||
− | # addNewOrder: A function that you can call to add a [[Mod API Reference:GameOrder|GameOrder]] to the | + | # addNewOrder: A function that you can call to add a [[Mod API Reference:GameOrder|GameOrder]] to the turn, which will be inserted just after the current order. Pass a single GameOrder as the only argument to this function. You may call this function multiple times if you wish. |
Line 59: | Line 56: | ||
** Arguments: | ** Arguments: | ||
# [[Mod API Reference:Game|Game]]: Provides read-only information about the game. | # [[Mod API Reference:Game|Game]]: Provides read-only information about the game. | ||
− | # addNewOrder: A function that you can call to add a [[Mod API Reference:GameOrder|GameOrder]] to the | + | # addNewOrder: A function that you can call to add a [[Mod API Reference:GameOrder|GameOrder]] to the end of the turn. Pass a single GameOrder as the only argument to this function. You may call this function multiple times if you wish. |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Client Hooks == | == Client Hooks == | ||
* Client_PresentConfigureUI (Client_PresentConfigureUI.lua) | * Client_PresentConfigureUI (Client_PresentConfigureUI.lua) | ||
− | ** Called when a player checks your mod on the Create Game page. If your mod has any configurable settings, you should create UI controls on the screen to allow players to configure them using the [[Mod API Reference:UI|UI API]]. Mods should also check the <code> | + | ** Called when a player checks your mod on the Create Game page. If your mod has any configurable settings, you should create UI controls on the screen to allow players to configure them using the [[Mod API Reference:UI|UI API]]. Mods should also check the <code>Mod.Settings</code> global to see if any settings are already defined, and if they are, default their UI state to match that. |
** Arguments: | ** Arguments: | ||
# rootParent: Pass this as an argument to the top-level UI element your mod creates. See the [[Mod API Reference:UI|UI API]] for details. | # rootParent: Pass this as an argument to the top-level UI element your mod creates. See the [[Mod API Reference:UI|UI API]] for details. | ||
Line 102: | Line 90: | ||
* Client_GameRefresh (Client_GameRefresh.lua) | * Client_GameRefresh (Client_GameRefresh.lua) | ||
− | ** Invoked whenever the client gets data about this game from the server. This can be used to check for updated Mod.PublicGameData or Mod.PlayerGameData, documented at [[Mod Game Data Storage]] | + | ** Invoked whenever the client gets data about this game from the server. This can be used to check for updated Mod.PublicGameData or Mod.PlayerGameData, documented at [[Mod Game Data Storage]] |
** Arguments: | ** Arguments: | ||
# [[Mod API Reference:ClientGame|ClientGame]]: Information about the game. | # [[Mod API Reference:ClientGame|ClientGame]]: Information about the game. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Notes == | == Notes == | ||
Line 119: | Line 100: | ||
− | No hooks have return values. Meaning, it doesn't matter if you return any values from your hook functions. Instead, the mod framework gives you callbacks to call to affect things. This is preferred over return values for a few reasons. First, it allows mods to call the callbacks early on or late on in their function, which can be easier than a return statement which must come at the end. Second, it allows mods to simply not call the callback, which can signal to | + | No hooks have return values. Meaning, it doesn't matter if you return any values from your hook functions. Instead, the mod framework gives you callbacks to call to affect things. This is preferred over return values for a few reasons. First, it allows mods to call the callbacks early on or late on in their function, which can be easier than a return statement which must come at the end. Second, it allows mods to simply not call the callback, which can signal to WarLight that the mod doesn't care about the result of this. This can be important in some cases where multiple mods that define the same hook. Sometimes the mods instructions can conflict and WarLight must decide which to obey. |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + |