Khan

The Drone Market plugin allows players to conveniently place their own drone marketplace directly at their base, providing easy access to Rust's in-game marketplace without needing to travel. Each player can deploy a personal drone market, subject to optional permission and building rules. Configuration { "Sets Drone Market console command to give": "market", "Require permission dronemarket.pickup to pick up the Drone Market": false, "Require permission dronemarket.use to place": false, "Set Drone Market amount limit: 0 = Disabled": 2, "Log to file when a Drone Market is placed": false, "Force Build Requirement to be within a TC Radius": true, "Destroy when foundation is removed under it": true, "Require Building Auth to use/loot the Drone Market": true, "Only allow Team Members to use/loot the Drone Market": true, "Block all Damage to Drone Market": true, "Sets Drone Market Condition Level: HP": 100.0, "Nope Sound": "assets/prefabs/locks/keypad/effects/lock.code.denied.prefab", "Ok Sound": "assets/prefabs/locks/keypad/effects/lock.code.updated.prefab", "Breaking Sound": "assets/bundled/prefabs/fx/item_break.prefab" } Permissions dronemarket.use "Require permission dronemarket.pickup to pick up the Drone Market": true, dronemarket.pickup "Require permission dronemarket.use to place": true, Commands // Server Rcon Command: market Name-Or-SteamID amount ( amount is optional defaults to 1 ) //In Game F1 Command: market amount ( amount is optional defaults to 1 ) Click here for > Drone Market Skin

Allows weapons to have modified magazine sizes, conditions, custom names, infinity ammo/condition, control if it should drop or not on death. Features 5 permission levels ( will default to lowest number if assigned multiple permissions to a player. ) infinity ammo toggle " Without needing to reload gun" infinity condition toggle Drop Weapon on Death toggle Custom Weapon Name options for each permission on each gun Condition Level Options on item crafted Skin Id Support on item crafted Ammo Type Support on item crafted Preloaded Magazine Size support on item crafted Each weapon has the ability to rename permission at the end. Example: weaponmodifier.1 to weaponmodifier.police Item Short-Names can be found here at this link. Chat Commands /switchperm 3 1 //permission 3 is removed & 1 is granted for everyone on the server /switchperm police cop //permission police is removed & cop is granted for everyone on the server /modify <shortname> <permission> max <true/false> /modify <shortname> <permission> maxammo <true/false> /modify <shortname> <permission> drop <true/false> // These below are only for when you craft a weapon. /modify <shortname> <permission> magazinesize <100> /modify <shortname> <permission> preloadsize <100> /modify <shortname> <permission> skin <skinID> /modify <shortname> <permission> condition <100> /modify <shortname> <permission> name <NewName> /modify <shortname> <permission> ammotype <ammoshortname> Localization The default messages are in the WeaponModifier file under the oxide lang/en directory. To add support for another language, create a new language folder (e.g. de for German) if not already created, copy the default language file to the new folder and then customize the messages. { "NoPerm": "Unknown Command: modify", "Syntax": "Invalid Params please do /modify shortname permission setting value", "InvalidSelection": "You've selected an invalid weapon to modify please type a valid weapon shortname", "InvalidWeaponOption": "Weapon {0} is not an available option in the config file.", "InvalidPermission": "Invalid Permission Selected please check config for current permission names", "Success": "You've successfully set {0} {1} to {2}", "InvalidSwitch": "Invalid, Example: /switchperm 3 1\n permission 3 is removed & 1 is granted" } Config

Easily identify the owner and ID of taken photographs, also logs all images taken to discord using a simple webhook. Permissions photographsowner.use -- Allows players to use the /photo chat command photographsowner.admin -- Allows players to toggle true/false config settings Chat Commands /photo -- Shows the photographs owner ID/Name Admin Commands /setphoto displayname true -- Enables/Shows the photographs owner Display Name /setphoto id true -- Enables/Shows the photographs owner Steam 64 ID Configuration { "Display Name": true, "Display SteamID": false, "Set Who's Photo Command": "photo", "Set Admin Command": "setphoto", "Set Discord Webhook Logging": "" } Localization The default messages are in the PhotographsOwner file under the oxide lang/en directory. To add support for another language, create a new language folder (e.g. de for German) if not already created, copy the default language file to the new folder and then customize the messages. { "NoPermPhoto": "Unkown Command: {0}", "NoneFound": "No Photos Found", "Syntax": "Invalid syntax. Please use {0} option true or false.", "CmdResponse": "Successfully set {0}, to {1}", "Photographers": "Photographers:\n{0}", "DisplayName": "Display Name", "SteamID": "Steam ID", "Title": "Photographer: {0}", "Description": "Photographed In Zone: {0}", }

Prevents players from being double handcuffed, which can cause them to become permanently stuck in a handcuffed state due to a glitch. Also includes a chat command that allows affected players to restore their normal status—only usable if the player is bugged but not currently handcuffed. /restorecuffs /restorecuffs userID ( you can also manually specify a player or NPC to restore )