How it runs

Ice Link Valley lives on a single machine called Ice Link — the same quiet box that hosts the wiki and this site. It isn't a rented panel or a big cloud instance; it's a small dedicated server with one focused job, and it does it well.

The world runs on Purpur 26.2 (Java Edition 26.2, on Java 25) — an optimized fork of Paper that keeps gameplay vanilla while staying fast and stable. The whole stack is containerized with rootless Podman, managed as systemd quadlets, so the service starts with the machine and updates itself on a schedule. That's why the server rarely needs a manual nudge.

• Game: Purpur 26.2, on Java 25
• Image: itzg/minecraft-server
• Runtime: rootless Podman, systemd quadlet
• Host OS: Rocky Linux, SELinux enforcing

• Ice Link bare-metal host — a 6-core / 12-thread Xeon with roughly 30 GB of RAM and a couple of hundred GB of disk to spare.
• The Minecraft container is allowed up to 16 GB of that RAM.
• The world is pre-generated ahead of play with Chunky, so terrain loads smoothly as you walk instead of stuttering into existence.

• ``25565`` / TCP — Java Edition
• ``19132`` / UDP — Bedrock Edition, via Geyser

The remote console (RCON) is off, and the server runs with online-mode, a whitelist, and secure profiles enforced. Ice Link is on the public internet, so it's set up with the quiet assumption that port scanners will knock on the door from time to time, and answered accordingly.

A deliberately modest set of plugins handles the details — permissions, block logging, the economy, seasons, fishing, pets, and the live map — and a set of datapacks shapes the world itself. Plugins and The world carry the specifics. None of it changes the game at its core; it's all there to make the world worth coming back to.