Start with the workload, not the biggest number
Player count matters, but it is only one part of sizing. Mods, plugins, world generation, automation, entity counts and game-specific simulation can change resource use dramatically.
Runic uses the selected game, expected players and workload profile to produce a RAM recommendation. The recommendation is a starting point, not a promise that every third-party modpack will fit the same allocation.
What RAM does — and what it does not do
RAM gives the server room to keep active world data, plugins, mods and game state in memory. Too little can cause stalls, crashes or aggressive cleanup.
More RAM does not automatically fix a CPU-bound server. Tick-heavy Minecraft plugins, large simulation workloads and poorly optimized mods can bottleneck CPU long before memory is exhausted.
A safe way to choose
- Choose the correct game and expected active player count.
- Select the workload profile that best matches vanilla/light, standard or heavier modded use.
- Start at the recommendation unless you already know the workload needs more.
- After launch, watch real memory and CPU behavior before paying for an upgrade.
ImportantRunic will not use an “unlimited RAM” label. Shared nodes have finite memory, storage and compute capacity.