Documentation — NoderaMC
Three reading paths: get playing, run a service, or build on the protocol. Start where you are.
NoderaMC is not a mod you drop in a folder, and pretending otherwise wastes your first hour. It needs a companion app running beside the game, every player in a world runs the mod, and the thing that makes it interesting — that the world keeps existing after you close Minecraft — is worth understanding before you install anything. The first path below is written to be read in order.
Play it
Start at the top and read down. Four pages, about twenty minutes.
- What NoderaMC is
Regions, committees, and what this is not.
- Install
The app first, then the mod. In that order, and here is why.
- Share a world, and join one
Both ends of the same session.
- Play with no mod installed
The tunnel, for the friend who will not install anything.
- When the host leaves
Why the world does not end when you close the game.
Run a service
A tracker or a relay. Neither holds authority over anyone's world, which is what makes running one a small decision.
- Why run one
What a service can and cannot do.
- Run a tracker
The image, the configuration, what to watch.
- Run a relay
NAT introduction and circuit fallback.
- Publish a service list
Get yours in front of people.
Build on it
The three documents that are normative, mirrored from the repository so they cannot drift from it.
- Start here
Where the code is and what the gate is.
- Wire protocol
The NDR2 frame and how two builds negotiate.
- Engine SDK
The deterministic region engine's surface.
- Mod compatibility
What another mod may do inside a validated region.
Two things to know about these pages
Pages marked mirrored are the repository's own documents, served here verbatim rather than summarised — a summary is a second copy that starts being wrong immediately. Everything else is written for this site and its capability claims are checked against the repository by the build.
Where the build stands is the index of what does not work yet: every open limitation, the task that owns it and the test that retires it.