Skip to content
Mamba Host Docs

Minecraft Java Setup

Mamba Host optimizes Minecraft Java workloads for instant provisioning, low-latency multiplayer, and turnkey modpack support. Every plan runs on Dell PowerEdge R630 nodes (dual E5-2680v4, 128 GB RAM, NVMe storage) inside our Texas facility with 99.9% uptime targets and built-in DDoS mitigation.

Before You Begin

Section titled “Before You Begin”
  • Decide whether you need Vanilla, Paper/Purpur, Forge, or Fabric. (You can switch later.)
  • List any required plugins/modpacks plus their RAM/CPU impact.
  • Gather your existing world files (world, world_nether, world_the_end) if migrating.
  • Optional: prepare SFTP credentials for automation or CI deployments.

1. Choose the Right Plan

Section titled “1. Choose the Right Plan”

Minecraft Java uses three standardized tiers (see src/games/game-server-products.ts for current pricing):

  • Starter – 1 GB RAM, 0.5 vCPU, 10 GB NVMe, ~5–8 players. Perfect for small vanilla servers.
  • Pro – 3 GB RAM, 1 vCPU, 25 GB NVMe, ~10–20 players, most popular for Paper + light modpacks.
  • Premium – 6 GB RAM, 2 vCPU, 50 GB NVMe, ~25–35 players or heavy modpacks with MySQL access.

Upgrade whenever sustained memory usage exceeds 80% or tick time regularly dips below 19 TPS.

2. Provision the Server

Section titled “2. Provision the Server”
  1. Sign in to https://panel.mambahost.com and select Create Server.
  2. Pick Minecraft Java and the desired version (Vanilla, Paper, Purpur, Forge, Fabric).
  3. Select a plan, region, Java version, and any optional add-ons (MySQL, extra storage, automated backups).
  4. Click Deploy. Builds complete in under two minutes with default world generation.
  5. Before first start, upload existing worlds or modpacks if you’re migrating to avoid overwriting the default seed.

3. First-Time Hardening

Section titled “3. First-Time Hardening”
  • Change the generated SFTP password (Account → Security) and add unique panel credentials per teammate.
  • Enable automated daily backups and retention (Scheduler → Tasks).
  • Configure scheduled restarts (e.g., 4 a.m. daily) to clear memory from long-running modpacks.
  • Set the server icon (server-icon.png 64×64) and MOTD inside the panel or server.properties.

4. Upload Worlds, Plugins, and Modpacks

Section titled “4. Upload Worlds, Plugins, and Modpacks”

Worlds

Section titled “Worlds”
  1. Stop the server.
  2. Upload your world directories via SFTP to /home/container.
  3. Update server.properties with the correct level-name.
  4. Start the server and verify spawn chunks load.

Plugins (Paper/Purpur/Spigot)

Section titled “Plugins (Paper/Purpur/Spigot)”
  • Drop .jar files into /plugins.
  • Review config files generated after first boot.
  • Use /timings on and /timings paste to profile performance.

Modpacks (Forge/Fabric)

Section titled “Modpacks (Forge/Fabric)”
  • Upload the provided mods, config, and libraries folders.
  • Ensure the server jar matches the client pack version.
  • Allocate more RAM via the panel startup settings if the pack recommends it.

5. Optimize Performance

Section titled “5. Optimize Performance”
  • Keep simulation/view distance between 8–12 unless your community is small.
  • Use Paper or Purpur for async chunk IO; enable use-faster-eigencraft-redstone, entity-collisions, and chunk-system optimizations in paper-global.yml.
  • Allocate Java flags via the panel (e.g., -Xms3G -Xmx3G for Pro) and keep G1GC enabled.
  • Monitor TPS/memory via console or /spark profiler and upgrade if TPS dips below 19 despite optimizations.
  • Offload databases (ShopGUI, economies) to MySQL to reduce region save lag.

6. Backups and Disaster Recovery

Section titled “6. Backups and Disaster Recovery”
  • Automatic daily backups are available on all plans; configure retention (e.g., keep last 7).
  • Trigger manual pre-update backups before installing large modpacks or plugin bundles.
  • Download critical backups offsite or sync to object storage for compliance-sensitive communities.

7. Common Tasks & Troubleshooting

Section titled “7. Common Tasks & Troubleshooting”
  • Changing versions: Stop server → select new jar in the panel → start. Always back up worlds before downgrading.
  • Whitelist management: Use /whitelist add <player> or edit whitelist.json directly.
  • Lag spikes: Run /spark profiler --timeout 60 (if Spark plugin installed) to identify heavy tasks; check for redstone clocks or poor hopper setups.
  • Modpack crashes: Verify Java args, ensure no duplicate mods, and confirm the forge or fabric-loader jar matches the mod list.
  • File uploads failing: Switch to SFTP (port 2022) rather than browser upload for files above 100 MB.

8. Scaling Beyond a Single Server

Section titled “8. Scaling Beyond a Single Server”
  • Link multiple instances using BungeeCord/Velocity by opening additional allocations through the panel.
  • Connect MySQL databases (available on request) for cross-server economies, ban sync, or LiteBans.
  • Use the Creator Labs program if you need a bundled website + Discord automation + Minecraft infra for content creators.

9. Maintenance & Operations

Section titled “9. Maintenance & Operations”
  • Schedule weekly restarts and patch windows; announce via Discord or in-game broadcasts.
  • Keep plugins/core up to date—test changes on a staging container before promoting.
  • Use panel schedulers for automated world backups, database exports, or pre-wipe snapshots.
  • Rotate staff access by issuing individual panel accounts with least privilege.
  • Store a runbook for recovering from griefing (restore backup, rollback database, rotate OPs).

10. Observability & Automation

Section titled “10. Observability & Automation”
  • Install Spark or Aikar Timings for profiling; archive reports after each major content update.
  • Use GitHub Actions or n8n flows to push config changes via SFTP and trigger restarts with the panel API.
  • Emit custom metrics (player counts, TPS averages) to Discord webhooks or Grafana for long-term trending.
Section titled “Helpful Links”