Minecraft Server (Java)

Reconnaissance — before touching anything

The run starts read-only. Before a single change, Servor checks the real state of your server — a real machine is rarely clean, and only what is actually there decides what happens next.

• 01Java already present? version compatible with the Minecraft version?
• 02does a dedicated user already exist?
• 03is the server port free?
• 04does a server already exist at this location? do not overwrite a world

The steps — each one proves itself

The playbook below guides the run; the model adapts each command to the distribution and state found during reconnaissance. A step only counts as done when its verification passes.

1. 01

   Install Java (headless JRE)

   Verified by

   java -version 2>&1
2. 02

   Create the user and the folder

   Verified by

   id minecraft && test -d /opt/minecraft && echo ok
3. 03

   Download the server (${flavor} ${mc_version})

   Verified by

   test -f /opt/minecraft/server.jar && echo ok
4. 04

   Accept the EULA + server.properties

   Verified by

   grep -q eula=true /opt/minecraft/eula.txt && echo ok
5. 05

   systemd service + startup

   Verified by

   systemctl is-active minecraft
6. 06

   The server is listening

   Verified by

   ss -tlnH "sport = :${port}" | grep -c LISTEN

Variables

What you choose before launching — the recipe fills in the rest.

${mc_version}

Minecraft version

${flavor}

Server type

${max_players}

Max players

${ram_mb}

RAM (MB)

${port}

Port

${difficulty}

Difficulty

How Servor runs this recipe

Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, an AI run reads the reconnaissance, plans the steps, and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed to the agent, which verifies the signature locally before executing.