Submit a mod
Finished a mod? Packaging goes through Depot however you built it — with the Mod SDK in code, or with the Mod Kit and the rest of the suite. From there you have two ways to get it out: one for the official, signed library, and one for keeping it entirely your own.
✅ Submit for review
The route into the official mod library. You package it in Depot and send it to us; we review it, cryptographically sign it, and publish it so it installs cleanly in the Hub and auto-updates.
📦 Publish locally
Just want the packaged mod for yourself, to share directly, or to run in a third-party loader? Hit Publish Locally in Depot. It writes an unsigned package to a folder — no review, no account, nothing sent to us. The official Hub won't load unsigned mods (that's the point), but any loader that accepts them will.
How review works
- Package — in Depot, open your mod and choose Submit for Review. It builds the
.mod.zipand opens the submission form with your mod's details pre-filled. - Attach & send — drag the
.mod.zipinto the issue (or link it) and submit. A GitHub account is all you need. - Review — we check it does what it says, works in-game, and carries no malicious code.
- Sign & publish — we sign it with the AshForge key and push it to the library. From then on it installs and updates through the Hub like any first-party tool.
Why we sign — and why Depot never does
Signing is what lets the Hub trust a mod. The signing key lives with the AshForge team and never ships in any tool, so Depot can package and submit, but it can never sign or upload to our infrastructure itself. That keeps the library trustworthy: every mod in it was reviewed by a person. Publishing locally is the deliberate escape hatch for everyone who doesn't want or need that — your mod, your rules.
Haven't built one yet? Writing code — start with the Mod SDK. Building content — start with the Mod Kit. Either way you end up back here, at Depot.