Lancer Tactics Wiki - User contributions [en]

Muse:General disclaimer

2026-07-05T07:58:42Z

Olive: vex link

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, used here with their permission.

''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.''

Main Page

2026-07-05T07:56:29Z

Olive: Add link to changes from the TTRPG

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

''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.''

== Modding ==
* [[Modding|Introduction to modding Lancer Tactics]]
* [[Modding EULA]]

== Combat Editor ==
* TODO

== Module Editor ==
* TODO

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

Changes from the TTRPG

2026-07-05T07:55:42Z

Olive: initial commit

While overall Lancer Tactics has been able to stay extremely close to the TTRPG ruleset, 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 ==
* 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 attempted to dissipate by hostile characters.
* Autopod and Seismic Deluge only trigger on hostile characters.

Muse:General disclaimer

2026-07-05T07:42:22Z

Olive: Added Lancer TTRPG disclaimer

''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.''

Main Page

2026-07-05T07:34:36Z

Olive: Add link to modding

Modding

2026-07-05T07:28:35Z

Olive: add link to godot

Get help: [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>

'''TODO INSERT IMAGE'''

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:

'''TODO INSERT IMAGE'''

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):

'''TODO INSERT IMAGE'''

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 the "replacing resources" section below 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 Packs, Content Packs and "Substantial" mods:

* '''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 EULA

2026-07-05T07:23:19Z

Olive: link to modding background

So you want to make mods for Lancer Tactics. That's great! There's just some legal guidelines we'd like to make clear before you get started with the [[Modding|Lancer Tactics modkit]].

== General Guidelines ==

* Contained in the modkit is the full commented source code for Lancer Tactics. You are welcome to open it in the Godot editor and run the game locally in order to build and test your mods, but you are NOT authorized to export the game into a standalone application without written permission from Wickworks.

* You are also not authorized to distribute this modkit; if you have a friend who's interested in getting started, please direct them towards the place where you got this from Wickworks.

* Content using the Lancer game system and universe, including both Lancer Tactics and any mods that you may create, is governed by Massif Press's Lancer Third-Party License. It can be reviewed at [https://massifpress.com/legal massifpress.com/legal]

* You need to own a copy of the game to legally use this modkit.

* If you publish your mod, we may showcase it on other platforms without compensation but we will attempt to credit you.

* When we update Lancer Tactics, it may break compatibility with other software such as mods. This is unfortunate, but we don't take responsibility for ensuring all mods will continue to work with new versions of the game.

* Use common sense, follow the law and these rules, respect the Game and its community.

* Please read the following policy carefully before creating any mod, as it is legally binding.

== License ==

* "The Game" - Refers to the game Lancer Tactics made by Wickworks.
* "Mod(s)" - Something original that you or someone else created that doesn't contain a substantial part of our copyrightable code or content.

If and as long as you comply with this policy, Wickworks grants you a personal, limited, non-transferable, revocable, and non-exclusive license to create Mods based on the Game - which you have duly obtained access to.

You hereby grant us and our affiliates a nonexclusive, royalty-free, sublicensable, irrevocable, and perpetual right to

* transmit, broadcast, otherwise communicate, publicly display, publicly perform your Mod
* in any manner or form and in any medium or forum, whether now known or later devised
* without compensation to you or any third party. This right shall survive the termination of this Agreement.

Unless otherwise agreed, the creation and publication of mods are strictly non-commercial. The mod shall be provided free of charge and be freely available, but you may accept donations for your time through Patreon or similar services, or through sponsorships.

Any third-party mods integrated into the Game (whether official or user-created) are not endorsed or supported by Wickworks unless explicitly stated. We do not assume responsibility for bugs, errors, or legal claims related to modded content. You are responsible for your own mod.

=== Intellectual Property (IP) rights ===

Your rights in your mod only extend to the new, original content you create as part of your mod and do not extend to or grant any rights to the Lancer Tactics game, any related IP rights or any content made available by Wickworks in relation to the Game. Please do not use any third-party content in your mod without permission and only use materials you are allowed to use.

If Wickworks coincidentally develops or has developed content similar to your mod or parts of your mod, Wickworks shall be free to fully use the content it has independently created without you gaining any rights to it. In other words: we will never steal content from your mods, but please understand that we also do not want to be prevented from making or finishing content for the Game, just because a mod accidentally contains similar contents or ideas.

=== Behaviour and Mod Content ===

Do not reverse engineer the Game, or any related tools except for the purpose of modding.
Tools and mods are being made available at your own risk.

The following are prohibited:

* creating mods that contain any material which is unlawful, infringing, inappropriate, or violates any contracts or third-party rights.
* using the Lancer Tactics IP in a way that is offensive, grotesque, racist, sexist, vulgar, disparaging, or defamatory.
* creating or using hacks - mods that unlock paid content like DLCs, or remove DRM.
* using your mod to add advertisements or any monetization feature into the Game.
* obfuscating or making your code ambiguous in any way. Players and staff must be able to easily audit and verify the safety of the mod.
* exporting and distributing modified builds of the game.

Wickworks has no obligation to use, distribute or continue to distribute mods, and we may restrict or remove mods breaking any of these rules at our sole discretion.

We have the final say on what constitutes a Mod and what doesn't. You may not distribute any Modded Versions of our Game or software, and we’d appreciate it if you didn’t use Mods for griefing. Basically, Mods are okay to distribute; hacked versions or Modded Versions of the game client or server software are not okay to distribute.

=== Reporting ===

If you encounter content created by another user that you find offensive, we encourage you to report this content by clicking on the report button on the Mod.io page.

In case of Dispute: first, let’s try to solve disputes informally. If it does not work, arbitration or the courts in Portland, Oregon will settle it.

Please note that third party EULAs like the Lancer Third Party License or Mod.io uploading agreement may apply.

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-07-05T07:22:01Z

Olive: /* Modkit */ link to modding eula

Get help: [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? ==

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>

'''TODO INSERT IMAGE'''

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:

'''TODO INSERT IMAGE'''

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):

'''TODO INSERT IMAGE'''

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 the "replacing resources" section below 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 Packs, Content Packs and "Substantial" mods:

* '''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-07-05T07:18:56Z

