Messages.lua: Difference between revisions

From Spring
Jump to navigationJump to search
Knorke (talk | contribs)
No edit summary
Flozi (talk | contribs)
95 ! remove engine support for gamedata/messages.tdf,
 
(14 intermediate revisions by 3 users not shown)
Line 1: Line 1:
==What and & Where is it?==
{{deprecated|Removed in Spring 95.0. See {{sourcelink|file=cont/examples/Widgets/game_messages.lua}} for a possible replacement.}}
'''messages.lua''' is a file in the '''gamedata\''' folder of a Spring Game.
 
It defines what messages are shown when a player dies. (and perhaps other messages too but nobody knows for sure)
==Location==
Before the introduction of Lua it was once called messages.tdf with a slighly different synthax. (this still works)
<code>messages.lua</code> is a file in the <code>Gamedata/</code> 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:
 
* {{sourcelink|file=rts/Game/Messages.cpp}}


==Details==
==Details==
In the message string %i is replaced with the teamnumber and %s is replaced with the players name.
In the message string <code>%i</code> is replaced with the player's team number and <code>%s</code> is replaced with the player's name.


==Example==
==Example==
The shortest example I found was in the Airraid game:
===Single Message===
Example taken from Air Raid:


<code>
<code><pre>
return {
return {
"Player %1(%s) is down!"
  "Player %i(%s) is down!"
}
}
</code>
</pre></code>


But there can be multiple messages as this (shortend) example from the zeroK game shows:
===Multiple Messages===
Example taken from [http://code.google.com/p/zero-k/ zeroK]. One message is picked from the list at random.


<code>
<code><pre>
local messages = {
local messages = {
        [ [[Team%i(%s) is no more]] ] = {
  [ [[Team%i(%s) is no more]] ] = {
                --AA/BA
    "Team%i (%s) has been obliterated",
                "Team%i (%s) has been obliterated",
    "Team%i (%s) has been liquidated",
                "Team%i (%s) has been liquidated",
    "Team%i (%s) has been eradicated",
                "Team%i (%s) has been eradicated",
    "Team%i (%s) has been terminated",
                "Team%i (%s) has been terminated",
    "Team%i (%s) has bowed out",
                "Team%i (%s) has bowed out",
    "Team%i (%s) has gone to a better place",
                "Team%i (%s) has gone to a better place",
    "Team%i (%s) beheld Satan as he fell from heaven LIKE LIGHTNING!",
                "Team%i (%s) beheld Satan as he fell from heaven LIKE LIGHTNING!",
    "Team%i (%s) is out of existence",
                "Team%i (%s) is out of existence",
    ...
        },
    },
        [ [[Team%i is no more]] ] = {
        },
}
}
return messages
return messages
<code>
</pre></code>
 


[[Category:Game development]]
[[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