Messages.lua: Difference between revisions
From Spring
Jump to navigationJump to search
tabs->doublespace in lua examples |
|||
| Line 23: | Line 23: | ||
<code><pre> | <code><pre> | ||
local messages = { | 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 | return messages | ||
Revision as of 21:48, 2 April 2011
Location
messages.lua is a file in the Gamedata/ directory of a Spring Game. It defines what messages are shown when a player dies.
Source
The engine source code which parses the data from this file is viewable here: https://github.com/spring/spring/blob/master/rts/Game/Messages.cpp
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