Home

NeroLink Wiki

Player-, admin- and developer-facing documentation for NeroLink, part of the Neroland ecosystem. Built on Neroland Core.

NeroLink is a server-side bridge mod. It embeds a small HTTP + WebSocket server so companion clients can check on a Neroland server while you are away — progression and energy at a glance, alerts, and a small set of safe, server-validated actions. It is a window, not a controller: it never edits the world, never moves your player, and does nothing you couldn't do standing at the relevant block in-game. NeroLink adds no blocks or items.

Status: alpha (version 0.0.1-alpha.1), built on Neroland Core 2.0.0+ across the six cross-loader cells (Fabric, Forge, NeoForge on Minecraft 26.1.2 and 26.2). The v1 bridge is implemented: pairing and device tokens, capability discovery, per-module snapshots, safe actions, live WebSocket deltas, privacy endpoints, and outbound relay access for servers behind NAT. Every other Nero mod is a progressive enhancement, discovered at connect time — a Core-only server is already useful.

Companion clients are the official Neroland companion app (coming soon) and anything else that speaks the NeroLink API. NeroLink itself ships no HTTP server behaviour beyond this bridge.

Contents

• Getting Started — install, LAN/direct quickstart on port 25580, and one-command remote access via the relay.
• Commands — the full /nerolink tree: pair, devices, revoke, status, and setup.
• Configuration — every key in nerolink.properties, with defaults and whether a change needs a restart.
• Relay — how the outbound tunnel reaches phones with no port forwarding, Server IDs, and self-hosting the relay Worker.
• API — for client and tool developers: base URLs, the envelope, auth, routes, the built-in core module, actions, the WebSocket protocol, and errors.
• Privacy — what the bridge stores, own-data-only scoping, erasure/export, and telemetry.

See also

• Build & contributor context
• Ecosystem overview
• This mod's planning docs