Rules,
short and enforced.
These are the rules we use to accept, test and remove a pack. They are also the reason a card can say “solo only” before you download it.
What belongs in the catalog
A pack is a manifest, not a folder of files. Every mod in it must exist in Horizon's public registry, with a version and a SHA-256 that the launcher can check.
We do not host mod files. The catalog stores ids, versions, licenses and hashes; the launcher downloads the file from the registry or the author's release page.
Packs that depend on a private registry, a modified client, or a session server we do not control are not accepted.
The manifest
The pack must install from a clean profile without manual edits. If it needs a config file, that file goes in overrides and is described on the pack page.
Use exact versions. A range that silently moves to a newer mod is not a pack; it is a bug report waiting to happen.
Include the license of every mod, keep the credits, and do not relicense someone else's work.
Conflicts and pins
Two mods from the same cluster (two maps, two recipe viewers, two HUD editors) do not go in one pack. Pick one and write down why.
Native mods pinned to a Horizon commit count. Two pins is the normal ceiling; three is allowed only for a kitchen-sink pack and is printed on the card.
A pack that leaves a mod out during the native build must say which mod and why. We would rather ship a smaller pack than a silent one.
Licenses
Every mod keeps its own license. Non-commercial mods stay non-commercial: no paid pack, no ad-gated download, no crypto.
If a project is revoked by its author, the pack drops it. We do not keep a copy around to avoid the change.
A pack page lists every license. If you reuse a manifest, keep that list intact.
Servers
Server-safe is a flag, not a marketing word. Packs built for single-player or LAN say so, and a server owner can still reject a client mod.
Cheats that lift server checks (X-Ray, Baritone, seed crackers, movement exploits) are excluded from every public pack. One single-player speedrun pack says it is solo/LAN on the card.
Review and revocation
We install the pack, build the native mods and launch it before listing. A pack that fails the build is not published with a note; it is fixed or rejected.
A listed pack can be updated or revoked. Revocation is visible on the card, and the launcher stops offering the version.
If you find a problem in a pack, write to hello@xhorizon.me with the pack id and the log. That is faster than a comment.
Ready to send one?
The form builds an email with the fields the review queue will use. Attach the .hpack or paste a link.