/// SUPPORTED THIRD-PARTY PLUGIN
Rust Kits
Free guide for configuring this third-party plugin in the Hub. To install it, use its plugin page or official source.
Prepare your file
- Check the installed version
This guide describes Rust Kits 4.4.9. Use the same version in the configurator.
- Get the settings
Click Import, then From my server. Select the files and confirm loading them. Selecting a server does not replace the open document. You can also import files from this device or a configuration from My projects.
- Edit and send
Adjust settings, fix errors, then use Send to transfer files to the selected server. A conflict blocks sending until you choose how to resolve it. You can still export only the files you need.
Server transfers have private backups. Save keeps your work in My projects; it does not send anything to the server. A download also lets you resume without a server connection.
Settings for this version
General 14
- Kit chat command
- Text · required
Chat command opening kits, without a leading /. Choose a name not already used by another plugin.
JSON path
Kit chat command - Purchase currency
- Choice · required
Currency used for paid kits: scrap items, Economics balance or ServerRewards points. The last two require their respective plugin.
JSON path
Currency used for purchase costs (Scrap, Economics, ServerRewards)Allowed values: Scrap, Economics, ServerRewards
- Log granted kits
- On / off · required
Log kit grants to help track claims and troubleshoot distribution.
JSON path
Log kits given - Wipe player usage data
- On / off · required
Clear player usage data on wipe, including kit uses and cooldowns. This does not delete kit definitions.
JSON path
Wipe player data when the server is wiped - Use Kits UI
- On / off · required
Use the graphical kit menu. When disabled, the plugin uses its command/chat workflow.
JSON path
Use the Kits UI menu - Filter player skins
- On / off · required
Check player ownership before showing or granting kit skins, and substitute unowned item variants when PlayerDLCAPI supports it. Without PlayerDLCAPI loaded, enabling this setting does not perform the check.
JSON path
Only show/give players skins that they are allowed to use (requires PlayerDLCAPI) - Allow NPC kit skins
- On / off · required
Allow skinned items in kits given to NPCs. This does not replace players’ skin-ownership checks.
JSON path
Allow NPCs to use skins in kits - Allow auto-kit toggle
- On / off · required
Let players choose whether auto-kits are granted on spawn. This does not create a new auto-kit.
JSON path
Allow players to toggle auto-kits on spawn - Show inaccessible permission kits
- On / off · required
Also show kits a player cannot access. Their permission is still required: visible does not mean claimable.
JSON path
Show kits with permissions assigned to players without the permission - Admins ignore usage restrictions
- On / off · required
Allow administrators to bypass kit usage restrictions. They must still have enough inventory space.
JSON path
Players with the admin permission ignore usage restrictions - Auto-kits by priority
- List · required
Exact kit names tried automatically on spawn in priority order. The plugin selects the first eligible kit; order matters.
JSON path
Autokits ordered by priority - Post-wipe cooldowns
- JSON value · required
Prevent claiming each named kit until this many seconds after the last wipe. This is not the delay between claims: 3600 makes the kit unavailable during the wipe’s first hour.
JSON path
Post wipe cooldowns (kit name | seconds) - CopyPaste parameters
- List · required
Option/value arguments passed to CopyPaste for kits containing a building. Requires CopyPaste and an existing building file.
JSON path
Parameters used when pasting a building via CopyPaste - HumanNPC kit menus
- JSON value · required
Choose kits offered when a player uses each configured HumanNPC. Names must identify existing kits; their permissions and restrictions are still checked. This table creates neither NPCs nor kits.
JSON path
Kit menu items when opened via HumanNPC (NPC user ID | Items)
UI options 2
- Default kit image URL
- Text · required
Illustrate kit cards without their own image. The direct image address is loaded through Image Library; it does not change granted items.
JSON path
UI Options → Default kit image URL - View-kit icon URL
- Text · required
Change the small button icon that opens a kit’s details. The direct image address is loaded through Image Library; the button behavior stays unchanged.
JSON path
UI Options → View kit icon URL
Configuration version 3
- Major version
- Choice · required
Internal configuration format marker. Keep the value supplied for this plugin version.
JSON path
Version → MajorAllowed values: 4
- Minor version
- Choice · required
Internal configuration format marker. Keep the value supplied for this plugin version.
JSON path
Version → MinorAllowed values: 4
- Patch version
- Choice · required
Internal configuration format marker. Keep the value supplied for this plugin version.
JSON path
Version → PatchAllowed values: 9
Pagination and section headings 2
- Background color (hex)
- Text · required
Recolor pagination-button and section-heading backgrounds without changing their actions. Use #RRGGBB; Alpha controls transparency separately.
JSON path
UI Options → Color 1 → Hex - Opacity
- Number · required
Opacity from 0 to 1 for pagination-button and section-heading backgrounds. 0 makes the background transparent, without disabling actions or necessarily hiding text.
JSON path
UI Options → Color 1 → Alpha
Available actions 2
- Background color (hex)
- Text · required
Recolor claim, purchase, create, edit, save and copy-inventory button backgrounds without changing their actions. Use #RRGGBB; Alpha controls transparency separately.
JSON path
UI Options → Color 2 → Hex - Opacity
- Number · required
Opacity from 0 to 1 for claim, purchase, create, edit, save and copy-inventory button backgrounds. 0 makes the background transparent, without disabling actions or necessarily hiding text.
JSON path
UI Options → Color 2 → Alpha
Close, back and clear 2
- Background color (hex)
- Text · required
Recolor close, back and clear button backgrounds without changing their actions. Use #RRGGBB; Alpha controls transparency separately.
JSON path
UI Options → Color 3 → Hex - Opacity
- Number · required
Opacity from 0 to 1 for close, back and clear button backgrounds. 0 makes the background transparent, without disabling actions or necessarily hiding text.
JSON path
UI Options → Color 3 → Alpha
Kit names and field areas 2
- Background color (hex)
- Text · required
Recolor kit-name, inventory-subheading, field-label and popup backgrounds without changing their actions. Use #RRGGBB; Alpha controls transparency separately.
JSON path
UI Options → Color 4 → Hex - Opacity
- Number · required
Opacity from 0 to 1 for kit-name, inventory-subheading, field-label and popup backgrounds. 0 makes the background transparent, without disabling actions or necessarily hiding text.
JSON path
UI Options → Color 4 → Alpha
Unavailable claim background 2
- Background color (hex)
- Text · required
Recolor unavailable claim-button backgrounds without changing their actions. Use #RRGGBB; Alpha controls transparency separately.
JSON path
UI Options → Disabled Color → Hex - Opacity
- Number · required
Opacity from 0 to 1 for unavailable claim-button backgrounds. 0 makes the background transparent, without disabling actions or necessarily hiding text.
JSON path
UI Options → Disabled Color → Alpha
Card and top-bar background 2
- Background color (hex)
- Text · required
Recolor kit-card backgrounds and the menu’s top bar without changing their actions. Use #RRGGBB; Alpha controls transparency separately.
JSON path
UI Options → Panel Color → Hex - Opacity
- Number · required
Opacity from 0 to 1 for kit-card backgrounds and the menu’s top bar. 0 makes the background transparent, without disabling actions or necessarily hiding text.
JSON path
UI Options → Panel Color → Alpha
Plugin instructions
Rust Kits 4.4.9
Create kits and configure their distribution under Oxide. The configurator manages two files: settings in oxide/config/Kits.json and the catalogue in oxide/data/Kits/kits_data.json.
Create a kit
- In Kit catalogue, enter its name and click Create kit.
- Add items to the main inventory, clothing slots or belt. The item picker provides Rust shortnames.
- Set a description, cooldown, cost and restrictions where needed. Use the pencil to rename the kit.
- Export the files or send them to the connected server. Reload Kits to load the catalogue.
Each slot holds one item: 24 main inventory slots, 8 clothing slots and 6 belt slots. Native slot numbers start at 0. Advanced options include skins, ammunition and durability. New items start with both durability values at 100; adjust them if your kit needs another value. Imported values remain unchanged.
Examples offers a daily starter kit and a builder kit claimed with /kit builder. Both include the catalogue and settings, ready to export.
Menu, appearance and distribution
Settings contains the chat command, economy, logging, auto-kits and post-wipe delays. Auto-kit lists and NPC menus must reference exact names from your catalogue. Auto-kits replace the respawn inventory: review this choice before enabling them. To block a kit for one hour after a wipe, add its name to the post-wipe delays with a value of 3600 (seconds).
In Appearance, edit menu colours and images. The preview uses your catalogue; its selector shows the kit list or the contents of a chosen kit. Player permissions and remaining cooldowns are not presented as live data.
Import and synchronization
Import your existing file before editing a server catalogue: replacing kits_data.json replaces all kit definitions. JSON files and ZIP archives with native folder paths are supported. Synchronization uses the same files with conflict checks.
Player claims and cooldowns in oxide/data/Kits/player_data.json are excluded from the editor. Capturing an inventory or a CopyPaste building still requires the Rust server.
Dependencies
ImageLibrary is required by this version. Economics or ServerRewards is required when selecting that currency. PlayerDLCAPI supports the skin-ownership filter; CopyPaste and HumanNPC are optional integrations.
Reference: uMod 4.4.9 source, MIT licence. The catalogue and native files were reviewed on 15 October 2026. This guide does not certify Carbon compatibility.
Install the files
With a connected server, click Send in the configurator. The result shows whether the files were sent and the plugin reloaded. Without RCON, reload the plugin from your server panel after sending.
Without a connected server: Keep a copy of the current files. Place each export in the folder shown before export, or follow the paths in the ZIP. Do not put data or translation files in the config folder.
Follow the plugin instructions above for dependencies and reloading. Exporting does not connect the site to your server.