Store rules

Addons run on players' PCs. These rules protect them and keep addons working on every Minecraft version.

Technical

• Use only the Lynx API (net.lynxclient.api.*). No Minecraft classes, no LynxClient internals (net.lynxclient.core.*).
• Exactly one entry point: "lynx" in fabric.mod.json. No other Fabric entry points, no mixins, no access wideners, no bundled jars.
• No classes in packages that are not yours (java.*, net.minecraft.*, com.mojang.*, net.fabricmc.*, net.lynxclient.* …).
• No libraries besides the Lynx API for now.
• Keep it light: no heavy work or allocations every frame. Use the HUD cache (stateHash).

Privacy and safety

• No access to login data of Minecraft, Microsoft, LynxClient or anything else.
• No sending data off the PC without the player clearly agreeing to it in your addon's settings, and never personal data.
• No reading or changing files outside what your addon clearly needs.
• No starting programs, no downloading or loading code at runtime, no obfuscation.
• No features that give an unfair advantage in multiplayer (no cheats, no automation that servers forbid).

Content

• Name, description and texts must describe what the addon really does.
• No ads, no offensive content, no impersonating LynxClient or other developers.
• Respect licences of anything you include (images, code).

Breaking these rules leads to rejection, withdrawal of published versions and, for clear abuse, losing developer access.