Going further
Extend your mod
Your own changes, on top of what Empire Forge builds.
Empire Forge covers what most civs need: tech trees, the bonus catalog, custom bonuses, unique units and techs. Some ideas are so specific to you that they are deliberately out of its scope – villagers can build rams, Petards garrison in rams, Outposts explode when destroyed, etc etc. You can still make them: build your civ in Empire Forge, then run a small script of your own on the finished mod. That's exactly how my Unhinged Empires mod adds its custom unique techs and second unique units.
This is the advanced route. Empire Forge itself needs no tools. This needs Python 3.11 or newer on your computer and some comfort with a terminal – or an AI code editor to do the typing for you. It can't harm your game install: you only edit your mod's own files, and the script keeps a copy of Empire Forge's original.
What you need
- A mod you built with Empire Forge, installed in your
mods/local/folder. - Python 3.11+ from python.org – on Windows, tick Add python.exe to PATH in the installer.
- genieutils-py, the library that reads and writes the game's data file:
pip install genieutils-py==0.1.2 - The template script and the modding notes – easiest is the repository's Code → Download ZIP.
- Recommended: an AI code editor (Claude Code, Cursor, GitHub Copilot, …).
Step by step
- Build and install your mod as usual.
- Find your civ's name in the data file. A custom civ keeps the name of the civ whose slot it
replaced – your civ in the Britons slot is
British. List them:python post_build_template.py "…/mods/local/MyMod-data" --list-civs - Try the example. As shipped, the template gives your civ's villagers +15 HP – the same
change Loom makes:
Start a skirmish with your mod as the data mod and check a villager's HP.python post_build_template.py "…/mods/local/MyMod-data" --civ British - Write your own change in the template's
apply_my_changes(). With an AI editor: open the template, paste the brief from the top of the file into the chat, then describe your idea. - Run it and test in game. Run it as often as you like – each run starts again from Empire Forge's original, so nothing applies twice.
- After rebuilding in Empire Forge, unzip the new mod over the old one and run your script again. It notices the new file and starts from it.
Briefing an AI
The brief at the top of the template points your AI at Empire Forge's modding notes – everything learned about the game's data file while building Empire Forge, written for exactly this. Then be specific:
Make my civ's Outposts deal 50 damage to nearby enemy units when destroyed. Find a vanilla unit that already damages things around it when it dies, and copy how it does it.
Ask it to explain what it changed and how to check it in game. If it can't find a similar example in the game already, treat that as a warning sign – the engine may not support the idea.
Rules that save you hours
- Copy something the game already does. Nearly every idea has a precedent in the data file.
- Find Empire Forge's techs by name, never by number – the numbers change between builds.
- Keep each effect under ~180 changes – the game crashes on load near 189.
- New text needs an existing text id – the game ignores brand-new ones. Reuse an id from your game's own strings file and put your text in your UI mod's strings file.
The full guide has the details, file locations and a troubleshooting table.
Sharing
Your mod is yours to publish; a mention of Empire Forge is appreciated. The template is GPL-3.0 like the rest of Empire Forge, so if you share your script, share it open source too.
Stuck, or have an idea that might belong in Empire Forge itself? Ask on Discord or open a GitHub issue.