Messages.lua: Difference between revisions
From Spring
Jump to navigationJump to search
m →Single Message: wanted link |
95 ! remove engine support for gamedata/messages.tdf, |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{deprecated|Removed in Spring 95.0. See {{sourcelink|file=cont/examples/Widgets/game_messages.lua}} for a possible replacement.}} | |||
==Location== | ==Location== | ||
<code>messages.lua</code> is a file in the <code>Gamedata/</code> directory of a Spring Game. | <code>messages.lua</code> is a file in the <code>Gamedata/</code> directory of a Spring Game. | ||
| Line 43: | Line 45: | ||
</pre></code> | </pre></code> | ||
[[Category:gamedata]] | [[Category:gamedata]] | ||
Latest revision as of 11:48, 17 November 2013
|
Removed in Spring 95.0. See cont/examples/Widgets/game_messages.lua for a possible replacement. |
Location
messages.lua is a file in the Gamedata/ directory of a Spring Game.
Purpose
This file defines what messages are shown when a player dies.
Source
The engine source code which parses the data from this file is viewable here:
Details
In the message string %i is replaced with the player's team number and %s is replaced with the player's name.
Example
Single Message
Example taken from Air Raid:
return {
"Player %i(%s) is down!"
}
Multiple Messages
Example taken from zeroK. One message is picked from the list at random.
local messages = {
[ [[Team%i(%s) is no more]] ] = {
"Team%i (%s) has been obliterated",
"Team%i (%s) has been liquidated",
"Team%i (%s) has been eradicated",
"Team%i (%s) has been terminated",
"Team%i (%s) has bowed out",
"Team%i (%s) has gone to a better place",
"Team%i (%s) beheld Satan as he fell from heaven LIKE LIGHTNING!",
"Team%i (%s) is out of existence",
...
},
}
return messages