Olive: Add security section

Get help: [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 LT’s Discord server].

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

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>

'''TODO INSERT IMAGE'''

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:

'''TODO INSERT IMAGE'''

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):

'''TODO INSERT IMAGE'''

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 the "replacing resources" section below 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 Packs, Content Packs and "Substantial" mods:

* '''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-07-05T07:13:54Z

Olive: Add background section

Get help: [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 LT’s Discord server].

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

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>

TODO INSERT IMAGE

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:

TODO INSERT IMAGE

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):

TODO INSERT IMAGE

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 the "replacing resources" section below 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 ==

Lancer Tactics distinguishes between three mod types: Asset Packs, Content Packs and "Substantial" mods. Asset and Content packs' changes are standardized and reversible, so can be enabled and disabled without restarting the game. Substantial mods change the base scripts or scenes the rest of the game relies on so require a restart.

* '''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.

Modding

2026-07-05T07:07:36Z

Olive: formatting

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

== Mod Types ==

Lancer Tactics distinguishes between three mod types: Asset Packs, Content Packs and "Substantial" mods. Asset and Content packs' changes are standardized and reversible, so can be enabled and disabled without restarting the game. Substantial mods change the base scripts or scenes the rest of the game relies on so require a restart.

* '''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.

== 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 the "replacing resources" section below 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.

Modding

2026-07-05T07:06:08Z

Olive: Bring the introduction in from modding_guide.txt

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

== Mod Types ==

Lancer Tactics distinguishes between three mod types: Asset Packs, Content Packs and "Substantial" mods. Asset and Content packs' changes are standardized and reversible, so can be enabled and disabled without restarting the game. Substantial mods change the base scripts or scenes the rest of the game relies on so require a restart.

* '''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 requires_restart 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 requires_restart as "true" in their manifest will be treated as Substantial Mods.

== 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 the "replacing resources" section below 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.

Modding EULA

2026-07-05T06:58:08Z

Olive: learned about heading syntax

So you want to make mods for Lancer Tactics (the “Game”). That's great! There's just some legal guidelines we'd like to make clear before you get started.

== General Guidelines ==

* Contained in the modkit is the full commented source code for Lancer Tactics. You are welcome to open it in the Godot editor and run the game locally in order to build and test your mods, but you are NOT authorized to export the game into a standalone application without written permission from Wickworks.

* You are also not authorized to distribute this modkit; if you have a friend who's interested in getting started, please direct them towards the place where you got this from Wickworks.

* Content using the Lancer game system and universe, including both Lancer Tactics and any mods that you may create, is governed by Massif Press's Lancer Third-Party License. It can be reviewed at [https://massifpress.com/legal massifpress.com/legal]

