The Muse - Recent changes [en]

Modding

Olive — Wed, 26 Aug 2026 21:49:14 GMT

Modkit: wording

← Older revision		Revision as of 21:49, 26 August 2026
(One intermediate revision by the same user not shown)
Line 5:		Line 5:
	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.		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~~].		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]

	~~Finally~~, ~~before getting started with~~ the ~~modkit~~, ~~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? ==		== Background — how do Godot mods work? ==

The Muse

Olive — Wed, 26 Aug 2026 21:41:31 GMT

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

← Older revision		Revision as of 21:41, 26 August 2026
Line 2:		Line 2:

	== Modding ==		== Modding ==
	* [[Modding EULA]]		* [https://lancertactics.com/modding-eula/ Modding EULA]
	* [[Modding\|Introduction to modding]]		* [[Modding\|Introduction to modding]]
	* [[Modding Cookbook]]		* [[Modding Cookbook]]

Modding

Olive — Wed, 26 Aug 2026 21:41:13 GMT

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

← Older revision		Revision as of 21:41, 26 August 2026
Line 7:		Line 7:
	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].		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]].		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? ==		== Background — how do Godot mods work? ==

Modding EULA

Olive — Wed, 26 Aug 2026 21:40:45 GMT

Olive deleted page Modding EULA Now hosted at https://lancertactics.com/modding-eula/

Modding Cookbook

Darloth — Thu, 06 Aug 2026 19:03:15 GMT

Make your mod: - thumbnail minimums

← Older revision		Revision as of 19:03, 6 August 2026
(4 intermediate revisions by the same user not shown)
Line 5:		Line 5:
	# Open it in the Godot editor (4.7 currently)		# Open it in the Godot editor (4.7 currently)
	# Go to Project Settings → Plugins and enable Mod Loader Dev Tool (it'll be the only thing that's unchecked)		# Go to Project Settings → Plugins and enable Mod Loader Dev Tool (it'll be the only thing that's unchecked)
	# There's now a tab call "Mod Tool" at the top-center of the window. Press the "Create new Mod" button, fill out the fields, and press Create.		# There's now a tab call "Mod Tool" at the top-center of the window. Press the "Create new Mod" button, fill out the fields, and press Create. Your mod will need to have at least 3 characters in both author and mod name, and it's best not to use any special characters aside from _ and -
	## See [[Modding#Mod Types & Security\|Mod Types]] for the difference between an Asset Pack, Content Pack, and Substantial mod. You can change what type it is later by adding scripts or toggling requires_restart.		## See [[Modding#Mod Types & Security\|Mod Types]] for the difference between an Asset Pack, Content Pack, and Substantial mod. You can change what type it is later by adding scripts or toggling requires_restart.<br> NOTE: If you wish to create an Asset Pack, there's currently a bug that will prevent it being created correctly unless you select a Content Pack first, then switch back to Asset Pack.
	# Fill out any information you'd like to provide in manifest fields~~, and press "Save to~~ manifest~~.json" in the top-right~~.		# Fill out any information you'd like to provide in manifest fields. The manifest should be automatically saved.
	# In the FileSystem window, you should see folder with the name of your mod under unpacked/, with a manifest.json and a mod_main.gd file.		# In the FileSystem window, you should see folder with the name of your mod under unpacked/, with a manifest.json and a mod_main.gd file.
	# (optional) Update thumbnail.png with the image you want to represent your mod.		# (optional) Update thumbnail.png with the image you want to represent your mod. The thumbnail should be in 16:9 ratio, and has a minimum size of 640x360 pixels.


	== Replace existing resources and scenes ==		== Replace existing resources and scenes ==
Line 54:		Line 53:
	# Modify the scene through the generated script's modify_resource function, as desired.		# Modify the scene through the generated script's modify_resource function, as desired.

	For example, to add the Barbarossa as an alt frame of the Napoleon license:		For example, to add the Barbarossa as an alt frame of the Napoleon license, find and Create Resource Extension for the li_napoleon.tres. In the resulting li_napoleon.tres_ext.gd file, you would put:

	func modify_resource(resource:Resource) -> Resource:		func modify_resource(resource:Resource) -> Resource:
