01
Account
A name, a password, and an API key. The profile is yours: name, text, color, links, avatar, and banner.
unofficial registry
Horizon mods that get checked before they ship
An account, a file, an automatic archive pass, then a person in the queue. The launcher fetches index.json and asks what to update.
- 01modsafter release
- 02updatessemver
- 03reviewbefore publish
02
Review before release
Archive, manifest, and file boundaries. The mod stays out of the index until a reviewer agrees.
03
Auto-update
The installed version is compared with the published one. The reply says whether a newer file exists.
04
API and limits
The same registry for scripts: a key, quotas, and HTTP 429 when the pace is too high.
How a file moves
- The mod page stores the id, license, and source.
- The zip is read from its central directory: paths, sizes, forbidden types.
- The manifest is checked against the page and the Horizon rules.
- If an external program is configured, it runs separately. Otherwise the reviewer explicitly accepts the static check.
- After publish, the launcher sees the file in the index and at /api/v1/updates.
Recent releases
No published mods yet. The empty list is honest: only files that passed review show up here.