Spawnpoint

The self-hosted Minecraft control panel where a broken pack can never reach your friends.

Click the image to watch the 2-minute launch film (9 MB mp4). A broken jar gets dragged in, boot-tested, and rolled back before anyone crashes. Then modpack installs, backups, and the in-game genie, all captured live.

Spawnpoint is a web panel you run on the machine that hosts your Minecraft servers. It fronts Crafty Controller (which owns the server processes) and adds everything around it: one-click mod/plugin installs from Modrinth + CurseForge, a config UI, Realms-style world slots, backups, and a verification pipeline no other panel has:

1. Dry-boot preflight. Every mod install is boot-tested in a sandbox before it counts. Missing dependencies are detected from the loader's own error output and installed automatically. A mod that still can't boot is rolled back, not left to crash the next restart.
2. Headless client boot test. The pack is launched in a real headless Minecraft client, so client-side crashes are caught server-side.
3. Multiplayer join gate. A throwaway clone of your server is booted and a real client actually joins it. If the join would kick your friends, you find out first.
4. Join-kick self-heal. When a gate identifies the offending mod, it is quarantined, the pack regenerates, and the gate re-runs. You get a notice, not a broken evening.

Optional extras: an in-game AI "chat genie" (bring your own Anthropic API token) that executes natural-language wishes over RCON and is engineered to never claim success it can't verify, AutoModpack-based client sync so friends never manage pack files, TPS monitoring, a web file manager, scheduled restarts, and a storage cleaner.

Screenshots

Requirements

• Node.js 22+
• Crafty Controller managing your servers
• Any OS. On headless Linux the client/join gates run invisibly under xvfb. On macOS/Windows (or a Linux desktop) the verification client opens as a small window for a few minutes instead: same real client, same verdict. A box with no display at all skips those two gates with an honest "not verified" verdict; the server-side dry-boot always runs.

Quick start

Install Crafty Controller first — Spawnpoint manages your servers through it. Then:

curl -fsSL https://raw.githubusercontent.com/vayungodara/spawnpoint/main/install.sh | bash

That checks Node 22+, creates the layout, builds, starts the panel on port 25570, and prints the URL. Your first browser visit is a three-step wizard: connect Crafty by pasting a Crafty API key (best from a dedicated non-superuser account scoped to the servers this panel should manage, so Spawnpoint never holds anything that could unlock your admin account; or log in once and it mints a token for you), set a PIN, and optionally add keys. Java itself is zero-touch: the right Temurin JDK downloads automatically the first time a server needs one.

API keys required: none. Modrinth browsing, dependency healing, boot testing, and client sync all work key-free. Optional: a free CurseForge key (adds their catalog) and an Anthropic key (enables the in-game genie).

Manual install instead

git clone https://github.com/vayungodara/spawnpoint
cd spawnpoint
npm ci
npm run build
SPAWNPOINT_ROOT=/path/to/your/layout node server/dist/index.js

SPAWNPOINT_ROOT points at the directory containing Crafty/servers, Shared/, Tools/, and Spawnpoint/ (see Layout below). The first-run wizard appears in the browser either way.

Architecture

The full system design (the four verification gates, their invariants, the genie, client sync) is documented in ARCHITECTURE.md.

Layout

• server/ — Fastify + TypeScript API; serves the built web app on :25570
• web/ — Vite + React + Tailwind frontend (pixel-art design system)
• data/ — all runtime state and secrets (settings, ledgers, session secret). Never committed.

Configuration (data/settings.json)

Created on first run. Notable optional fields:

• pinHash: set a PIN from the Settings page to gate remote access (localhost always bypasses; sessions are HMAC-signed cookies)
• curseforgeApiKey: enables the CurseForge half of the content browser
• vercelToken + laneDomain/laneSrvTarget/laneRelayIp/laneBoxIp: optional "public lane" provisioning. Each server automatically gets a <name>.<your-domain> address via a relay droplet + Vercel DNS SRV records. Leave unset and servers are LAN/Tailscale-only.
• modrinthContact: contact string appended to the Modrinth User-Agent

Development

npm run dev:server   # API on :25570
npm run dev:web      # Vite dev server, proxies /api

Security notes

• Designed to sit behind Tailscale or a LAN. Do not expose the panel port to the open internet.
• Remote access is PIN-gated (hashed at rest, per-IP lockout, signed session cookies). The genie has a commandPolicy setting: no-admin blocks op/whitelist/ban-class commands for installs where wish access isn't fully trusted.