* You need to own a copy of the game to legally use this modkit.

* If you publish your mod, we may showcase it on other platforms without compensation but we will attempt to credit you.

* When we update Lancer Tactics, it may break compatibility with other software such as mods. This is unfortunate, but we don't take responsibility for ensuring all mods will continue to work with new versions of the game.

* Use common sense, follow the law and these rules, respect the Game and its community.

* Please read the following policy carefully before creating any mod, as it is legally binding.

== License ==

* "The Game" - Refers to the game Lancer Tactics made by Wickworks.
* "Mod(s)" - Something original that you or someone else created that doesn't contain a substantial part of our copyrightable code or content.

If and as long as you comply with this policy, Wickworks grants you a personal, limited, non-transferable, revocable, and non-exclusive license to create Mods based on the Game - which you have duly obtained access to.

You hereby grant us and our affiliates a nonexclusive, royalty-free, sublicensable, irrevocable, and perpetual right to

* transmit, broadcast, otherwise communicate, publicly display, publicly perform your Mod
* in any manner or form and in any medium or forum, whether now known or later devised
* without compensation to you or any third party. This right shall survive the termination of this Agreement.

Unless otherwise agreed, the creation and publication of mods are strictly non-commercial. The mod shall be provided free of charge and be freely available, but you may accept donations for your time through Patreon or similar services, or through sponsorships.

Any third-party mods integrated into the Game (whether official or user-created) are not endorsed or supported by Wickworks unless explicitly stated. We do not assume responsibility for bugs, errors, or legal claims related to modded content. You are responsible for your own mod.

=== Intellectual Property (IP) rights ===

Your rights in your mod only extend to the new, original content you create as part of your mod and do not extend to or grant any rights to the Lancer Tactics game, any related IP rights or any content made available by Wickworks in relation to the Game. Please do not use any third-party content in your mod without permission and only use materials you are allowed to use.

If Wickworks coincidentally develops or has developed content similar to your mod or parts of your mod, Wickworks shall be free to fully use the content it has independently created without you gaining any rights to it. In other words: we will never steal content from your mods, but please understand that we also do not want to be prevented from making or finishing content for the Game, just because a mod accidentally contains similar contents or ideas.

=== Behaviour and Mod Content ===

Do not reverse engineer the Game, or any related tools except for the purpose of modding.
Tools and mods are being made available at your own risk.

The following are prohibited:

* creating mods that contain any material which is unlawful, infringing, inappropriate, or violates any contracts or third-party rights.
* using the Lancer Tactics IP in a way that is offensive, grotesque, racist, sexist, vulgar, disparaging, or defamatory.
* creating or using hacks - mods that unlock paid content like DLCs, or remove DRM.
* using your mod to add advertisements or any monetization feature into the Game.
* obfuscating or making your code ambiguous in any way. Players and staff must be able to easily audit and verify the safety of the mod.
* exporting and distributing modified builds of the game.

Wickworks has no obligation to use, distribute or continue to distribute mods, and we may restrict or remove mods breaking any of these rules at our sole discretion.

We have the final say on what constitutes a Mod and what doesn't. You may not distribute any Modded Versions of our Game or software, and we’d appreciate it if you didn’t use Mods for griefing. Basically, Mods are okay to distribute; hacked versions or Modded Versions of the game client or server software are not okay to distribute.

=== Reporting ===

If you encounter content created by another user that you find offensive, we encourage you to report this content by clicking on the report button on the Mod.io page.

In case of Dispute: first, let’s try to solve disputes informally. If it does not work, arbitration or the courts in Portland, Oregon will settle it.

Please note that third party EULAs like the Lancer Third Party License or Mod.io uploading agreement may apply.

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 EULA

2026-07-05T06:51:35Z

Olive: Protected "Modding EULA" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

So you want to make mods for Lancer Tactics (the “Game”). That's great! There's just some legal guidelines we'd like to make clear before you get started.

== General Guidelines ==

* Contained in the modkit is the full commented source code for Lancer Tactics. You are welcome to open it in the Godot editor and run the game locally in order to build and test your mods, but you are NOT authorized to export the game into a standalone application without written permission from Wickworks.

* You are also not authorized to distribute this modkit; if you have a friend who's interested in getting started, please direct them towards the place where you got this from Wickworks.

