Skip to content
Mamba Host Docs

Minecraft Bedrock Setup

Minecraft Bedrock hosting at Mamba Host is tuned for cross-platform play across Xbox, PlayStation, Switch, mobile, and Windows 10/11. All worlds run on Dell PowerEdge R630 nodes (dual Intel E5-2680v4, 128 GB RAM, NVMe storage) with 99.9% uptime targets, panel-based backups, and built-in DDoS protection.

Before You Begin

Section titled “Before You Begin”
  • Confirm your players use Bedrock-capable devices (console, mobile, Win10/11). Java clients cannot join these servers.
  • Decide whether you are uploading an existing world or generating a new seed.
  • Collect resource packs, behavior packs, and world templates you plan to install.
  • Optional: set up a DNS record (e.g., bedrock.example.com) pointing to the server IP/port for easier console access.

Plan Selection

Section titled “Plan Selection”

Bedrock relies on standardized Starter/Pro/Premium tiers defined in src/games/game-server-products.ts. Use these guardrails:

Player CountSuggested PlanNotes
Up to 10Starter (≈2 GB RAM)Friends/family with simple builds
10–25Pro (≈4 GB RAM)Communities using resource packs and light automation
25–50Premium (≈6 GB RAM)Public servers with busy spawn areas
50+Premium+ (8 GB+ RAM)Feature-rich hubs, Marketplace content, heavy redstone

Upgrade when ticking areas spike CPU above 75% or when autosave durations exceed a few seconds.

Provision the Server

Section titled “Provision the Server”
  1. Sign in at https://panel.mambahost.com.
  2. Click Create Server → choose Minecraft Bedrock.
  3. Pick the plan/region, select default version (latest official build), and deploy. Provisioning finishes in under two minutes.
  4. Note the IP and Bedrock port (default 19132). Consoles require both host and port.

Upload Worlds and Packs

Section titled “Upload Worlds and Packs”
  1. Stop the server.
  2. Connect over SFTP (port 2022) and upload your worlds/<world> folder or zipped world to /home/container.
  3. Update server.properties with level-name=<your world>.
  4. Place behavior/resource packs under /behavior_packs and /resource_packs, then register them in world_resource_packs.json and world_behavior_packs.json.
  5. Start the server and verify players spawn with the correct packs.

Core Configuration

Section titled “Core Configuration”
  • Set white-list=true if you want allow-listed access and manage whitelist.json through the panel.
  • Use the panel to toggle game mode, difficulty, simulation distance, and cheats.
  • Configure operator permissions inside permissions.json for trusted admins.
  • Share the Server Address + Port with players. Console users must add a new entry in the Multiplayer tab.

Performance Tips

Section titled “Performance Tips”
  • Keep simulation distance at 8–10 for large public servers; Bedrock spreads CPU load across chunks as more platforms join.
  • Use scheduled restarts (once every 12–24 hours) to free memory when running large behavior packs.
  • Avoid unbounded XP/item farms that stay loaded near spawn; consider relocating heavy automation to low-traffic chunks.
  • Monitor disk usage; Bedrock worlds grow quickly when players explore on mobile. Expand storage in the panel if usage exceeds 80%.
  • For redstone-heavy hubs, disable autosave during peak events and trigger manual saves during off-hours.

Operations & Cross-Platform Notes

Section titled “Operations & Cross-Platform Notes”
  • Console onboarding: provide both IP and port in welcome docs; consider Geyser dashboards or DNS records to simplify entries.
  • Marketplace content: verify licensing allows third-party hosting before uploading. Keep .mcpack UUIDs consistent.
  • Security: enforce operator levels carefully; Bedrock has four tiers (0–4). Restrict high-level ops to staff accounts only.
  • Backups: store snapshots before large builds or seasonal events so you can revert quickly if griefing occurs.
  • Automation: use scheduler tasks to rotate seed-based minigames, clone worlds, or reset survival seasons.

Troubleshooting

Section titled “Troubleshooting”
  • Console players cannot join: double-check that the firewall/ISP allows UDP on the Bedrock port and that the player typed both host and port.
  • Resource pack mismatch: confirm the UUID/version in world_resource_packs.json matches the pack manifest; delete caches on consoles if needed.
  • World upload fails: upload via SFTP, not the web file manager, when files exceed 100 MB. Ensure level.dat exists at the root of your world folder.
  • Lag on mobile clients: lower simulation distance, disable experimental features not used, and schedule off-peak restarts.
  • Operators lose perms: confirm permissions.json survived uploads and that the UUIDs match Xbox Live IDs.
  • Chat sync issues: Bedrock ignores some formatting codes—test announcements on multiple devices.
Section titled “Helpful Links”