Search the Community

Adds hacker kit to the server. Just pick up a geiger counter and use it to hack. Just get close to the crate and hold the left mouse button. This plugin uses a geiger counter. Since this is not an item that players can usually get through loot, it is perfect for this purpose. Just use a plugin like BetterLoot to insert a geiger counter into your loot tables and then any geiger counter picked up by the player can be used as a hacker kit. Permissions: hackerkit.use - required to use hacker kit To assign a permission, use: oxide.grant <user or group> <name or steam id> hackerkit.use To remove a permission, use: oxide.revoke <user or group> <name or steam id> hackerkit.use (or just use the permission manager plugin) Config file: { "Hack speed": 10, "Prohibition message": "You don't have permission to use hackerkit", "SFX prefab": "assets/prefabs/gamemodes/objects/capturepoint/effects/capturepoint_progress_beep.prefab" }

Say goodbye to the hassle of manual code locking! With this plugin, you can easily auto-lock items with a preset code straight from your inventory. Your teammates will also get instant access, no extra steps needed. The interface is super easy to use, making code updates and settings changes quick and simple. Give your Rust server a boost with this must-have plugin! Join our Discord community to stay informed on new plugins and updates. Click here to get started. Automated code locking: Automatically applies a code lock to any lockable item with a predetermined code. 3 plugins in 1: Lock regular items, secure things that normally can't be locked (like furnaces or turrets, great for PVE), and easily add automatic door closers. Balanced gameplay: Optional use of the players inventory code locks or key locks. Team authorization: Automatically grants and removes the players team to the code lock. Configuration options for data management: Provides configurable options to automatically clean up saved data on each server wipe or after a specified number of days of player inactivity. User-friendly interface: Offers an intuitive interface for players to easily update their code and adjust settings. Streamer mode: Lock items that normally cannot be locked like furnaces, turrets, and more (Great for PVE!): Optional feature for automatic door closers: Easily customizable - Toggle each item on or off to suit your server: Lockable Items: As mentioned before each of these can be individually enabled/disabled on your server! Vanilla - Doors and Ladder hatches, Storage containers, Tool Cupboards, Lockers. Extra - Furnaces, Electric ovens, Composters, Mixing Tables, Repair Benches, Research Tables, Drop Boxes, Flame Turrets, Gun Traps, Auto Turrets, Sam Sites. Automatic Door Closer Features/Config Settings: Enable/disable door closer functionality. Automatically closes the door after a player specified delay. All door types are supported, including doors, hatches, and gates. Block door removal if not placed by the player. Option to prevent door closers from being returned upon removal. Optional required resources to use door closers. 1 metal spring, 100 metal fragments per closer for example. Chat commands to manage door closers. (Required) Image Library /lock – Opens the auto lock settings UI. (Configurable) /closer – Adds or removes a door closer to the door in front of the player. (Configurable, Optional) autolock.wipe – Removes and resets all saved user data. (Automatic data cleanup included as well) autolock.admin – Grants access to the autolock.wipe console command. autolock.use – Grants access to the /lock chat command.

A lightweight plugin that disables various teaming methods to restrict players to solo gameplay. Now featuring an automated warning system with kick/ban abilities! Permissions soloenforcement.enforce Configuration { "Discord webhook URL": "https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks", "Discord message color": 9109504, "Log turret violations to Discord": false, "Log respawn violations to Discord": true, "Log revive violations to Discord": false, "Log cupboard auth violations to Discord": false, "Log team violations to Discord": false, "Log crafting violations to Discord": true, "Log automatic kicks/bans from warning system to Discord": false, "Show violation messages in chat (does not need automatic warning turned on)": true, "Use automatic warning system": false, "Maximum warnings": 3, "Show warning count (popup)": false, "Warning popup time (seconds)": 5, "Ban after maximum warnings reached (will kick otherwise)": false, "Warn for turret violations": false, "Warn for respawn violations": false, "Warn for revive violations": false, "Warn for cupboard violations (recommended NOT to use)": false, "Warn for team violations": false, "Warn for crafting violations": false, "Restrict tool cupboards": true, "Require destruction of tool cupboards": true, "Ignore tool cupboard restrictions on decaying bases": true, "Restrict turrets": true, "Restrict sleeping bags & beds": true, "Restrict team creation": true, "Restrict codelock & keylock crafting": true } Localization { "DiscordTitle": "Solo Enforcement", "ChatCupboard": "Another player is already authorized on this tool cupboard.", "DiscordCupboard": "{player1} ({player1_id}) attempted to authorize themselves on an already authorized tool cupboard.", "ChatTurretAuth": "Another player is already authorized on this turret.", "DiscordTurret": "{player1} ({player1_id}) attempted to assign {player2} ({player2_id}) to their turret.", "ChatTurretAssign": "You are not allowed to assign players to your turret.", "DiscordRespawnAssign": "{player1} ({player1_id}) attempted to assign their sleeping bag/bed to {player2} ({player2_id}).", "ChatRespawnAssign": "You are not allowed to assign players to your sleeping bags/beds.", "DiscordPublicBed": "{player1} ({player1_id}) attempted to set their bed to public.", "ChatPublicBed": "You are not allowed to set your bed to public.", "DiscordTeam": "{player1} ({player1_id}) attempted to create a team.", "ChatTeam": "Teams have been disabled.", "DiscordCraft": "{player1} ({player1_id}) attempted to craft a codelock/key.", "ChatCraft": "You are not allowed to craft that item.", "DiscordRevive": "{player1} ({player1_id}) revived {player2} ({player2_id}).", "BanMessage": "Too many teaming violations detected (auto ban).", "KickMessage": "Too many teaming violations detected (auto kick).", "WarningPopup": "Warning {0}/{1}" }

What is it? This allows players to unlock codelocks on any storage containers, there are 2 options: With a command (most likely for admins), where you come to a locked chest, type /loothack and the codelock instantly unlocks With an item (targeting computer), where you come to a locked chest, select targeting computer in your hotbar, then left-click the storage container and there you will need to wait for few seconds (if set) untill the container unlocks, also you can set in the config if the targeting computer gets consumed. Permissions loothacker.cmnd -- Gives player permission to use the command. loothacker.item -- Gives player permission to use the item. Chat Command /loothack -- Instantly unlocks the codelock on the storage cont. you are looking at Localization //FORMAT: {0} = storage short prefab name, {1} = seconds to unlock ["MustLookAtStorage"] = "You must be looking at a locked storage container to hack it!", ["NoPerms"] = "You don't have permission to use this!", ["UnlocksIn"] = "{0} will unlock in {1} secs", ["Unlocked"] = "Unlocked {0}" Configuration { "Seconds until storage unlocks": 5.0, "Consume Targeting Computer on use": true }