GavstarB: minor fomatting tweaks

2026-07-25T11:12:04Z

minor fomatting tweaks

← Older revision		Revision as of 11:12, 25 July 2026
Line 7:		Line 7:
	The file may have any number of columns. The first column is the translation key and any subsequent columns are translations of the text for a particular language. The locale for each column is specified in the first row.		The file may have any number of columns. The first column is the translation key and any subsequent columns are translations of the text for a particular language. The locale for each column is specified in the first row.

	~~======~~ Any time you make a change to this file, you must <code>Reimport</code> it for the changes to apply. ~~======~~		'''<big>Any time you make a change to this file, you must <code>Reimport</code> it for the changes to apply.</big>'''

	Translation keys are generally made up of three parts: the prefix, the compcon id of the Resource (and any parent resources), and the suffix.		Translation keys are generally made up of three parts: the prefix, the compcon id of the Resource (and any parent resources), and the suffix.

Line 43:		Line 44:
	For Actions, we use the <code>gear.</code> prefix and include the compcon id of the Kit before the compcon id of the Action.		For Actions, we use the <code>gear.</code> prefix and include the compcon id of the Kit before the compcon id of the Action.

	===== Example Frame: =====		===== Example Frame =====
	id,en,		id,en,
	frame.mf_example.name,"Example",		frame.mf_example.name,"Example",
Line 49:		Line 50:
	frame.mf_example.flavor.short,"Helpful Example",		frame.mf_example.flavor.short,"Helpful Example",

	===== Example Kit: =====		===== Example Kit =====
	id,en,		id,en,
	gear.ms_example.name,"Example Kit",		gear.ms_example.name,"Example Kit",
	gear.ms_example.effect,"Does nothing.",		gear.ms_example.effect,"Does nothing.",

	===== Example Kit (with an Action): =====		===== Example Kit (with an Action) =====
	id,en,		id,en,
	gear.ms_example.name,"Example Kit",		gear.ms_example.name,"Example Kit",
Line 77:		Line 78:
	* Modders often highlight <code>\|efficient\|</code> even though it is not a keyword in the base game.		* Modders often highlight <code>\|efficient\|</code> even though it is not a keyword in the base game.

	====== Keywords~~: =~~=====		===== Keywords =====
	{\| class="wikitable"		{\| class="wikitable"
	!Type		!Type
Line 122:		Line 123:
	\|}		\|}

	===== Complete example - the Hecatoncheires: =====		===== Complete example - the Hecatoncheires =====
	id,en,		id,en,
	"frame.mf_balor_alt_hecatoncheires.name","Hecatoncheires",		"frame.mf_balor_alt_hecatoncheires.name","Hecatoncheires",

GavstarB: Added Localizations and Text Highlighting page.

2026-07-25T11:09:35Z

Added Localizations and Text Highlighting page.

New page

== Localization ==
All text in Lancer Tactics is translated through Godot's [https://docs.godotengine.org/en/4.4/tutorials/assets_pipeline/importing_translations.html localization system]. In the modkit, the complete translations for the game can be found at <code>res://assets/localization/localizations.csv</code>. For mods, the <code>res://unpacked/<MOD_ID>/localization/localizations.csv</code> file will be generated automatically by the mod tool.

It looks something like this:
id,en,
mod.yourname-example.name,example,
The file may have any number of columns. The first column is the translation key and any subsequent columns are translations of the text for a particular language. The locale for each column is specified in the first row.

====== Any time you make a change to this file, you must <code>Reimport</code> it for the changes to apply. ======
Translation keys are generally made up of three parts: the prefix, the compcon id of the Resource (and any parent resources), and the suffix.

For mods, generally the prefixes we need to worry about are <code>frame.</code> for Frames and <code>gear.</code> for Kits.

