Publishing to Core Prime
Checking a package, offering it to the content library, how a release appears in the catalogue and in every player's Library, and how to run a registry of your own.
Check the package first
oa-tool check reads a package as the game would and reports what it found: the manifest's verdict, every map's fit against the base game, and for a mod the hacks and limits it declares.
$ oa-tool check my-maps.oamap $ oa-tool check escalation.oamod --game ~/Games/TA
A package the tool refuses is refused by the game too, so fix it before offering it.
Offer it to Core Prime
Core Prime's content library is published from a maintainer's machine: the catalogue is signed with a key that never leaves it. To have a package listed:
- Open an issue on the Open Annihilation repository with the package file (or a link to it), its author and licence.
- A maintainer runs the checks against every mod and game folder and adds it to the library's package records.
- The next publish uploads the file by its hash, signs the new catalogue and raises its sequence.
- Minutes later it is in every player's Library and on this site.
Running a registry of your own
A registry is a descriptor (.oareg) a player adds to the game, a signed catalogue, and the package files it names, served over HTTP. The engine docs describe the descriptor, the catalogue and its signature, the download API and mirrors.
An unsigned registry is only for Developer Mode on 127.0.0.1; a public one signs every catalogue.