logo1
GSD Skill Creator
Minecraft Server

Documentation > Specialized Systems > Minecraft Server Management

Guide IDSS-4
AudienceSysAdmins, Teachers, Students
PrerequisitesGS-1: Installation, basic Linux administration
Time20 minutes
DifficultyIntermediate

Minecraft Server Management

Minecraft server management in gsd-skill-creator combines game server operations with educational infrastructure. The Den provides the hardware platform, the provisioning scripts configure the VM, and knowledge packs connect in-game activities to structured learning objectives. This guide covers Fabric server deployment, RCON remote management, the quiesced backup system, monitoring integration, and how Minecraft connects to the educational curriculum.

Server Deployment

The Minecraft server runs on a Fabric modding platform, chosen for its lightweight footprint and compatibility with server-side performance mods. Deployment uses the Den's VM provisioning system to create a dedicated virtual machine with resources allocated from the hardware budget.

The resource budget (infra/local/resource-budget.yaml) dedicates a specific allocation to the Minecraft VM -- typically 16 GB RAM, 1 CPU core, and 50 GB storage. This allocation is computed from the host's total hardware capabilities, ensuring the game server never starves the host OS or other workloads. The budget calculator classifies the deployment tier (minimal, adequate, comfortable) based on remaining headroom after all allocations.

Fabric Server Setup

The server setup process installs Fabric Loader, configures JVM arguments for the allocated memory, and deploys server-side mods. The client-side configuration is managed through Prism Launcher instances stored in minecraft/client/prism-instance/, which synchronize mod lists with the server to ensure compatibility. Mod management includes version pinning, update checks, and rollback capabilities through the backup system.

RCON Management

Remote Console (RCON) provides command-line access to the running Minecraft server without joining as a player. RCON is used for all automated server management: sending chat messages, managing whitelists, executing server commands, and critically, coordinating with the backup system. The RCON connection is authenticated with a password stored in the server's local configuration (gitignored), and access is restricted to the local network to prevent remote exploitation.

Backup System

The backup system uses RCON quiescing to ensure data consistency. Before each backup, the system executes a three-step protocol through the RCON connection:

  • Step 1: save-all -- Forces the server to write all pending world data to disk, ensuring no in-memory changes are lost.
  • Step 2: save-off -- Disables automatic saving, preventing the server from modifying world files during the backup copy. Players can continue to play; changes accumulate in memory.
  • Step 3: Backup copy -- The world directory is copied to the backup location while the server's disk state is frozen.
  • Step 4: save-on -- Re-enables automatic saving. Accumulated in-memory changes are written to disk on the next auto-save cycle.

This quiescing protocol produces consistent backups without server downtime. Players experience no interruption -- the only observable effect is a brief pause in auto-saving.

Backup Rotation

Backups follow a 24/7/4 rotation scheme:

  • 24 hourly -- One backup per hour, retained for 24 hours. Provides fine-grained recovery for recent issues (griefing, accidental destruction, mod conflicts).
  • 7 daily -- One backup per day (the last hourly backup of the day), retained for 7 days. Covers medium-term recovery for issues discovered days later.
  • 4 weekly -- One backup per week (the last daily backup of the week), retained for 4 weeks. Provides long-term recovery for fundamental issues like world corruption or major mod incompatibilities.

Expired backups are pruned automatically after the rotation cycle runs. Restore procedures reverse the process: stop the server, replace the world directory with the backup copy, and restart. The backup manifest in infra/output/minecraft/ records every backup with timestamps, sizes, and checksums for verification.

Monitoring

The Minecraft server integrates with the Den's Prometheus monitoring stack. Key metrics include:

  • Ticks Per Second (TPS) -- The server's processing rate. A healthy server maintains 20 TPS; drops below 18 indicate performance issues from overloaded chunks, excessive entities, or insufficient CPU.
  • Player count -- Current online players. Useful for correlating performance drops with player activity and for capacity planning.
  • Memory usage -- JVM heap utilization. When heap approaches the allocated maximum, GC pauses increase and TPS drops. Alert rules trigger when memory exceeds 80% of the allocated budget.
  • World size -- Total disk usage of the world directory. Growth rate tracking helps predict when storage allocation needs to be increased in the resource budget.

Alert rules notify operators when TPS drops below threshold, memory exceeds budget, or the backup system fails to complete within its expected window. Alerts integrate with the Den's notification system for immediate visibility.

Educational Integration

Minecraft is not just a game server in the Den -- it is an educational platform connected to three knowledge pack curricula:

  • CODE-101: Redstone Logic -- Uses Minecraft's redstone system as an introduction to digital logic and programming. Students build logic gates (AND, OR, NOT, XOR) from redstone components, chain them into circuits (adders, multiplexers, memory cells), and explore how physical constraints (signal strength, tick delays) mirror real hardware timing. Lesson plans progress from single gates through combinational logic to sequential circuits with feedback.
  • ENGR-101: Architecture and Design -- Uses large-scale building projects to teach engineering principles: structural planning, material budgeting, modular design, and iterative construction. Students plan builds before placing blocks, estimate resource requirements, divide projects into substructures, and document their designs -- all skills that transfer directly to software architecture.
  • MATH-101: Spatial Reasoning and Geometry -- Uses Minecraft's voxel world to make geometry tangible. Students calculate volumes, surface areas, and distances in three-dimensional space. Coordinate systems (x, y, z) have immediate physical meaning. Construction challenges require geometric transformations: rotation, reflection, and scaling of structures.

Each curriculum connects in-game activities to formal learning objectives tracked by the knowledge pack system. Students earn progress by completing in-game challenges that demonstrate understanding of the underlying concepts.

Operational Runbooks

Common maintenance tasks are documented as runbooks:

  • Server update -- Update Fabric Loader and mods, test in a staging environment, then deploy to production with a pre-update backup.
  • World restore -- Stop the server, identify the correct backup from the rotation manifest, restore the world directory, verify integrity, and restart.
  • Performance tuning -- Analyze TPS metrics, identify chunk loading bottlenecks, adjust view distance and entity limits, and update JVM garbage collection parameters.
  • VM resize -- Update the resource budget, resize the VM allocation (RAM, CPU, storage), and restart the server with updated JVM arguments.

What's Next