Gamedev:Glossary: Difference between revisions
m →QTPFS: link to 2nd screenshot |
Silentwings (talk | contribs) m fix invisibility |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 18: | Line 18: | ||
This gives a '''ColorMap''' with 2 colours, the first one blue and second one white:<br> | This gives a '''ColorMap''' with 2 colours, the first one blue and second one white:<br> | ||
<code>colorMap = "1.0 0.0 0.0 | <code>colorMap = "1.0 0.0 0.0 1.0 1.0 1.0 1.0 1.0",</code> | ||
Or it can be pointed to a bitmap file:<br> | Or it can be pointed to a bitmap file:<br> | ||
<code>colorMap = "bitmap_file.tga",</code> | <code>colorMap = "bitmap_file.tga",</code> | ||
'''ColorMaps''' usually describe how the colours of an entity will shift during its lifetime, where the first colour will be used at the beginning and then cycle through all colours until the last one is used at the end of its lifetime. | '''ColorMaps''' usually describe how the colours of an entity will shift during its lifetime, where the first colour will be used at the beginning and then cycle through all colours until the last one is used at the end of its lifetime. | ||
== OTAism == | == OTAism == | ||
| Line 35: | Line 35: | ||
* [[Media:qtpfs1.png | Another screenshot of QTPFS]] | * [[Media:qtpfs1.png | Another screenshot of QTPFS]] | ||
* {{forumlink|topic=27663|title=Feedback on QTPFPS pathing (Forum)}} | * {{forumlink|topic=27663|title=Feedback on QTPFPS pathing (Forum)}} | ||
== springcontent.sdz == | |||
A base content package which is '''always''' loaded for all Spring games. It supplies many 'background' files that games generally won't need to overwrite (but may do so). It also supplies example gadgets in the <code>LuaGadgets/Gadgets/</code> directory which can be directly included by a game, most importantly: | |||
* <code>unit_script.lua</code> - For running [[Animation-LuaScripting | LUS]] animation scripts | |||
* <code>game_spawn.lua</code> - For spawning units on game start | |||
* <code>game_end.lua</code> - For controlling game ends conditions | |||
Example: | |||
<code>return include("luagadgets/gadgets/unit_script.lua")</code> in <code>LuaRules/Gadgets/unit_script.lua</code> | |||
as well as the base content gadget handler itself: | |||
<code>VFS.Include("luagadgets/gadgets.lua",nil, VFS.BASE)</code> in <code>LuaRules/main.lua</code> and <code>LuaRules/draw.lua</code> | |||
See also: | |||
* {{sourcelink|file=cont/base/springcontent}} | |||
[[Category:Game Dev]] | [[Category:Game Dev]] | ||
Latest revision as of 19:26, 9 October 2015
Game Dev Glossary
This page contains definitions of technical terms and acronyms associated with Spring game development.
AtlasedTexture
An alias to a texture. This means the alias must be defined somewhere and pointing to to a real texture. For AtlasedTextures used in projectiles (like those spawned by explosiongenerator) they need to be defined in resources.lua under the [projectiletextures].
A line defining a texture alias in resources.lua looks like this:
alias = "real_image.tga",
Most spring supported image format can be used in AtlasedTextures, but not compressed dds.}}
CColorMap
A collection of 2 or more RGBA colours. They can be expressed either as a string of decimal numbers, or pointing to an image file where each pixel will be used as a colour.
Example:
This gives a ColorMap with 2 colours, the first one blue and second one white:
colorMap = "1.0 0.0 0.0 1.0 1.0 1.0 1.0 1.0",
Or it can be pointed to a bitmap file:
colorMap = "bitmap_file.tga",
ColorMaps usually describe how the colours of an entity will shift during its lifetime, where the first colour will be used at the beginning and then cycle through all colours until the last one is used at the end of its lifetime.
OTAism
Refers to a feature, bug or design quirk which traces its routes back to the early days of Spring when it was designed to reproduce Total Annihilation gameplay.
QTPFS
Quad-Tree Path-Finder System. A path finding algorithm based on a Quadtree data structure.
See also:
springcontent.sdz
A base content package which is always loaded for all Spring games. It supplies many 'background' files that games generally won't need to overwrite (but may do so). It also supplies example gadgets in the LuaGadgets/Gadgets/ directory which can be directly included by a game, most importantly:
unit_script.lua- For running LUS animation scriptsgame_spawn.lua- For spawning units on game startgame_end.lua- For controlling game ends conditions
Example:
return include("luagadgets/gadgets/unit_script.lua") in LuaRules/Gadgets/unit_script.lua
as well as the base content gadget handler itself:
VFS.Include("luagadgets/gadgets.lua",nil, VFS.BASE) in LuaRules/main.lua and LuaRules/draw.lua
See also:
