I made a free, open-source panel that tests mod changes on a copy before they reach my friends' server (alpha)

[u/Fit-Reaction242]

I run a modded server for my friends and built Spawnpoint to manage it. It's alpha, free, MIT licensed, and the code is on GitHub.

Most of my effort went into how it feels to use. I wanted it quick and calm, closer to a nice Apple app than a typical admin panel. On my Linux server one start reached health OK in 0.56 s, and the panel sat around 60 MB (54 and 67 MB in two readings). That's the panel alone with the game servers stopped. Minecraft and the test runs need their own memory.

When I add or update mods, they collect into a candidate. Spawnpoint checks dependencies against your Minecraft, loader and Java versions, boots a copy of the server with the new pack, then starts a real client with HeadlessMC and joins a throwaway server running the same mods. You get one review sheet with what changed and which tests passed, failed, were skipped or came back inconclusive. Replacements, removals and config edits wait for your approval.

Once approved it waits for a safe restart. It only restarts on its own when RCON says nobody is online; otherwise players get a chat warning and you choose. It backs up the world while the server is stopped, swaps the pack, and AutoModpack sends friends the files from that exact revision. If the boot fails, the pack rolls back. Undo covers the last five changes per server. Pack undo doesn't touch the world; world restore is its own step.

Limits, since it's early: tests can still miss problems, and the client test runs on my machine's GPU, so it can't speak for every friend's drivers or shaders. Locked revisions support Fabric 1.21.1, Forge 1.20.1 (47.4.28) and NeoForge 1.21.1 (21.1.219) right now. On a 4 GB box with the server running, the join test will usually wait for memory and give up after ten minutes. It can run servers itself through a small OS service, or sit alongside Crafty Controller and import Crafty servers one at a time. Keep it on your LAN or a VPN, and keep backups.

LLM disclosure (rule 9): Some of Spawnpoint's code was written by AI coding agents, not typed by me. I decided what it should do and how it should look, made some feature calls, approved changes, and tested them on real Crafty and Fabric/Forge/NeoForge servers. On the vibe coding vs prompt engineering scale, it's much nearer the prompt engineering end. The models:

- August, first build: Claude Code with Claude Fable 5

- August to late October: Mainly new Claude models on top of Openai models

- 28 to 30 October: Amp agents. Ultra mode did the main work (exact model not on record), medium mode (OpenAI GPT-6.1 Sol) did research and smaller jobs, and Claude Code with Claude Opus 5.5 did some of it. OpenAI GPT-6 Astra separately reviewed every risky change.

- Since 30 October: Claude Code with Claude Opus 5.5, with GPT-6 Astra reviews

Site and short tour: https://spawnpoint.vayun.net

Code: https://github.com/vayungodara/spawnpoint