Why game hosts still sell slots, not hardware

The player slot is a unit left over from years when it measured something. On a Counter-Strike server twenty years ago, each extra player cost roughly the same bandwidth and processor time, so pricing by the slot meant pricing a share of the machine. Hosts still sell slots because buyers understand them, but for Minecraft, modded servers and single-thread games the number measures almost nothing.

What a slot used to measure

The Half-Life-era server was a small and predictable thing. The game was the same on every box and the player cap was a few dozen at most. Each connected player was a stream of updates at a rate the server's own settings capped, and the load grew with the number of players in a way a host could plan around. Pack enough of those servers onto one machine and the slot became a sensible unit. The customer could count it, and behind it sat a slice of CPU and bandwidth that did not vary much from one customer to the next.

Nothing about that model was dishonest. The unit described the product, and a buyer comparing two hosts by the slot was comparing roughly like with like.

Where the unit stopped meaning anything

Minecraft is where it broke most obviously. The slot count on a Minecraft server is max-players in server.properties, a single number that defaults to 20 and costs nothing to change. What costs money is the world. The server sends each player the terrain within ten chunks in every direction by default, and it updates the living things near every player twenty times a second, with 50 milliseconds for each tick. Ten players building in one town share most of that load. Ten players exploring in different directions each bring their own, and generate new terrain as they go. The slot count is identical and the work behind it is not.

Most of that work still happens on one main thread. Folia, PaperMC's fork that spreads a world across several threads, describes itself as suited to servers with very high player counts whose game modes naturally spread players out, and warns that it will break most public plugins. Read the other way round, that says the ordinary server does its ticking on one thread and that players scattered across a map are among the things it finds most expensive.

Modded servers drifted further from the slot, since a large modpack needs its memory before anyone connects. FiveM drifted furthest: sv_maxclients accepts any number from 1 to 2048, and the figure on a listing says nothing about the machine behind it. Any game whose simulation is tied to one thread cares far more about a core's clock speed than about how many players the plan allows, which the guide on cores and clock speed sets out in detail.

What the unit does to owners

A unit that measures nothing still shapes behaviour. The slot count is what a server list shows, so an owner paying per slot is buying a number that doubles as advertising, and the temptation is to buy more than the server will fill. Any list shows where that leads: a server at 3 of 64 that looks deserted, next to one at 14 of 16 that looks like the place to be. Sizing slots to the players who actually turn up fixes that from the owner's side, while the pricing model keeps nudging the other way.

The model also hides the parts that decide performance. A plan sold by the slot often says nothing about the CPU model, whether the core is shared, how much of it the server may use or what kind of disk it sits on, so a host can sell the same core several times over without the buyer ever seeing a number that would reveal it. Many Minecraft hosts moved to plans sold by the gigabyte of memory, which is at least a real resource, but memory is also the easiest resource to sell someone more of than their server uses.

What the panel actually allocates

Behind the shop page, the host counts something else. Pterodactyl, a free and open-source game server panel, asks for these when an admin creates a server: memory, swap, disk space, an IO weight, and a CPU limit written as a percentage of a thread, where 100 is one full thread and 50 is half of one. There is no field for slots. The player cap is left to the game's own configuration, where the customer can set it to anything.

So the host knows exactly what it is selling, in the units that matter, and translates it into slots or gigabytes for the pricing page. The useful question for a buyer is the untranslated one: what is my CPU limit, and on which processor?

Buying the machine instead

The other way out is to rent the machine itself. A VPS or a dedicated server is sold in cores and gigabytes, and the slot becomes a line in your own config. The trade is that you run everything yourself, and on a cheap VPS the cores may still be shared with other tenants whose load shows up as your lag. The comparison of VPS and dedicated hosting covers where each makes sense, and the arithmetic of renting against running your own box covers what each costs.

Translating a slot back into hardware

Whatever unit the plan is priced in, a buyer can ask for the numbers the panel uses:

1. The CPU model, so its single-thread performance can be looked up.
2. The CPU limit as a percentage, and whether the core is dedicated or shared.
3. The memory the server is guaranteed, as opposed to what it may briefly use.
4. The disk type, and whether disk activity is throttled.
5. What happens when the server hits any of those limits.

A host that answers quickly and specifically is usually worth using, and the six questions for choosing a host treat that reply as the most reliable signal on offer. The slot count can come afterwards, set by the owner, to match the number of players who actually arrive.