Skip to content

Terraria Setup

Terraria benefits from frequent backups, TShock permissions, and optional tModLoader support. Mamba Host runs Terraria workloads on Dell PowerEdge R630 hardware (dual Intel E5-2680v4, 128 GB RAM, NVMe storage) so world saves, boss fights, and automation stay responsive.

  • Decide whether you’re hosting vanilla, TShock, or tModLoader.
  • Gather world files (.wld), configs (serverconfig.txt, tshock.json), and mod packs.
  • Determine difficulty (Journey, Classic, Expert, Master) and world size.
  • Plan backup cadence and whitelist/password policy.
Players / World SizeRecommended PlanNotes
≤12 players, small worldStarter (≈1 GB RAM)Vanilla or light TShock
12–20 players, medium worldPro (≈2 GB RAM)Calamity/Thorium or multiple plugins
25–40 players, large worldPremium (≈3 GB RAM)Heavy modpacks, multiple concurrent worlds

Upgrade when autosaves take longer than a few seconds or when modded servers throw memory errors.

  1. Go to https://panel.mambahost.comCreate ServerTerraria.
  2. Select plan, runtime (vanilla, TShock, or tModLoader), and deploy (~2 minutes).
  3. Download autogenerated configs from /home/container.
  4. Enable automatic backups (hourly/daily) before importing worlds.
  • Stop the server, upload .wld files to /worlds, and set world=/home/container/worlds/<name>.wld inside serverconfig.txt.
  • For TShock, edit config.json, permissions.json, and sscconfig.json.
  • For tModLoader, place .tmod files in /Mods, enable them via Enabled.json, and restart so dependencies install.
  • Create superadmin via console (authlogin) and store the password securely.
  • Define permission groups (builder, mod, admin) in permissions.json.
  • Install plugins for regions, teleporters, economy, anti-grief, etc., in /ServerPlugins.
  • Schedule restarts to clear NPC/pathing glitches and to trigger auto-saves.
  • Balance npcstream and maxplayers—large NPC counts on small plans can lag clients.
  • Disable autosave on heavy modpacks and rely on panel backups if you notice micro-freezes.
  • Allocate more RAM (Pro/Premium) for Calamity/Thorium or Magic Storage heavy worlds.
  • Use panel snapshots to restore corrupted chunks or undo griefing within minutes.
  • Version mismatch: ensure server version matches clients; update via panel or switch betas (e.g., 1.4.x).
  • TShock login issues: delete tshock.sqlite when migrating and re-run setup.
  • tModLoader crashes: review /Logs/Server.txt for missing dependencies; disable problem mods until patched.
  • Mass griefing: restore from backup, tighten regions/permissions, and log staff actions.