Use the Kits Plugin on Rust

Kits lets you define bundles of items that players claim with a command or a menu, with optional cooldowns, use limits, permissions and costs. It can also hand out a starter kit every time someone respawns. This guide covers installing it on a Rust server, the permission model, how to build your first kit, and the settings that decide how kits are claimed.

Checked against Kits 4.4.10 by k1lly0u on uMod (released 27 September 2026), October 2026. In the Store it is listed as Rust Kits, and uMod describes it as item kits, autokits, kit cooldowns and more. It was installed and loaded on our Rust test server on build 2635, on both Oxide and Carbon 2.0.262.

Install it

Open the Plugins tab, search the Store for Kits and press Install on Rust Kits. How to install Oxide/uMod plugins on your Rust server covers the tab, Oxide and Carbon.

On Oxide, the plugin stays unloaded after the install. On our test server oxide.plugins showed it as Unloaded, and typing oxide.load Kits in the Console compiled and loaded it, creating oxide/config/Kits.json. A restart loads it too. On Carbon it loads by itself within seconds, and the commands are c.load, c.unload and c.reload. The oxide.* commands, oxide.grant included, print nothing and do nothing on Carbon. Its config is carbon/configs/Kits.json there. Permissions only exist once the plugin has loaded, so grant them afterwards.

Permissions

Kits registers one permission of its own, kits.admin, which allows creating, editing, deleting and giving kits. There is no general "use" permission: any player can claim any kit they can see, unless that kit has its own permission set. A kit permission must start with kits., for example kits.vip.

oxide.grant user 76561198000000001 kits.admin
oxide.grant group default kits.vip

On Carbon:

c.grant user 76561198000000001 kits.admin
c.grant group default kits.vip

On our Carbon test server c.grant group admin kits.admin answered Granted group 'admin' permission 'kits.admin', and c.grant user <SteamID64> kits.admin answered Granted user 'Unnamed' permission 'kits.admin', so both forms work, even for a player who has never joined.

Build your first kit

Kits are created in game, by an admin holding kits.admin.

1. Fill your inventory with the items you want in the kit.
2. Type /kit new. An editor opens.
3. Enter a Name, then press Copy From Inventory to take the items from your inventory. Clear Items empties the list again.
4. Fill in what applies: Description, Permission, Maximum Uses, Cooldown (seconds), Purchase Cost, Auth Level, Is Hidden, Icon URL.
5. Press Save Kit. A kit must hold at least one item, and re-saving an existing name needs Overwrite Existing ticked.

A Maximum Uses, Cooldown (seconds) or Purchase Cost of 0 means no limit, no wait and no charge. The cost is paid in Scrap, Economics coins or Server Rewards points, chosen by the Currency used for purchase costs (Scrap, Economics, ServerRewards) setting.

Commands

Players use /kit to open the menu, /kit <name> to claim a kit and /kit list to see theirs. Admins also have:

• /kit edit <name> and /kit delete <name>; /kit list shows every kit rather than only theirs.
• /kit give <player name or ID> <kit name>.
• /kit givenpc <kit name> for the NPC you are looking at.
• /kit reset, which wipes every player's usage data, and /kit resetuses <player> <kit> for one player and one kit.

The server Console has its own kit command for the same admin jobs: kit list, kit delete <kitname>, kit give <playername> <kitname>, kit reset and kit resetuses <playername> <kitname>. The plugin turns away only a connected player who is not a Kits admin, so the panel Console is allowed.

Settings

Press Config on the plugin in the Installed list. The settings worth knowing:

• Kit chat command is kit. Use the Kits UI menu opens the menu from /kit; without it /kit prints help instead.
• Autokits ordered by priority is a list of kit names. On respawn the plugin gives the first one the player can claim. It strips their inventory first, so use it only for a starter kit.
• Allow players to toggle auto-kits on spawn lets players switch that off with /kit autokit.
• Wipe player data when the server is wiped is false by default; Post wipe cooldowns (kit name | seconds) blocks a kit for a time after a wipe.
• Players with the admin permission ignore usage restrictions is false by default.
• Only show/give players skins that they are allowed to use (requires PlayerDLCAPI) is true by default. The plugin warns that giving players paid skins they do not own is against Rust's Terms of Service and can get a server delisted, so leave it on.

Kits themselves are saved in oxide/data/Kits/kits_data.json, and player usage in oxide/data/Kits/player_data.json. On Carbon the same files sit under carbon/data/Kits/.

Common problems

1. "You do not have the required permission to access this kit." The kit has a permission and the player lacks it.
2. A kit does not appear in the menu. Kits with a permission are hidden from players without it unless Show kits with permissions assigned to players without the permission is on, and Is Hidden kits are listed for admins only. A kit whose Auth Level is above the player's is hidden too.
3. "You do not have enough space in your inventory to claim this kit". Claiming needs room for every item.