// Gameplay
Rust Kits
Configure kits, usage restrictions, and their interface.
What you can configure
Create Rust kits and arrange their items, then set permissions, cooldowns, respawn rules and the kit menu.
Edit global Kits.json settings and kit inventories in oxide/data/Kits/kits_data.json. Player redemption history in player_data.json is excluded.
Choose an ordered respawn kit with a fallback
- Create starter and fallback in the Hub’s Kit catalogue, add their items, then synchronize the catalogue to the server. Use your actual kit names in the next step.
- In Autokits ordered by priority, add starter first and fallback second. Enable Allow players to toggle auto-kits on spawn only if players should be able to opt out.
- Reload Kits and test a respawn with an ordinary player. It tries kits in order and gives the first eligible one; permissions, cooldowns and maximum uses still matter.
Auto-kits remove respawn inventory before giving a kit and skip auth-level/purchase-cost checks. Test away from production and do not use those two checks as auto-kit access controls.
Delay an existing starter kit for one hour after wipe
- In Post wipe cooldowns (kit name | seconds), add a setting named starter (or your real kit name), then enter 3600 in its value field.
- Keep Players with the admin permission ignore usage restrictions false while checking the rule.
- Verify the delay against a fresh test map save with an ordinary player. Decide separately whether Wipe player data when the server is wiped should reset prior usage records.
Do not wipe a live server merely to test this recipe.
Common questions
Can I create kit items in this configurator?
Yes. In Kit catalogue, create a kit and add items to its main inventory, clothing or belt. Export kits_data.json or synchronize it to the server. Auto-kit, NPC and post-wipe lists refer to these kit names.
What dependencies do these settings need?
This version requires Image Library. The enabled skin-ownership filter needs PlayerDLCAPI. Economics, ServerRewards, CopyPaste and HumanNPC are needed only for their selected integrations; selecting an option in the form does not install its dependency.
Before you export
- Kits 4.4.10 loads on the tested Rust/Oxide server. Kit file transfers are verified; claiming a kit as a player still needs an in-game check.
- Auto-kits replace respawn inventory and do not enforce auth-level or purchase-cost checks. Test ordered fallbacks and permissions as a non-admin.
- The Kits menu is its own Rust CUI, not a PimpMyCUI project. Leave Version plugin-managed and verify selected dependencies on the server.
Server permissions
kits.admin- Create/manage kits and use admin commands; optional restriction bypass is a separate setting.
kits.<your-kit-permission>- A custom permission assigned in the kit definition, not in global Kits.json; use its exact registered name.
Guide checked against version 4.4.10 · 2026-10-17. k1lly0u · Official plugin · Source for this version
ON PIMPMYRUST
Guided configuration
Import this version’s JSON, edit the settings, and export the finished file.
Choose a connected server to read and apply settings, or keep your export for manual installation. The server receives only the changes you choose to send.