Search the Community

Unique kit system with the highest possible functionality and beautiful design. This will please you (no need to sit in the config every time and try to fill in some incomprehensible values, etc.), and your players (convenient, clear and informative interface). You just start editing items directly in the game) and your players (comfortable, clear, informative interface)! Features of Kits Beautiful User Interface: Experience a visually appealing and user-friendly design. High Performance: Optimized for fast, reliable performance. Automatic Kit Conversion (uMod): Easily convert your existing kits. In-Game Kit and Item Setup: Configure kits directly in the game. Auto Kits & Wipes (Optional): Automate kit distribution and server wipes. Custom Items & Commands: Assign unique items and commands to kits. Advanced Item Settings: Fine-tune every aspect of your items. CopyPaste Integration: Seamlessly work with CopyPaste. Optional Features: Delays after wipes, set blocking in Building Block, logging, and item chances. Skills & ServerPanel Support: Enhance player experience with integrated support. Commands kit – open the kit interface kit help – get help with kits kit autokit – enable or disable automatic kit. Requires the "kits.changeautokit" permission. You can set this permission up in the plugin configuration under "Permission to enable/disable autokit". kit list – display all available kits kit [name] – redeem a specific kit kits.resetkits – delete all kits kits.give [name/steamid] [kitname] – grant a kit to player kits.convert – convert from uMod Kits kits.wipe – clear players data kits.reset – resets the player data or kits in the kits system. kits.reset data [<targetID>/all] – resets the data of a player or all players. Parameters: <targetID>: The ID of the player whose data is to be reset. If you specify all, the data of all players will be reset. kits.reset kits – resets all kits in the data kits.template <interface_type> <interface_style> <template> [template_version] – allows the administrator to customize the appearance of the bundles interface by choosing between fullscreen and inmenu mode. Different styles and templates are available for each interface type. The old style (old) is only available for fullscreen mode, while the new Rust style (rust) is available for both interface types. When using the Rust style, you must specify a specific template such as normal, content, categories or content_categories. For inmenu rust templates, you can also specify the ServerPanel template version (1 or 2). Parameters: <interface_type>: The type of interface template. Valid values: fullscreen: Fullscreen interface template. inmenu: Menu interface template. <interface_style>: The style of the interface. Valid values: old: The old interface style (fullscreen only). rust: New Rust interface style (for fullscreen and inmenu). <template>: The name of the target template. Valid values depend on the interface style: normal, content, categories, content_categories. [template_version]: (Optional, only for inmenu rust) ServerPanel template version. Valid values: 1 or 2. Specifies the template version to be used with the selected inmenu rust template. Examples: kits.template fullscreen old - Sets the fullscreen interface to the old style. kits.template fullscreen rust normal - Sets the fullscreen interface to the Rust style with the normal template. kits.template fullscreen rust content - Sets the fullscreen interface to the Rust style with the content template. kits.template fullscreen rust categories - Sets the fullscreen interface to the Rust style with the categories template. kits.template fullscreen rust content_categories - Sets the fullscreen interface to the Rust style with the content_categories template. kits.template inmenu rust normal 1 - Sets the menu interface to the Rust style with the normal template for ServerPanel version 1. kits.template inmenu rust content 2 - Sets the menu interface to the Rust style with the content template for ServerPanel version 2. kits.template inmenu rust categories 1 - Sets the menu interface to Rust style with the categories template for ServerPanel version 1. kits.template inmenu rust content_categories 1 - Sets the menu interface to the Rust style with the content_categories template for ServerPanel version 1. Video P.S. Video of the old version, video for the V2+ version is now in development Showcase Full screen Templates Template OLD STYLE Template NEW RUST Default: Content: Categories: Content & Categories: In-Menu Templates Template V1 (V1.1) Default: Content: Categories: Content & Categories: Template V2 Default: Content: Categories: Content & Categories: Editor TEST SERVER Join our test server to view and experience all our unique features yourself! Copy the IP Address below to start playing! connect 194.147.90.147:28015 FAQ Q: Where can I see an example of a config? A: Config Q: Where can I see an example of a data? A: Data Q: I have a question/problem. What should I do? A: You can write to me in a PM on the site, create a ticket. Or write me in Discord: Mevent#4546 Q: Does the Kits plugin support other plugins? A: Yes, this Kits plugin has an API similar to other popular kits plugins. If the plugin works with Kits - it works with this plugin too. Q: How do I enable the sale of kits? A: You need to configure the plugin economy (which plugin, its hooks, etc.), enable "Enable sale" in the Kits data (oxide/data/Kits/Kits.json or carbon/data/Kits/Kits.json) and set the price to "Selling price" "Enable sale": true, "Selling price": 100, Q: How do I use Economics to pay for kits? A: Example configuration settings: "Economy": { "Type (Plugin/Item)": "Plugin", "Plugin name": "Economics", "Balance add hook": "Deposit", "Balance remove hook": "Withdraw", "Balance show hook": "Balance", "ShortName": "", "Display Name (empty - default)": "", "Skin": 0 }, Q: How do I use ServerRewards to pay for kits? A: Example configuration settings: "Economy": { "Type (Plugin/Item)": "Plugin", "Plugin name": "ServerRewards", "Balance add hook": "AddPoints", "Balance remove hook": "TakePoints", "Balance show hook": "CheckPoints", "ShortName": "", "Display Name (empty - default)": "", "Skin": 0 }, Q: How do I use scrap to pay for kits? A: Example configuration settings: "Economy": { "Type (Plugin/Item)": "Item", "Plugin name": "", "Balance add hook": "", "Balance remove hook": "", "Balance show hook": "", "ShortName": "scrap", "Display Name (empty - default)": "", "Skin": 0 }, Q: How do I resize the kit image? A: You can do this in the config, here's an example of the image setup (-32 and 32 are width, and -75 and -11 are height "Image Settings": { "AnchorMin": "0.5 1", "AnchorMax": "0.5 1", "OffsetMin": "-32 -75", "OffsetMax": "32 -11" }, Q: How can I remove the numbers on the kits ("#1", "#2", etc.)? A: You need to turn off "Show Number?" in the config: "Show Number?": false, Q: How do I make it so that others can see kits with different permissions without being able to claim them? A: You need to turn off "Show All Kits?" in the config: "Show All Kits?": true, Q: Where can I edit the names in the plugin or add my own language? A: You can edit lang files that are located (for example) at "oxide/lang/en/Kits.json" or "carbon/lang/en/Kits.json". HOOKS private string[] canRedeemKit(BasePlayer player) private void OnKitRedeemed(BasePlayer player, string kitName) private double OnKitCooldown(BasePlayer player, double cooldown) API private bool TryClaimKit(BasePlayer player, string name, bool usingUI) private string[] GetAllKits() private object GetKitInfo(string kitname) private string[] GetKitContents(string kitname) private double GetKitCooldown(string kitname) private double PlayerKitCooldown(ulong ID, string kitname) private int KitMax(string kitname) private double PlayerKitMax(ulong ID, string kitname) private string KitImage(string kitname) private bool IsKit(string kitname) private bool isKit(string kitname) private void GetKitNames(List<string> list) private double GetPlayerKitCooldown(ulong userId, string name) private double GetPlayerKitCooldown(string userId, string name) private void SetPlayerCooldown(ulong userId, string name, int amount) private int GetPlayerKitUses(ulong userId, string name) private int GetPlayerKitUses(string userId, string name) private void SetPlayerKitUses(ulong userId, string name, int amount) private JObject GetKitObject(string name) private int GetKitMaxUses(string name) private string GetKitDescription(string name) private string GetKitImage(string name) private bool GiveKit(BasePlayer player, string name, bool usingUI) private bool HasKitAccess(string userId, string name) private int GetPlayerKitAmount(string userId, string name)

