Terraria Starter · 2 GB
€2.14 / month
- vCPU
- 2 cores
- RAM
- 2 GB
- Storage
- 30 GB SSD
- Processor
- Intel Xeon E5-2699 v4
- Location
- Turkey
More features
- Traffic
- Unlimited
- Operating system
- Selectable operating system
SANDBOX · PC
Terraria server load varies with world size, exploration, active enemies and projectiles, boss events, and the selected server mode.
€2.14 / month
€3.03 / month
€4.10 / month
€5 / month
€7.14 / month
Boss fights, event waves, and dense automation create different peaks from ordinary building; do not test only an empty world.
The first resource profile for a controlled launch and measurement baseline.
A middle profile to assess as community and content workload grows.
A higher resource profile to compare when measured CPU, RAM or storage needs increase.
Evaluate CPU, memory, and storage options against the expected game workload.
Players fighting across biomes activate more regions and entities, while one arena concentrates enemies and projectiles.
Measure processor peaks and game-loop response during a busy session.
Track peak memory use together with growth headroom.
Measure storage behaviour across saves, logs, and backups.
Measure actual mod, plugin, and script workload separately from extension count.
Track world size, active regions, and persistent-data growth together.
Evaluate concurrent-player distribution, activity, and content workload together.
| Scenario | Resource effect | Check |
|---|---|---|
| Concurrent players | Players fighting across biomes activate more regions and entities, while one arena concentrates enemies and projectiles. | Measure a busy session |
| Game activity | Boss fights, event waves, and dense automation create different peaks from ordinary building; do not test only an empty world. | Repeat the peak scenario |
| World / save growth | World edits and player characters expand backup scope; preserve restorable world and player files before major mod updates. | Track save and restore duration |
Estimate starting capacity from your player and world goals.
Estimated CPU, memory, storage, and a suitable resource profile appear here.
tModLoader content can add items, NPCs, and world data. Pin the mod collection and versions with the save.
Mod compatibility can vary by game and server-software release.
Verify world, difficulty, password, player limit, ban list, and mod load order during maintenance.
After deployment, manage Terraria processes, version changes, and settings that require restarts in controlled maintenance windows.
Back up Terraria saves, configuration, and additional-content data as separate restore points before changes.
Limit file access to Terraria configuration, logs, and managed content directories; stop the relevant process before replacing active files.
Evaluate a boss or event session with your intended world and mods, not only quiet building. Compare plans using the CPU and memory usage observed in that representative session.
Observe both a split group and a shared arena session. Enemy and projectile activity can differ, so connection count alone is not enough to establish capacity.
Keep world and player files together with the mod collection and version list. Confirm the intended software and compatibility before setup; a resource plan alone does not mean a preconfigured mod installation.
Test compatibility on a save copy and measure a busy event first. After separating unused content, compare resources if the measured CPU or memory requirement has actually increased.
Include the character data you intend to preserve. Record the versions associated with world and player files and test recovery; the existence of a file alone does not establish a usable backup.
Contact support for ordering details and special requirements.