TokyoNocturnMinecraft

Connecting to the server

  1. Start Minecraft 1.8.8 or 1.8.9 with a premium (paid) account. The server is online-mode=true.
  2. Multiplayer → Add Server → address livedaw.store. Port 25565 is resolved through the SRV record, so do not add a port.
  3. If your client shows "Unknown host" or ignores SRV, use livedaw.store:25565, or the direct host mc.livedaw.store:25565.

On a phone or tablet? Bedrock apps cannot join a Java server directly. See Mobile & Bedrock for the route that works today (the Java 1.8.8 client on Android/iOS) and what a Bedrock bridge would require.

Which versions work

The server speaks the 1.8.8 protocol (47). Newer clients are refused by the vanilla protocol check. The optional TokyoNocturn mod set lives on a separate 1.21.11 Fabric profile and never changes the version you join with.

Installing the client set (optional)

  1. Download the Fabric Installer and choose Minecraft 1.21.11, loader 0.20.1. This creates a new profile and leaves existing profiles untouched.
  2. In %APPDATA%\.minecraft\mods, place the TokyoNocturn Servers browser mod — it needs Fabric Loader and Java 21, and no Fabric API. Add fabric-api plus mouse-tweaks and zume only if you want those extras; ksyxis works without Fabric API.
  3. Place SmoothFont_1.21.zip in resourcepacks\, not mods\, then enable it in Options → Resource Packs.
  4. Launch the profile and use the TokyoNocturn Servers button on the title screen to see live status and join.

All mods are client-side. The server does not require any of them and will not kick you for using or skipping them.

Running the server software

  1. Install Java 8. Paper 1.8.8 cannot run on Java 17+; the launcher will exit immediately with an UnsupportedClassVersionError.
  2. Download paper-1.8.8.jar from the download center and start it once to generate the world and configuration.
  3. Drop ProtocolLib-4.8.0.jar and DawGuard-1.0.0.jar into plugins/, then restart.
  4. Allow TCP 25565 inbound and forward it to the host. For DNS, use an A record (DNS only) plus an _minecraft._tcp SRV record pointing at it.

Start command used in production:

java -Xms8G -Xmx8G -XX:+UseG1GC -jar paper-1.8.8.jar nogui

Status API

A small JSON API powers both this site and the in-game browser. It answers from a short cache so a page refresh never hammers the server.

GET /api/status            → the primary server
GET /api/status?server=ID  → one configured server
GET /api/servers           → every configured server
GET /api/downloads         → download manifest with sizes and SHA-256
GET /healthz               → liveness for the reverse proxy

Example response (values are real, taken from the server's status packet):

{
  "id": "livedaw",
  "name": "livedaw.store",
  "address": "livedaw.store",
  "online": true,
  "players": { "online": 0, "max": 50, "sample": [] },
  "motd": "LIVEDAW » 1.8 PvP | Anti-Cheat | 50 Slots",
  "version": "1.8.8",
  "latencyMs": 1,
  "checkedAt": "2026-11-09T20:31:07.412Z",
  "stale": false
}

Semantics

  • online:false means the server did not answer a status request. players is null in that case — the API never reports zero players for an unreachable server.
  • latencyMs is the round trip measured from the hub to the server, not from your browser.
  • stale:true means a refresh failed and the last good value (under two minutes old) is being served.
  • Responses are cached for 10 seconds and rate limited per client. Backend host and port are never exposed.

Troubleshooting

  • Connection refused / timed out — the server is down or the router forward for TCP 25565 is missing.
  • Unknown host — your client is not resolving the SRV record; use livedaw.store:25565.
  • Kicked for cheating — DawGuard flagged movement that its vanilla model cannot explain. Ask in Discord with the timestamp.
  • Status shows offline while you are connected — the status request uses the same port; check that your client is not connected through a proxy that blocks it.