This article provides general preparation guidance. Final service recommendations depend on the actual software, data, licensing, integrations, and operating requirements involved.
Start with the workload, not the biggest number
Memory recommendations should begin with the game, server software, world or map size, plugins, mods, scripts, and expected activity. Two servers with the same player count can require very different resources.
Use the common range as a starting point
Each OutlawCoreStudios game page shows a common memory range and a live sizing signal. Choose a realistic starting point, then include the details of your content stack when requesting the configuration.
Leave room for real growth
A small amount of headroom helps with updates, temporary spikes, and new content. It is usually better to begin with a sensible configuration and scale deliberately than to overbuy resources that the server will not use.
What we review before launch
We review versions, frameworks, loaders, databases, map or world size, content count, expected concurrency, migration needs, and any special services before treating the public estimate as a final recommendation.
Never place passwords, private tokens, recovery codes, API keys, database credentials, or license keys into a public form or unverified message.