Line 65:		Line 64:

	Note: modify_resource is run after resources are moved in the virtual filesystem from your mod's res/ directory into their res:// locations, so I believe that if you load new resources from your mod you should use their res://content/... paths instead of the unpacked location.		Note: modify_resource is run after resources are moved in the virtual filesystem from your mod's res/ directory into their res:// locations, so I believe that if you load new resources from your mod you should use their res://content/... paths instead of the unpacked location.

			To be safe, a function such as this can always return what should be the correct path:

			func sload(file: String):
			if(ResourceLoader.exists(file)):
			return ResourceLoader.load(file)
			else:
			return ResourceLoader.load('res://'+file.split('/res/')[1])

			Then use sload instead of load to load resource references.

	This will work even if two different mods extend the same resource.		This will work even if two different mods extend the same resource.


	== Modify existing scenes ==		== Modify existing scenes ==
Line 105:		Line 113:

	If you change an autoload, that autoload will be reloaded after all mods are applied.		If you change an autoload, that autoload will be reloaded after all mods are applied.

			If you find that the autoload's functions do not run your extended code, you may need to manually refresh the script of an autoload after your mod's mod_main._init() function. Example code that does this for the UnitRelation autoload is provided below, you'll need to adjust it to the specific autoloads that you're affecting.
			<pre>
			func _init() -> void:
			ModLoaderLog.info("Activating.", MOD_ID)

			LancerTacticsMod.add_translations(MOD_ID)

			LancerTacticsMod.add_overwrite_extend_mod_resources(MOD_ID)
			# other things might be here
			# ...
			call_deferred(&"fix_scripts")

			func fix_scripts():
			#print("fix UnitRelation")
			UnitRelation.set_script(load("res://engine/character/unit/service/unit_relation.gd"))
			</pre>

			WARNING: Due to unknown reasons, if a static function on an autoload calls other static functions on the same autoload more than two function calls deep, it reverts to the original code rather than the extended code. So far no workaround has been discovered.

	WARNING: Due to a bug in Godot, we can't extend scripts with a class_name. See [[Modding#Hooks and class name scripts\|Hooks and class name scripts]] for details.		WARNING: Due to a bug in Godot, we can't extend scripts with a class_name. See [[Modding#Hooks and class name scripts\|Hooks and class name scripts]] for details.


	== Replace existing scripts ==		== Replace existing scripts ==

The Muse

Darloth — Fri, 31 Jul 2026 17:07:42 GMT

Editors: - link to basics of module creation guide

← Older revision		Revision as of 17:07, 31 July 2026
Line 13:		Line 13:
	== Editors ==		== Editors ==
	* [[Module Editor]]		* [[Module Editor]]
			** [[Basics of Module Creation]]
	* [[Combat Editor Cookbook]]		* [[Combat Editor Cookbook]]
	* [[Editor Triggers\|Editor Triggers List]]		* [[Editor Triggers\|Editor Triggers List]]

Basics of Module Creation

Potatocubed — Fri, 31 Jul 2026 15:34:44 GMT

adding images

← Older revision		Revision as of 15:34, 31 July 2026
Line 80:		Line 80:

	<div style="clear: both"></div>		<div style="clear: both"></div>

	== Expositions ==		== Expositions ==
			[[File:A Sample Exposition Moment.png\|thumb\|How it looks in the editor...]]
			[[File:Exposition In-engine.png\|thumb\|...and in the game.]]
	Expositions allow you to display blocks of text for players to read, and also show them deliberate branching choices. Aside from the usual options expositions have:		Expositions allow you to display blocks of text for players to read, and also show them deliberate branching choices. Aside from the usual options expositions have:

Line 92:		Line 93:

	Note that although the button says 'add choice' you can totally have just one choice. This is useful for certain edge case scenarios where you need to chain two beats together but because you can't do that directly, you can put a quick exposition in between. If you never encounter this problem, don't worry about it.		Note that although the button says 'add choice' you can totally have just one choice. This is useful for certain edge case scenarios where you need to chain two beats together but because you can't do that directly, you can put a quick exposition in between. If you never encounter this problem, don't worry about it.
			<div style="clear: both">
	== Dialogues ==		== Dialogues ==
	I keep calling these 'chats' in my internal notes so you'll probably see me slip into that vernacular.		I keep calling these 'chats' in my internal notes so you'll probably see me slip into that vernacular.
Line 189:		Line 190:

	== Combats ==		== Combats ==
			[[File:A sample combat briefing moment.png\|thumb\|How it looks in the editor...]]
			[[File:Combat Briefing In-Engine.png\|thumb\|...and in the game.]]
	Much like with conversations, before you can add a 'combat briefing' moment to your module, you have to have a combat for it to brief you about. Head to those icons in the top-left, and the second one will take you to your (probably empty) list of combats.		Much like with conversations, before you can add a 'combat briefing' moment to your module, you have to have a combat for it to brief you about. Head to those icons in the top-left, and the second one will take you to your (probably empty) list of combats.

Line 206:		Line 209:

	'''Important:''' In theory the outputs from a combat can be linked to anything. In practice, at the time of writing, this doesn't work. '''A combat moment can only output directly to a beat.''' If you try anything else it'll go wrong. ''Yes, this includes endpoints''. Beats only.		'''Important:''' In theory the outputs from a combat can be linked to anything. In practice, at the time of writing, this doesn't work. '''A combat moment can only output directly to a beat.''' If you try anything else it'll go wrong. ''Yes, this includes endpoints''. Beats only.
			<div style="clear: both">
	== Congratulations ==		== Congratulations ==
	This is all you actually ''need'' to know to get a module up and running. Lancer Tactics' module editor has great testing features for conversations, and a playtest button on the metadata tab that lets you skip fights and deliver a win or loss outcome as you like.		This is all you actually ''need'' to know to get a module up and running. Lancer Tactics' module editor has great testing features for conversations, and a playtest button on the metadata tab that lets you skip fights and deliver a win or loss outcome as you like.

	For next steps, I would suggest learning about '''module states''', which let you track events which happen both at the module level and in combats within a module, and how to use them with '''branch''' moments to have the module start feeling more responsive. You can already respond to player choices through exposition scenes with choices added, but module states let you react to things in a more organic sort of way.		For next steps, I would suggest learning about '''module states''', which let you track events which happen both at the module level and in combats within a module, and how to use them with '''branch''' moments to have the module start feeling more responsive. You can already respond to player choices through exposition scenes with choices added, but module states let you react to things in a more organic sort of way.

File:Combat Briefing In-Engine.png

Potatocubed — Fri, 31 Jul 2026 15:33:23 GMT

Potatocubed uploaded File:Combat Briefing In-Engine.png

New page

A sample combat briefing as it appears in the game.

File:A sample combat briefing moment.png

Potatocubed — Fri, 31 Jul 2026 15:32:06 GMT

Potatocubed uploaded File:A sample combat briefing moment.png

New page

A combat briefing moment as seen in the module editor.

File:Exposition In-engine.png

Potatocubed — Fri, 31 Jul 2026 15:30:05 GMT

Potatocubed uploaded File:Exposition In-engine.png

New page

A sample exposition moment, as it appears when displayed in the game.

File:A Sample Exposition Moment.png

Potatocubed — Fri, 31 Jul 2026 15:28:48 GMT

Potatocubed uploaded File:A Sample Exposition Moment.png

New page

A sample exposition moment with all the optional bits filled in.

Basics of Module Creation

Potatocubed — Fri, 31 Jul 2026 15:06:09 GMT

First draft complete.

Show changes

First Module

Potatocubed — Fri, 31 Jul 2026 11:44:05 GMT

Potatocubed moved page First Module to Basics of Module Creation Got the name wrong when I created the page.

← Older revision		Revision as of 11:44, 31 July 2026
(One intermediate revision by the same user not shown)
Line 49:		Line 49:
	* '''Background''' lets you set something to display while the beat is... beating. You can noodle around with this to see what you can select, but the important thing is that files in your module's media folder have to start with "bg_" or they won't be selectable here.		* '''Background''' lets you set something to display while the beat is... beating. You can noodle around with this to see what you can select, but the important thing is that files in your module's media folder have to start with "bg_" or they won't be selectable here.
	The important thing to understand about beats is that they act as 'containers' for all the stuff that follows them. In practical terms this means that whatever background image you pick will be the background for any other elements connected to the beat (unless that element has a background of its own) and that if players have a chance to pause (e.g. at a combat briefing screen or between conversations) they will be able to go back and adjust their lancers based on the permissions granted by the kind of beat. So if you have a combat briefing after a full repair, they can go back and tune their builds specifically for that combat because they're still 'in' that full repair beat.		The important thing to understand about beats is that they act as 'containers' for all the stuff that follows them. In practical terms this means that whatever background image you pick will be the background for any other elements connected to the beat (unless that element has a background of its own) and that if players have a chance to pause (e.g. at a combat briefing screen or between conversations) they will be able to go back and adjust their lancers based on the permissions granted by the kind of beat. So if you have a combat briefing after a full repair, they can go back and tune their builds specifically for that combat because they're still 'in' that full repair beat.

			=== Back to the Module Editor, Briefly ===
			[[File:Module Editor Icons.png\|alt=A row of icons.\|thumb\|From left to right: beat, combat, exposition, dialogue, branch, receiver, trigger, endpoint.]]
			Take a look at the top of the module editor screen and you'll see a row of icons. These will create 'moments', which are the individual chunks of module you glue together to make a complete thing: in order left to right you'll see beats, combats, expositions, dialogues, branches, receivers, triggers, and endpoints.

			You've already created a beat (which technically isn't a moment, but a container for moments, but that doesn't matter right now). This tutorial will now cover the rest of them, in a different order to the way they're presented, and excepting triggers and receivers. Those are for more complex setups than this intro is meant to cover.

			=== Endpoints ===
			[[File:Endpoint Example.png\|alt=An endpoint moment connected to a beat in the module editor.\|thumb\|How it looks in the editor...]]
			[[File:An Endpoint In-game.png\|thumb\|...and in the game.]]
			The easiest one to explain. When you connect an endpoint, it creates an option in the attached beat to end the game and return to the main menu. ''They do not offer the user a chance to save their game''. Endpoints have no settings to tweak, and cannot be made to autoplay: they always provide the ''option'' to quit out but do not compel it.

	=== Expositions ===		=== Expositions ===

File:An Endpoint In-game.png

Potatocubed — Fri, 31 Jul 2026 11:32:26 GMT

Potatocubed uploaded File:An Endpoint In-game.png

New page

A screenshot of a beat showing the END option on the right.

File:Endpoint Example.png

Potatocubed — Fri, 31 Jul 2026 11:30:32 GMT

Potatocubed uploaded File:Endpoint Example.png

New page

An endpoint moment connected to a beat.

File:Module Editor Icons.png

Potatocubed — Fri, 31 Jul 2026 11:20:48 GMT

Potatocubed uploaded File:Module Editor Icons.png

New page

The row of icons at the top of the module editor.

First Module

2A00:23C6:9C78:8701:E155:E30:F12F:3F61 — Fri, 31 Jul 2026 11:18:41 GMT

@@ Line 36: / Line 36: @@
 * A '''custom''' seat requires the player to create a new character for the module, or load an already-created character. Note that if you've set a starting license level for the module and left the 'enforced' checkbox active, this new character will have to be in that level range. I don't ''think'' enforced LL applies to origin characters but I haven't checked.
 * And a '''flex''' seat can be an origin character or a custom one as the player sees fit.
 === Beats ===
-Okay, back to that beat you created.
+[[File:A Sample Beat 2.png|alt=A sample beat, as seen in the module editor.|thumb|How it looks in the editor...]]

File:My First Beat example 1.png

Potatocubed — Fri, 31 Jul 2026 10:14:06 GMT

Potatocubed uploaded File:My First Beat example 1.png

New page

Showing how beat number and name appear in-game.

File:A Sample Beat 2.png

Potatocubed — Fri, 31 Jul 2026 10:07:05 GMT

Potatocubed uploaded File:A Sample Beat 2.png

New page

A sample beat, as viewed in the module editor.

First Module

Potatocubed — Fri, 31 Jul 2026 10:05:40 GMT

← Older revision		Revision as of 10:05, 31 July 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	placeholder ~~while I do~~ other stuff		== Basics of Module Creation ==
			[[File:The module editor button.png\|alt=The module editor button from the Lancer Tactics main page.\|thumb\|The scary button.]]
			An informal walkthrough of how to get the basics of a module up and running.

			'''Remember:''' Any module you have downloaded can be opened in the module editor so you can see how it works. (This is true of combats also.) If there's a particular trick you liked and want to replicate, and you can't figure out a way to do it yourself, crack open the module you played and see how they did it.

			When you create a new module you'll need to give it a name. This will serve as a filename and also its identifier on mod.io if you ever upload it. Don't be scared to give your module a placeholder name, though -- when it's done you can use the 'save as' button to duplicate the whole thing under a more sensible name.

			Aside from that, remember that ''everything here can be changed later''. You don't have to get things right first time.

			=== First Time in the Module Editor ===
			[[File:New Module Screen.png\|alt=An image of the new module screen. Almost everything on the screen is greyed out, except for the 'new beat' button, which is aggressively highlighted.\|left\|thumb]]
			When you open the module editor for the first time, or when you click the 'new' button within it, this is what you're going to see. You'll note one button here is aggressively highlighted, which is the 'create beat' button. You need to click this first because modules are structured in beats which 'contain' all the other stuff. No container, no module. Anyway, click the button to get a beat into your module, then ignore it and look over at the left.

			==== Module Metadata ====
			I think this is metadata? I've never been super-certain about what metadata is. Anyway, this is where you put down all the details about your module. The key things you'll need to think about for a working module are:

			* '''Module Title.''' I don't think this is ''strictly'' necessary, but you should put something in here anyway.
			* '''Starting Beat.''' Players who fire up this module will start here. This is automatically set to the first beat you just created, but can be changed later. I found switching it around was really useful for bug-testing later on, but remember to change it back to your actual starting beat before release!
			* '''Starting License Level.''' What level range is this module meant for? At the time of writing I don't think this data is ''surfaced'' anywhere, but it's useful metadata anyway and you can enforce it to prevent players bringing LL12 demigods into a LL0 scrub module. Or not!
			* '''Lancers.''' This bit gets it's own subheading.

			===== Lancers =====
			Right now this module is for zero Lancers. I don't know what happens if you try to run a combat scene with no Lancers but it probably isn't good. You'll want to 'add seat' until you have the number of Lancers this module is for -- there's a maximum of four and, let's say, a practical minimum of one. If in doubt, go with four. Each Lancer with a 'seat' will be fully player-controlled during combats and level-ups. Lancer seats all have an index (0-3) which is how the game will refer to them in triggers, and are set to one of four states: flex, origin, custom, or fixed. To understand these, you'll need to know what an 'origin character' is.

			====== Origin Characters ======
			(Really testing how low the sub-headings can go on MediaWiki here.)

			An origin character is basically a fixed NPC that can join the player's squad and can level up and such. The distinction between them and 'module NPCs' is that origin characters can level up, that level up is controlled by the player, and they have the full range of PC level up options. They have consistent portraits, and are easy to refer to in triggers, so they fill the role of NPC squadmates who have consistent characters throughout the storyline. A module can have as many origin characters as you like, and there are triggers which can add and remove them, but I'm not getting into that in this tutorial.

			====== Lancer Seats ======
			So, back to Lancer seats.

			* A '''fixed''' seat is set to a particular origin character for your module. When a player fires up this module, that seat will always be filled with that character.
			* An '''origin''' seat requires the player to pick an origin character from the list your module contains, but could be any of them.
			* A '''custom''' seat requires the player to create a new character for the module, or load an already-created character. Note that if you've set a starting license level for the module and left the 'enforced' checkbox active, this new character will have to be in that level range. I don't ''think'' enforced LL applies to origin characters but I haven't checked.
			* And a '''flex''' seat can be an origin character or a custom one as the player sees fit.

			=== Beats ===
			Okay, back to that beat you created.

File:A Sample Beat.png

Potatocubed — Fri, 31 Jul 2026 10:03:59 GMT

Potatocubed uploaded File:A Sample Beat.png

New page

A beat, as viewed in the module editor.

File:New Module Screen.png

Potatocubed — Fri, 31 Jul 2026 09:22:34 GMT

Potatocubed uploaded File:New Module Screen.png

New page

The opening screen when you create a new module.

File:The module editor button.png

Potatocubed — Fri, 31 Jul 2026 09:16:20 GMT

Potatocubed uploaded File:The module editor button.png

New page

The module editor button from the Lancer Tactics main menu.

User:Potatocubed

Potatocubed — Fri, 31 Jul 2026 09:12:51 GMT

User account Potatocubed was created

First Module

2A00:23C6:9C78:8701:E155:E30:F12F:3F61 — Fri, 31 Jul 2026 09:12:22 GMT

page created

New page

placeholder while I do other stuff

User:Abrukt

Abrukt — Thu, 30 Jul 2026 09:36:21 GMT

User account Abrukt was created