Publishing

Players can only install addons that we reviewed and signed. Here is how your addon gets into the store.

1. Developer access

Submitting needs developer access on your LynxClient account. Your account is your Minecraft account, there is no separate sign-up. Ask for access on our Discord and tell us your Minecraft name.

2. Submit

In the launcher: Addons → For developers → Choose project… and pick your project folder.

• Only the source code is uploaded: src/main/java/**/*.java and src/main/resources/ (json, png, txt, properties, md), at most 2 MB zipped.
• Enter the version (taken from build.gradle.kts when it says version = "…") and what is new.
• Every new version needs a higher version number. A version whose build failed or that was rejected can be submitted again with the same number.

3. Build and review

1. We build your addon ourselves, against the Lynx API only, on a separate build server without network access. Your build.gradle is not used, and annotation processors are off.
2. A scanner checks the source and the compiled code for network access, starting programs, loading code at runtime, reflection, file access and obfuscation. You see its findings under Your submissions.
3. We review the addon. For updates we look at the changes since the last published version.
4. If it is fine, we sign the jar and publish it. If not, you see the reason under Your submissions and can submit a fixed version.

Findings of the scanner are not automatically a rejection. A file access can be fine when it is clear why. Explain unusual things in What's new.

4. Published

• Players find your addon in the launcher (Addons) and in game (mod menu → Addons). The store shows your LynxClient account as the developer.
• Updates reach players automatically: the launcher installs the newest version before the next start.
• We can withdraw a version or block an addon if it breaks the rules. Launchers then remove it from every player's addon folder.

States

State	Meaning
Queued	Waiting for the build server
Building	Being compiled and scanned
Build failed	Did not compile, see the build log
In review	Built, waiting for our review
Published	Live in the store
Rejected	See the note for the reason
Revoked	Withdrawn after publishing