How a SCUM server generates events

Why this matters

Almost every disappointment while configuring a server comes from turning a dial without knowing the system behind it. You raise loot quantity and the towns stay empty anyway. You lower puppet counts and the server still stutters. You raise the tick rate and everything gets worse.

This text explains the five systems running continuously on a SCUM server. Know them and you will know where to look at the next problem — and which setting can actually change anything.

1. Tick rate: the heartbeat

Everything starts here. The tick rate is how many times per second the server recalculates the state of the world: who stands where, what is in flight, what falls, what hits whom. The defaults allow between 5 and 30 calculations per second.

Under light load the server runs at the top of that range. As it fills up — many players, many vehicles, many enemies — the rate drops. That is intended behaviour: better to compute slower than to crash.

Which is precisely why the common reaction is wrong. Raising the lower bound makes no server faster. All it does is remove its ability to slow down cleanly — and instead of smooth slowdown you get stutter and disconnects. Smooth play does not come from demanding more of the server but from giving it less work: fewer vehicles, fewer loose items, fewer simultaneous enemies.

How to spot a low tick rate: shots that do not land although the crosshair was on target. Vehicles snapping back. Doors reacting late. All of that is a load problem, not a settings problem.

2. The encounter system: where enemies come from

Puppets and armed NPCs do not simply stand in the world. They are produced by a dedicated system SCUM calls encounters — and that system is why the island feels inhabited even though only a fraction of its enemies actually exist.

The island is divided into threat zones, from quiet outskirts to military sites. Each zone has a base number of enemies plus a supplement per player present — which is why a town grows more dangerous as more people move through it. A cap stops that from growing without limit.

Enemies do not appear in front of players but at a distance from them, and reinforcements arrive in batches after a waiting period. Hordes are their own case: triggered by noise or by the death of a loot puppet, they bring many enemies at once.

The practical consequence: there are two routes to controlling enemies. Global caps work island-wide and crudely — once the budget is consumed elsewhere, your area stays empty. The encounter settings work per zone and finely. For nearly everything, the second route is the right one.

3. Spawners and expiration: where loot comes from

Loot in SCUM does not lie around permanently; it is produced by spawn points. Each point has a probability of producing anything at all, a pool of possible items, and an expiration time after which it withdraws its contents and rolls again.

Those three quantities produce a server's felt level of supply:

Probability determines in how many buildings there is anything at all. It does not change what lies there — a rare rifle stays proportionally just as rare.

Expiration decides whether searching the same town twice is worthwhile. Short times turn towns into loops; long ones send players across the map.

Item group cooldowns are the most underestimated part. After a find the whole group is blocked for a while — which is why you do not find three sniper rifles in a row. If your regulars seem over-equipped, look here before cutting loot quantity.

On top of that sit the examinable sources with their own values: laundry baskets, rubble, wrecks. They reward slow, careful searching and can be set more generously than the rest of the loot.

4. Scheduled events: cargo drops and bunkers

Alongside the continuously running world there are events with a timetable. They are the backbone of server life, because they bring players to the same place.

The cargo drop follows a four-step sequence: the server rolls the gap to the next drop between a minimum and a maximum, announces it, lets the crate fall after a nine-minute lead time, and destroys it itself twenty minutes after landing. Every one of those steps is configurable — and every one changes the event fundamentally. The lead time decides who can make it at all; the self-destruction creates the time pressure that turns a crate into an event.

Abandoned bunkers work on a rotation: only some are open at once, each for a set duration. Which ones open is up to the game. Two open bunkers mean everyone meets there; four spread it out. Keycards open a bunker outside the rotation — for a shorter time, but at a moment you choose.

Inside a bunker its own mechanism runs: the server tracks noise. Two thresholds decide whether commotion arises and whether the enemies wake up, each with a supplement per player present so groups are not inherently disadvantaged. A triggered alarm can summon the dropship — typically just as you try to leave with a full load.

5. Virtualization: why the server copes at all

After a few months a busy server holds hundreds of thousands of items: in bases, in crates, in vehicles, in the grass. Managing all of them simultaneously would be impossible.

SCUM solves this with virtualization. Anything far from all players is collapsed into a record — it exists but is not simulated. Come closer and it becomes a real item again. The same applies to animals, where SCUM distinguishes fully simulated from purely virtual ones.

The system checks every second, and every time a player has moved a metre, which items within a hundred-metre radius need expanding. For that it has a budget of five milliseconds per run — whatever does not finish waits for the next one.

Practical consequence: when crate contents appear only after seconds or equipment briefly seems missing, that is virtualization — not data loss. And when a server turns sluggish after months, it is usually the sheer volume: clearing up helps more than any setting.

Where to look for which problem

"The towns are empty." Loot probability first, then spawn point expiration. Not enemy counts.

"One player has everything, the others nothing." Item group cooldowns, not loot quantity.

"There are no zombies." First check whether a global cap is set. Then the encounter settings for the zones in question.

"The server stutters in the evening." Vehicle count, volume of loose items, number of simultaneous animals. Not the tick rate.

"Enemies appear out of nowhere." The cull distances for puppets, NPCs and animals — somebody has probably lowered them.

"Nobody reaches the cargo drop." The lead time before the fall. Nine minutes crosses half the island by vehicle but not on foot.