* Content using the Lancer game system and universe, including both Lancer Tactics and any mods that you may create, is governed by Massif Press's Lancer Third-Party License. It can be reviewed at [https://massifpress.com/legal massifpress.com/legal]

* You need to own a copy of the game to legally use this modkit.

* If you publish your mod, we may showcase it on other platforms without compensation but we will attempt to credit you.

* When we update Lancer Tactics, it may break compatibility with other software such as mods. This is unfortunate, but we don't take responsibility for ensuring all mods will continue to work with new versions of the game.

* Use common sense, follow the law and these rules, respect the Game and its community.

* Please read the following policy carefully before creating any mod, as it is legally binding.

== License ==

* "The Game" - Refers to the game Lancer Tactics made by Wickworks.
* "Mod(s)" - Something original that you or someone else created that doesn't contain a substantial part of our copyrightable code or content.

If and as long as you comply with this policy, Wickworks grants you a personal, limited, non-transferable, revocable, and non-exclusive license to create Mods based on the Game - which you have duly obtained access to.

You hereby grant us and our affiliates a nonexclusive, royalty-free, sublicensable, irrevocable, and perpetual right to

* transmit, broadcast, otherwise communicate, publicly display, publicly perform your Mod
* in any manner or form and in any medium or forum, whether now known or later devised
* without compensation to you or any third party. This right shall survive the termination of this Agreement.

Unless otherwise agreed, the creation and publication of mods are strictly non-commercial. The mod shall be provided free of charge and be freely available, but you may accept donations for your time through Patreon or similar services, or through sponsorships.

Any third-party mods integrated into the Game (whether official or user-created) are not endorsed or supported by Wickworks unless explicitly stated. We do not assume responsibility for bugs, errors, or legal claims related to modded content. You are responsible for your own mod.

== Intellectual Property (IP) rights ==

Your rights in your mod only extend to the new, original content you create as part of your mod and do not extend to or grant any rights to the Lancer Tactics game, any related IP rights or any content made available by Wickworks in relation to the Game. Please do not use any third-party content in your mod without permission and only use materials you are allowed to use.

If Wickworks coincidentally develops or has developed content similar to your mod or parts of your mod, Wickworks shall be free to fully use the content it has independently created without you gaining any rights to it. In other words: we will never steal content from your mods, but please understand that we also do not want to be prevented from making or finishing content for the Game, just because a mod accidentally contains similar contents or ideas.

== Behaviour and Mod Content ==

Do not reverse engineer the Game, or any related tools except for the purpose of modding.
Tools and mods are being made available at your own risk.

The following are prohibited:

* creating mods that contain any material which is unlawful, infringing, inappropriate, or violates any contracts or third-party rights.
* using the Lancer Tactics IP in a way that is offensive, grotesque, racist, sexist, vulgar, disparaging, or defamatory.
* creating or using hacks - mods that unlock paid content like DLCs, or remove DRM.
* using your mod to add advertisements or any monetization feature into the Game.
* obfuscating or making your code ambiguous in any way. Players and staff must be able to easily audit and verify the safety of the mod.
* exporting and distributing modified builds of the game.

Wickworks has no obligation to use, distribute or continue to distribute mods, and we may restrict or remove mods breaking any of these rules at our sole discretion.

We have the final say on what constitutes a Mod and what doesn't. You may not distribute any Modded Versions of our Game or software, and we’d appreciate it if you didn’t use Mods for griefing. Basically, Mods are okay to distribute; hacked versions or Modded Versions of the game client or server software are not okay to distribute.

== Reporting ==

If you encounter content created by another user that you find offensive, we encourage you to report this content by clicking on the report button on the Mod.io page.

In case of Dispute: first, let’s try to solve disputes informally. If it does not work, arbitration or the courts in Portland, Oregon will settle it.

Please note that third party EULAs like the Lancer Third Party License or Mod.io uploading agreement may apply.

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 EULA

2026-07-05T06:50:55Z

Olive: Copied in the modding EULA

So you want to make mods for Lancer Tactics (the “Game”). That's great! There's just some legal guidelines we'd like to make clear before you get started.

== General Guidelines ==

* Contained in the modkit is the full commented source code for Lancer Tactics. You are welcome to open it in the Godot editor and run the game locally in order to build and test your mods, but you are NOT authorized to export the game into a standalone application without written permission from Wickworks.

* You are also not authorized to distribute this modkit; if you have a friend who's interested in getting started, please direct them towards the place where you got this from Wickworks.

