Safehouse Lab
Modding has an image problem. It gets filed somewhere near fan art — a hobby, adjacent to the real work. Anyone who has actually shipped one knows better. A mod is engineering performed inside a system you did not design, cannot change, and do not own, against documentation that is frequently the source code and the forum.
It is one of the most honest technical exercises available, and the etiquette around it is as much a part of the discipline as the code.
You are working without the usual escape hatches
In normal software, when the platform fights you, you change the platform. A mod has no such move. The engine is the engine. If the thing you need is not exposed, your options are to find a seam, to find someone who already found one, or to want something else.
This produces a specific kind of engineer. You read before you write. You learn the system's own idioms instead of importing yours. You build the smallest thing that can work, because every extra surface is another place the next patch can break you — and there will be a next patch, and it will not be announced to you.
Our current work is a mod for X4: Foundations, a space simulation with an unusually deep economy and an unusually open scripting layer. It is in development and not released. The interesting part has not been the features; it has been learning where the seams are, and which ones are safe to lean on.
Stand on the shoulders, and say whose
Almost no serious mod is built from nothing. Communities around long-lived games produce shared tooling — frameworks, API layers, loaders — maintained for years by people who are not paid for it. Our own work depends on the community Mod Support APIs by SirNukes, and that dependency gets named every time, in the readme, on the page, here.
Crediting is not politeness. In a modding community the shared tooling is the infrastructure, and infrastructure that nobody credits is infrastructure that stops being maintained. The person who built the layer you rely on finds out whether it mattered by whether anyone says so.
The part people get wrong
Here is the line that matters most, and it is not technical.
You are a guest. The world belongs to the studio that made it. They spent years and real money building the thing your work sits inside, and your mod exists because they chose to allow it — most publishers do, many formalise it, and a few do not allow it at all.
So the rules are simple, and we keep them whether or not anyone is checking:
- Do not put the game's name or marks on your work as if it were yours.
- Do not ship their files. Build something that loads alongside, not something
- Do not monetise someone else's game. No paywalls, no early access tiers, no
- Say plainly that you are unofficial and unaffiliated.
None of that is a legal reading and this is not legal advice. It is the posture we think is right, and it has a practical edge too: a project that plays by those rules is a project a studio has no reason to shut down.
Free, and open, on purpose
Ours will be free, forever, and open source at launch. Not as a marketing position — as the only arrangement that is consistent with the paragraph above. If the world is not ours, the thing we built inside it should not be something we charge rent on.
The work still pays for itself. It pays in what it teaches, and it happens live on stream, which is its own kind of return.