Publish a mod for OpenDoctrines

Step oneSign in

The same account you use in the game. We never see your email address — what we store is a nickname and a one-way hash.

Step oneChoose a nickname

This is the name shown on your listings.

Nickname

Step twoThe guidelines

Step threeThe mod

Drop your .odmod here

or click to choose it — it is read locally and never uploaded

Mod id Reverse-DNS, from MANIFEST.json. It cannot change later. Version semver

Name One-line summary Shown on the card in the directory. Up to 160 characters. Description Optional. Plain text; line breaks are kept. Page about the mod Where someone reads about it — a repo, a forum thread, your site. This is what the directory links to. Download link Straight at the .odmod file. https only. SHA-256 of the .odmod Filled in from the file you dropped. It is what the security check is run against.

Gearbox API Where it runs From your manifest's "side". Shown on the listing, because it decides whether other players need your file too.

Capabilities it asks for From your manifest. Shown on the listing, because it tells people what the mod can reach.

Tags Comma separated, up to 8. Thumbnail URL Optional, https. 16:9 looks best.

Cancel

OptionalPublish from your release pipeline

A publish key lets a build server update this listing without a browser. It can publish and read your own listings — and nothing else: it cannot withdraw a listing, touch your account, or agree to the guidelines on your behalf. Treat it like any other CI secret.

Name a new key So you know which one to revoke later.

What to run

Built from the form above, so it already carries your details. The hash is computed from the file at release time — which is what makes this worth automating.

A changed file goes back into the review queue automatically, so a release appears once the check passes. Poll GET /mods/mine with the same key if your pipeline wants to wait for it.