* Content using the Lancer game system and universe, including both Lancer Tactics and any mods that you may create, is governed by Massif Press's Lancer Third-Party License. It can be reviewed at [https://massifpress.com/legal massifpress.com/legal]

* You need to own a copy of the game to legally use this modkit.

* If you publish your mod, we may showcase it on other platforms without compensation but we will attempt to credit you.

* When we update Lancer Tactics, it may break compatibility with other software such as mods. This is unfortunate, but we don't take responsibility for ensuring all mods will continue to work with new versions of the game.

* Use common sense, follow the law and these rules, respect the Game and its community.

* Please read the following policy carefully before creating any mod, as it is legally binding.

== License ==

* "The Game" - Refers to the game Lancer Tactics made by Wickworks.
* "Mod(s)" - Something original that you or someone else created that doesn't contain a substantial part of our copyrightable code or content.

If and as long as you comply with this policy, Wickworks grants you a personal, limited, non-transferable, revocable, and non-exclusive license to create Mods based on the Game - which you have duly obtained access to.

You hereby grant us and our affiliates a nonexclusive, royalty-free, sublicensable, irrevocable, and perpetual right to

* transmit, broadcast, otherwise communicate, publicly display, publicly perform your Mod
* in any manner or form and in any medium or forum, whether now known or later devised
* without compensation to you or any third party. This right shall survive the termination of this Agreement.

Unless otherwise agreed, the creation and publication of mods are strictly non-commercial. The mod shall be provided free of charge and be freely available, but you may accept donations for your time through Patreon or similar services, or through sponsorships.

Any third-party mods integrated into the Game (whether official or user-created) are not endorsed or supported by Wickworks unless explicitly stated. We do not assume responsibility for bugs, errors, or legal claims related to modded content. You are responsible for your own mod.

== Intellectual Property (IP) rights ==

Your rights in your mod only extend to the new, original content you create as part of your mod and do not extend to or grant any rights to the Lancer Tactics game, any related IP rights or any content made available by Wickworks in relation to the Game. Please do not use any third-party content in your mod without permission and only use materials you are allowed to use.

If Wickworks coincidentally develops or has developed content similar to your mod or parts of your mod, Wickworks shall be free to fully use the content it has independently created without you gaining any rights to it. In other words: we will never steal content from your mods, but please understand that we also do not want to be prevented from making or finishing content for the Game, just because a mod accidentally contains similar contents or ideas.

== Behaviour and Mod Content ==

Do not reverse engineer the Game, or any related tools except for the purpose of modding.
Tools and mods are being made available at your own risk.

The following are prohibited:

* creating mods that contain any material which is unlawful, infringing, inappropriate, or violates any contracts or third-party rights.
* using the Lancer Tactics IP in a way that is offensive, grotesque, racist, sexist, vulgar, disparaging, or defamatory.
* creating or using hacks - mods that unlock paid content like DLCs, or remove DRM.
* using your mod to add advertisements or any monetization feature into the Game.
* obfuscating or making your code ambiguous in any way. Players and staff must be able to easily audit and verify the safety of the mod.
* exporting and distributing modified builds of the game.

Wickworks has no obligation to use, distribute or continue to distribute mods, and we may restrict or remove mods breaking any of these rules at our sole discretion.

We have the final say on what constitutes a Mod and what doesn't. You may not distribute any Modded Versions of our Game or software, and we’d appreciate it if you didn’t use Mods for griefing. Basically, Mods are okay to distribute; hacked versions or Modded Versions of the game client or server software are not okay to distribute.

== Reporting ==

If you encounter content created by another user that you find offensive, we encourage you to report this content by clicking on the report button on the Mod.io page.

In case of Dispute: first, let’s try to solve disputes informally. If it does not work, arbitration or the courts in Portland, Oregon will settle it.

Please note that third party EULAs like the Lancer Third Party License or Mod.io uploading agreement may apply.

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.

MediaWiki:Pagetitle-view-mainpage

2026-07-05T06:36:15Z

Olive: rename tab title to The Muse

The Muse

Main Page

2026-07-05T06:32:01Z

Olive: Remove mediawiki boilerplate

MediaWiki:Common.css

2026-07-05T06:13:17Z

Olive: fix profile icon size mobile

