Untitled

---

title: Kits vs Autokits on Rust Console: What Is the Difference? description: The difference between kits and autokits on a Rust Console server, how binds trigger kit delivery, when to use each, and why a kit that exists can still fail to be delivered. relatedCommand: /bind

Short Answer

• A kit is the contents — a named bundle of items you define once.
• An autokit is the delivery — a bind that hands a kit to a player automatically when they trigger it, without staff involvement.

Put simply: the kit is what players get, the autokit is how they get it. You always need a kit first; the autokit is the automation layer on top.

	Kit	Autokit
What it is	A defined bundle of items	A bind that delivers a kit
Who triggers it	Usually staff, or a shop purchase	The player, in-game
Needs staff online	Often	No
Typical use	Rewards, shop products, compensation	Starter kits, VIP kits, recurring perks

When to Use Each

Use a plain kit when delivery should be deliberate: shop products, event prizes, compensation after an incident, or anything where you want a human decision in the loop.

Use an autokit when the same players should get the same items repeatedly without asking: starter kits for new players, VIP kits tied to a Discord role, or a perk attached to another action.

If players are asking staff for the same thing more than a few times a day, it should be an autokit.

Prerequisites

• A connected server in Helios.
• Manage Server permission in Discord.
• Kit naming and role policy decided before you build anything — renaming later breaks binds.

Setting Up an Autokit

1. Create the bind workflow with /bind.
2. Attach the kit action to the intended bind route.
3. Validate role and account-link requirements using a test account, not your owner account.
4. Add spawn or teleport dependencies if the kit requires them.
5. Re-test every bind after a wipe or map change.

/bind
/spawn
/tp home
/settings server

Why a Kit Exists but Is Not Delivered

This is the most common autokit problem, and it is almost never the kit itself. Work through these in order:

Symptom	Likely cause	Fix
Nothing happens on trigger	Bind target is stale	Recheck the bind target, then retest
Works for staff, not players	Role or link requirement unmet	Verify the required role and that the player is linked
Worked before the wipe	Bind references something map-specific	Re-test and re-point the bind
Works intermittently	Kit name changed but bind was not updated	Standardise names; update both together

Practical Conventions

• Standardise kit and bind names. Ad-hoc names are the root cause of most stale-bind problems. Decide a convention before your first wipe.
• Keep one starter autokit. Multiple overlapping starter kits make it very hard to tell which one failed.
• Tie VIP kits to roles, not to individual players. Per-player grants do not survive staff turnover.
• Re-test after every wipe. Add it to your wipe day checklist.
• Be careful pairing kits with teleports. A kit granted on every teleport can become an unintended currency faucet; see Economy Without Inflation.

Related Pages

• Autokit Setup Guide
• How to Set Up Autokits
• Autokit Setup Examples by Server Style
• Binds and Command Groups
• Autokits feature overview