Commands

NeroLink adds a single command tree, /nerolink, built with vanilla Brigadier so it behaves identically on every loader. Player sub-commands work for anyone; operator sub-commands require permission level 2 (game-master / op).

/nerolink pair#

Mints a single-use pairing code and whispers it — and only it — to the running player. Nothing is broadcast or logged. The whisper contains:

• Pairing code — format XXXX-XXXX, bold/gold. Valid for 5 minutes, single-use.
• Server ID — shown only when a relay registration is active; this is what players enter in the app alongside the code.
• Direct address — host:port for direct mode (the first site-local IPv4 and the configured port), tagged (same network - NOT the 'open to LAN' game port). Shown only when direct mode is reachable from the network (not when bound to 127.0.0.1).
• Security code — the first 16 hex digits of the bridge's TLS certificate fingerprint, as XXXX-XXXX-XXXX-XXXX, shown with the direct address. The app shows the same code; check they match before trusting the pairing.

If neither a relay nor a reachable direct listener is available, the whisper explains how to fix it (/nerolink setup, or singleplayerLanAccess=true in single-player).

Only a player can run this (it needs an in-game identity); running it from console fails with "Only a player can pair a device." If the bridge isn't running you'll see "The NeroLink bridge is not running on this server."

The in-game session is the identity proof — there are no passwords or emails. A client redeems the code once via the API to receive its device token. Repeated wrong codes are rate-limited per source (and server-wide during a flood); your code stays valid for its 5 minutes, so just try again a moment later.

/nerolink devices#

Lists your paired devices, one per line, as deviceName (deviceId). Tokens are never shown — only names and ids. Ends with a reminder to revoke with /nerolink revoke <device-id>. If you have none, it prints "No paired devices." Scoped to the calling player's own devices only.

/nerolink revoke <device>#

Revokes one of your own devices by its id (<device> is the device id from /nerolink devices). The bridge deletes the stored token hash and forgets the device's rate-limit bucket, so that device can no longer authenticate. Its live connection is closed immediately and, if a relay is set up, its push registration is removed (queued until the tunnel reconnects if it is down). If the id isn't one of yours it fails with "No such device of yours: <id>" — you can never revoke another player's device.

/nerolink status (op)#

Operator-only summary of the bridge:

[NeroLink] Bridge running. Paired devices: N. Relay: connected. Server ID: <id>. Modules: core, ...

• Paired devices — an aggregate count across online players (no personal data).
• Relay — connected, connecting, or disabled.
• Server ID — shown when a relay registration is active.
• Modules — the link modules currently registered (always at least core).

If the bridge isn't running it reports "Bridge is not running."

/nerolink setup [origin] (op)#

One-shot relay onboarding. Registers this server with a NeroLink relay (POST <origin>/register) off the server thread, persists the returned credentials per-world, and dials the tunnel immediately — no server restart.

• With no argument it uses the relayOrigin config value (default https://relay.nerolandmc.net).
• /nerolink setup <https-origin> registers against a specific relay origin.
• If this server is already registered with that origin, plain setup doesn't re-register — it just re-dials the existing tunnel and reports the stored Server ID.

On success the operator sees "Relay registered!", then the bold/gold Server ID (players enter this in the app), the App URL, and a Tunnel connecting — check /nerolink status hint. The secret serverKey is never printed or logged.

Failure messages are specific:

• Unreachable — "Could not reach the relay at <origin>…" (check the origin and the server's connection).
• Registration closed — "Registration is closed on this relay (REGISTRATION_OPEN=false)…" (ask the relay operator to reopen it).
• Bad response — "The relay returned an unexpected response…" (make sure the origin points at a NeroLink relay).

/nerolink setup force [origin] (op)#

Same as setup, but discards the stored credentials and registers afresh, producing a new Server ID even if a registration already exists. Use this to move to a different relay or rotate the registration. Optionally takes an [origin] (/nerolink setup force <https-origin>).

See also#

• Getting Started
• Relay
• Configuration
• Home