Skip to main content

Managing Survival Loadouts: Player Kits

Providing an initial “Starter Kit” - typically consisting of basic tools and primitive weaponry - is a important strategy for improving player retention by enabling new community members to navigate the high-risk initial minutes of a server wipe. also, implementing “VIP Kits” serves as a fundamental mechanism for server owners to reward donors or established community veterans. The Kits framework for Oxide provides a sophisticated graphical interface for managing these assets directly within your FREAKHOSTING instance.

Difficulty

Intermediate

Time

5 Minutes

Technical Initialization

Follow these steps to deploy the Kits framework to your server’s technical stack.
1

Enable Oxide Support

Ensure that Oxide/uMod is set to Enabled within your Game Panel Startup settings.
2

Deploy Plugin Script

Download the latest Kits.cs binary from the uMod repository and upload it into the /oxide/plugins/ directory.
3

Authorize Authority

To manage kits in-game, your SteamID64 must be registered as an Authenticated Server Owner.

Technical Kit Construction (GUI)

The Kits plugin uses a “Copy-from-Inventory” logic, ensuring your kit contents are precisely identical to your current character loadout.
1

Prepare the Prototype

Clear your character’s inventory and equip the exact combination of items, including ammunition counts and weapon attachments, that you wish the kit to contain.
2

Initialize the Registry

Execute the following command in the in-game chat: /kit add "starter"
3

Calibrate Parameters

Type /kit edit "starter" to reveal the graphical configuration overlay.
  • Cooldown: The temporal delay (in seconds) required between redemptions.
  • Usage Limit: The maximum number of times a single player can use the kit per world wipe.
  • Permission Node: For restricted kits, assign a custom node (e.g., kits.vip) and grant it to your group: oxide.grant group vip kits.vip.

Operational Strategies

To provide survivors with items the instant they wake up on the beach, use the command: /kit autokit "starter" true. This instructs the engine to replace the default rock and torch with your custom template upon character initialization.
The Kits plugin stores usage counts within the /oxide/data/ directory. To ensure your “Per-Wipe” limits reset correctly, we recommend deleting the Kits_Data.json file whenever you perform a World Wipe.

Need Extra Help?

If you encounter any issues, our support team is ready to assist:

Save on Your Hosting

Ready to get a new server? Use code KB20 at checkout for 20% off your first month!

Last Updated: January 2026 | Rust: Kits configured.