The most common suffixes are:
{| class="wikitable"
!Suffix
!Meaning
|-
|<code>.name</code>
|The name of the Resource.
|-
|<code>.effect</code>
|For Kits, this is the main body of the tooltip.
|-
|<code>.flavor</code>
|Lore text for the Frame or Kit. For Kits, this is usually omitted entirely.
|-
|<code>.flavor.short</code>
|For Frames, this is the short description of the Frame which appears on the Licenses ring screen.
|-
|<code>.on_attack</code>
|For Kits with ActionAttacks, this displays any <code>On attack:</code> effects in the tooltip.
|-
|<code>.on_hit</code>
|For Kits with ActionAttacks, this displays any <code>On hit:</code> effects in the tooltip.
|-
|<code>.on_crit</code>
|For Kits with ActionAttacks, this displays any <code>On crit:</code> effects in the tooltip.
|-
|<code>.on_miss</code>
|For Kits with ActionAttacks, this displays any <code>On miss:</code> effects in the tooltip.
|}
For Actions, we use the <code>gear.</code> prefix and include the compcon id of the Kit before the compcon id of the Action.

===== Example Frame: =====
id,en,
frame.mf_example.name,"Example",
frame.mf_example.flavor,"The Example frame was created by GMS to use as an example in their various pieces of documentation. It is unclear if any were ever constructed in reality.",
frame.mf_example.flavor.short,"Helpful Example",

===== Example Kit: =====
id,en,
gear.ms_example.name,"Example Kit",
gear.ms_example.effect,"Does nothing.",

===== Example Kit (with an Action): =====
id,en,
gear.ms_example.name,"Example Kit",
gear.ms_example.action_example.name,"Example Action",
gear.ms_example.action_example.effect,"Does nothing.",

