The Muse - User contributions [en]

Modding

2026-08-26T21:49:14Z

Olive: /* Modkit */ wording

Get help at [https://wick.itch.io/lancer-tactics/community wick.itch.io/lancer-tactics] or [https://discord.com/invite/2t7Efg2Fbj Discord]

== Modkit ==

To make mods, you'll first need to get your hands on the source of the game. It’s possible to decompile any game made in Godot which is what bootleg (affectionate) modders have been doing up til now, but we’re making the source available through official channels for convenience. Lancer’s TTRPG creator ecosystem is based on a belief that it should be hackable & extensible, and we want to carry that culture forward.

As of v1.3.3, you can download the modkit [https://wick.itch.io/lancer-tactics via itch.io]. Please be sure you've reviewed and agree to the [https://lancertactics.com/modding-eula/ Modding EULA]

If you want to adapt a third-party supplement that you did not design, be sure to get explicit permission from the creator — for your convenience & safety, we've hosted a standard license you can refer to for that permission: [https://lancertactics.com/homebrew-mod-license/ Homebrew Mod License]

== Background — how do Godot mods work? ==

Lancer Tactics is made in the [https://godotengine.org/ Godot] game engine; at time of writing on version 4.7. In order to make mods for anything besides asset packs, you'll need to become comfortable working in its editor. I hope this doesn't scare you off; of all the major game engines, it has a reputation of being easy to pick up.

Godot projects have an internal filesystem much like the one on your computer; a series of folders and files. The root is referred to as <code>res://</code>

[[File:Godot_filesystem.png]]

However, to run the game Godot needs assets (images, music, etc) to be in a different format than you’d find with them sitting in your filesystem. It compiles these files into a big pile of files that look like this, all jumbled together in one folder.

[[File:Mod_background_imports.png|thumb|A scattering of processed image files from Godot's .import folder. ]]

To keep knowing where things are, it maintains a skeleton of the original filesystem with all the orignal files swapped out with “.remap” placeholders that just point to where in that big pile the asset they represent went. Furthermore, whenever the game attempts to load a specific asset at a location (e.g. <code>res://assets/icons/mech.svg</code>), it caches whatever it loaded into memory. Whenever we ask it to load that asset again, it doesn’t have to go ask the .remap file where the original one went and load it up — it just returns whatever it ended up loading from there last time. This cache is like a ghost sitting on top of a skeleton.

For modding, this gives us an opportunity. Instead of needing to actually copy in modded files and override the originals, we can manipulate this ghost-filesystem-cache by lying about what files are at what locations. Here’s what a mod looks like for Lancer Tactics (using a modified system from Godot Mod Loader):

[[File:ModBackgroundUnpacked.png]]

We have a special folder where we put the actual mod files: “unpacked”, then another folder with the specific mod’s identifier “Wickworks-Sawhorse”. Within that, we have a “res” folder, and that’s where the lying starts. When loading up the mod, we can grab everything inside of the mod’s “res” and tell the ghost-cache that the mod’s files are the ones that are actually at that location. In this example, by the end of it when we ask Godot to load <code>res://assets/frames/horus/mf_sawhorse.png</code>, it will return the file that’s actually over in <code>res://unpacked/Wickworks-Sawhorse/res/assets/frames/horus/mf_sawhorse.png</code>.

Now that we have the power to insert files as we’d like, Godot Mod Loader additionally has some functions that through dark magic allows multiple mods to all alter the same script instead of overriding it. I’m a little fuzzy on these details, but the shape of it is that while loading each successive script that extends the same file actually extends the previous one that also extended that script so all the changes end up getting applied.

In order to change what mods are active, the out-of-the-box Godot Mod Loader addon expects you to restart the game so it can start work with a clean slate each time. For Lancer Tactics, I modified this so it tracks all files inserted so we can go and undo all of our lies and reset the ghost-cache to files’ original locations. This was important because I’m expecting people to want to be able to make maps and modules with bundled-in mods that substantially alter the content of the game, and requiring a restart whenever you load one up would be a terrible experience.

== Mod Loader ==
Lancer Tactics is using the [https://wiki.godotmodding.com/ Godot Mod Loader addon], but has made some changes to it:

=== Implicit Overrides ===
Instead of having to manually declare each asset you want to override in code (via an overwrites.gd that the Mod Tools would generate and put into an extensions/ or overwrites/ sub-directory), assets and resources are overridden implicitly by matching file paths and names from a mod's res/ directory. See [[Modding Cookbook#Replacing Resources|replacing resources]] for details. This should allow people to make texture asset pack mods fully outside the Godot editor by downloading a template, dropping images into a folder, and zipping it up.

=== Hooks and class_name scripts ===
Unfortunately, it ended up not being feasible to support their script Hook system, which means it's not possible to change class_name scripts (or is unreliable to do so). Hooks were designed to work around a bug in Godot that has been unaddressed since 4.3 and do some crazy preprocessing of scripts that involves decompiling them, editing names of functions, and swapping in the copies. For the time being, we decided to instead convert the most likely targets of mods (UnitCondition, UnitTile, UnitAction, etc) into autoloads so they can be accessed by normal script Extensions instead. This will provide better backwards compatibility for mods once the bug is addressed than having to go back and tear out all the Hook code.

TL;DR: You are NOT able to currently extend a script with a class_name. If you want to make a mod that extends a class_name script and it looks like it could be an Autoload, let me know and I'll see if I can convert it!

The engine bug necessitating hooks: [https://github.com/godotengine/godot/issues/83542 github.com/godotengine/godot/issues/83542]

A possible fix to the godot engine that'll solve all this: [https://github.com/godotengine/godot/pull/116556 github.com/godotengine/godot/pull/116556]

=== Formatting and Paths ===
Additionally, we've made some path and formatting tweaks for styling and ease of use:

* We're using <code>res://unpacked/</code> instead of <code>res://mods-unpacked/</code> for the directory in the godot project that mods are unpacked into. I don't like hypens in filenames, it's a bit shorter, and will be sorted alphabetically to the end of the project folders. Plus mod zips will be structured like <code>unpacked/Author-ModName/manifest.json</code> which is a bit cleaner than having an extra "mods-" at the start of it.

* Our manifest.json doesn't have the <code>"extra": {"godot: {...}}</code> keys, opting instead to just put all that stuff at the root.

* Mod config files are stored in <code>user://mod_configs/</code> instead of straight <code>user://</code> for mod-tool-plugin-save.json, mod_user_profiles.json, and mod_loader_cache.json. Keeps the user directory cleaner.

== Mod Types & Security ==

Mods are code that some rando wrote that the game downloads and then runs on your machine. Godot does not have built-in sandboxing for gdscript, so this code has just as much access as the game does, ie, can read or write any file on your computer and talk to the internet. Uh oh!

To be fair, this is a issue with most mods for most games. It’s a very trust-based at-your-own-risk sort of country. This is fine if mods aren’t tightly integrated, but as soon as you as a developer start removing barriers and letting people accidentally stumble into downloading harmful code by just pressing buttons in-game, you start taking on the responsibility in the case of something bad happening.

Slay The Spire 2, another game made in Godot, handles this by putting a big warning screen that it forces you to click through before you can start installing mods. We’ve done something similar:

'''TODO INSERT IMAGE'''

To help manage this, Lancer Tactics distinguishes between three mod types:

; Asset Pack
: Just images and tres files. Doesn't even have a mod_main.gd; just a json manifest and images in various places to get picked up by the appropriate resources. These can be required by combats/modules and they'll be treated as safe since not having scripts makes them risk-free. We allow tres files to be in asset packs as long as they do not contain any inline scripts.
: Mods that do not contain any .gd files (including mod_main.gd) will be treated as Asset Packs.

; Content Pack
: Can have scripts and a mod_main.gd to do non-standard things, but are responsible for making sure anything off-standard they do is reversible without a restart. Since these allow arbitrary code execution, they will prompt additional warnings to the player before they are enabled.
: Mods that contain .gd files and are marked as <code>requires_restart</code> as "false" in their manifest will be treated as Content Packs.

; Substantial Mod
: As above, but the changes are not cleanly reversible so require a restart to turn off or on.
: Mods that contain .gd files and are marked as <code>requires_restart</code> as "true" in their manifest will be treated as Substantial Mods.

An area for future growth, given substantially more resources, would be to add the ability to script game content in a nice sandboxed environment by setting up an internal .lua API for new abilities to use. This would allow new mechs and whatnot to count as asset packs, but the time-benefit tradeoff isn’t favorable given our current time and labor constraints.

Modding

2026-08-26T21:48:21Z

Olive: /* Modkit */ Added links to the new modkit licenses

Get help at [https://wick.itch.io/lancer-tactics/community wick.itch.io/lancer-tactics] or [https://discord.com/invite/2t7Efg2Fbj Discord]

== Modkit ==

To make mods, you'll first need to get your hands on the source of the game. It’s possible to decompile any game made in Godot which is what bootleg (affectionate) modders have been doing up til now, but we’re making the source available through official channels for convenience. Lancer’s TTRPG creator ecosystem is based on a belief that it should be hackable & extensible, and we want to carry that culture forward.

As of v1.3.3, you can download the modkit [https://wick.itch.io/lancer-tactics via itch.io]. Please be sure you've reviewed and agree to the [https://lancertactics.com/modding-eula/ Modding EULA]

If you want to adapt a third-party supplement that you did not design, be sure to get explicit permission from the creator — for your convenience & safety, we've hosted a standard license you can refer to for the terms of the adaptation here: [https://lancertactics.com/homebrew-mod-license/ Homebrew Mod License]

== Background — how do Godot mods work? ==

Lancer Tactics is made in the [https://godotengine.org/ Godot] game engine; at time of writing on version 4.7. In order to make mods for anything besides asset packs, you'll need to become comfortable working in its editor. I hope this doesn't scare you off; of all the major game engines, it has a reputation of being easy to pick up.

Godot projects have an internal filesystem much like the one on your computer; a series of folders and files. The root is referred to as <code>res://</code>

[[File:Godot_filesystem.png]]

However, to run the game Godot needs assets (images, music, etc) to be in a different format than you’d find with them sitting in your filesystem. It compiles these files into a big pile of files that look like this, all jumbled together in one folder.

[[File:Mod_background_imports.png|thumb|A scattering of processed image files from Godot's .import folder. ]]

To keep knowing where things are, it maintains a skeleton of the original filesystem with all the orignal files swapped out with “.remap” placeholders that just point to where in that big pile the asset they represent went. Furthermore, whenever the game attempts to load a specific asset at a location (e.g. <code>res://assets/icons/mech.svg</code>), it caches whatever it loaded into memory. Whenever we ask it to load that asset again, it doesn’t have to go ask the .remap file where the original one went and load it up — it just returns whatever it ended up loading from there last time. This cache is like a ghost sitting on top of a skeleton.

For modding, this gives us an opportunity. Instead of needing to actually copy in modded files and override the originals, we can manipulate this ghost-filesystem-cache by lying about what files are at what locations. Here’s what a mod looks like for Lancer Tactics (using a modified system from Godot Mod Loader):

[[File:ModBackgroundUnpacked.png]]

We have a special folder where we put the actual mod files: “unpacked”, then another folder with the specific mod’s identifier “Wickworks-Sawhorse”. Within that, we have a “res” folder, and that’s where the lying starts. When loading up the mod, we can grab everything inside of the mod’s “res” and tell the ghost-cache that the mod’s files are the ones that are actually at that location. In this example, by the end of it when we ask Godot to load <code>res://assets/frames/horus/mf_sawhorse.png</code>, it will return the file that’s actually over in <code>res://unpacked/Wickworks-Sawhorse/res/assets/frames/horus/mf_sawhorse.png</code>.

Now that we have the power to insert files as we’d like, Godot Mod Loader additionally has some functions that through dark magic allows multiple mods to all alter the same script instead of overriding it. I’m a little fuzzy on these details, but the shape of it is that while loading each successive script that extends the same file actually extends the previous one that also extended that script so all the changes end up getting applied.

In order to change what mods are active, the out-of-the-box Godot Mod Loader addon expects you to restart the game so it can start work with a clean slate each time. For Lancer Tactics, I modified this so it tracks all files inserted so we can go and undo all of our lies and reset the ghost-cache to files’ original locations. This was important because I’m expecting people to want to be able to make maps and modules with bundled-in mods that substantially alter the content of the game, and requiring a restart whenever you load one up would be a terrible experience.

== Mod Loader ==
Lancer Tactics is using the [https://wiki.godotmodding.com/ Godot Mod Loader addon], but has made some changes to it:

=== Implicit Overrides ===
Instead of having to manually declare each asset you want to override in code (via an overwrites.gd that the Mod Tools would generate and put into an extensions/ or overwrites/ sub-directory), assets and resources are overridden implicitly by matching file paths and names from a mod's res/ directory. See [[Modding Cookbook#Replacing Resources|replacing resources]] for details. This should allow people to make texture asset pack mods fully outside the Godot editor by downloading a template, dropping images into a folder, and zipping it up.

=== Hooks and class_name scripts ===
Unfortunately, it ended up not being feasible to support their script Hook system, which means it's not possible to change class_name scripts (or is unreliable to do so). Hooks were designed to work around a bug in Godot that has been unaddressed since 4.3 and do some crazy preprocessing of scripts that involves decompiling them, editing names of functions, and swapping in the copies. For the time being, we decided to instead convert the most likely targets of mods (UnitCondition, UnitTile, UnitAction, etc) into autoloads so they can be accessed by normal script Extensions instead. This will provide better backwards compatibility for mods once the bug is addressed than having to go back and tear out all the Hook code.

TL;DR: You are NOT able to currently extend a script with a class_name. If you want to make a mod that extends a class_name script and it looks like it could be an Autoload, let me know and I'll see if I can convert it!

The engine bug necessitating hooks: [https://github.com/godotengine/godot/issues/83542 github.com/godotengine/godot/issues/83542]

A possible fix to the godot engine that'll solve all this: [https://github.com/godotengine/godot/pull/116556 github.com/godotengine/godot/pull/116556]

=== Formatting and Paths ===
Additionally, we've made some path and formatting tweaks for styling and ease of use:

* We're using <code>res://unpacked/</code> instead of <code>res://mods-unpacked/</code> for the directory in the godot project that mods are unpacked into. I don't like hypens in filenames, it's a bit shorter, and will be sorted alphabetically to the end of the project folders. Plus mod zips will be structured like <code>unpacked/Author-ModName/manifest.json</code> which is a bit cleaner than having an extra "mods-" at the start of it.

* Our manifest.json doesn't have the <code>"extra": {"godot: {...}}</code> keys, opting instead to just put all that stuff at the root.

* Mod config files are stored in <code>user://mod_configs/</code> instead of straight <code>user://</code> for mod-tool-plugin-save.json, mod_user_profiles.json, and mod_loader_cache.json. Keeps the user directory cleaner.

== Mod Types & Security ==

Mods are code that some rando wrote that the game downloads and then runs on your machine. Godot does not have built-in sandboxing for gdscript, so this code has just as much access as the game does, ie, can read or write any file on your computer and talk to the internet. Uh oh!

To be fair, this is a issue with most mods for most games. It’s a very trust-based at-your-own-risk sort of country. This is fine if mods aren’t tightly integrated, but as soon as you as a developer start removing barriers and letting people accidentally stumble into downloading harmful code by just pressing buttons in-game, you start taking on the responsibility in the case of something bad happening.

Slay The Spire 2, another game made in Godot, handles this by putting a big warning screen that it forces you to click through before you can start installing mods. We’ve done something similar:

'''TODO INSERT IMAGE'''

To help manage this, Lancer Tactics distinguishes between three mod types:

; Asset Pack
: Just images and tres files. Doesn't even have a mod_main.gd; just a json manifest and images in various places to get picked up by the appropriate resources. These can be required by combats/modules and they'll be treated as safe since not having scripts makes them risk-free. We allow tres files to be in asset packs as long as they do not contain any inline scripts.
: Mods that do not contain any .gd files (including mod_main.gd) will be treated as Asset Packs.

; Content Pack
: Can have scripts and a mod_main.gd to do non-standard things, but are responsible for making sure anything off-standard they do is reversible without a restart. Since these allow arbitrary code execution, they will prompt additional warnings to the player before they are enabled.
: Mods that contain .gd files and are marked as <code>requires_restart</code> as "false" in their manifest will be treated as Content Packs.

; Substantial Mod
: As above, but the changes are not cleanly reversible so require a restart to turn off or on.
: Mods that contain .gd files and are marked as <code>requires_restart</code> as "true" in their manifest will be treated as Substantial Mods.

An area for future growth, given substantially more resources, would be to add the ability to script game content in a nice sandboxed environment by setting up an internal .lua API for new abilities to use. This would allow new mechs and whatnot to count as asset packs, but the time-benefit tradeoff isn’t favorable given our current time and labor constraints.

The Muse

2026-08-26T21:41:31Z

Olive: EULA now hosted at https://lancertactics.com/modding-eula/

The Muse (aka the Lancer Tactics Wiki) is a compilation of editor documentation and guides for [https://lancertactics.com/ Lancer Tactics], a video game adaptation of the [https://massifpress.com/lancer Lancer TTRPG] by Tom Bloom and Miguel Lopez-Hall. The in-universe concept of the Muse is from the [https://vexwerewolf.itch.io/in-golden-flame-act-1 In Golden Flame] module by Vex Werewolf.

== Modding ==
* [https://lancertactics.com/modding-eula/ Modding EULA]
* [[Modding|Introduction to modding]]
* [[Modding Cookbook]]
* [[Basic Troubleshooting]]
* [[Fx Groups]]
* [[Localization and Text Highlighting]]
* [[Pixel Art]]
* [[Adding a new License]]

== Editors ==
* [[Module Editor]]
** [[Basics of Module Creation]]
* [[Combat Editor Cookbook]]
* [[Editor Triggers|Editor Triggers List]]
* [[Playtesting|Playtesting tips]]

== Other ==
* [[Changes from the TTRPG]]

== External Links & Resources ==
* [https://wick.works/devlog/category/lancer-tactics Devlog at wick.works]
* [https://discord.com/invite/2t7Efg2Fbj Lancer Tactics Discord]
* [https://wick.itch.io/lancer-tactics/community itch.io forums]
* [https://wick.itch.io/lancer-tactics itch.io store page]
* [https://store.steampowered.com/app/4049810/Lancer_Tactics/ Wishlist on Steam]
* [https://mod.io/g/lancer-tactics Lancer Tactics on mod.io]
* [https://compcon.app/ COMP/CON]

''Lancer Tactics is not an official Lancer product; it is a third party work, and is not affiliated with Massif Press. Lancer Tactics is published via the Lancer Third Party License. Lancer is copyright Massif Press.''

Modding

2026-08-26T21:41:13Z

Olive: EULA now hosted at https://lancertactics.com/modding-eula/

Get help at [https://wick.itch.io/lancer-tactics/community wick.itch.io/lancer-tactics] or [https://discord.com/invite/2t7Efg2Fbj Discord]

== Modkit ==

To make mods, you'll first need to get your hands on the source of the game. It’s possible to decompile any game made in Godot which is what bootleg (affectionate) modders have been doing up til now, but we’re making the source available through official channels for convenience. Lancer’s TTRPG creator ecosystem is based on a belief that it should be hackable & extensible, and we want to carry that culture forward.

We (Wickworks) are talking to a lawyer to make sure we have all our hatches buttoned down legally to make sure we maintain ownership of the game code itself (and maybe like watermark some assets?), but once we get that squared away we’ll add the modkit alongside the rest of the downloads on itch. Until then, you can request early access to it on [https://discord.com/invite/2t7Efg2Fbj Lancer Tactic’s Discord server].

Finally, before getting started with the modkit, please be sure you've reviewed and agree to the [https://lancertactics.com/modding-eula/ Modding EULA].

== Background — how do Godot mods work? ==

Lancer Tactics is made in the [https://godotengine.org/ Godot] game engine; at time of writing on version 4.7. In order to make mods for anything besides asset packs, you'll need to become comfortable working in its editor. I hope this doesn't scare you off; of all the major game engines, it has a reputation of being easy to pick up.

Godot projects have an internal filesystem much like the one on your computer; a series of folders and files. The root is referred to as <code>res://</code>

[[File:Godot_filesystem.png]]

However, to run the game Godot needs assets (images, music, etc) to be in a different format than you’d find with them sitting in your filesystem. It compiles these files into a big pile of files that look like this, all jumbled together in one folder.

[[File:Mod_background_imports.png|thumb|A scattering of processed image files from Godot's .import folder. ]]

To keep knowing where things are, it maintains a skeleton of the original filesystem with all the orignal files swapped out with “.remap” placeholders that just point to where in that big pile the asset they represent went. Furthermore, whenever the game attempts to load a specific asset at a location (e.g. <code>res://assets/icons/mech.svg</code>), it caches whatever it loaded into memory. Whenever we ask it to load that asset again, it doesn’t have to go ask the .remap file where the original one went and load it up — it just returns whatever it ended up loading from there last time. This cache is like a ghost sitting on top of a skeleton.

For modding, this gives us an opportunity. Instead of needing to actually copy in modded files and override the originals, we can manipulate this ghost-filesystem-cache by lying about what files are at what locations. Here’s what a mod looks like for Lancer Tactics (using a modified system from Godot Mod Loader):

[[File:ModBackgroundUnpacked.png]]

We have a special folder where we put the actual mod files: “unpacked”, then another folder with the specific mod’s identifier “Wickworks-Sawhorse”. Within that, we have a “res” folder, and that’s where the lying starts. When loading up the mod, we can grab everything inside of the mod’s “res” and tell the ghost-cache that the mod’s files are the ones that are actually at that location. In this example, by the end of it when we ask Godot to load <code>res://assets/frames/horus/mf_sawhorse.png</code>, it will return the file that’s actually over in <code>res://unpacked/Wickworks-Sawhorse/res/assets/frames/horus/mf_sawhorse.png</code>.

Now that we have the power to insert files as we’d like, Godot Mod Loader additionally has some functions that through dark magic allows multiple mods to all alter the same script instead of overriding it. I’m a little fuzzy on these details, but the shape of it is that while loading each successive script that extends the same file actually extends the previous one that also extended that script so all the changes end up getting applied.

In order to change what mods are active, the out-of-the-box Godot Mod Loader addon expects you to restart the game so it can start work with a clean slate each time. For Lancer Tactics, I modified this so it tracks all files inserted so we can go and undo all of our lies and reset the ghost-cache to files’ original locations. This was important because I’m expecting people to want to be able to make maps and modules with bundled-in mods that substantially alter the content of the game, and requiring a restart whenever you load one up would be a terrible experience.

== Mod Loader ==
Lancer Tactics is using the [https://wiki.godotmodding.com/ Godot Mod Loader addon], but has made some changes to it:

=== Implicit Overrides ===
Instead of having to manually declare each asset you want to override in code (via an overwrites.gd that the Mod Tools would generate and put into an extensions/ or overwrites/ sub-directory), assets and resources are overridden implicitly by matching file paths and names from a mod's res/ directory. See [[Modding Cookbook#Replacing Resources|replacing resources]] for details. This should allow people to make texture asset pack mods fully outside the Godot editor by downloading a template, dropping images into a folder, and zipping it up.

=== Hooks and class_name scripts ===
Unfortunately, it ended up not being feasible to support their script Hook system, which means it's not possible to change class_name scripts (or is unreliable to do so). Hooks were designed to work around a bug in Godot that has been unaddressed since 4.3 and do some crazy preprocessing of scripts that involves decompiling them, editing names of functions, and swapping in the copies. For the time being, we decided to instead convert the most likely targets of mods (UnitCondition, UnitTile, UnitAction, etc) into autoloads so they can be accessed by normal script Extensions instead. This will provide better backwards compatibility for mods once the bug is addressed than having to go back and tear out all the Hook code.

TL;DR: You are NOT able to currently extend a script with a class_name. If you want to make a mod that extends a class_name script and it looks like it could be an Autoload, let me know and I'll see if I can convert it!

The engine bug necessitating hooks: [https://github.com/godotengine/godot/issues/83542 github.com/godotengine/godot/issues/83542]

A possible fix to the godot engine that'll solve all this: [https://github.com/godotengine/godot/pull/116556 github.com/godotengine/godot/pull/116556]

=== Formatting and Paths ===
Additionally, we've made some path and formatting tweaks for styling and ease of use:

* We're using <code>res://unpacked/</code> instead of <code>res://mods-unpacked/</code> for the directory in the godot project that mods are unpacked into. I don't like hypens in filenames, it's a bit shorter, and will be sorted alphabetically to the end of the project folders. Plus mod zips will be structured like <code>unpacked/Author-ModName/manifest.json</code> which is a bit cleaner than having an extra "mods-" at the start of it.

* Our manifest.json doesn't have the <code>"extra": {"godot: {...}}</code> keys, opting instead to just put all that stuff at the root.

* Mod config files are stored in <code>user://mod_configs/</code> instead of straight <code>user://</code> for mod-tool-plugin-save.json, mod_user_profiles.json, and mod_loader_cache.json. Keeps the user directory cleaner.

== Mod Types & Security ==

Mods are code that some rando wrote that the game downloads and then runs on your machine. Godot does not have built-in sandboxing for gdscript, so this code has just as much access as the game does, ie, can read or write any file on your computer and talk to the internet. Uh oh!

To be fair, this is a issue with most mods for most games. It’s a very trust-based at-your-own-risk sort of country. This is fine if mods aren’t tightly integrated, but as soon as you as a developer start removing barriers and letting people accidentally stumble into downloading harmful code by just pressing buttons in-game, you start taking on the responsibility in the case of something bad happening.

Slay The Spire 2, another game made in Godot, handles this by putting a big warning screen that it forces you to click through before you can start installing mods. We’ve done something similar:

'''TODO INSERT IMAGE'''

To help manage this, Lancer Tactics distinguishes between three mod types:

; Asset Pack
: Just images and tres files. Doesn't even have a mod_main.gd; just a json manifest and images in various places to get picked up by the appropriate resources. These can be required by combats/modules and they'll be treated as safe since not having scripts makes them risk-free. We allow tres files to be in asset packs as long as they do not contain any inline scripts.
: Mods that do not contain any .gd files (including mod_main.gd) will be treated as Asset Packs.

; Content Pack
: Can have scripts and a mod_main.gd to do non-standard things, but are responsible for making sure anything off-standard they do is reversible without a restart. Since these allow arbitrary code execution, they will prompt additional warnings to the player before they are enabled.
: Mods that contain .gd files and are marked as <code>requires_restart</code> as "false" in their manifest will be treated as Content Packs.

; Substantial Mod
: As above, but the changes are not cleanly reversible so require a restart to turn off or on.
: Mods that contain .gd files and are marked as <code>requires_restart</code> as "true" in their manifest will be treated as Substantial Mods.

An area for future growth, given substantially more resources, would be to add the ability to script game content in a nice sandboxed environment by setting up an internal .lua API for new abilities to use. This would allow new mechs and whatnot to count as asset packs, but the time-benefit tradeoff isn’t favorable given our current time and labor constraints.

Basic Troubleshooting

2026-07-25T00:19:41Z

Olive: /* Troubleshooting Code/Content Additions */

== Troubleshooting Code/Content Additions ==
This is a checklist of common mistakes that may be causing your mod to work incorrectly. It's not a comprehensive guide on all the things that can go wrong, but it's a good place to start if you're stuck.

* '''Missing Script:''' If the addition is a custom action or buff that requires a custom script to implement, make sure you've assigned that script to the resource for that action or buff. Besides not executing your custom code, certain settings can create even more erratic behavior on default resources for custom scripts. For example, the root "Buff" resource with "trigger on" events set will simply remove themselves when those events trigger.

* '''Null Checks:''' Whenever you await ''anything'' within an action, make sure you check if your unit and/or target are still valid before proceeding. If the unit dies or the player exits the game before the ability resumes the references may become null. There are a variety of abort_ functions on EventCores that make this more painless. For example:

await run_system_fxgs(unit)
if activation.abort_without_unit(unit): return

or

var plan:CompconPlan = await TargetActionUtil.ask_for_targets(activation)
if activation.abort_when(not CompconPlan.is_valid_with_targets(plan, context)): return

Basic Troubleshooting

2026-07-25T00:19:15Z

Olive: /* Troubleshooting Code/Content Additions */ add null check tip

== Troubleshooting Code/Content Additions ==
This is a checklist of common mistakes that may be causing your mod to work incorrectly. It's not a comprehensive guide on all the things that can go wrong, but it's a good place to start if you're stuck.

* '''Missing Script:''' If the addition is a custom action or buff that requires a custom script to implement, make sure you've assigned that script to the resource for that action or buff. Besides not executing your custom code, certain settings can create even more erratic behavior on default resources for custom scripts. For example, the root "Buff" resource with "trigger on" events set will simply remove themselves when those events trigger.

* '''Null Checks:''' Whenever you await 'anything' within an action, make sure you check if your unit and/or target are still valid before proceeding. If the unit dies or the player exits the game before the ability resumes the references may become null. There are a variety of abort_ functions on EventCores that make this more painless. For example:

await run_system_fxgs(unit)
if activation.abort_without_unit(unit): return

or

var plan:CompconPlan = await TargetActionUtil.ask_for_targets(activation)
if activation.abort_when(not CompconPlan.is_valid_with_targets(plan, context)): return

The Muse

2026-07-23T22:52:21Z

Olive: /* Editors */

The Muse (aka the Lancer Tactics Wiki) is a compilation of editor documentation and guides for [https://lancertactics.com/ Lancer Tactics], a video game adaptation of the [https://massifpress.com/lancer Lancer TTRPG] by Tom Bloom and Miguel Lopez-Hall. The in-universe concept of the Muse is from the [https://vexwerewolf.itch.io/in-golden-flame-act-1 In Golden Flame] module by Vex Werewolf.

== Modding ==
* [[Modding EULA]]
* [[Modding|Introduction to modding]]
* [[Modding Cookbook]]
* [[Basic Troubleshooting]]
* [[Fx Groups]]
* [[Pixel Art]]
* [[Adding a new License]]

== Editors ==
* [[Module Editor]]
* [[Combat Editor Cookbook]]
* [[Editor Triggers|Editor Triggers List]]
* [[Playtesting|Playtesting tips]]

== Other ==
* [[Changes from the TTRPG]]

== External Links & Resources ==
* [https://wick.works/devlog/category/lancer-tactics Devlog at wick.works]
* [https://discord.com/invite/2t7Efg2Fbj Lancer Tactics Discord]
* [https://wick.itch.io/lancer-tactics/community itch.io forums]
* [https://wick.itch.io/lancer-tactics itch.io store page]
* [https://store.steampowered.com/app/4049810/Lancer_Tactics/ Wishlist on Steam]
* [https://mod.io/g/lancer-tactics Lancer Tactics on mod.io]
* [https://compcon.app/ COMP/CON]

''Lancer Tactics is not an official Lancer product; it is a third party work, and is not affiliated with Massif Press. Lancer Tactics is published via the Lancer Third Party License. Lancer is copyright Massif Press.''

The Muse

2026-07-23T22:52:02Z

Olive: /* Editors */ link to playtesting tips

The Muse (aka the Lancer Tactics Wiki) is a compilation of editor documentation and guides for [https://lancertactics.com/ Lancer Tactics], a video game adaptation of the [https://massifpress.com/lancer Lancer TTRPG] by Tom Bloom and Miguel Lopez-Hall. The in-universe concept of the Muse is from the [https://vexwerewolf.itch.io/in-golden-flame-act-1 In Golden Flame] module by Vex Werewolf.

== Modding ==
* [[Modding EULA]]
* [[Modding|Introduction to modding]]
* [[Modding Cookbook]]
* [[Basic Troubleshooting]]
* [[Fx Groups]]
* [[Pixel Art]]
* [[Adding a new License]]

== Editors ==
* [[Module Editor]]
* [[Combat Editor Cookbook]]
* [[Editor Triggers|Editor Triggers List]]
* [[Playtesting tips|Playtesting]]

== Other ==
* [[Changes from the TTRPG]]

== External Links & Resources ==
* [https://wick.works/devlog/category/lancer-tactics Devlog at wick.works]
* [https://discord.com/invite/2t7Efg2Fbj Lancer Tactics Discord]
* [https://wick.itch.io/lancer-tactics/community itch.io forums]
* [https://wick.itch.io/lancer-tactics itch.io store page]
* [https://store.steampowered.com/app/4049810/Lancer_Tactics/ Wishlist on Steam]
* [https://mod.io/g/lancer-tactics Lancer Tactics on mod.io]
* [https://compcon.app/ COMP/CON]

''Lancer Tactics is not an official Lancer product; it is a third party work, and is not affiliated with Massif Press. Lancer Tactics is published via the Lancer Third Party License. Lancer is copyright Massif Press.''

Playtesting

2026-07-23T22:51:15Z

Olive: Add playtesting tips page

== Tips ==

* You can open the console with the ` key. These commands can be helpful in getting and checking the invisible state of the combat or module (type "help" for details on all available commands):

get_module_state
set_module_state
get_combat_state
set_combat state
get_clocks
set_clock

MediaWiki:Common.css

2026-07-22T22:55:00Z

Olive:

/* CSS placed here will be applied to all skins */

/* latin */
@import url('https://fonts.googleapis.com/css2?family=Open+Sans:ital,wght@0,300..800;1,300..800&family=Space+Mono:ital,wght@0,400;0,700;1,400;1,700&display=swap');

body {
background: #1a212b;
font-family: 'Open Sans', 'Segoe UI','Segoe UI Emoji','Segoe UI Symbol','Lato','Liberation Sans','Noto Sans','Helvetica Neue','Helvetica',sans-serif;

dt {
font-family: 'Open Sans', 'Segoe UI','Segoe UI Emoji','Segoe UI Symbol','Lato','Liberation Sans','Noto Sans','Helvetica Neue','Helvetica',sans-serif;
margin: 0 1em 4px;
}

h1, h2, h3, h4, h5, h6 {
font-family: 'Space Mono', monospace !important;
}

input {
font-family: 'Space Mono', monospace !important;
}

.mw-createacct-benefits-heading, .mw-number-text, .mw-number-text strong {
font-family: 'Space Mono', monospace !important;
background: none !important;
padding: 0 !important;
}

#simpleSearch {
border: solid 1px #36455C;

#searchInput {
font-family: 'Space Mono', monospace;
background: #11151C;
color: white;
border-radius: 0;
}

#searchButton {
background-image: url(/skins/Timeless/resources/images/search-ltr-light.svg);
background-size: 20px 20px;
}
}

#mw-header-container {
background: #1a212b;
border-bottom: 4px solid #E5B91A;

#p-logo-text a {
font-family: 'Space Mono', monospace;
text-transform: uppercase;
color: #8197b8;
}

#personal h2 {
font-family: 'Space Mono', monospace;
color: #8197b8;
background-image: url(/skins/Timeless/resources/images/user-light.svg);
@media screen and (min-width: 850px) {
background-size: 20px 20px;
background-position: left 13px;
}

&::after {
background-image: url(/skins/Timeless/resources/images/arrow-down-light.svg);
}
}

#p-search {
padding-top: 1px;
}
}

#site-navigation, #site-tools, #page-tools {
background: #eee !important;
}

@media screen and (max-width: 850px) {
#site-navigation h2 {
background-image: url(/skins/Timeless/resources/images/menu-large-light.svg);
}

#site-tools h2 {
background-image: url(/skins/Timeless/resources/images/gear-large-light.svg);

&::after {
background-image: url(/skins/Timeless/resources/images/arrow-down-light.svg);
}
}
}

#mw-header-hack {
display: none;
}

#mw-header-nav-hack {
background: #eee !important;

.color-middle, .color-left, .color-right {
background: #E5B91A;
height: 4px;
}
}

#mw-content-container {
background: #36455C;
border-bottom: solid 4px #E5B91A;

input[type="button"], input[type="submit"], #wpCreateaccount {
background-color: #E5B91A !important;
color: #11151C !important;
border-color: #E5B91A !important;

&:hover {
color: #fff !important;
}
}

#mw-content {
background: #eee !important;
}

.mw-body h1.firstHeading {
border-color: #52698C;
padding-bottom: 6px;
}

.mw-indicators {
font-family: 'Space Mono',monospace !important;
.mw-helplink-icon { display: none; }
}

.tools-inline li {
font-family: 'Space Mono',monospace !important;
padding-bottom: 2px;

&.selected { border-color: #52698C; }

&:not(.mw-watchlink) a {
background: none;
padding: 0 2px;
}
}

.mw-editsection {
font-family: 'Space Mono', monospace !important;
background: none;
margin: 0;

a:first-of-type {
padding: 0;
margin: 0 20px 0 0;
}
}
}

#mw-footer-container {
color: #8197b8;

a {
color: #8197b8;
}

#footer-poweredbyico {
background: #8197b8;
padding: 4px;
border-radius: 5px;
}
}
}

The Muse

2026-07-22T22:43:58Z

Olive: /* Modding */ link to fx groups

The Muse (aka the Lancer Tactics Wiki) is a compilation of editor documentation and guides for [https://lancertactics.com/ Lancer Tactics], a video game adaptation of the [https://massifpress.com/lancer Lancer TTRPG] by Tom Bloom and Miguel Lopez-Hall. The in-universe concept of the Muse is from the [https://vexwerewolf.itch.io/in-golden-flame-act-1 In Golden Flame] module by Vex Werewolf.

== Modding ==
* [[Modding EULA]]
* [[Modding|Introduction to modding]]
* [[Modding Cookbook]]
* [[Basic Troubleshooting]]
* [[Fx Groups]]
* [[Pixel Art]]
* [[Adding a new License]]

== Editors ==
* [[Module Editor]]
* [[Combat Editor Cookbook]]

== Other ==
* [[Changes from the TTRPG]]

== External Links & Resources ==
* [https://wick.works/devlog/category/lancer-tactics Devlog at wick.works]
* [https://discord.com/invite/2t7Efg2Fbj Lancer Tactics Discord]
* [https://wick.itch.io/lancer-tactics/community itch.io forums]
* [https://wick.itch.io/lancer-tactics itch.io store page]
* [https://store.steampowered.com/app/4049810/Lancer_Tactics/ Wishlist on Steam]
* [https://mod.io/g/lancer-tactics Lancer Tactics on mod.io]
* [https://compcon.app/ COMP/CON]

''Lancer Tactics is not an official Lancer product; it is a third party work, and is not affiliated with Massif Press. Lancer Tactics is published via the Lancer Third Party License. Lancer is copyright Massif Press.''

Fx Groups

2026-07-22T22:42:47Z

Olive: initial commit, copied over from internal documentation

== Testing FxGroups ==
Open up '''fx_group_texter.tscn''' and Run Current Scene (Ctrl+R).
[[File:FX Group tester.png|thumb|Screenshot of the FX Group tester.]]
The two panels on the left are:

* '''Attack FXGs'''. These are fxgs that have a corresponding target fxg. The base one runs at the originating tile and the target one runs at the target tile(s).
* '''Other FXGs'''. Abilities or events, at the originating tile only.

FXGs are added to each list by their file names; when the system finds a pair of fxgs with one ending in "_target", it will add the two to the top list and otherwise in the bottom.

'''This scene hot-reloads!''' If you modify an FXG scene in the editor, '''save it''', and then switch back to the running tester, re-running the FXG should use the updated values! This should work for tweaking resources, but you may have to re-run the scene in order to obtain new graphic files or sounds.

== Anatomy of an FxGroup ==
[[File:FXG node tree.png|thumb|378x378px|FXG node tree.]]
Fx Group scenes are composed of a FxGroup node with some number of children nodes that play sprite animations, FMOD sound effect events, particle emitters, and movements of the originating mech token.

They can also have sub-FxGroup nodes as children to coordinate the ordering and timing of such effects. These children FxGroups can have their own basic effects and FxGroup children of their own, etc. The timing of when children FxGroups play their effects is detailed below.

In order to allow the game to show results of an action mid-completion of the effect, the '''Preamble''' signal can be emitted at some point during the effect.

FxGroup scene files should live in the '''content/fx_groups/''' directory. Subfolders can be created at the developer's discretion.

== Timing of an FxGroup ==
[[File:FxGroup Timing.png|center|thumb|775x775px|Diagram of an FxGroup's lifecycle.]]

=== Start ===
The root FxGroup is kicked off by code. It may or may not be awaited; attacks wait for the effect to finish, while terrain destruction just kind of happens in the background.

=== Start delay & jitter ===
It can wait some amount of time before kicking off its children effects. Jitter will randomly add ''up to'' its amount of time in seconds to this delay.

=== Basic children ===
AnimatedSprite3D, MuzzleFlash, GPUParticle3D, and BumpNodes all count as "basic children". They all kick off at the same time here.

=== Children FxGroups ===
These have three possible start points:

* Immediate — start at the same time as the rest of the basic children
* Parent Preamble — start whenever the parent fires its Preamble signal.
* Basic Siblings Finished — start when the basic children of its parent finish

=== Preamble ===
This has four possible points it could be emitted:

* Immediate — effectively no preamble; emits as soon as all the rest of the effects start
* Basic Children Finished — emits when all non-FXG children complete (animations
* Duration — emit after a set time (looks at the "Preamble Duration" value, which no other preamble mode uses)
* At finish — effectively the entire thing is preamble; emits when all children have completed.

When the Preamble is emitted:

* Any children FXGs set to "Parent Preamble" are kicked off.
* Any awaiting game code is resumed so we don't have to wait for the entire FXG to complete before showing results.

For example, the attack event sequence uses the preamble point like this:
[[File:FxGroup attack timing.png|center|thumb|600x600px|Diagram of how an FxGroup interacts with an attack sequence.]]

* The result of the attack is calculated.
* Attack FXG is started, and the event code halts. (e.g. for the "wind up" to the attack)
* Event code awaits the Preamble to be emitted.
* The result of the attack is shown: miss/hit text, damage popcorn, etc.
* The Target FXG ''also'' begins playing, even though the post-preamble of the attack FXG is still playing at the same time.
* The event code waits for the Target FXG to emit its preamble.
* Game proceeds apace, allowing for the dice rolls and stuff to happen while the Target FXG is still finishing up.

Other abilities may also await for/respond to a Preamble signal separately from the completion of the entire FxGroup, but since they're less standardized it's case-by-case. Only the root FxGroup's preamble affects outside code like this; children FxGroup preambles are only used for internal timings.

=== Complete ===
An FxGroup marks itself as complete when ''both'' all basic effects children (including sounds) and all FxGroup children have marked themselves as complete.

== Useful FXG sub-nodes ==

=== SfxEmitter ===
Plays a sound effect event set up in FMOD. Variations and timing are set up there. You shouldn't need to set any values on these nodes besides which event to play. This does not count as a "basic child", so the FXG will not await this sound completing for the animations.

=== GPUParticles3D ===
Particle emitters! This is a whole thing that might be a bit much to make a written guide on. The important values to set for these are:

* the '''Time''' dropdown (lifetime, explosiveness)
* creating a new '''Process Material''' (emission position and particle movement) with Animation Speed = 1 if you want a spritesheet.
* '''Draw Passes''' > New '''Quadmesh''' for Pass 1 > New '''StandardMaterial3D''' with the static sprite/horizontal single-strip spritesheet in question.

Since particle emitters don't have a reliable "run for this long" mechanism, the length of time particle emitters run for is set by '''Emitter Duration''' on the parent FxGroup node. The emitter will run for that duration then hang out for an extra particle's lifetime before declaring itself finished.

There is also a custom node called '''GpuParticles3DPointing''' that is identical to the basic particles node but it gets angled towards the target of the fx (or the origin, if on the target). Basically a muzzle flare but for particles.

=== BumpNodes / BumpCores ===
[[File:BumpNode.png|thumb|BumpNode in the inspector.]]
BumpNodes directly move or flash mech sprites. BumpCores exist so they can be passed around as resources via code; just create a new one for each BumpNode when creating these via the editor.

You should set up the FXG so only one of these are active at a time; chaining them together is fine, but they'll likely conflict if you have two running at once on the same mech.

The direction of the bump will be provided by the code that calls this. For attacks, this will be the angle from the attacker to the target; to get the attacker to recoil backwards, for example, you'd want to set Angle Offset to 180.

There's currently a default Hit Bump that plays when a mech gets damaged, so don't worry about adding that to each target. I think that default will eventually be superseded by FXGs specific to each damage type in the future.

* '''angle_random''' — Check to ignore Angle Offset and pick a random direction each time get_angle_offset() is called
* '''angle offset''' — direction of the bump in DEGREES (offsets the base_angle given to the BumpNode)
* '''repeats''' — 1 is one-shot
* '''distance''' — how far in world coords to bump them (1.0 = one entire tile)
* '''duration out''' — time to the extent of the bump to the extent
* '''duration in''' — time from the extent of the bump to return to baseline
* '''hold''' — delay at max before returning to baseline
* '''pause''' — delay at baseline before starting the next round
* '''smooth''' — do we pop them to the end point or tween them there
* '''flash color''' — when bumping back, tweens albedo to this color. (1,1,1) is normal, (4,4,4) is a reasonable flash to white.

=== Muzzle Flash ===
[[File:Muzzle Flash.png|center|thumb|571x571px|Muzzle flash node.]]
Extends AnimatedSprite3D for some extra common functionality. This will position itself to:

* be on a plane parallel to the ground
* be on a ring centered on the mech of the given diameter, pointing outwards

It will also run the given animation for the given '''repeats''' before automatically stopping & marking itself as finished.

If you give it additional sprite frames in its '''alternate_sprite_frames''' property, it will randomly shuffle sprite frames after finishing each animation loop (you could have it weigh certain possibilities more heavily by adding them to the array multiple times). The total pool of possible spriteframes is this array + its original '''sprite_frames'''.

You can give a muzzle flash a GPUParticles3D as a child and it will run those particles as one-shots, re-enabling the emitter at the end of each animation loop. You probably want high explosiveness for the emitter to emit a bunch, but be careful to not toggle it back on again before those original particles are gone or no new ones will spawn.

=== AnimatedSprite3D / SpriteFrames ===
''Note: the stock game has moved away from using AnimatedSprite3D nodes, generally opting instead to use a genuine particle system. However, the machinery for these are still in place.''

AnimatedSprite3D is one-shot an out-of-the-box Godot node that will animate a SpriteFrames resource. When the FXG starts, it will cause the AnimatedSprite3D to:

* run its SpriteFrames from the start of the animation
* run the animation a single time before stopping & marking itself as finished.
* fade in from transparency at start and fade out on finish if the parent FXGroup has '''Animated Sprite Fade Time''' set.

FXGs will automatically set the following values on animated sprites, in order to keep things consistent:

* billboard: enabled
* double_sided: disabled
* texture_filter: nearest w/ mipmaps
* render_priority: 1

==== SpriteFrames ====
SpriteFrame resources are created from the FileSystem panel and live next to the spritesheet image asset. They define how a spritesheet should be sliced up into an animation, and are shared across all FXGs that might want to use an AnimatedSprite3D with this animation.

To make a new one, right-click near the spritesheet > Create new > Resource > SpriteFrames, and name it the same thing as the spritesheet png. Double-click the new SpriteFrames file to open up the SpriteFrames editor from the bottom of the screen.

There's a little grid icon underneath the Animation Frames label that you can press to go and open up the spritesheet and set the size an ordering of the of the frames. You may also want to set the FPS of the animations here.

After that, you can use this SpriteFrames resource in any AnimatedSprite3D node!

=== Launched Projectile ===
todo: write docs

=== Arcing Projectile ===
todo: write docs

=== Arcing Sprite ===
todo: write docs

=== Rotating Mesh ===
It spins by some speed and direction endlessly.

=== Controlled Light & Controlled Decal ===
todo: touch grass

File:FxGroup attack timing.png

2026-07-22T22:41:48Z

Olive:

Diagram of how an FxGroup interacts with attack sequences.

File:FxGroup Timing.png

2026-07-22T22:38:33Z

Olive:

Diagram of the timing of an FxGroup over its lifespan.

File:BumpNode.png

2026-07-22T22:36:12Z

Olive:

Example values for a BumpNode

File:Muzzle Flash.png

2026-07-22T22:34:59Z

Olive:

Example of a muzzle flash node.

File:FXG node tree.png

2026-07-22T22:28:32Z

Olive:

Screenshot of an FXG node tree as seen in the editor.

File:FX Group tester.png

2026-07-22T22:26:31Z

Olive:

Screenshot of the FX group tester in FXG mode.

Changes from the TTRPG

2026-07-22T21:07:00Z

Olive: reorganize

While overall Lancer Tactics has been able to stay extremely close to the TTRPG ruleset (you can even import a character made in [https://compcon.app/ COMP/CON]), we've had to make a number of changes for the sake of UX and/or computational ability. The following is a non-exhaustive list.

== Major ==
* Flying is a on/off status that puts you +3 above the surface instead of free elevation control.
* You have two "action points" instead of an explicit quick+quick/full; in practice this ends up being extremely similar to tabletop, minus some restrictions (eg you have more movement flexibility in between your attacks while Barraging). It also locks out being able to attack multiple times with the same weapon via Asura; I'll lose no sleep there.
* We had to limit brace triggering to not prompt-spam you each time you take damage. Currently it gives you the option to brace whenever you'd otherwise be structured/stressed or if would take over half your health in one hit.
* We're using Kai's NPC rebake project instead of the CRB NPCs; this was [https://www.kickstarter.com/projects/wickworks/lancer-tactics/posts/4379409 hotly debated] but through the discussion we decided that it's a dramatic improvement in experience while being a light enough touch that it doesn't compromise tabletop compatibility.

== Minor ==
* We don't enforce the limit of locking pilots to rank 1 talents at LL0, nor the rules for respeccing. RAW they allow a loophole to get rank 3 in a talent at LL1, so are only ever functionally relevant at LL0 and that made it seem not worth enforcing.
* Metahook and similar effects that mirror the duration of statuses only apply the mirrored statuses until the end of that character's next turn.
* Gravity Grenade counts both voluntary and involuntary movement.
* The timing of Ideal Image's systems check happens a lot sooner; before targets are declared.
* Cable Winch can be detached by a hull check instead of that weird attack thing.
* Blademaster's Feint makes you immune to triggering ''all'' reactions from the target until the end of your current turn.

== Trivial ==
* Mirage's Dataveil can't be returned to the Mirage. The AI isn't smart enough to know when it would be a good idea to do so.
* Spector's Machine Pistol only grants extra movement after the attack instead of optionally before.
* Dimensional Emblems can only be quick-action dissipated by hostile characters.
* Autopod and Seismic Deluge only trigger on hostile characters.

Changes from the TTRPG

2026-07-22T21:04:52Z

Olive: /* Major */ Rank 1 talent limitation skip

While overall Lancer Tactics has been able to stay extremely close to the TTRPG ruleset (you can even import a character made in [https://compcon.app/ COMP/CON]), we've had to make a number of changes for the sake of UX and/or computational ability. The following is a non-exhaustive list.

== Major ==
* Flying is a on/off status that puts you +3 above the surface instead of free elevation control.
* You have two "action points" instead of an explicit quick+quick/full; in practice this ends up being extremely similar to tabletop, minus some restrictions (eg you have more movement flexibility in between your attacks while Barraging). It also locks out being able to attack multiple times with the same weapon via Asura; I'll lose no sleep there.
* We had to limit brace triggering to not prompt-spam you each time you take damage. Currently it gives you the option to brace whenever you'd otherwise be structured/stressed or if would take over half your health in one hit.
* We're using Kai's NPC rebake project instead of the CRB NPCs; this was [https://www.kickstarter.com/projects/wickworks/lancer-tactics/posts/4379409 hotly debated] but through the discussion we decided that it's a dramatic improvement in experience while being a light enough touch that it doesn't compromise tabletop compatibility.
* We don't enforce the limit of locking pilots to rank 1 talents at LL0, nor the rules for respeccing. RAW they allow a loophole to get rank 3 in a talent at LL1, so are only ever functionally relevant at LL0 and that made it seem not worth enforcing.

== Minor ==
* Metahook and similar effects that mirror the duration of statuses only apply the mirrored statuses until the end of that character's next turn.
* Gravity Grenade counts both voluntary and involuntary movement.
* The timing of Ideal Image's systems check happens a lot sooner; before targets are declared.
* Cable Winch can be detached by a hull check instead of that weird attack thing.
* Blademaster's Feint makes you immune to triggering ''all'' reactions from the target until the end of your current turn.

== Trivial ==
* Mirage's Dataveil can't be returned to the Mirage. The AI isn't smart enough to know when it would be a good idea to do so.
* Spector's Machine Pistol only grants extra movement after the attack instead of optionally before.
* Dimensional Emblems can only be quick-action dissipated by hostile characters.
* Autopod and Seismic Deluge only trigger on hostile characters.

Pixel Art

2026-07-22T16:32:14Z

Olive: Added link to color palette for photoshop

== Portrait Slices ==
* Portraits are made by lining up a bunch of portraits in order, kind of like a complicated sandwich. These are called slices.
* Slices are just PNGs arranged in the right folder (corresponding to the Slice Type).
* Some slice types can accommodate front and back, but at minimum they need a base
** eg: in the <code>hair/</code> folder, we can put <code>bowlcut.png</code>. We could also put <code>bowlcut_front.png</code> and/or <code>bowlcut_back.png</code>
** but in the above example, we still need <code>bowlcut.png</code>, even if it's a blank image
* all slices are 128 x 128px. You aren't guaranteed to see the top or the sides of this, depending on where the portrait is being displayed
* slices are displayed in the following order (subject to change)

clothing_outer_back
accessory_jewelry_bac
clothing_inner_back
accessory_scarves_back
accessory_hair_back
hair_back
body
body_extra
clothing_inner
clothing_outer
head
ears
eyes_back
eyes
eyebrows
nose_back
mouth_bac
face_extra
mouth
mustache
eyes_front
nose
accessory_jewelry
accessory_other
beard
mouth_front
accessory_scarves
hair
accessory_hair
accessory_glasses
hair_front
accessory_hair_front
accessory_other_front
accessory_jewelry_front
accessory_scarves_front

== RGB Color System ==
The other main thing that define our portrait maker is that we dynamically recolor the image in a specific way. The important part to know is that you need to make your slices with very specific colors:

* Magenta (#FF00FF) is used as a "mask", covering up lower layers for slice types set up to do so (e.g. hats cover up hair at all pixels marked with magenta on the hat slice)

* Red, Green, and Blue are our "primary", "seconday", and "tertiary" colors. The easiest way to know which color is being used is to copy another slice in the same category.

* Specific colors map to specific indexes in our 7-color "color ramps", that the user selects in-game. To be recolored, the pixel needs to be an '''exact''' match to one of these values.

Index Reds Greens Blues
1 #ff0000 #00ff00 #0000ff
2 #dd0000 #00dd00 #0000dd
*3 #bb0000 #00bb00 #0000bb
4 #990000 #009900 #000099
5 #770000 #007700 #000077
6 #550000 #005500 #000055
7 #330000 #003300 #000033

* NOTE: Artistically, we're using index 3 as the "base color" for that entire ramp (not index 4).

=== Resources ===
* Photoshop color palette: [[File:Photoshop_recoloring_pallete.act]]

File:Photoshop recoloring pallete.act

2026-07-22T16:30:58Z

Olive: Color table for the pixels that get recolored by Lancer Tactics.

== Summary ==
Color table for the pixels that get recolored by Lancer Tactics.

The Muse

2026-07-22T16:23:31Z

Olive: /* Modding */

The Muse (aka the Lancer Tactics Wiki) is a compilation of editor documentation and guides for [https://lancertactics.com/ Lancer Tactics], a video game adaptation of the [https://massifpress.com/lancer Lancer TTRPG] by Tom Bloom and Miguel Lopez-Hall. The in-universe concept of the Muse is from the [https://vexwerewolf.itch.io/in-golden-flame-act-1 In Golden Flame] module by Vex Werewolf.

== Modding ==
* [[Modding EULA]]
* [[Modding|Introduction to modding]]
* [[Modding Cookbook]]
* [[Basic Troubleshooting]]
* [[Pixel Art]]

== Editors ==
* [[Module Editor]]
* [[Combat Editor Cookbook]]

== Other ==
* [[Changes from the TTRPG]]

== External Links & Resources ==
* [https://wick.works/devlog/category/lancer-tactics Devlog at wick.works]
* [https://discord.com/invite/2t7Efg2Fbj Lancer Tactics Discord]
* [https://wick.itch.io/lancer-tactics/community itch.io forums]
* [https://wick.itch.io/lancer-tactics itch.io store page]
* [https://store.steampowered.com/app/4049810/Lancer_Tactics/ Wishlist on Steam]
* [https://mod.io/g/lancer-tactics Lancer Tactics on mod.io]
* [https://compcon.app/ COMP/CON]

''Lancer Tactics is not an official Lancer product; it is a third party work, and is not affiliated with Massif Press. Lancer Tactics is published via the Lancer Third Party License. Lancer is copyright Massif Press.''

Pixel Art

2026-07-22T16:22:59Z

Olive: copied in carpenter's pixel art guide from discord

Pixel Art

2026-07-13T22:56:40Z

Olive: /* Portrait Slices */

== Portrait Slices ==
* Portraits are made by lining up a bunch of portraits in order, kind of like a complicated sandwich. These are called slices.
* Slices are just PNGs arranged in the right folder (corresponding to the Slice Type).
* Some slice types can accommodate front and back, but at minimum they need a base
** eg: in the `hair/` folder, we can put `bowlcut.png`. We could also put `bowlcut_front.png` and/or `bowlcut_back.png`
** but in the above the example, we *need* `bowlcut.png`, even if it's a blank image
* all slices are 128 x 128px. You aren't guaranteed to see the top or the sides of this, depending on where the portrait is being displayed
* slices are displayed in the following order (subject to change)

ZCAT.clothing_outer_back: 15,
ZCAT.accessory_jewelry_back:17,
ZCAT.clothing_inner_back: 20,
ZCAT.accessory_scarves_back: 25,
ZCAT.accessory_hair_back: 29,
ZCAT.hair_back: 30,
ZCAT.body: 50,
ZCAT.body_extra: 51,
ZCAT.clothing_inner: 55,
ZCAT.clothing_outer: 59,
ZCAT.head: 60,
ZCAT.ears: 63,
ZCAT.eyes_back: 65,
ZCAT.eyes: 66,
ZCAT.eyebrows: 67,
ZCAT.nose_back: 68,
ZCAT.mouth_back:69,
ZCAT.face_extra: 71,
ZCAT.mouth: 72,
ZCAT.mustache: 73,
ZCAT.eyes_front: 76,
ZCAT.nose: 77,
ZCAT.accessory_jewelry: 80,
ZCAT.accessory_other: 81,
ZCAT.beard: 86,
ZCAT.mouth_front: 87,
ZCAT.accessory_scarves: 89,
ZCAT.hair: 90,
ZCAT.accessory_hair: 91,
ZCAT.accessory_glasses: 92,
ZCAT.hair_front: 94,
ZCAT.accessory_hair_front: 95,
ZCAT.accessory_other_front: 96,
ZCAT.accessory_jewelry_front: 97,
ZCAT.accessory_scarves_front: 99,

== RGB Color System ==
* The other main thing that define our portrait maker is that we dynamically recolor the image in a specific way. The important part to know is that you need to make your slices with very specific colors

* Magenta (#FF00FF) is used as a "mask", covering up parts of other slices, sometimes

* Red, Green, and Blue are our "primary", "seconday", and "tertiary" colors. The easiest way to know which color is being used is to copy another slice in the same category.

* Specific colors map to specific indexes in our 7-color "color ramps", that the user selects in-game

Index Reds Greens Blues
1 #ff0000 #00ff00 #0000ff
2 #dd0000 #00dd00 #0000dd
*3 #bb0000 #00bb00 #0000bb
4 #990000 #009900 #000099
5 #770000 #007700 #000077
6 #550000 #005500 #000055
7 #330000 #003300 #000033

* NOTE: it's extremely important you use ''exactly'' the color above. At this point #222200 doesn't map to anything (though it may in the future "blend" the two colors together). And #210000 also doesn't map to anything

* NOTE: Index 3 is important, because that's the "base color" for that entire ramp (not index 4). Not all of the slices currently respect this, but they will. eventually

Pixel Art

2026-07-13T22:46:28Z

Olive: /* RGB Color System */

== Portrait Slices ==
- First and foremost, our portraits are made by lining up a bunch of portraits in order, kind of like a complicated sandwich. These are called **slices**
* Slices are just PNGs arranged in the right folder (corresponding to the **Slice Type**).
* Some slice types can accommodate front and back, but at minimum they need a base
** eg: in the `hair/` folder, we can put `bowlcut.png`. We could also put `bowlcut_front.png` and/or `bowlcut_back.png`
** but in the above the example, we *need* `bowlcut.png`, even if it's a blank image
* all slices are 128 x 128px. You aren't guaranteed to see the top or the sides of this, depending on where the portrait is being displayed
* slices are displayed in the following order (subject to change)

ZCAT.clothing_outer_back: 15,
ZCAT.accessory_jewelry_back:17,
ZCAT.clothing_inner_back: 20,
ZCAT.accessory_scarves_back: 25,
ZCAT.accessory_hair_back: 29,
ZCAT.hair_back: 30,
ZCAT.body: 50,
ZCAT.body_extra: 51,
ZCAT.clothing_inner: 55,
ZCAT.clothing_outer: 59,
ZCAT.head: 60,
ZCAT.ears: 63,
ZCAT.eyes_back: 65,
ZCAT.eyes: 66,
ZCAT.eyebrows: 67,
ZCAT.nose_back: 68,
ZCAT.mouth_back:69,
ZCAT.face_extra: 71,
ZCAT.mouth: 72,
ZCAT.mustache: 73,
ZCAT.eyes_front: 76,
ZCAT.nose: 77,
ZCAT.accessory_jewelry: 80,
ZCAT.accessory_other: 81,
ZCAT.beard: 86,
ZCAT.mouth_front: 87,
ZCAT.accessory_scarves: 89,
ZCAT.hair: 90,
ZCAT.accessory_hair: 91,
ZCAT.accessory_glasses: 92,
ZCAT.hair_front: 94,
ZCAT.accessory_hair_front: 95,
ZCAT.accessory_other_front: 96,
ZCAT.accessory_jewelry_front: 97,
ZCAT.accessory_scarves_front: 99,

== RGB Color System ==
* The other main thing that define our portrait maker is that we dynamically recolor the image in a specific way. The important part to know is that you need to make your slices with very specific colors

* Magenta (#FF00FF) is used as a "mask", covering up parts of other slices, sometimes

* Red, Green, and Blue are our "primary", "seconday", and "tertiary" colors. The easiest way to know which color is being used is to copy another slice in the same category.

* Specific colors map to specific indexes in our 7-color "color ramps", that the user selects in-game

Index Reds Greens Blues
1 #ff0000 #00ff00 #0000ff
2 #dd0000 #00dd00 #0000dd
*3 #bb0000 #00bb00 #0000bb
4 #990000 #009900 #000099
5 #770000 #007700 #000077
6 #550000 #005500 #000055
7 #330000 #003300 #000033

* NOTE: it's extremely important you use ''exactly'' the color above. At this point #222200 doesn't map to anything (though it may in the future "blend" the two colors together). And #210000 also doesn't map to anything

* NOTE: Index 3 is important, because that's the "base color" for that entire ramp (not index 4). Not all of the slices currently respect this, but they will. eventually

Pixel Art

2026-07-13T22:44:17Z

Olive: copied in color system

== RGB Color System ==
* The other main thing that define our portrait maker is that we dynamically recolor the image in a specific way. The important part to know is that you need to make your slices with very specific colors

* Magenta (#FF00FF) is used as a "mask", covering up parts of other slices, sometimes

* Red, Green, and Blue are our "primary", "seconday", and "tertiary" colors. The easiest way to know which color is being used is to copy another slice in the same category.

* Specific colors map to specific indexes in our 7-color "color ramps", that the user selects in-game

Index Reds Greens Blues
1 #ff0000 #00ff00 #0000ff
2 #dd0000 #00dd00 #0000dd
*3 #bb0000 #00bb00 #0000bb
4 #990000 #009900 #000099
5 #770000 #007700 #000077
6 #550000 #005500 #000055
7 #330000 #003300 #000033

* NOTE: it's extremely important you use ''exactly'' the color above. At this point #222200 doesn't map to anything (though it may in the future "blend" the two colors together). And #210000 also doesn't map to anything

* NOTE: Index 3 is important, because that's the "base color" for that entire ramp (not index 4). Not all of the slices currently respect this, but they will. eventually

The Muse

2026-07-12T01:36:22Z

Olive: /* Editors */

The Muse (aka the Lancer Tactics Wiki) is a compilation of editor documentation and guides for [https://lancertactics.com/ Lancer Tactics], a video game adaptation of the [https://massifpress.com/lancer Lancer TTRPG] by Tom Bloom and Miguel Lopez-Hall. The in-universe concept of the Muse is from the [https://vexwerewolf.itch.io/in-golden-flame-act-1 In Golden Flame] module by Vex Werewolf.

== Modding ==
* [[Modding EULA]]
* [[Modding|Introduction to modding]]
* [[Modding Cookbook]]

== Editors ==
* [[Module Editor]]
* [[Combat Editor Cookbook]]

== Other ==
* [[Changes from the TTRPG]]

== External Links & Resources ==
* [https://wick.works/devlog/category/lancer-tactics Devlog at wick.works]
* [https://discord.com/invite/2t7Efg2Fbj Lancer Tactics Discord]
* [https://wick.itch.io/lancer-tactics/community itch.io forums]
* [https://wick.itch.io/lancer-tactics itch.io store page]
* [https://store.steampowered.com/app/4049810/Lancer_Tactics/ Wishlist on Steam]
* [https://mod.io/g/lancer-tactics Lancer Tactics on mod.io]
* [https://compcon.app/ COMP/CON]

''Lancer Tactics is not an official Lancer product; it is a third party work, and is not affiliated with Massif Press. Lancer Tactics is published via the Lancer Third Party License. Lancer is copyright Massif Press.''

Combat Editor Cookbook

2026-07-12T01:34:38Z

Olive: initial commit

Here are some common patterns for triggers in the [[Combat Editor]].

Other good ways to learn:
* You can inspect the triggers used for all the stock sitreps through the Edit Sitreps button at the bottom of the Triggers tab & adding them to your combat.
* You can open the Tutorial by pressing Open → Stock → tutorial in the Combat Editor. It's a good example of a fairly complex scenario choreography managed via triggers.

== Deploy PCs at start of combat ==

'''[ Combat start ]'''

''Effects:''
; Play combat intro banner
: (optional) Plays a UI animation announcing what, where, and who will be involved in this upcoming combat.

; Deploy lancers
: Then pick the zone or zones that you want the player to be able to arrange their Lancers in.

== Deploy the OpFor at start of round 1 ==

'''[ Round started ]'''

''Conditions:''
; Round count - is - Number
: Check if the current round count is 1. You can omit this condition if you instead want additional reinforcements to be deployed every round; unless "can re-deploy units" is checked in the event, once all units have been deployed from the group it will stop deploying new ones.

''Effects:''
; Deploy Reinforcements
: Pick how many reinforcements you want. What reinforcements to spawn are indicated via <code>String: Specific Reinforcement Group</code>, the list of which is populated in the Units tab (you'll have to make a new Group).
: You can also enter the magic string "Reserves" to use the OpFor defined on the Instant Action screen, if you'll be playing the combat through that.
: There's a good number of flags for this event. Some of the more useful ones:

*; Extend or shrink to match sitrep
*: If the provided reinforcement group doesn't meet the recommended size requirement for the number of Lancers (e.g. 2 normal NPCs per PC) the group will have additional units added or be shrunk to try and match the recommended number of NPCs.

*; Cap maximum NPC activations
*: If the current number of NPCs on the field already dramatically exceed the number of PCs, this will prevent additional NPCs from spawning in this round. The limits are, for PC:NPC → 1:2, 2:3, 3:5, and 4:6.

*; Maintain minimum Opfor rating
*: If the PCs are wiping the floor with the Opfor and have prematurely cleared the field, this will spawn additional NPCs from the reserve group (if available) this round. The recommended ratings are, for PC:NPC and a normal NPC being worth .5 → 1:0.5, 2:1.5, 3:2.5, 4:3.5

The Muse

2026-07-12T00:43:54Z

Olive:

The Muse (aka the Lancer Tactics Wiki) is a compilation of editor documentation and guides for [https://lancertactics.com/ Lancer Tactics], a video game adaptation of the [https://massifpress.com/lancer Lancer TTRPG] by Tom Bloom and Miguel Lopez-Hall. The in-universe concept of the Muse is from the [https://vexwerewolf.itch.io/in-golden-flame-act-1 In Golden Flame] module by Vex Werewolf.

== Modding ==
* [[Modding EULA]]
* [[Modding|Introduction to modding]]
* [[Modding Cookbook]]

== Editors ==
* [[Module Editor]]

== Other ==
* [[Changes from the TTRPG]]

== External Links & Resources ==
* [https://wick.works/devlog/category/lancer-tactics Devlog at wick.works]
* [https://discord.com/invite/2t7Efg2Fbj Lancer Tactics Discord]
* [https://wick.itch.io/lancer-tactics/community itch.io forums]
* [https://wick.itch.io/lancer-tactics itch.io store page]
* [https://store.steampowered.com/app/4049810/Lancer_Tactics/ Wishlist on Steam]
* [https://mod.io/g/lancer-tactics Lancer Tactics on mod.io]
* [https://compcon.app/ COMP/CON]

''Lancer Tactics is not an official Lancer product; it is a third party work, and is not affiliated with Massif Press. Lancer Tactics is published via the Lancer Third Party License. Lancer is copyright Massif Press.''

Module Editor

2026-07-12T00:42:37Z

Olive:

[[File:ModuleEditorBeats.png|thumb]]

The Module Editor is a tool for adding downtime scenes between combats.

A player is always within exactly one active Beat, which itself can contain one or more Moments. Beats are like a room and Moments are like the things you can do in that room.

== Beats ==

Beats determine what the player can do with the Lancers character-sheet-wise whenever another Moment isn't currently active. The available values:
; Hidden
: All Lancers are hidden. The player cannot open characters sheets or see who's in the current party.
; None
: The player can inspect character sheets, but not spend repairs or otherwise modify their Lancers.
; Short repair
: The player can spend repairs to restore Structure/Stress or destroyed systems and mechs, but not modify their current loadout.
; Full repair
: All stats are restored to full and the player is free to modify loadouts.
; Level up
: On entering this beat for the first time, all Lancers increase in License Level. Otherwise acts as a full repair.

== Moments ==

The current Moment types are:
; Combat Briefing
: Shows a preview of a combat with any available sitrep and map information. Players can press Launch to start the combat. There's also a checkbox to skip the briefing screen and jump straight into the combat as soon as this Moment becomes active.
; Exposition
: A flexible text box, optional image media, and player choices.
; Dialogue
: Runs a cutscene of characters speaking to each other, defined in the Conversation tool.
; Branch
: Automatically proceeds to one of two connected Moments depending on whether its condition returns true/false.
; Signal receiver
: Immediately becomes the active Moment when a Trigger emits a matching module signal effect and proceeds to whatever it's connected to.
; Trigger
: Runs some number of effects (as long as its conditions are met) and proceeds to whatever it's connected to. The interface for defining trigger conditions and effects is the same as in the Combat Editor but the list of what effects are available is different.

== Media ==

When a UI element needs to display a player-defined image, it does so through a Media picker.

The current Media types are:
; PNG
: An arbitrary static image. Players can place .png files in the media/ folder within their module folder.
; Diorama
: A miniature map, created in a feature-reduced version of the combat editor.
; Mech
: The image of a mech from a module origin character or NPC.
; Pilot
: The image of one of the player's character portraits.
; NPC
: The image of one of the module NPC portraits.

=== Backgrounds ===
''Available media types: PNG, Diorama, Combat''

Beats and Moments can specify a Background Media, which underlays all the downtime UI and buttons. Unless an active Moment specifies otherwise, a Beat determines the current Background.

Currently, only .png filenames that begin with the text "bg_" will show up and be available for backgrounds. (This is likely to change.) Backgrounds are recommended to be at least 1280x720 or a lower multiple with the same ratio.

=== Handouts ===
[[File:ExpositionMedia.png|thumb|Example of an Exposition Moment screen with a Diorama provided as the Handout Media. ]]

''Available media types: Any''

Exposition moments can specify a Handout Media which shows up alongside the text.

Handout images will be rendered at a maximum of 512x512

=== Banner ===
[[File:Custom_Module_Banner.png|thumb|Example view of the screen where you pick what module to play, showing the description and banner. ]]

''Available media types: PNG''

Shown above your module description when picking what module to play. The required dimensions or format of module banners may change in the future.

Currently, only .png filenames that begin with the text "banner_" will show up and be available for banners.

Module Editor

2026-07-12T00:41:53Z

Olive:

DRAFT DRAFT DRAFT

[[File:ModuleEditorBeats.png|thumb]]

The Module Editor is a tool for adding downtime scenes between combats.

A player is always within exactly one active Beat, which itself can contain one or more Moments. Beats are like a room and Moments are like the things you can do in that room.

== Beats ==

Beats determine what the player can do with the Lancers character-sheet-wise whenever another Moment isn't currently active. The available values:
; Hidden
: All Lancers are hidden. The player cannot open characters sheets or see who's in the current party.
; None
: The player can inspect character sheets, but not spend repairs or otherwise modify their Lancers.
; Short repair
: The player can spend repairs to restore Structure/Stress or destroyed systems and mechs, but not modify their current loadout.
; Full repair
: All stats are restored to full and the player is free to modify loadouts.
; Level up
: On entering this beat for the first time, all Lancers increase in License Level. Otherwise acts as a full repair.

== Moments ==

The current Moment types are:
; Combat Briefing
: Shows a preview of a combat with any available sitrep and map information. Players can press Launch to start the combat. There's also a checkbox to skip the briefing screen and jump straight into the combat as soon as this Moment becomes active.
; Exposition
: A flexible text box, optional image media, and player choices.
; Dialogue
: Runs a cutscene of characters speaking to each other, defined in the Conversation tool.
; Branch
: Automatically proceeds to one of two connected Moments depending on whether its condition returns true/false.
; Signal receiver
: Immediately becomes the active Moment when a Trigger emits a matching module signal effect and proceeds to whatever it's connected to.
; Trigger
: Runs some number of effects (as long as its conditions are met) and proceeds to whatever it's connected to. The interface for defining trigger conditions and effects is the same as in the Combat Editor but the list of what effects are available is different.

== Media ==

When a UI element needs to display a player-defined image, it does so through a Media picker.

The current Media types are:
; PNG
: An arbitrary static image. Players can place .png files in the media/ folder within their module folder.
; Diorama
: A miniature map, created in a feature-reduced version of the combat editor.
; Mech
: The image of a mech from a module origin character or NPC.
; Pilot
: The image of one of the player's character portraits.
; NPC
: The image of one of the module NPC portraits.

=== Backgrounds ===
''Available media types: PNG, Diorama, Combat''

Beats and Moments can specify a Background Media, which underlays all the downtime UI and buttons. Unless an active Moment specifies otherwise, a Beat determines the current Background.

Currently, only .png filenames that begin with the text "bg_" will show up and be available for backgrounds. (This is likely to change.) Backgrounds are recommended to be at least 1280x720 or a lower multiple with the same ratio.

=== Handouts ===
[[File:ExpositionMedia.png|thumb|Example of an Exposition Moment screen with a Diorama provided as the Handout Media. ]]

''Available media types: Any''

Exposition moments can specify a Handout Media which shows up alongside the text.

Handout images will be rendered at a maximum of 512x512

=== Banner ===
[[File:Custom_Module_Banner.png|thumb|Example view of the screen where you pick what module to play, showing the description and banner. ]]

''Available media types: PNG''

Shown above your module description when picking what module to play. The required dimensions or format of module banners may change in the future.

Currently, only .png filenames that begin with the text "banner_" will show up and be available for banners.

Module Editor

2026-07-12T00:41:26Z

Olive:

DRAFT DRAFT DRAFT

[[File:ModuleEditorBeats.png|thumb]]

The Module Editor is a tool for adding downtime scenes between combats.

A player is always within exactly one active Beat, which itself can contain one or more Moments. Beats are like a room and Moments are like the things you can do in that room.

== Beats ==

Beats determine what the player can do with the Lancers character-sheet-wise whenever another Moment isn't currently active. The available values:
; Hidden
: All Lancers are hidden. The player cannot open characters sheets or see who's in the current party.
; None
: The player can inspect character sheets, but not spend repairs or otherwise modify their Lancers.
; Short repair
: The player can spend repairs to restore Structure/Stress or destroyed systems and mechs, but not modify their current loadout.
; Full repair
: All stats are restored to full and the player is free to modify loadouts.
; Level up
: On entering this beat for the first time, all Lancers increase in License Level. Otherwise acts as a full repair.

== Moments ==

The current Moment types are:
; Combat Briefing
: Shows a preview of a combat with any available sitrep and map information. Players can press Launch to start the combat. There's also a checkbox to skip the briefing screen and jump straight into the combat as soon as this Moment becomes active.
; Exposition
: A flexible text box, optional image media, and player choices.
; Dialogue
: Runs a cutscene of characters speaking to each other, defined in the Conversation tool.
; Branch
: Automatically proceeds to one of two connected Moments depending on whether its condition returns true/false.
; Signal receiver
: Immediately becomes the active Moment when a Trigger emits a matching module signal effect and proceeds to whatever it's connected to.
; Trigger
: runs some number of effects (as long as its conditions are met) and proceeds to whatever it's connected to. The interface for defining trigger conditions and effects is the same as in the Combat Editor but the list of what effects are available is different.

== Media ==

When a UI element needs to display a player-defined image, it does so through a Media picker.

The current Media types are:
; PNG
: An arbitrary static image. Players can place .png files in the media/ folder within their module folder.
; Diorama
: A miniature map, created in a feature-reduced version of the combat editor.
; Mech
: The image of a mech from a module origin character or NPC.
; Pilot
: The image of one of the player's character portraits.
; NPC
: The image of one of the module NPC portraits.

=== Backgrounds ===
''Available media types: PNG, Diorama, Combat''

Beats and Moments can specify a Background Media, which underlays all the downtime UI and buttons. Unless an active Moment specifies otherwise, a Beat determines the current Background.

Currently, only .png filenames that begin with the text "bg_" will show up and be available for backgrounds. (This is likely to change.) Backgrounds are recommended to be at least 1280x720 or a lower multiple with the same ratio.

=== Handouts ===
[[File:ExpositionMedia.png|thumb|Example of an Exposition Moment screen with a Diorama provided as the Handout Media. ]]

''Available media types: Any''

Exposition moments can specify a Handout Media which shows up alongside the text.

Handout images will be rendered at a maximum of 512x512

=== Banner ===
[[File:Custom_Module_Banner.png|thumb|Example view of the screen where you pick what module to play, showing the description and banner. ]]

''Available media types: PNG''

Shown above your module description when picking what module to play. The required dimensions or format of module banners may change in the future.

Currently, only .png filenames that begin with the text "banner_" will show up and be available for banners.

Module Editor

2026-07-12T00:38:07Z

Olive:

DRAFT DRAFT DRAFT

[[File:ModuleEditorBeats.png|thumb]]

The Module Editor is a tool for adding downtime scenes between combats.

A player is always within exactly one active Beat, which itself can contain one or more Moments. Beats are like a room and Moments are like the things you can do in that room.

== Beats ==

Beats determine what the player can do with the Lancers character-sheet-wise whenever another Moment isn't currently active. The available values:
; Hidden
: All Lancers are hidden. The player cannot open characters sheets or see who's in the current party.
; None
: The player can inspect character sheets, but not spend repairs or otherwise modify their Lancers.
; Short repair
: The player can spend repairs to restore Structure/Stress or destroyed systems and mechs, but not modify their current loadout.
; Full repair
: All stats are restored to full and the player is free to modify loadouts.
; Level up
: On entering this beat for the first time, all Lancers increase in License Level. Otherwise acts as a full repair.

== Moments ==

The current Moment types are:

; Combat Briefing
: Shows a preview of a combat with any available sitrep and map information. Players can press Launch to start the combat. There's also a checkbox to skip the briefing screen and jump straight into the combat as soon as this Moment becomes active.

; Exposition
: A flexible text box, optional image media, and player choices.

; Dialogue
: Runs a cutscene of characters speaking to each other, defined in the Conversation tool.

; Branch
: Automatically proceeds to one of two connected Moments depending on whether its condition returns true/false.

; Signal receiver
: Immediately becomes the active Moment when a Trigger emits a matching module signal effect and proceeds to whatever it's connected to.

; Trigger
: runs some number of effects (as long as its conditions are met) and proceeds to whatever it's connected to. The interface for defining trigger conditions and effects is the same as in the Combat Editor but the list of what effects are available is different.

== Media ==

When a UI element needs to display a player-defined image, it does so through a Media picker.

The current Media types are:

; PNG
: An arbitrary static image. Players can place .png files in the media/ folder within their module folder.

; Diorama
: A miniature map, created in a feature-reduced version of the combat editor.

; Mech
: The image of a mech from a module origin character or NPC.

; Pilot
: The image of one of the player's character portraits.

; NPC
: The image of one of the module NPC portraits.

=== Backgrounds ===
''Available media types: PNG, Diorama, Combat''

Beats and Moments can specify a Background Media, which underlays all the downtime UI and buttons. Unless an active Moment specifies otherwise, a Beat determines the current Background.

Currently, only .png filenames that begin with the text "bg_" will show up and be available for backgrounds. (This is likely to change.) Backgrounds are recommended to be at least 1280x720 or a lower multiple with the same ratio.

TODO: EXAMPLE SCREENSHOT

=== Handouts ===
[[File:ExpositionMedia.png|thumb|Example of an Exposition Moment screen with a Diorama provided as the Handout Media. ]]
''Available media types: Any''

Exposition moments can specify a Handout Media which shows up alongside the text.

Handout images will be rendered at a maximum of 512x512

TODO: EXAMPLE SCREENSHOT

=== Banner ===
[[File:Custom_Module_Banner.png|thumb|Example view of the screen where you pick what module to play, showing the description and banner. ]]

''Available media types: PNG''

Shown above your module description when picking what module to play. The required dimensions or format of module banners may change in the future.

Currently, only .png filenames that begin with the text "banner_" will show up and be available for banners.

File:ExpositionMedia.png

2026-07-12T00:35:08Z

Olive: Example of an Exposition Moment screen with a Diorama provided as the Handout Media.

== Summary ==
Example of an Exposition Moment screen with a Diorama provided as the Handout Media.

File:Custom Module Banner.png

2026-07-12T00:34:31Z

Olive:

Example view of the screen where you pick what module to play, showing the description and banner.

File:Custom Module Banner.png

2026-07-12T00:30:27Z

Olive:

Module Editor

2026-07-11T00:20:26Z

Olive:

Modding

2026-07-06T03:01:40Z

Olive: use definitions instead of lists

Get help at [https://wick.itch.io/lancer-tactics/community wick.itch.io/lancer-tactics] or [https://discord.com/invite/2t7Efg2Fbj Discord]

== Modkit ==

To make mods, you'll first need to get your hands on the source of the game. It’s possible to decompile any game made in Godot which is what bootleg (affectionate) modders have been doing up til now, but we’re making the source available through official channels for convenience. Lancer’s TTRPG creator ecosystem is based on a belief that it should be hackable & extensible, and we want to carry that culture forward.

We (Wickworks) are talking to a lawyer to make sure we have all our hatches buttoned down legally to make sure we maintain ownership of the game code itself (and maybe like watermark some assets?), but once we get that squared away we’ll add the modkit alongside the rest of the downloads on itch. Until then, you can request early access to it on [https://discord.com/invite/2t7Efg2Fbj Lancer Tactic’s Discord server].

Finally, before getting started with the modkit, please be sure you've reviewed and agree to the [[Modding EULA]].

== Background — how do Godot mods work? ==

Lancer Tactics is made in the [https://godotengine.org/ Godot] game engine; at time of writing on version 4.7. In order to make mods for anything besides asset packs, you'll need to become comfortable working in its editor. I hope this doesn't scare you off; of all the major game engines, it has a reputation of being easy to pick up.

Godot projects have an internal filesystem much like the one on your computer; a series of folders and files. The root is referred to as <code>res://</code>

[[File:Godot_filesystem.png]]

However, to run the game Godot needs assets (images, music, etc) to be in a different format than you’d find with them sitting in your filesystem. It compiles these files into a big pile of files that look like this, all jumbled together in one folder.

[[File:Mod_background_imports.png|thumb|A scattering of processed image files from Godot's .import folder. ]]

To keep knowing where things are, it maintains a skeleton of the original filesystem with all the orignal files swapped out with “.remap” placeholders that just point to where in that big pile the asset they represent went. Furthermore, whenever the game attempts to load a specific asset at a location (e.g. <code>res://assets/icons/mech.svg</code>), it caches whatever it loaded into memory. Whenever we ask it to load that asset again, it doesn’t have to go ask the .remap file where the original one went and load it up — it just returns whatever it ended up loading from there last time. This cache is like a ghost sitting on top of a skeleton.

For modding, this gives us an opportunity. Instead of needing to actually copy in modded files and override the originals, we can manipulate this ghost-filesystem-cache by lying about what files are at what locations. Here’s what a mod looks like for Lancer Tactics (using a modified system from Godot Mod Loader):

[[File:ModBackgroundUnpacked.png]]

We have a special folder where we put the actual mod files: “unpacked”, then another folder with the specific mod’s identifier “Wickworks-Sawhorse”. Within that, we have a “res” folder, and that’s where the lying starts. When loading up the mod, we can grab everything inside of the mod’s “res” and tell the ghost-cache that the mod’s files are the ones that are actually at that location. In this example, by the end of it when we ask Godot to load <code>res://assets/frames/horus/mf_sawhorse.png</code>, it will return the file that’s actually over in <code>res://unpacked/Wickworks-Sawhorse/res/assets/frames/horus/mf_sawhorse.png</code>.

Now that we have the power to insert files as we’d like, Godot Mod Loader additionally has some functions that through dark magic allows multiple mods to all alter the same script instead of overriding it. I’m a little fuzzy on these details, but the shape of it is that while loading each successive script that extends the same file actually extends the previous one that also extended that script so all the changes end up getting applied.

In order to change what mods are active, the out-of-the-box Godot Mod Loader addon expects you to restart the game so it can start work with a clean slate each time. For Lancer Tactics, I modified this so it tracks all files inserted so we can go and undo all of our lies and reset the ghost-cache to files’ original locations. This was important because I’m expecting people to want to be able to make maps and modules with bundled-in mods that substantially alter the content of the game, and requiring a restart whenever you load one up would be a terrible experience.

== Mod Loader ==
Lancer Tactics is using the [https://wiki.godotmodding.com/ Godot Mod Loader addon], but has made some changes to it:

=== Implicit Overrides ===
Instead of having to manually declare each asset you want to override in code (via an overwrites.gd that the Mod Tools would generate and put into an extensions/ or overwrites/ sub-directory), assets and resources are overridden implicitly by matching file paths and names from a mod's res/ directory. See [[Modding Cookbook#Replacing Resources|replacing resources]] for details. This should allow people to make texture asset pack mods fully outside the Godot editor by downloading a template, dropping images into a folder, and zipping it up.

=== Hooks and class_name scripts ===
Unfortunately, it ended up not being feasible to support their script Hook system, which means it's not possible to change class_name scripts (or is unreliable to do so). Hooks were designed to work around a bug in Godot that has been unaddressed since 4.3 and do some crazy preprocessing of scripts that involves decompiling them, editing names of functions, and swapping in the copies. For the time being, we decided to instead convert the most likely targets of mods (UnitCondition, UnitTile, UnitAction, etc) into autoloads so they can be accessed by normal script Extensions instead. This will provide better backwards compatibility for mods once the bug is addressed than having to go back and tear out all the Hook code.

TL;DR: You are NOT able to currently extend a script with a class_name. If you want to make a mod that extends a class_name script and it looks like it could be an Autoload, let me know and I'll see if I can convert it!

The engine bug necessitating hooks: [https://github.com/godotengine/godot/issues/83542 github.com/godotengine/godot/issues/83542]

A possible fix to the godot engine that'll solve all this: [https://github.com/godotengine/godot/pull/116556 github.com/godotengine/godot/pull/116556]

=== Formatting and Paths ===
Additionally, we've made some path and formatting tweaks for styling and ease of use:

* We're using <code>res://unpacked/</code> instead of <code>res://mods-unpacked/</code> for the directory in the godot project that mods are unpacked into. I don't like hypens in filenames, it's a bit shorter, and will be sorted alphabetically to the end of the project folders. Plus mod zips will be structured like <code>unpacked/Author-ModName/manifest.json</code> which is a bit cleaner than having an extra "mods-" at the start of it.

* Our manifest.json doesn't have the <code>"extra": {"godot: {...}}</code> keys, opting instead to just put all that stuff at the root.

* Mod config files are stored in <code>user://mod_configs/</code> instead of straight <code>user://</code> for mod-tool-plugin-save.json, mod_user_profiles.json, and mod_loader_cache.json. Keeps the user directory cleaner.

== Mod Types & Security ==

Mods are code that some rando wrote that the game downloads and then runs on your machine. Godot does not have built-in sandboxing for gdscript, so this code has just as much access as the game does, ie, can read or write any file on your computer and talk to the internet. Uh oh!

To be fair, this is a issue with most mods for most games. It’s a very trust-based at-your-own-risk sort of country. This is fine if mods aren’t tightly integrated, but as soon as you as a developer start removing barriers and letting people accidentally stumble into downloading harmful code by just pressing buttons in-game, you start taking on the responsibility in the case of something bad happening.

Slay The Spire 2, another game made in Godot, handles this by putting a big warning screen that it forces you to click through before you can start installing mods. We’ve done something similar:

'''TODO INSERT IMAGE'''

To help manage this, Lancer Tactics distinguishes between three mod types:

; Asset Pack
: Just images and tres files. Doesn't even have a mod_main.gd; just a json manifest and images in various places to get picked up by the appropriate resources. These can be required by combats/modules and they'll be treated as safe since not having scripts makes them risk-free. We allow tres files to be in asset packs as long as they do not contain any inline scripts.
: Mods that do not contain any .gd files (including mod_main.gd) will be treated as Asset Packs.

; Content Pack
: Can have scripts and a mod_main.gd to do non-standard things, but are responsible for making sure anything off-standard they do is reversible without a restart. Since these allow arbitrary code execution, they will prompt additional warnings to the player before they are enabled.
: Mods that contain .gd files and are marked as <code>requires_restart</code> as "false" in their manifest will be treated as Content Packs.

; Substantial Mod
: As above, but the changes are not cleanly reversible so require a restart to turn off or on.
: Mods that contain .gd files and are marked as <code>requires_restart</code> as "true" in their manifest will be treated as Substantial Mods.

An area for future growth, given substantially more resources, would be to add the ability to script game content in a nice sandboxed environment by setting up an internal .lua API for new abilities to use. This would allow new mechs and whatnot to count as asset packs, but the time-benefit tradeoff isn’t favorable given our current time and labor constraints.

MediaWiki:Common.css

2026-07-06T03:01:06Z

Olive: spacing for definitions

/* CSS placed here will be applied to all skins */

/* latin */
@import url('https://fonts.googleapis.com/css2?family=Open+Sans:ital,wght@0,300..800;1,300..800&family=Space+Mono:ital,wght@0,400;0,700;1,400;1,700&display=swap');

body {
background: #1a212b;
font-family: 'Open Sans', 'Segoe UI','Segoe UI Emoji','Segoe UI Symbol','Lato','Liberation Sans','Noto Sans','Helvetica Neue','Helvetica',sans-serif;

dt {
font-family: 'Open Sans', 'Segoe UI','Segoe UI Emoji','Segoe UI Symbol','Lato','Liberation Sans','Noto Sans','Helvetica Neue','Helvetica',sans-serif;
margin: 0 1em 4px;
}

h1, h2, h3, h4, h5, h6 {
font-family: 'Space Mono', monospace !important;
}

input {
font-family: 'Space Mono', monospace !important;
}

.mw-createacct-benefits-heading, .mw-number-text, .mw-number-text strong {
font-family: 'Space Mono', monospace !important;
background: none !important;
padding: 0 !important;
}

#simpleSearch {
border: solid 1px #36455C;

#searchInput {
font-family: 'Space Mono', monospace;
background: #11151C;
color: white;
border-radius: 0;
}

#searchButton {
background-image: url(/skins/Timeless/resources/images/search-ltr-light.svg);
background-size: 20px 20px;
}
}

#mw-header-container {
background: #1a212b;
border-bottom: 4px solid #E5B91A;

#p-logo-text a {
font-family: 'Space Mono', monospace;
text-transform: uppercase;
color: #8197b8;
}

#personal h2 {
font-family: 'Space Mono', monospace;
color: #8197b8;
background-image: url(/skins/Timeless/resources/images/user-light.svg);
@media screen and (min-width: 850px) {
background-size: 20px 20px;
background-position: left 13px;
}

&::after {
background-image: url(/skins/Timeless/resources/images/arrow-down-light.svg);
}
}

#p-search {
padding-top: 1px;
}
}

#site-navigation, #site-tools, #page-tools {
background: #eee !important;
}

@media screen and (max-width: 850px) {
#site-navigation h2 {
background-image: url(/skins/Timeless/resources/images/menu-large-light.svg);
}

#site-tools h2 {
background-image: url(/skins/Timeless/resources/images/gear-large-light.svg);

&::after {
background-image: url(/skins/Timeless/resources/images/arrow-down-light.svg);
}
}
}

#mw-header-hack {
display: none;
}

#mw-header-nav-hack {
background: #eee !important;

.color-middle, .color-left, .color-right {
background: #E5B91A;
height: 4px;
}
}

#mw-content-container {
background: #36455C;
border-bottom: solid 4px #E5B91A;

input[type="button"], input[type="submit"], #wpCreateaccount {
background-color: #E5B91A !important;
color: #11151C !important;
border-color: #E5B91A !important;

&:hover {
color: #fff !important;
}
}

#mw-content {
background: #eee !important;
}

.mw-body h1.firstHeading {
border-color: #52698C;
padding-bottom: 6px;
}

.mw-indicators {
font-family: 'Space Mono',monospace !important;
.mw-helplink-icon { display: none; }
}

.tools-inline li {
font-family: 'Space Mono',monospace !important;
padding-bottom: 2px;

&.selected { border-color: #52698C; }

&:not(.mw-watchlink) a {
background: none;
padding: 0 2px;
}
}

.mw-editsection {
font-family: 'Space Mono', monospace !important;
background: none;
margin: 0;

a:first-of-type {
padding: 0;
margin: 0;
}
}
}

#mw-footer-container {
color: #8197b8;

a {
color: #8197b8;
}

#footer-poweredbyico {
background: #8197b8;
padding: 4px;
border-radius: 5px;
}
}
}

Module Editor

2026-07-05T23:55:32Z

Olive: Created page with "DRAFT DRAFT DRAFT The Module Editor is a tool for adding downtime scenes between combats. == Beats & Notes == A player is always within exactly one active Beat, which itself can contain one or more Notes. Beats are like a room and Notes are like the things you can do in that room. File:ModuleEditorBeats.png Unless an active Note specifies otherwise, a Beat determines the current background that underlays whatever's..."

DRAFT DRAFT DRAFT

The Module Editor is a tool for adding downtime scenes between combats.

== Beats & Notes ==

A player is always within exactly one active Beat, which itself can contain one or more Notes. Beats are like a room and Notes are like the things you can do in that room.

[[File:ModuleEditorBeats.png]]

Unless an active Note specifies otherwise, a Beat determines the current [[Module Editor#Backgrounds|background]] that underlays whatever's going on in the UI.

Beats also determine what the player can do with the Lancers character-sheet-wise whenever another Note isn't currently active. The available values:
** '''Hidden:''' All Lancers are hidden. The player cannot open characters sheets or see who's in the current party.
** '''None:''' The player can inspect character sheets, but not spend repairs or otherwise modify their Lancers.
** '''Short repair:''' The player can spend repairs to restore Structure/Stress or destroyed systems and mechs, but not modify their current loadout.
** '''Full repair:''' All stats are restored to full and the player is free to modify loadouts.
** '''Level up:''' On entering this beat for the first time, all Lancers increase in License Level. Otherwise acts as a full repair.

The current Note types are:

; Combat Briefing
: Shows a preview of a combat with any available sitrep and map information. Players can press Launch to start the combat. There's also a checkbox to skip the briefing screen and jump straight into the combat as soon as this Note becomes active.

; Exposition
: A flexible text box, optional image media, and player choices.

; Dialogue
: Runs a cutscene of characters speaking to each other, defined in the Conversation tool.

; Branch
: automatically proceeds to one of two connected Notes depending on whether its condition returns true/false.

; Signal receiver
: Immediately becomes the active Note when a Trigger emits a matching module signal effect and proceeds to whatever it's connected to.

; Trigger
: runs some number of effects (as long as its conditions are met) and proceeds to whatever it's connected to. The interface for defining trigger conditions and effects is the same as in the Combat Editor but the list of what effects are available is different.

== Backgrounds ==

MediaWiki:Common.css

2026-07-05T23:55:19Z

Olive:

/* CSS placed here will be applied to all skins */

/* latin */
@import url('https://fonts.googleapis.com/css2?family=Open+Sans:ital,wght@0,300..800;1,300..800&family=Space+Mono:ital,wght@0,400;0,700;1,400;1,700&display=swap');

body {
background: #1a212b;
font-family: 'Open Sans', 'Segoe UI','Segoe UI Emoji','Segoe UI Symbol','Lato','Liberation Sans','Noto Sans','Helvetica Neue','Helvetica',sans-serif;

dt {
font-family: 'Open Sans', 'Segoe UI','Segoe UI Emoji','Segoe UI Symbol','Lato','Liberation Sans','Noto Sans','Helvetica Neue','Helvetica',sans-serif;
}

h1, h2, h3, h4, h5, h6 {
font-family: 'Space Mono', monospace !important;
}

input {
font-family: 'Space Mono', monospace !important;
}

.mw-createacct-benefits-heading, .mw-number-text, .mw-number-text strong {
font-family: 'Space Mono', monospace !important;
background: none !important;
padding: 0 !important;
}

#simpleSearch {
border: solid 1px #36455C;

#searchInput {
font-family: 'Space Mono', monospace;
background: #11151C;
color: white;
border-radius: 0;
}

#searchButton {
background-image: url(/skins/Timeless/resources/images/search-ltr-light.svg);
background-size: 20px 20px;
}
}

#mw-header-container {
background: #1a212b;
border-bottom: 4px solid #E5B91A;

#p-logo-text a {
font-family: 'Space Mono', monospace;
text-transform: uppercase;
color: #8197b8;
}

#personal h2 {
font-family: 'Space Mono', monospace;
color: #8197b8;
background-image: url(/skins/Timeless/resources/images/user-light.svg);
@media screen and (min-width: 850px) {
background-size: 20px 20px;
background-position: left 13px;
}

&::after {
background-image: url(/skins/Timeless/resources/images/arrow-down-light.svg);
}
}

#p-search {
padding-top: 1px;
}
}

#site-navigation, #site-tools, #page-tools {
background: #eee !important;
}

@media screen and (max-width: 850px) {
#site-navigation h2 {
background-image: url(/skins/Timeless/resources/images/menu-large-light.svg);
}

#site-tools h2 {
background-image: url(/skins/Timeless/resources/images/gear-large-light.svg);

&::after {
background-image: url(/skins/Timeless/resources/images/arrow-down-light.svg);
}
}
}

#mw-header-hack {
display: none;
}

#mw-header-nav-hack {
background: #eee !important;

.color-middle, .color-left, .color-right {
background: #E5B91A;
height: 4px;
}
}

#mw-content-container {
background: #36455C;
border-bottom: solid 4px #E5B91A;

input[type="button"], input[type="submit"], #wpCreateaccount {
background-color: #E5B91A !important;
color: #11151C !important;
border-color: #E5B91A !important;

&:hover {
color: #fff !important;
}
}

#mw-content {
background: #eee !important;
}

.mw-body h1.firstHeading {
border-color: #52698C;
padding-bottom: 6px;
}

.mw-indicators {
font-family: 'Space Mono',monospace !important;
.mw-helplink-icon { display: none; }
}

.tools-inline li {
font-family: 'Space Mono',monospace !important;
padding-bottom: 2px;

&.selected { border-color: #52698C; }

&:not(.mw-watchlink) a {
background: none;
padding: 0 2px;
}
}

.mw-editsection {
font-family: 'Space Mono', monospace !important;
background: none;
margin: 0;

a:first-of-type {
padding: 0;
margin: 0;
}
}
}

#mw-footer-container {
color: #8197b8;

a {
color: #8197b8;
}

#footer-poweredbyico {
background: #8197b8;
padding: 4px;
border-radius: 5px;
}
}
}

File:ModuleEditorBeats.png

2026-07-05T23:23:24Z

Olive: A series of three beats connected by intervening dialogue or combat nodes.

== Summary ==
A series of three beats connected by intervening dialogue or combat nodes.

The Muse

2026-07-05T23:09:29Z

Olive: lancer disclaimer to bottom

The Muse (aka the Lancer Tactics Wiki) is a compilation of editor documentation and guides for [https://lancertactics.com/ Lancer Tactics], a video game adaptation of the [https://massifpress.com/lancer Lancer TTRPG] by Tom Bloom and Miguel Lopez-Hall. The in-universe concept of the Muse is from the [https://vexwerewolf.itch.io/in-golden-flame-act-1 In Golden Flame] module by Vex Werewolf.

== Modding ==
* [[Modding EULA]]
* [[Modding|Introduction to modding]]
* [[Modding Cookbook]]

== Combat Editor ==
* TODO

== Module Editor ==
* TODO

== Other ==
* [[Changes from the TTRPG]]

== External Links & Resources ==
* [https://wick.works/devlog/category/lancer-tactics Devlog at wick.works]
* [https://discord.com/invite/2t7Efg2Fbj Lancer Tactics Discord]
* [https://wick.itch.io/lancer-tactics/community itch.io forums]
* [https://wick.itch.io/lancer-tactics itch.io store page]
* [https://store.steampowered.com/app/4049810/Lancer_Tactics/ Wishlist on Steam]
* [https://mod.io/g/lancer-tactics Lancer Tactics on mod.io]
* [https://compcon.app/ COMP/CON]

''Lancer Tactics is not an official Lancer product; it is a third party work, and is not affiliated with Massif Press. Lancer Tactics is published via the Lancer Third Party License. Lancer is copyright Massif Press.''

The Muse

2026-07-05T22:13:51Z

Olive: seo edit trigger

The Muse (aka the Lancer Tactics Wiki) is a compilation of editor documentation and guides for [https://lancertactics.com/ Lancer Tactics.]

Lancer Tactics is a port of the [https://massifpress.com/lancer Lancer TTRPG] by Tom Bloom and Miguel Lopez-Hall.

''Lancer Tactics is not an official Lancer product; it is a third party work, and is not affiliated with Massif Press. Lancer Tactics is published via the Lancer Third Party License. Lancer is copyright Massif Press.''

''The in-universe concept of the Muse is from the [https://vexwerewolf.itch.io/in-golden-flame-act-1 In Golden Flame] module by Vex Werewolf.''

== Modding ==
* [[Modding EULA]]
* [[Modding|Introduction to modding]]
* [[Modding Cookbook]]

== Combat Editor ==
* TODO

== Module Editor ==
* TODO

== Other ==
* [[Changes from the TTRPG]]

== External Links & Resources ==
* [https://wick.works/devlog/category/lancer-tactics Devlog at wick.works]
* [https://discord.com/invite/2t7Efg2Fbj Lancer Tactics Discord]
* [https://wick.itch.io/lancer-tactics/community itch.io forums]
* [https://wick.itch.io/lancer-tactics itch.io store page]
* [https://store.steampowered.com/app/4049810/Lancer_Tactics/ Wishlist on Steam]
* [https://mod.io/g/lancer-tactics Lancer Tactics on mod.io]
* [https://compcon.app/ COMP/CON]

MediaWiki:Common.css

2026-07-05T21:52:29Z

Olive: eee background

/* CSS placed here will be applied to all skins */

/* latin */
@import url('https://fonts.googleapis.com/css2?family=Open+Sans:ital,wght@0,300..800;1,300..800&family=Space+Mono:ital,wght@0,400;0,700;1,400;1,700&display=swap');

body {
background: #1a212b;
font-family: 'Open Sans', 'Segoe UI','Segoe UI Emoji','Segoe UI Symbol','Lato','Liberation Sans','Noto Sans','Helvetica Neue','Helvetica',sans-serif;

h1, h2, h3, h4, h5, h6 {
font-family: 'Space Mono', monospace !important;
}

input {
font-family: 'Space Mono', monospace !important;
}

.mw-createacct-benefits-heading, .mw-number-text, .mw-number-text strong {
font-family: 'Space Mono', monospace !important;
background: none !important;
padding: 0 !important;
}

#simpleSearch {
border: solid 1px #36455C;

#searchInput {
font-family: 'Space Mono', monospace;
background: #11151C;
color: white;
border-radius: 0;
}

#searchButton {
background-image: url(/skins/Timeless/resources/images/search-ltr-light.svg);
background-size: 20px 20px;
}
}

#mw-header-container {
background: #1a212b;
border-bottom: 4px solid #E5B91A;

#p-logo-text a {
font-family: 'Space Mono', monospace;
text-transform: uppercase;
color: #8197b8;
}

#personal h2 {
font-family: 'Space Mono', monospace;
color: #8197b8;
background-image: url(/skins/Timeless/resources/images/user-light.svg);
@media screen and (min-width: 850px) {
background-size: 20px 20px;
background-position: left 13px;
}

&::after {
background-image: url(/skins/Timeless/resources/images/arrow-down-light.svg);
}
}

#p-search {
padding-top: 1px;
}
}

#site-navigation, #site-tools, #page-tools {
background: #eee !important;
}

@media screen and (max-width: 850px) {
#site-navigation h2 {
background-image: url(/skins/Timeless/resources/images/menu-large-light.svg);
}

#site-tools h2 {
background-image: url(/skins/Timeless/resources/images/gear-large-light.svg);

&::after {
background-image: url(/skins/Timeless/resources/images/arrow-down-light.svg);
}
}
}

#mw-header-hack {
display: none;
}

#mw-header-nav-hack {
background: #eee !important;

.color-middle, .color-left, .color-right {
background: #E5B91A;
height: 4px;
}
}

#mw-content-container {
background: #36455C;
border-bottom: solid 4px #E5B91A;

input[type="button"], input[type="submit"], #wpCreateaccount {
background-color: #E5B91A !important;
color: #11151C !important;
border-color: #E5B91A !important;

&:hover {
color: #fff !important;
}
}

#mw-content {
background: #eee !important;
}

.mw-body h1.firstHeading {
border-color: #52698C;
padding-bottom: 6px;
}

.mw-indicators {
font-family: 'Space Mono',monospace !important;
.mw-helplink-icon { display: none; }
}

.tools-inline li {
font-family: 'Space Mono',monospace !important;
padding-bottom: 2px;

&.selected { border-color: #52698C; }

&:not(.mw-watchlink) a {
background: none;
padding: 0 2px;
}
}

.mw-editsection {
font-family: 'Space Mono', monospace !important;
background: none;
margin: 0;

a:first-of-type {
padding: 0;
margin: 0;
}
}
}

#mw-footer-container {
color: #8197b8;

a {
color: #8197b8;
}

#footer-poweredbyico {
background: #8197b8;
padding: 4px;
border-radius: 5px;
}
}
}

MediaWiki:Common.css

2026-07-05T20:52:50Z

Olive: padding

/* CSS placed here will be applied to all skins */

/* latin */
@import url('https://fonts.googleapis.com/css2?family=Open+Sans:ital,wght@0,300..800;1,300..800&family=Space+Mono:ital,wght@0,400;0,700;1,400;1,700&display=swap');

body {
background: #1a212b;
font-family: 'Open Sans', 'Segoe UI','Segoe UI Emoji','Segoe UI Symbol','Lato','Liberation Sans','Noto Sans','Helvetica Neue','Helvetica',sans-serif;

h1, h2, h3, h4, h5, h6 {
font-family: 'Space Mono', monospace !important;
}

input {
font-family: 'Space Mono', monospace !important;
}

.mw-createacct-benefits-heading, .mw-number-text, .mw-number-text strong {
font-family: 'Space Mono', monospace !important;
background: none !important;
padding: 0 !important;
}

#simpleSearch {
border: solid 1px #36455C;

#searchInput {
font-family: 'Space Mono', monospace;
background: #11151C;
color: white;
border-radius: 0;
}

#searchButton {
background-image: url(/skins/Timeless/resources/images/search-ltr-light.svg);
background-size: 20px 20px;
}
}

#mw-header-container {
background: #1a212b;
border-bottom: 4px solid #E5B91A;

#p-logo-text a {
font-family: 'Space Mono', monospace;
text-transform: uppercase;
color: #8197b8;
}

#personal h2 {
font-family: 'Space Mono', monospace;
color: #8197b8;
background-image: url(/skins/Timeless/resources/images/user-light.svg);
@media screen and (min-width: 850px) {
background-size: 20px 20px;
background-position: left 13px;
}

&::after {
background-image: url(/skins/Timeless/resources/images/arrow-down-light.svg);
}
}

#p-search {
padding-top: 1px;
}
}

@media screen and (max-width: 850px) {
#site-navigation h2 {
background-image: url(/skins/Timeless/resources/images/menu-large-light.svg);
}

#site-tools h2 {
background-image: url(/skins/Timeless/resources/images/gear-large-light.svg);

&::after {
background-image: url(/skins/Timeless/resources/images/arrow-down-light.svg);
}
}
}

#mw-header-hack {
display: none;
}

#mw-header-nav-hack {
.color-middle, .color-left, .color-right {
background: #E5B91A;
height: 4px;
}
}

#mw-content-container {
background: #36455C;
border-bottom: solid 4px #E5B91A;

input[type="button"], input[type="submit"], #wpCreateaccount {
background-color: #E5B91A !important;
color: #11151C !important;
border-color: #E5B91A !important;

&:hover {
color: #fff !important;
}
}

.mw-body h1.firstHeading {
border-color: #52698C;
padding-bottom: 6px;
}

.mw-indicators {
font-family: 'Space Mono',monospace !important;
.mw-helplink-icon { display: none; }
}

.tools-inline li {
font-family: 'Space Mono',monospace !important;
padding-bottom: 2px;

&.selected { border-color: #52698C; }

&:not(.mw-watchlink) a {
background: none;
padding: 0 2px;
}
}

.mw-editsection {
font-family: 'Space Mono', monospace !important;
background: none;
margin: 0;

a:first-of-type {
padding: 0;
margin: 0;
}
}
}

#mw-footer-container {
color: #8197b8;

a {
color: #8197b8;
}

#footer-poweredbyico {
background: #8197b8;
padding: 4px;
border-radius: 5px;
}
}
}

MediaWiki:Common.css

2026-07-05T20:51:58Z

Olive: !important

/* CSS placed here will be applied to all skins */

/* latin */
@import url('https://fonts.googleapis.com/css2?family=Open+Sans:ital,wght@0,300..800;1,300..800&family=Space+Mono:ital,wght@0,400;0,700;1,400;1,700&display=swap');

body {
background: #1a212b;
font-family: 'Open Sans', 'Segoe UI','Segoe UI Emoji','Segoe UI Symbol','Lato','Liberation Sans','Noto Sans','Helvetica Neue','Helvetica',sans-serif;

h1, h2, h3, h4, h5, h6 {
font-family: 'Space Mono', monospace !important;
}

input {
font-family: 'Space Mono', monospace !important;
}

.mw-createacct-benefits-heading, .mw-number-text, .mw-number-text strong {
font-family: 'Space Mono', monospace !important;
background: none !important;
}

#simpleSearch {
border: solid 1px #36455C;

#searchInput {
font-family: 'Space Mono', monospace;
background: #11151C;
color: white;
border-radius: 0;
}

#searchButton {
background-image: url(/skins/Timeless/resources/images/search-ltr-light.svg);
background-size: 20px 20px;
}
}

#mw-header-container {
background: #1a212b;
border-bottom: 4px solid #E5B91A;

#p-logo-text a {
font-family: 'Space Mono', monospace;
text-transform: uppercase;
color: #8197b8;
}

#personal h2 {
font-family: 'Space Mono', monospace;
color: #8197b8;
background-image: url(/skins/Timeless/resources/images/user-light.svg);
@media screen and (min-width: 850px) {
background-size: 20px 20px;
background-position: left 13px;
}

&::after {
background-image: url(/skins/Timeless/resources/images/arrow-down-light.svg);
}
}

#p-search {
padding-top: 1px;
}
}

@media screen and (max-width: 850px) {
#site-navigation h2 {
background-image: url(/skins/Timeless/resources/images/menu-large-light.svg);
}

#site-tools h2 {
background-image: url(/skins/Timeless/resources/images/gear-large-light.svg);

&::after {
background-image: url(/skins/Timeless/resources/images/arrow-down-light.svg);
}
}
}

#mw-header-hack {
display: none;
}

#mw-header-nav-hack {
.color-middle, .color-left, .color-right {
background: #E5B91A;
height: 4px;
}
}

#mw-content-container {
background: #36455C;
border-bottom: solid 4px #E5B91A;

input[type="button"], input[type="submit"], #wpCreateaccount {
background-color: #E5B91A !important;
color: #11151C !important;
border-color: #E5B91A !important;

&:hover {
color: #fff !important;
}
}

.mw-body h1.firstHeading {
border-color: #52698C;
padding-bottom: 6px;
}

.mw-indicators {
font-family: 'Space Mono',monospace !important;
.mw-helplink-icon { display: none; }
}

.tools-inline li {
font-family: 'Space Mono',monospace !important;
padding-bottom: 2px;

&.selected { border-color: #52698C; }

&:not(.mw-watchlink) a {
background: none;
padding: 0 2px;
}
}

.mw-editsection {
font-family: 'Space Mono', monospace !important;
background: none;
margin: 0;

a:first-of-type {
padding: 0;
margin: 0;
}
}
}

#mw-footer-container {
color: #8197b8;

a {
color: #8197b8;
}

#footer-poweredbyico {
background: #8197b8;
padding: 4px;
border-radius: 5px;
}
}
}

MediaWiki:Common.css

2026-07-05T20:51:29Z

Olive: no icons

/* CSS placed here will be applied to all skins */

/* latin */
@import url('https://fonts.googleapis.com/css2?family=Open+Sans:ital,wght@0,300..800;1,300..800&family=Space+Mono:ital,wght@0,400;0,700;1,400;1,700&display=swap');

body {
background: #1a212b;
font-family: 'Open Sans', 'Segoe UI','Segoe UI Emoji','Segoe UI Symbol','Lato','Liberation Sans','Noto Sans','Helvetica Neue','Helvetica',sans-serif;

h1, h2, h3, h4, h5, h6 {
font-family: 'Space Mono', monospace !important;
}

input {
font-family: 'Space Mono', monospace !important;
}

.mw-createacct-benefits-heading, .mw-number-text, .mw-number-text strong {
font-family: 'Space Mono', monospace !important;
background: none;
}

#simpleSearch {
border: solid 1px #36455C;

#searchInput {
font-family: 'Space Mono', monospace;
background: #11151C;
color: white;
border-radius: 0;
}

#searchButton {
background-image: url(/skins/Timeless/resources/images/search-ltr-light.svg);
background-size: 20px 20px;
}
}

#mw-header-container {
background: #1a212b;
border-bottom: 4px solid #E5B91A;

#p-logo-text a {
font-family: 'Space Mono', monospace;
text-transform: uppercase;
color: #8197b8;
}

#personal h2 {
font-family: 'Space Mono', monospace;
color: #8197b8;
background-image: url(/skins/Timeless/resources/images/user-light.svg);
@media screen and (min-width: 850px) {
background-size: 20px 20px;
background-position: left 13px;
}

&::after {
background-image: url(/skins/Timeless/resources/images/arrow-down-light.svg);
}
}

#p-search {
padding-top: 1px;
}
}

@media screen and (max-width: 850px) {
#site-navigation h2 {
background-image: url(/skins/Timeless/resources/images/menu-large-light.svg);
}

#site-tools h2 {
background-image: url(/skins/Timeless/resources/images/gear-large-light.svg);

&::after {
background-image: url(/skins/Timeless/resources/images/arrow-down-light.svg);
}
}
}

#mw-header-hack {
display: none;
}

#mw-header-nav-hack {
.color-middle, .color-left, .color-right {
background: #E5B91A;
height: 4px;
}
}

#mw-content-container {
background: #36455C;
border-bottom: solid 4px #E5B91A;

input[type="button"], input[type="submit"], #wpCreateaccount {
background-color: #E5B91A !important;
color: #11151C !important;
border-color: #E5B91A !important;

&:hover {
color: #fff !important;
}
}

.mw-body h1.firstHeading {
border-color: #52698C;
padding-bottom: 6px;
}

.mw-indicators {
font-family: 'Space Mono',monospace !important;
.mw-helplink-icon { display: none; }
}

.tools-inline li {
font-family: 'Space Mono',monospace !important;
padding-bottom: 2px;

&.selected { border-color: #52698C; }

&:not(.mw-watchlink) a {
background: none;
padding: 0 2px;
}
}

.mw-editsection {
font-family: 'Space Mono', monospace !important;
background: none;
margin: 0;

a:first-of-type {
padding: 0;
margin: 0;
}
}
}

#mw-footer-container {
color: #8197b8;

a {
color: #8197b8;
}

#footer-poweredbyico {
background: #8197b8;
padding: 4px;
border-radius: 5px;
}
}
}

MediaWiki:Common.css

2026-07-05T20:50:23Z

Olive: font

/* CSS placed here will be applied to all skins */

/* latin */
@import url('https://fonts.googleapis.com/css2?family=Open+Sans:ital,wght@0,300..800;1,300..800&family=Space+Mono:ital,wght@0,400;0,700;1,400;1,700&display=swap');

body {
background: #1a212b;
font-family: 'Open Sans', 'Segoe UI','Segoe UI Emoji','Segoe UI Symbol','Lato','Liberation Sans','Noto Sans','Helvetica Neue','Helvetica',sans-serif;

h1, h2, h3, h4, h5, h6 {
font-family: 'Space Mono', monospace !important;
}

.mw-createacct-benefits-heading, .mw-number-text, .mw-number-text strong {
font-family: 'Space Mono', monospace !important;
}

input {
font-family: 'Space Mono', monospace !important;
}

#simpleSearch {
border: solid 1px #36455C;

#searchInput {
font-family: 'Space Mono', monospace;
background: #11151C;
color: white;
border-radius: 0;
}

#searchButton {
background-image: url(/skins/Timeless/resources/images/search-ltr-light.svg);
background-size: 20px 20px;
}
}

#mw-header-container {
background: #1a212b;
border-bottom: 4px solid #E5B91A;

#p-logo-text a {
font-family: 'Space Mono', monospace;
text-transform: uppercase;
color: #8197b8;
}

#personal h2 {
font-family: 'Space Mono', monospace;
color: #8197b8;
background-image: url(/skins/Timeless/resources/images/user-light.svg);
@media screen and (min-width: 850px) {
background-size: 20px 20px;
background-position: left 13px;
}

&::after {
background-image: url(/skins/Timeless/resources/images/arrow-down-light.svg);
}
}

#p-search {
padding-top: 1px;
}
}

@media screen and (max-width: 850px) {
#site-navigation h2 {
background-image: url(/skins/Timeless/resources/images/menu-large-light.svg);
}

#site-tools h2 {
background-image: url(/skins/Timeless/resources/images/gear-large-light.svg);

&::after {
background-image: url(/skins/Timeless/resources/images/arrow-down-light.svg);
}
}
}

#mw-header-hack {
display: none;
}

#mw-header-nav-hack {
.color-middle, .color-left, .color-right {
background: #E5B91A;
height: 4px;
}
}

#mw-content-container {
background: #36455C;
border-bottom: solid 4px #E5B91A;

input[type="button"], input[type="submit"], #wpCreateaccount {
background-color: #E5B91A !important;
color: #11151C !important;
border-color: #E5B91A !important;

&:hover {
color: #fff !important;
}
}

.mw-body h1.firstHeading {
border-color: #52698C;
padding-bottom: 6px;
}

.mw-indicators {
font-family: 'Space Mono',monospace !important;
.mw-helplink-icon { display: none; }
}

.tools-inline li {
font-family: 'Space Mono',monospace !important;
padding-bottom: 2px;

&.selected { border-color: #52698C; }

&:not(.mw-watchlink) a {
background: none;
padding: 0 2px;
}
}

.mw-editsection {
font-family: 'Space Mono', monospace !important;
background: none;
margin: 0;

a:first-of-type {
padding: 0;
margin: 0;
}
}
}

#mw-footer-container {
color: #8197b8;

a {
color: #8197b8;
}

#footer-poweredbyico {
background: #8197b8;
padding: 4px;
border-radius: 5px;
}
}
}