Rust Kits Explained: Cooldowns, Stacking and Server Balance
What kits actually are, why every well run server puts limits on them, and where the line sits between saving you time and selling you an advantage.
Kits are one of the first things people argue about when they move from official Rust to a modded server, and most of the argument happens without anyone agreeing what a kit is. This page is the straight version: what kits are, what cooldowns are actually protecting, why stacking gets restricted, and how to tell a convenience feature from a paid advantage.
None of this is specific to one server. It is how the mechanic works everywhere it exists, which is what makes it worth understanding before you judge any particular server by it.
What kits are on modded Rust servers
A kit is a preset bundle of items the server hands you on a command, rather than something you craft or farm. It is a plugin feature, so kits exist only on modded servers. On official Rust there is no such thing, and everything in your inventory got there because you made it, looted it or took it off someone.
What sits inside a kit varies enormously, and that variation is the whole story. A starter kit of tools and a sleeping bag changes almost nothing about a wipe. A kit containing an assault rifle and full metal armour changes what the first two hours of that wipe even look like. Same mechanic, completely different effect on the server.
How cooldowns work and why they exist
A cooldown is a timer between claims. Take the kit, and you cannot take it again until the timer runs out. Servers usually also lock kits for the opening hours of a fresh wipe, so the early rush is decided by who showed up rather than by who typed a command fastest.
The reason is not fussiness, it is that Rust only works when dying costs something. Every other system in the game assumes it: raiding is a gamble because the loot has to be worth the explosives, fights are tense because the gear on your back took time to assemble. A kit with no cooldown removes that. You die, you respawn, you type a command and you are back at full strength, and the player who beat you gained nothing for winning. The cooldown puts the cost of dying back.
Why servers restrict stacking
Stacking is claiming several kits together, or layering kit perks on top of each other, so the combined effect skips an entire progression tier in one go. Individually each kit might be reasonable. Together they can put a player in endgame gear before anyone else has finished a base.
The restriction exists to keep the gap bridgeable. A player with kits being slightly ahead is fine, that is a normal wipe. A player with kits being unreachable is not a server anymore, it is a queue to get farmed. Most servers handle this by making perks non cumulative: you can own several kits, but claiming one does not multiply the others.
Kits vs a store, and where the line sits
A kit is a mechanic. A store is a way of getting one. They get talked about as the same thing, which is why the pay to win argument goes in circles: people are arguing about the till when the question is what is on the shelf.
The useful test is whether an item changes the outcome of a fight or only the time spent reaching it. Cosmetics, chat colours and queue priority do not touch the fight. Instant building and free transport save time without arming anyone. Weapons and armour handed out on a short timer do change fights, and that is where a store stops being convenience. Facepunch draws its own line here too, and servers that cross it lose the right to be listed at all, which is a fairly strong incentive to stay on the correct side of it.
How Scarab handles kits
Cooldowns on every kit, a lock over the opening hours of a wipe, and perks that do not stack. Nothing on offer arms you faster than the raid economy can answer. The current rules for each server are published on that server's page rather than here, so they stay accurate when they change.
Related reading
Looking for playtesters
Early access now, plus free VIP when we go live.