== Text Highlighting ==
Text in Lancer Tactics supports [https://docs.godotengine.org/en/stable/tutorials/ui/bbcode_in_richtextlabel.html bbcode formatting]. This means we can make text '''bold''' with <code>[b]text[/b]</code> and ''italic'' with <code>[i]text[/i]</code>.

The text may also contain keywords, formatted as <code>|keyword|</code>, which are highlighted in orange and display a tooltip explaining their meaning when hovered. The text highlighted with <code>||</code> may also contain a valid dice string such as <code>+2</code> or <code>1d6</code> either before or after the word.

The tooltip for a Kit may be displayed on hover by using <code>|Stabilize=gear.ms_stabilize|</code> where <code>Stabilize</code> is the string and <code>ms_stabilize</code> is the compcon id of the Kit. These will be colored green instead of orange.

====== Formatting Tips: ======

* Keywords in Lancer Tactics are always lowercase, with the exception of acronyms like <code>|HP|</code> and <code>|AP|</code>.
* The names of Actions, Kits and Deployables are capitalized. Where they cannot be given a green tooltip, they are '''bolded''' instead.
* Plurals of a keyword, such as <code>|protocols|</code>, are usually considered valid.
* Highlighting <code>|1 AP kinetic|</code> will not work, it must be split into <code>|1 AP| |kinetic|</code>.
* As <code>|ranged attack|</code> and <code>|melee attack|</code> are keywords, it is customary to highlight <code>|ranged| or |melee attack|</code> even though the first tooltip will not work.
* Although <code>|teleport|</code> and <code>|teleports|</code> work, <code>|teleported|</code> does not. Use <code>|teleport||ed|</code> instead.
* Modders often highlight <code>|efficient|</code> even though it is not a keyword in the base game.

====== Keywords: ======
{| class="wikitable"
!Type
!Keywords
|-
|Actions
|<code><nowiki>|barrage|</nowiki></code>, <code><nowiki>|boost|</nowiki></code>, <code><nowiki>|free action|</nowiki></code>, <code><nowiki>|full action|</nowiki></code>, <code><nowiki>|grapple|</nowiki></code>, <code><nowiki>|invade|</nowiki></code>, <code><nowiki>|overcharge|</nowiki></code>, <code><nowiki>|overwatch|</nowiki></code>, <code><nowiki>|protocol|</nowiki></code>, <code><nowiki>|quick action|</nowiki></code>, <code><nowiki>|ram|</nowiki></code>, <code><nowiki>|reaction|</nowiki></code>, <code><nowiki>|tech|</nowiki></code>
|-
|AOEs
|<code><nowiki>|blast|</nowiki></code>, <code><nowiki>|burst|</nowiki></code>, <code><nowiki>|chain|</nowiki></code>, <code><nowiki>|cone|</nowiki></code>, <code><nowiki>|line|</nowiki></code>, <code><nowiki>|area|</nowiki></code>
|-
|Attacks
|<code><nowiki>|melee attack|</nowiki></code>, <code><nowiki>|ranged attack|</nowiki></code>, <code><nowiki>|tech attack|</nowiki></code>
|-
|Checks & Saves
|<code><nowiki>|check|</nowiki></code>, <code><nowiki>|save|</nowiki></code>, <code><nowiki>|agility save|</nowiki></code>, <code><nowiki>|engineering save|</nowiki></code>, <code><nowiki>|hull save|</nowiki></code>, <code><nowiki>|systems save|</nowiki></code>
|-
|Cover
|<code><nowiki>|cover|</nowiki></code>, <code><nowiki>|hard cover|</nowiki></code>, <code><nowiki>|soft cover|</nowiki></code>
|-
|Damage
|<code><nowiki>|burn|</nowiki></code>, <code><nowiki>|energy|</nowiki></code>, <code><nowiki>|explosive|</nowiki></code>, <code><nowiki>|heat|</nowiki></code>, <code><nowiki>|kinetic|</nowiki></code>
|-
|Gear
|<code><nowiki>|AI|</nowiki></code>, <code><nowiki>|deployable|</nowiki></code>, <code><nowiki>|drone|</nowiki></code>, <code><nowiki>|indestructible|</nowiki></code>, <code><nowiki>|limited|</nowiki></code>, <code><nowiki>|recharge {x}+|</nowiki></code>, <code><nowiki>|{x} heat (self)|</nowiki></code>, <code><nowiki>|shield|</nowiki></code>, <code><nowiki>|uncharged|</nowiki></code>, <code><nowiki>|unique|</nowiki></code>, <code><nowiki>|weapon mod|</nowiki></code>
|-
|HASE
|<code><nowiki>|agility|</nowiki></code>, <code><nowiki>|engineering|</nowiki></code>, <code><nowiki>|grit|</nowiki></code>, <code><nowiki>|hull|</nowiki></code>, <code><nowiki>|systems|</nowiki></code>
|-
|Stats
|<code><nowiki>|armor|</nowiki></code>, <code><nowiki>|e-defense|</nowiki></code>, <code><nowiki>|evasion|</nowiki></code>, <code><nowiki>|health|</nowiki></code>/<code><nowiki>|HP|</nowiki></code>, <code><nowiki>|heat cap|</nowiki></code>, <code><nowiki>|limited bonus|</nowiki></code>, <code><nowiki>|reactions|</nowiki></code>, <code><nowiki>|repair cap|</nowiki></code>, <code><nowiki>|save target|</nowiki></code>, <code><nowiki>|sensor range|</nowiki></code>/<code><nowiki>|sensors|</nowiki></code>, <code><nowiki>|size|</nowiki></code>, <code><nowiki>|speed|</nowiki></code>, <code><nowiki>|stress|</nowiki></code>, <code><nowiki>|structure|</nowiki></code>, <code><nowiki>|system points|</nowiki></code>/<code><nowiki>|SP|</nowiki></code>, <code><nowiki>|tech attack|</nowiki></code>
|-
|Statuses & Conditions
|<code><nowiki>|blinded|</nowiki></code>, <code><nowiki>|danger zone|</nowiki></code>, <code><nowiki>|dazed|</nowiki></code>, <code><nowiki>|disengaged|</nowiki></code>, <code><nowiki>|engaged|</nowiki></code>, <code><nowiki>|eva-equipped|</nowiki></code>, <code><nowiki>|exiled|</nowiki></code>, <code><nowiki>|exposed|</nowiki></code>, <code><nowiki>|flying|</nowiki></code>, <code><nowiki>|grappled|</nowiki></code>, <code><nowiki>|hidden|</nowiki></code>, <code><nowiki>|immobilized|</nowiki></code>, <code><nowiki>|impaired|</nowiki></code>, <code><nowiki>|intangible|</nowiki></code>, <code><nowiki>|invisible|</nowiki></code>, <code><nowiki>|invulnerable|</nowiki></code>, <code><nowiki>|jammed|</nowiki></code>, <code><nowiki>|lock on|</nowiki></code>, <code><nowiki>|prone|</nowiki></code>, <code><nowiki>|shredded|</nowiki></code>, <code><nowiki>|shut down|</nowiki></code>, <code><nowiki>|slowed|</nowiki></code>, <code><nowiki>|stunned|</nowiki></code>
|-
|Terms
|<code><nowiki>|accuracy|</nowiki></code>, <code><nowiki>|bonus damage|</nowiki></code>, <code><nowiki>|CORE Power|</nowiki></code>/<code><nowiki>|CP|</nowiki></code>, <code><nowiki>|critical hit|</nowiki></code>/<code><nowiki>|crit|</nowiki></code>, <code><nowiki>|dangerous terrain|</nowiki></code>, <code><nowiki>|difficult terrain|</nowiki></code>, <code><nowiki>|difficulty|</nowiki></code>, <code><nowiki>|engagement|</nowiki></code>, <code><nowiki>|fly|</nowiki></code>, <code><nowiki>|free space|</nowiki></code>/<code><nowiki>|free|</nowiki></code>, <code><nowiki>|full repair|</nowiki></code>, <code><nowiki>|immunity|</nowiki></code>, <code><nowiki>|invisibility|</nowiki></code>, <code><nowiki>|knockback|</nowiki></code>, <code><nowiki>|line of sight|</nowiki></code>, <code><nowiki>|movement|</nowiki></code>, <code><nowiki>|object|</nowiki></code>, <code><nowiki>|obstruction|</nowiki></code>, <code><nowiki>|overshield|</nowiki></code>, <code><nowiki>|range|</nowiki></code>, <code><nowiki>|reactor meltdown|</nowiki></code>/<code><nowiki>|meltdown|</nowiki></code>, <code><nowiki>|reserve|</nowiki></code>, <code><nowiki>|resistance|</nowiki></code>, <code><nowiki>|rest|</nowiki></code>, <code><nowiki>|skirmish|</nowiki></code>, <code><nowiki>|teleport|</nowiki></code>, <code><nowiki>|zero-g|</nowiki></code>
|-
|Weapons
|<code><nowiki>|accurate|</nowiki></code>, <code><nowiki>|armor-piercing|</nowiki></code>/<code><nowiki>|AP|</nowiki></code>, <code><nowiki>|arcing|</nowiki></code>, <code><nowiki>|attack bonus|</nowiki></code>, <code><nowiki>|auxiliary|</nowiki></code>/<code><nowiki>|aux|</nowiki></code>, <code><nowiki>|cannon|</nowiki></code>, <code><nowiki>|CQB|</nowiki></code>, <code><nowiki>|heavy|</nowiki></code>, <code><nowiki>|inaccurate|</nowiki></code>, <code><nowiki>|irreducible|</nowiki></code>, <code><nowiki>|launcher|</nowiki></code>, <code><nowiki>|loading|</nowiki></code>, <code><nowiki>|main|</nowiki></code>, <code><nowiki>|melee|</nowiki></code>, <code><nowiki>|nexus|</nowiki></code>, <code><nowiki>|ordnance|</nowiki></code>, <code><nowiki>|overkill|</nowiki></code>, <code><nowiki>|reliable|</nowiki></code>, <code><nowiki>|rifle|</nowiki></code>, <code><nowiki>|seeking|</nowiki></code>, <code><nowiki>|smart|</nowiki></code>, <code><nowiki>|superheavy|</nowiki></code>, <code><nowiki>|threat|</nowiki></code>, <code><nowiki>|thrown|</nowiki></code>, <code><nowiki>|unloaded|</nowiki></code>
|-
|Lore
|<code><nowiki>|NHP|</nowiki></code>, <code><nowiki>|General Massive Systems|</nowiki></code>/<code><nowiki>|GMS|</nowiki></code>, <code><nowiki>|Harrison Armory|</nowiki></code>/<code><nowiki>|HA|</nowiki></code>, <code><nowiki>|HORUS|</nowiki></code>, <code><nowiki>|IPS-Northstar|</nowiki></code>/<code><nowiki>|IPS-N|</nowiki></code>, <code><nowiki>|Smith-Shimano Corpro|</nowiki></code>/<code><nowiki>|SSC|</nowiki></code>
|}

===== Complete example - the Hecatoncheires: =====
id,en,
"frame.mf_balor_alt_hecatoncheires.name","Hecatoncheires",
"frame.mf_balor_alt_hecatoncheires.flavor","Officially, the Hecatoncheires does not exist. Baronic...",
"frame.mf_balor_alt_hecatoncheires.flavor.short","Sneaky Swarm",
"gear.cp_myrios_long_leash_directed_greywash_hecatoncheires.name","MYRIOS Long-Leash Directed Greywash",
"gear.cp_myrios_long_leash_directed_greywash_hecatoncheires.action_deploy_razor_swarm.name","Deploy Razor Swarm",
"gear.cp_myrios_long_leash_directed_greywash_hecatoncheires.action_deploy_razor_swarm.effect","Deploy a [b]Razor Swarm[/b] to a valid |blast 1| area within |sensors| that contains no hostile characters. The Hecatoncheires may only have a single [b]Razor Swarm[/b] deployed at any one time. The [b]Razor Swarm[/b] persists until the end of the scene or until recalled or redeployed as a |quick action|.\nA [b]Razor Swarm[/b] is a |blast 1| area that provides |soft cover| to allied characters that are at least partially within the area. Hostile characters that start their turn at least partially within the area or move into it for the first time in a round take |2 burn|.\nA [b]Razor Swarm[/b] counts as a |drone| for the purposes of your and your allies' systems, talents, traits, and so on, but is not a character and is otherwise treated as a zone on the battlefield. It does not obstruct movement or cause |engagement|, and hostile characters cannot affect the [b]Razor Swarm[/b] in any way.",
"frame.dep_razor_swarm_hecatoncheires.name","Razor Swarm",
"gear.mt_razor_swarm_hecatoncheires.name","Razor Swarm",
"gear.mt_razor_swarm_hecatoncheires.effect","A [b]Razor Swarm[/b] is a |blast 1| area that provides |soft cover| to allied characters that are at least partially within the area. Hostile characters that start their turn at least partially within the area or move into it for the first time in a round take |2 burn|.\nA [b]Razor Swarm[/b] counts as a |drone| for the purposes of your and your allies' systems, talents, traits, and so on, but is not a character and is otherwise treated as a zone on the battlefield. It does not obstruct movement or cause |engagement|, and hostile characters cannot affect the [b]Razor Swarm[/b] in any way.",
"gear.cp_myrios_long_leash_directed_greywash_hecatoncheires.action_enrage_swarm.name","Enrage Swarm",
"gear.cp_myrios_long_leash_directed_greywash_hecatoncheires.action_enrage_swarm.effect","Each hostile character in one or more areas created by your |drones| takes |4 burn|. This action is |efficient| and will refund |1 CP| at the end of any scene in which this action was used.",
"gear.mt_dispersed_profile_hecatoncheires.name","Dispersed Profile",
"gear.mt_dispersed_profile_hecatoncheires.effect","When the Hecatoncheires is in |soft cover|, ranged attackers receive |+2 difficulty| instead of |+1 difficulty|.",
"gear.mt_smoke_and_mirrors_hecatoncheires.name","Smoke and Mirrors",
"gear.mt_smoke_and_mirrors_hecatoncheires.effect","The Hecatoncheires can always |Hide=gear.ms_hide| in an area of |soft cover|, regardless of |engagement| or enemy traits and systems.",
"gear.mt_panoptes_targeting_hecatoncheires.name","Panoptes Targeting",
"gear.mt_panoptes_targeting_hecatoncheires.effect","The Hecatoncheires' |smart| weapons ignore the |invisible| status of characters within |sensors|.",

Localization and Text Highlighting - Revision history

GavstarB: minor fomatting tweaks

GavstarB: Added Localizations and Text Highlighting page.