XAutoKits - offers a beautiful menu of auto kits for your server, offering a seamless experience for players to access and manage their kits. What about giving kits to players? The plugin features its own system for granting kits, both temporarily and permanently. It can operate entirely on a permissions system. You can easily combine both options for flexibility. Key Features: Language Support: Switch plugin language in the code - LanguageEnglish = true. Interface Optimization: Adjusts for different monitor resolutions. Data Storage: Player data is stored in oxide/data/XDataSystem/XAutoKits. Multi-language Support: Available in Russian, English, Ukrainian, and Spanish. Sound Effects: Adds sound effects when interacting with the menu. Optimized UI Timer: Enhanced UI update timer for better performance. CoolDown Reset: Automatic reset of CoolDown after server wipe. Easy Kit Management: Create, edit, and view kits, cooldowns, items, modules, and more in the UI. UI Kit Editor: Edit kit items directly within the UI. Inventory Protection: Prevents misplacement of items in the Wear/Belt container. Chat Customization: Customize avatar and prefix for chat messages. Default Kits: Set default kits for new players and a list of kits available immediately. Kit Deletion: Specify the duration before a kit is deleted, ideal for events. CoolDown Setting: Set a CoolDown period for each kit. Inventory Check: Clears player inventory before giving an autokit. Kit Availability: Displays kit settings, including deletion time and CoolDown, in view all kits mode. Automatic Kit Selection: Players can independently select/change their automatic kit from the available ones. Custom Kit Images: Default size is 230x544, adjustable in configuration. Custom images available for an additional fee. Permissions xautokits.use - access to menu. xautokits.admin - access to admin functionality. xautokits.showall - access to the ability to view all kits. xautokits.ignorecd - allow to ignore CoolDown. Commands /ak, /autokit, /autokits - to open the autokits menu. [ Commands can be changed in the config. ] /autokit.admin setkit kitName - set the kit to the player, you are looking at. (Admin permission) xautokits_admin_kit_ccmd give steamID kitName seconds - give kit to a player. [ You can change the seconds and thus change the date of deleting the kit from the player. 0 - the kit will always be available to the player. seconds: 1000 or -1000. Automatically converted to Unix-time. ] xautokits_admin_kit_ccmd remove steamID kitName - remove a kit from a player. [ The kit will no longer be available to the player. ] xautokits_admin_kit_ccmd set steamID kitName - set the kit to player. [ The player inventory will be cleared. ] API bool API_SetPlayerKit(BasePlayer player, string setKitName) - set the kit to player. [ The player inventory will be cleared. ] bool IsAutoKit(string kitName) - check if a kit exists. double GetKitCooldown(string kitName) - get kit CoolDown. (sec.) double GetDeleteKitUnixDate(string kitName) - get date of kit deletion. (Unix-time) string GetKitImageURL(string kitName) - get link to the image of the kit. string GetKitPermission(string kitName) - get permission of the kit. void PlayerTimerRemove(BasePlayer player) - remove player from UI update timer. (Useful for custom menu) Hooks object CanUseAutoKit(BasePlayer player, string setKitName) - is called when a set is kit to a player after respawning. Returning non null will prevent this action. object CanSetAutoKit(BasePlayer player, string setKitName) - is called when a set is kit to a player using the API. Returning non null will prevent this action. Config { "General settings": { "SteamID profile for custom avatar": 0, "Chat prefix": "<size=12><color=#FFFFFF50>[</color> <color=#00FF0050>XAutoKits</color> <color=#FFFFFF50>]</color></size>\n", "The name of the default kit for new players": "", "List of kits that will be available to the player at all times - [ Will be given to the player ]": [], "List of commands to open the menu": [ "ak", "autokit", "autokits" ] }, "GUI settings": { "Color_background_1": "0.517 0.521 0.509 0.95", "Color_background_2": "0.217 0.221 0.209 0.95", "Color_background_3": "0.217 0.221 0.209 1", "Button color (icons)": "1 1 1 0.75", "Block color": "0.517 0.521 0.509 0.5", "Color of the active button next": "0.35 0.45 0.25 1", "Color of the inactive button next": "0.35 0.45 0.25 0.4", "Text color of the active button next": "0.75 0.95 0.41 1", "Text color of the inactive button next": "0.75 0.95 0.41 0.4", "Color of the active button back": "0.65 0.29 0.24 1", "Color of the inactive button back": "0.65 0.29 0.24 0.4", "Text color of the active button back": "0.92 0.79 0.76 1", "Text color of the inactive button back": "0.92 0.79 0.76 0.4", "MainIMG_OffsetMin": "16.5 -99.55", "MainIMG_OffsetMax": "-16.5 117.25", "InfoIMG_OffsetMin": "10 35", "InfoIMG_OffsetMax": "106.2 -35" } }