How to setup Kits
Rust Kits Guide
Kits by k1lly0u lets players claim predefined sets of items from a clean in-game menu: starter gear for fresh spawns, VIP packages for supporters, and admin loadouts for staff. It is one of the first plugins almost every modded server installs.
This guide assumes Oxide is installed. If not, start with How to Install Oxide.
Step 1: Install the Plugin
- Download
Kits.csfrom umod.org/plugins/rust-kits. - In the GSK panel File Manager, upload it to
oxide/plugins/. - Watch the Console for the loaded confirmation.
If you plan to use custom kit icons in the menu, also install Image Library from umod.org/plugins/image-library. The menu works without it, but icons make it look professional.
Step 2: Grant Yourself Admin Access
The kits.admin permission unlocks kit creation and management:
oxide.grant user YourName kits.admin
Step 3: Create Your First Kit
Kit contents come from your own inventory, so the flow is:
- Clear your inventory completely.Anything in it ends up in the kit.
- Give yourself exactly the items the kit should contain (F1 console as admin).
- Type
/kit newin chat, or open/kitand press the Create New button. - In the kit editor, the options sit on the left and the item view on the right. Name the kit and set its rules.
The options you will use most:
| Option | What it does |
|---|---|
| Cooldown | Seconds before the same player can claim again |
| Maximum uses | Total claims per player, 0 for unlimited |
| Required permission | Locks the kit behind a custom permission node |
| Cost | Charge for the kit via a supported economy plugin |
| Hidden | Hides the kit from the menu (useful for autokits) |
Step 4: A Free Starter Kit for Everyone
The classic setup is a basic kit every new player can claim:
- Create a kit named
starterwith a stone hatchet, a few bandages, and basic clothes. - Set a cooldown so it cannot be farmed, one hour is common.
- If you set a required permission on it, grant that node to the default group:
oxide.grant group default kits.starter
The exact node is whatever you typed in the kit's permission field, shown in the kit editor.
Step 5: VIP Kits
VIP kits work the same way, just with a better item list and a permission only your VIP group has:
- Create the kit with the permission field set, for example
kits.vip. - Grant it to the VIP group:
oxide.grant group vip kits.vip
This is the same group structure BetterChat and NTeleportation hang off, so one oxide.usergroup add puts a supporter into all their perks at once. See Oxide Permissions 101.
Autokits: Gear on Respawn
Kits can be granted automatically when a player spawns. In oxide/config/Kits.json, find the autokits list, ordered by priority, and add your kit names. Mark autokits as hidden so they do not clutter the claim menu. Players can toggle their own autokit with /kit autokit if you allow it.
After config edits, reload:
oxide.reload Kits
Command Reference
| Command | Who | What it does |
|---|---|---|
/kit | Players | Open the kit menu |
/kit name | Players | Claim a kit directly |
/kit new | Admin | Create a new kit |
/kit edit name | Admin | Edit an existing kit |
/kit delete name | Admin | Delete a kit |
/kit list | Admin | List all kits |
/kit give player name | Admin | Hand a kit to a player |
Common Issues
| Problem | Fix |
|---|---|
| Kit claims but gives nothing | The kit was created with an empty inventory. Edit it with the items in your inventory |
| Players cannot see a kit | It is hidden, or locked behind a permission their group lacks |
| Icons not loading | Install Image Library and check the image URLs in the kit setup |
| Kit items wrong after an update | Item shortnames occasionally change with Rust updates, re-edit the kit |
What to Read Next
- How to Setup BetterChat to give those VIP groups visible titles
- Oxide Permissions 101 for the group structure behind kit tiers