/* 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;
}

#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-content-container {
background: #36455C;
border-bottom: solid 4px #E5B91A;

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

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

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

a {
color: #8197b8;
}

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

MediaWiki:Common.css

2026-07-05T06:05:40Z

Olive: light search button

/* 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;
}

#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);
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-content-container {
background: #36455C;
border-bottom: solid 4px #E5B91A;

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

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

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

a {
color: #8197b8;
}

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

MediaWiki:Common.css

2026-07-05T06:01:16Z

Olive: dark search bar

/* 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;
}

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

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

#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);
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-content-container {
background: #36455C;
border-bottom: solid 4px #E5B91A;

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

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

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

a {
color: #8197b8;
}

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

MediaWiki:Common.css

2026-07-05T05:47:13Z

Olive: yellow buttons

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

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

body {
background: #1a212b;

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

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

#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);
background-size: 20px 20px;
background-position: left 13px;

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

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

@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-content-container {
background: #36455C;
border-bottom: solid 4px #E5B91A;

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

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

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

a {
color: #8197b8;
}

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

MediaWiki:Common.css

2026-07-05T05:35:01Z

Olive: borders and colors and header I think

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

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

body {
background: #1a212b;

input, #searchInput {
font-family: 'Space Mono', monospace;
}

.mw-body {
h1, h2, h3, h4, h5, h6 {
font-family: 'Space Mono', monospace;
}
}

#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);
background-size: 20px 20px;
background-position: left 13px;

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

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

@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-content-container {
background: #36455C;
border-bottom: solid 4px #E5B91A;
}

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

a {
color: #8197b8;
}

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

MediaWiki:Common.css

2026-07-05T05:20:44Z

Olive: Add space mono font

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

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

body {
background: #1a212b;

input, #searchInput {
font-family: 'Space Mono', monospace;
}

.mw-body {
h1, h2, h3, h4, h5, h6 {
font-family: 'Space Mono', monospace;
}
}

#mw-header-container {
background: #1a212b;

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

#personal h2 {
font-family: 'Space Mono', monospace;
color: #E5B91A;
background-image: url(/skins/Timeless/resources/images/user-glow.svg);
background-size: 20px 20px;
background-position: left 13px;

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

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

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

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

#mw-content-container {
background: #36455C;

// #mw-content {
// background: #36455C;
// }
}

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

a {
color: #8197b8;
}

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

MediaWiki:Common.css

2026-07-05T05:05:31Z

Olive: media wiki button light background

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

body {
background: #1a212b;

#mw-header-container {
background: #1a212b;

#p-logo-text a {
color: #E5B91A;
}

#personal h2 {
background-image: url(/skins/Timeless/resources/images/user-glow.svg);
background-size: 20px 20px;
color: #E5B91A;

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

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

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

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

#mw-content-container {
background: #36455C;

// #mw-content {
// background: #36455C;
// }
}

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

a {
color: #8197b8;
}

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

MediaWiki:Common.css

2026-07-05T05:01:19Z

Olive: footer text color for real

MediaWiki:Common.css

2026-07-05T05:00:32Z

Olive: footer text color

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

body {
background: #1a212b;

#mw-header-container {
background: #1a212b;

#p-logo-text a {
color: #E5B91A;
}

#personal h2 {
background-image: url(/skins/Timeless/resources/images/user-glow.svg);
background-size: 20px 20px;
color: #E5B91A;

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

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

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

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

#mw-content-container {
background: #36455C;

// #mw-content {
// background: #36455C;
// }
}

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

a {
color: #8197b8;
}
}
}

MediaWiki:Common.css

2026-07-05T04:58:31Z

Olive: footer link colors

MediaWiki:Common.css

2026-07-05T04:55:38Z

Olive: Glow colors for header links

MediaWiki:Common.css

2026-07-05T04:45:27Z

Olive: Dark header and footer

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

body {
background: #1a212b;

#mw-header-container {
background: #1a212b;

#p-logo-text a {
color: #8197b8;
}

#personal {
h2 {
background-image: url(/skins/Timeless/resources/images/user-glow.svg);
background-size: 20px 20px;
color: #E5B91A;
}

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

#mw-content-container {
background: #36455C;

// #mw-content {
// background: #36455C;
// }
}
}

Main Page

2026-07-05T03:59:40Z

Olive:

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

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.

== Installation boilerplate ==
MediaWiki has been installed.

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

Main Page

2026-07-05T03:55:14Z

Olive: Olive moved page / to Main Page over a redirect without leaving a redirect

MediaWiki has been installed.

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

Main Page

2026-07-05T03:53:23Z

Olive: Olive moved page Main Page to /