moincraft

🧠 Stack

Moincraft process map, ports, stable boundaries, startup order, and orchestration rules.

Hermes/Hermit operator ──REST/ops──▶ Relay :55667
       │                              ▲
       └─ persona + memory + skills   │ optional dashboard token

PM2 / launch_all.sh
  ├─ mc-server        Paper :25565
  ├─ dashboard        Svelte :55666 + relay :55667
  ├─ mindcraft-bots   MindServer :55668 + main.js
  └─ prismarine-viewer WebGL :55669

Port map#

Port Service
25565 Paper Minecraft server
55666 Svelte dashboard UI
55667 Dashboard relay backend / Socket.IO
55668 MindServer agent hub + WebApp
55669 Prismarine Viewer WebGL
55661+ Per-agent viewer ports

Stable layer split#

  • Soul/operator: Hermes owns durable persona, memory, skills, and remote messaging.
  • Runtime bridge: relay :55667 is the stable API boundary for dashboard/Hermes integration.
  • Embodied agents: Mindcraft/Mineflayer owns Minecraft state, pathfinding, actions, and in-world coordination.

Startup order#

  1. Paper server; wait for :25565.
  2. Mindcraft bots; stagger agent startup.
  3. Prismarine viewer after server readiness.
  4. Dashboard UI/relay.

Use one orchestrator at a time. Mixing systemd units, PM2, and manual scripts can create port collisions and Minecraft session.lock conflicts.

Sources: moincraft/docs/moincraft-stack-cheatsheet.md, moincraft/docs/deployment-guide.md.