All Activity

The thick fog disappears, revealing an incredible sight before you - the Experimental Islands. These lost in the ocean present a challenge of survival. In every corner of the world lurk dangers and treasures waiting to be discovered. Features: The center island has the usual fishing village, consisting of a bandit village and a peaceful town, a peaceful town and an office filled with booty. Variety of PTs on other islands Here you will find many useful PTs such as a warehouse, gas station, lighthouse, an "Industrial Center” garden, a serious quarry and an abandoned military base. This is a real treasure trove of resources and secrets. Convenient Transportation System The entire building is equipped with a subway branch system and ziplines for quick and comfortable transportation. You can easily and conveniently move between islands. Other attractions are also available. Bradley island

Chest Finder lets players find items in storage containers within their TC-authorized base. Matching containers are marked for the searching player, with item names and quantities shown. Use /finditem <item> to search by an item name or part of a name. Searches are case-insensitive and match exact names, prefixes, and partial names. Features Markers are visible only to the player who searched. Markers show matching item names and total quantities per container. Searches are limited to the same building as the authorized TC. Previous markers are replaced when a new search starts. Search cooldown. Maximum marked containers. Setup Place ChestFinder.cs in carbon/plugins. Grant the chestfinder.use permission to the desired users or groups. Load the plugin. Its configuration file is created automatically (ChestFinder.json). The configuration includes search distance, marker duration, cooldown, minimum search length, marker limit, height, scale, color, and opacity. Tested on Carbon.

New wipe sorting system got you dreading the filtering process? Rust's native filtering system is a pain. Easy Conveyors helps remove that pain. Your players just have to set their filters once more then the filters are stored to use for the next wipe. Saving Profiles: Set your desired filters. Look at a conveyor, press shift + right click and select Save Profile. Name your profile for the filter set you are saving. Do this for each conveyor filter set you want to save. Loading Profiles: Look at the conveyor you want to load, press shift + right click and select Load Profile. Choose the profile you want for the conveyors filtering set and left click it. Done, fully developed profile that you made is loaded to the conveyor. Save over existing profiles when you add new items to the filters.

IndustrialFarming is a lightweight, vanilla-style quality-of-life plugin designed to make farming automation easier without taking away from Rust's original gameplay experience. Our focus is on improving existing mechanics rather than introducing unnecessary changes. Features: Industrial Storage Adaptor support for Composters, Beehives, and Chicken Coops. (More soon!) Automated item transfers using Rust's existing industrial system. Improved composting and automatic chicken feeding. Support for connecting multiple farming deployables together. (Daisy Chain them) Simple configuration with minimal impact on vanilla gameplay. Our goal is simple: Keep Rust feeling like Rust while making everyday farming a little easier. More Coming Soon! We're committed to improving IndustrialFarming and plan to release major updates down the line, bringing new automation features, additional content, and more quality-of-life improvements. Stay tuned!

Keep your crops harvest-ready without worrying about them dying before you return! RipeFreeze is a lightweight Rust plugin that automatically freezes player-planted crops at 5% of the Ripe growth stage, preventing them from aging until players harvest them. Perfect for servers where players want to maintain their farms without constantly monitoring crop growth. Features Automatic Growth Freeze: Crops stop aging at 5% of the Ripe stage. Vanilla Growth: Plants develop normally until reaching the configured threshold. One-Time Harvesting: Each plant can only be harvested once. Persistent Withered Plants: After harvesting, plants enter the Dying stage and remain in place until manually removed. Vanilla Genetics: Does not modify plant genetics or normal harvest yields. Existing Crop Support: Automatically detects already planted crops. Customizable Settings: Adjust the Ripe freeze percentage and monitoring interval. No Permissions Required: Works automatically without player commands. How It Works Players plant their crops normally. Plants grow through their natural growth stages. At 5% of the Ripe stage, growth automatically stops. Crops remain ready for harvesting. After harvesting, the plant enters the Dying stage. Withered plants remain until manually removed by players. RipeFreeze v1.0.0 – Tested and Functional Version 1.0.0 has been tested on a live Rust server and is functioning as intended. Installation Download RipeFreeze.cs. Place the file in your server's oxide/plugins directory. The plugin loads automatically. To reload manually: oxide.reload RipeFreeze Configuration Default settings: Ripe stage freeze percentage: 5% Check interval: 2 seconds Only affect player-planted crops: Enabled Compatibility Game: Rust Framework: Oxide/uMod Dependencies: None Author: SandFox Version: 1.0.0 Development Notice This plugin was developed by SandFox with AI assistance. Testing, configuration, and ongoing maintenance are handled by the author.

ServerPad adds a customizable virtual tablet to your Rust server, giving players a convenient desktop for accessing server commands and information. Features Custom applications: configure each application's name, icon, position, command, permission, and enabled state. Appearance presets: switch between the included Default and Halloween designs, or create your own. Three application sizes: choose Small, Middle, or Big to adjust icon and button sizes. Numbered admin grid: display cell numbers to help arrange applications in the configuration. Access permissions: control access to the entire tablet and individual applications. In-game clock: display Rust game time with configurable formatting and appearance. Player counters: show online or sleeping player counts in application labels. Local images: use PNG files stored on your server. ImageLibrary and external image hosting are not required. Included ServerPad.cs plugin. Two ready-to-use presets: Default and Halloween, with tablet frames, wallpapers, application icons, and preset settings. Four additional tablet frame images for customizing your presets. How applications work Applications are shortcuts to commands configured by the server owner. For example, setting an application's command to chat.say /store makes it execute the player's /store chat command. Selecting a command shortcut closes the tablet and runs the command as that player. Existing permission checks in the target plugin still apply. ServerPad provides the tablet interface; features such as shops, statistics, skins, and friends systems are supplied by separate plugins. Install and configure any plugins your shortcuts require. They are not included with ServerPad and may have their own costs. Installation — Oxide/uMod Extract the archive. Copy the included oxide/data/ServerPad/ folder into your server's oxide/data/ directory. Copy ServerPad.cs into oxide/plugins/. Open the generated oxide/config/ServerPad.json file and configure your applications, preset, and access settings. After making changes, run oxide.reload ServerPad. Use /tablet in chat to open the tablet. Copy the preset files before loading the plugin. Keep their folder names and image filenames intact. Commands Command Purpose /tablet Open the tablet. The chat command can be changed in the configuration. tablet open Open the tablet from the player's F1 console. tablet close Close the tablet from the player's F1 console. tablet grid Toggle the numbered grid while the tablet is open. Requires administrator status and the grid option enabled in the configuration. Enabling the administrator grid option also adds a GRID button to the tablet. Permissions By default, the tablet is available to all players. To restrict access, set the main permission to serverpad.use, reload the plugin, and grant it to the desired users or groups. For example: oxide.grant group vip serverpad.use Each application can also require its own permission. Applications are hidden from players who do not have that permission. Customizing presets Each preset has its own folder under oxide/data/ServerPad/, containing: tablet_frame.png — tablet frame. wallpaper_desktop.png — desktop background. Application icon PNG files. preset.json — clock and close-button settings. The clock and close button support configurable text, text size, text color, font, alignment, and position. The clock also has a configurable time format. To create a preset, copy an existing preset folder, give it a new name, replace the images, adjust its settings, and select it in the main configuration. Applications share the same configuration across presets, so provide matching icons in each preset you use. Configuration notes Small supports 66 cells, Middle supports 45, and Big supports 28. Larger sizes reduce the available positions. Use the numbered grid to choose valid positions; applications outside the available area are hidden and are not moved automatically. The grid is a placement guide. Application positions are edited in JSON. Player counters refresh when the tablet is opened. The clock shows Rust game time, not real-world time. ServerPad.json

Raid Warden Raid protection that players buy at their tool cupboard, Softcore raid hours for normal servers, daily raid limits, raid alerts in game and on Rust+, and cupboard ruins that hold a base until its owners repair it. Built so raiders can't game it. Oxide and Carbon. Built for the October 2026 Rust update. Ten languages. No ImageLibrary needed. About Raid Warden lets players protect their base while they sleep, at a price you set. Owners pay at their tool cupboard with scrap, Economics, Server Rewards, or any items you choose, each with its own value. Protection cuts raid damage by a percent you choose for each tier: one level while an owner is online, another once every owner has logged off. Raiders can't game it. Anyone who authorizes on a cupboard during a raid is flagged: they don't count as an owner, can't pause or refund, and stay flagged if they leave and come back. Offline protection only starts after a quiet period with no raid hits, so logging off in the middle of a raid doesn't save a base. Raiders can't keep it off forever by chipping at a wall either, because hits can only delay it for a set time. Raid Warden also brings Rust's Softcore raid rules to normal servers: raid hours with an on-screen timer, and cupboard ruins that stop anyone building on a base until its owners repair it. Add daily raid limits per team, alerts to owners when their base is hit, and Discord logging, and one plugin covers what used to take three or four. Admins run all of it from an in-game panel: every setting, raid hours on a week grid, tiers, and a list of every protected base with its live status and history. Changes apply straight away, without reloading the plugin. Features Protection time Players buy hours at the tool cupboard from a panel beside the cupboard screen, or with /rw. Separate protection levels while an owner is online and once all owners are offline, set per tier. Offline protection starts after a delay and a quiet period with no raid hits. Raid hits can only hold it off for a set time, 60 minutes by default. Tiers by permission (raidwarden.tier.<name>), with a fallback tier for everyone else. Hourly cost with extras per authorized player and per 50 building blocks, or a cost per 100 damage blocked. A tier with no cost is free and switches on by itself. Charge only while protection is actually blocking damage, or all the time. Limits on banked hours and on protected cupboards per player. If a player drops to a plan with fewer cupboards, say when a VIP permission runs out, protection switches off on their newest ones and the time stays on them. Offline protection can switch on at once or build up over a set time. Each player's first tool cupboard after a wipe can come with free starter hours. Free time can't be refunded, and that includes time added or given back by an admin or another plugin, so nobody can cash a reward out as currency. A refund pays back the bought time and leaves the free time on the cupboard. Protected bases can be set not to decay, per tier. Those tiers use banked time whenever protection is on, since it's stopping decay too. Take more than one item: the main currency plus any items you add, each with its own value, like metal fragments at 10 per scrap. Players pick what to pay with at the cupboard, and the prices change to match. Refunds at a percent you choose, behind a two-click confirm. They go back in the items each base was paid with, in proportion to what's left of each payment, so nobody can swap frags for scrap through a refund. Works on tugboats as well as bases. Owners and raiders Owners are the players authorized on the cupboard, plus their team, their clan and the other players on code locks an owner uses, each one switchable. Someone who sets a new code on a lock left unlocked doesn't become an owner. A player who leaves still counts as an owner for a few hours, so owners can't switch on offline protection by deauthorizing teammates who are still online. Anyone who authorizes within a set time after a raid hit is flagged as a raider, and stays flagged if they leave and come back. Clearing the cupboard list removes them at once. When someone refunds, pauses or switches off protection, the base's other owners are told. Owners get a warning before their protection runs out, a set number of hours ahead. Owners who were offline get it, and any other message about their base, when they next log in. If two protected bases get joined together, Rust removes one cupboard. Its protection time moves to the cupboard Rust keeps. Players with raidwarden.exempt never count as owners, which keeps admins from holding bases at their online level. Raid alerts Owners who are online get a Rust alert when raiders hit their base, saying how much protection is blocking. Owners who are offline get a phone alert through the Rust+ app, the same push Rust uses for smart alarms. No bot or extra service. At most one alert per base every few minutes, so nobody gets spammed. Alerts only go to the base's current owners, never to players who have left. Works for every base with a cupboard, protected or not. Raid limits Each team can raid a set number of different bases a day. Going back to a base it already raided that day doesn't count again. A whole clan can count as one team, with Rust's own clans or the Clans plugin. Leaving a team doesn't give raids back. The raids it used that day still count for everyone who was in it. Raiders get a toast when a raid counts and when they've hit the limit, with the time until it resets. The panel shows how many raids their team has left. The day resets at a time you choose, in your time zone. Admins can check and reset counts from the console. Raid hours Open hours for each day of the week, several ranges per day, and ranges that run past midnight. Your time zone by name, or a fixed offset like UTC+10. Outside raid hours raiders can't damage bases at all, including with fire and bullets, and banked protection time isn't used. Or let a share of damage through, such as 25%, if you want closed hours to be softer. Twig stays breakable and decay keeps working. A new base can be raided at any hour for its first hour, like Softcore, so nobody can claim a spot outside raid hours. A raid underway at closing time can run on for a set number of minutes. Raids can stay closed for a set time after a wipe. MLRS strikes are blocked while raids are closed, and so are ladders on other players' bases. Your own server commands can run when raids open and when they close, and once at server start for whichever state raids are in, so settings that don't survive a restart are put back. A week view in the panel shows every day's raid window and where you are now. An on-screen countdown, announcements when raids open and close, and a warning before each. Players can hide the display with /rw hud. Admins can force raids open or closed from the console. Cupboard ruins A cupboard destroyed by raiders leaves Rust's own cupboard ruin, holding half its contents. Nobody can build within a radius of the ruin until an owner repairs it with a hammer and 200 Wood. The repair brings back the cupboard, its lock, its authorized players and its banked protection time. An owner breaking their own cupboard leaves no ruin. A flagged raider who authorized on it still leaves one. Base history and rollback Every purchase, refund, pause, stretch of protection used, admin change and raid attempt is logged per base, with who did it. Owners see it on the History page of the panel or with /rw history. Attacker names stay hidden unless you turn them on. Admins can undo any single entry, or give back the protection time used in the last 30 minutes, 2 hours or any window, for one base or every base, with a preview before anything changes. Admin panel Open it with /rw admin in chat or raidwarden.admin in the F1 console. It needs the raidwarden.admin permission or Rust admin. Overview: protected bases, bases blocking damage right now, raids in the last day, total banked, the latest raids across the server, and whether raids are open, with buttons to open or close them now or go back to the schedule. Bases: every protected base with its grid, owner, tier, live status, time left and last raid. Search by owner, Steam ID or grid, filter to protected, unprotected, flagged, raided today or ruins, and sort by any column. Each base: add or remove time, clear it, pause or resume, switch protection on or off, clear raider flags, reset the record, teleport there, and undo any single history entry. Ruins can be inspected and removed. Raid hours: click hours on a week grid to open or close them, click a day to switch the whole day, or type exact ranges. Copy Monday to every day in one click. If a change would open or close raids right now, the panel asks you to confirm first. Raid limits: who has raided today and how many bases they've used, with a reset for one team or everyone. Tiers: add a tier from a copy, rename it, change any value, delete it, and pick the default tier. Renaming keeps the default tier pointing at it. Payment: pick the main currency or item, then add other items with a click on their icon and set what each is worth. Every config setting is in the panel, grouped into pages. Changes apply at once, with no plugin reload, and are written to the config file. Bad values are refused with the reason, such as an item that doesn't exist or a time zone the machine doesn't know. Undo my changes puts every setting back the way it was when you opened the panel, and Reload config file picks up edits made by hand. Give back protection time used in a recent window, with a preview first. Discord webhook test button, detected plugins list, and damage check timings. Every admin change can be posted to Discord with who made it, what changed, and the old and new values. The server commands that run when raids open or close, and the Discord webhook, can only be changed by the server owner (auth level 2). Moderators you give raidwarden.admin can't use the panel to run console commands or redirect your logs. Discord Post raids on protected bases, raids opening and closing, purchases and refunds, and admin changes to a Discord webhook. Each kind can be switched on or off. Each post names the base in its title, then the raider, owner and protection on one line. Player names link to their Steam profiles and your server's name sits at the bottom. Raid hour posts show the next change in each reader's own time zone. Only raid posts are marked in red, so they stand out in a busy log channel. Posts use your server's language, so a Russian or German server gets Russian or German posts. Posts are batched to stay inside Discord's rate limits on busy raid nights. On screen A PROTECTION button on the cupboard panel, beside LOOT, that shows time left or what's wrong. With BetterTC installed it moves to the top bar so the two don't overlap, and you can pin it to either spot. Panel pages for the base, the rules (written from your config), raid hours and history. Rust's own tooltips explain every greyed-out button. A badge under the raid timer shows owners how protected their base is while they stand in it. You can show it to everyone or no one instead. Every message a player gets without asking can be a Rust toast, chat, both, Notify, or switched off: attacker notices, raid alerts, messages to owners about their protection and raid hour announcements. The placement tip switches off too. Switch those off along with the button, badge and timer, and players get base protection with nothing on screen. Chat commands can be renamed, or removed so players only use the cupboard button. Every icon is built into Rust, so there are no image downloads and no ImageLibrary. Ten languages built in. Each player sees their own, picked from their Rust language setting. Works with Economics Pay for protection and get refunds in Economics money Server Rewards Pay for protection and get refunds in RP Clans (k1lly0u) Clan members count as owners, and a clan can count as one team for raid limits Rust teams and clans Team and clan members count as owners Zone Manager Bases inside the zones you list get no protection and no raid hours TruePVE Hits TruePVE blocks don't count as raids and don't start raider flags Raidable Bases Its bases are left alone and never leave ruins Abandoned Bases Bases inside an abandoned event are left alone until it ends Rust+ companion app Phone alerts to owners who are offline when their base is hit Discord Raid, raid hours, purchase and admin posts to a webhook UI Notify (Mevent) Attacker notices, owner raid alerts and raid hour announcements as UI Notify popups Notify (Mevent) The same, through the same API as UI Notify BetterTC (ninco90) The PROTECTION button moves to the top bar so it doesn't cover BetterTC's cupboard buttons Placeholder API {raidwarden.raids}, {raidwarden.raids.left}, {raidwarden.protection} and {raidwarden.limit.left} for scoreboards and HUD plugins. The protection placeholder only shows to a base's owners, unless the badge is set to everyone Tested means Raid Warden ran against that plugin's current release on both Oxide and Carbon. Documented means Raid Warden follows the plugin's published API, but it hasn't been run against the plugin itself. Raid Warden only ever returns true or nothing from OnEntityTakeDamage, the same contract TruePVE, Zone Manager and Raidable Bases use, so it doesn't trigger hook conflict warnings with them. Quick setup Put RaidWarden.cs in oxide/plugins or carbon/plugins. Every player gets the standard tier: 85% protection once all owners are offline, for 7 scrap an hour plus a little per extra owner and per 50 building blocks. Grant raidwarden.tier.vip to a group for 30% online and 100% offline protection at 5 scrap an hour. Common setups. Each one can be done in the config file or in game with /rw admin: Free offline protection for everyone: set every cost in a tier to 0. Softcore rules on a normal server: turn on Raid hours and Destroyed tool cupboards. Raid hours only: leave the fallback tier blank and turn on Raid hours. Raid limits: turn on Raid limits and set how many bases each team can raid a day. Discord logging: paste a webhook URL under Discord. Commands Players (chat) /rw Open the protection panel for the base you're in /rw status Protection details in chat /rw buy <hours|max> [item] Buy protection time. The item is optional and takes everyday names like frags or hqm. /rw pause, /rw resume Stop or restart protection /rw refund Get banked time back /rw activate, /rw release Use or free one of your protected cupboard slots /rw raids Raid hours, when raids next open or close, and raids left today /rw history What happened at this base /rw hud Show or hide the raid timer and protection badge The chat commands are /rw and /raidwarden by default and can be renamed in the config. Admins (F1 console or RCON) raidwarden.admin or /rw admin Open the admin panel raidwarden.list Every protected base with its cupboard id, owner, balance and state raidwarden.history [cupboard id] Numbered history for a base, or the base you're standing in raidwarden.undo [cupboard id] <entry> Undo one history entry, numbered from your last raidwarden.history listing raidwarden.rollback <30m|2h|1d> [cupboard id] [confirm] Give back the protection time used in that window. Without confirm it only shows what would change. raidwarden.credit <cupboard id> <amount> Add to or take from a base's balance (added time is free time) raidwarden.raids [open|closed|auto] Show raid hours, or force raids open or closed until you set auto raidwarden.limits [steamid] Raid limit counts for today, for everyone or one player's team raidwarden.limits reset [steamid] Reset raid limits for everyone or one player's team raidwarden.tp <cupboard id> Teleport to a base (F1 console in game) raidwarden.perf [reset] How much time the damage hook has used Permissions raidwarden.admin The admin panel, console commands, viewing any base's panel, the admin row in the panel and clearing raider flags raidwarden.exempt Never counts as an owner of any base raidwarden.tier.<name> Uses that tier. The player who placed the cupboard decides the tier. Created for every tier in the config. Configuration The default config, as written on first load. Every option says what it does in its name. { "Chat commands": [ "rw", "raidwarden" ], "Tier for players without a tier permission (blank = no protection)": "standard", "Tip players about protection when they place a tool cupboard": true, "Free protection hours on each player's first tool cupboard after a wipe (0 = off)": 0.0, "Seconds between protection notices to an attacker": 8.0, "Interface": { "Add a Protection button to the tool cupboard screen": true, "Protection button position (Auto, Loot, TopBar)": "Auto", "Chat command opens the protection panel (false = chat text)": true, "Attacker notice (Toast, Chat, Both, Notify, None)": "Toast", "Protection badge for players standing in a protected base (Owners, Everyone, None)": "Owners", "Hours on the buy buttons (up to 4)": [ 1.0, 6.0, 24.0 ] }, "Raid alerts": { "Alert owners in game when raiders hit their base (Toast, Chat, Both, Notify, None)": "Toast", "Send Rust+ phone alerts to owners who are offline": true, "Minutes between alerts for the same base": 5.0, "Protection messages to owners: running low, ran out, other owners' changes, starter hours, ruins (Chat, Toast, Both, Notify, None)": "Chat", "Warn owners when this many hours of protection are left (0 = off)": 2.0 }, "Payment": { "Currency (Item, Economics, ServerRewards)": "Item", "Item shortname": "scrap", "Item skin ID (0 = unskinned only)": 0, "Allow refunds": true, "Percent returned on refund": 90.0, "Other items players can pay with (item shortname: what one is worth in the main currency)": {} }, "Ownership": { "Count native team members as owners": true, "Count native clan members as owners": true, "Count Clans plugin members as owners": true, "Count players on owners' code locks as owners": true, "Hours a player still counts as an owner after leaving": 8.0, "Minutes after a raid hit during which new authorizations count as raiders": 25.0 }, "Protected parts": { "Building blocks": true, "Twig building blocks": false, "Doors, hatches and gates": true, "Windows, bars and other wall inserts": true, "Deployables": true, "Tool cupboard": true, "Tugboat hulls": true }, "Protected against": { "Players who are not owners": true, "Owners": false, "NPCs, helicopters and tanks": true, "Damage with no known attacker": true }, "Raid hours": { "Enabled (raids only work during the hours below)": false, "Time zone (blank = server clock, or e.g. Europe/London, Eastern Standard Time, UTC+10)": "", "Open hours by day (24h clock, ranges split by commas, 22:00-02:00 runs past midnight, blank = closed)": { "Monday": "18:00-21:00", "Tuesday": "18:00-21:00", "Wednesday": "18:00-21:00", "Thursday": "18:00-21:00", "Friday": "18:00-21:00", "Saturday": "17:00-22:00", "Sunday": "17:00-22:00" }, "Hours after a map wipe before raids can open": 0.0, "Minutes a raid already underway can run past closing time": 0.0, "Minutes a new base stays raidable at any hour after its cupboard is placed": 60.0, "Damage that still gets through while raids are closed (%)": 0.0, "Block MLRS strikes while raids are closed": true, "Block ladders on other players' bases while raids are closed": true, "Show the raid timer on screen": true, "Timer anchor (0 0 = bottom left, 1 1 = top right)": "1 1", "Timer offset from the anchor (x y, at 1280x720)": "-52 -16", "Announce raids opening and closing (Toast, Chat, Both, Notify, None)": "Toast", "Warn this many minutes before raids open or close (0 = off)": 10.0, "Server commands to run when raids open": [], "Server commands to run when raids close": [] }, "Raid limits": { "Enabled (each team can only raid a set number of bases a day)": false, "Bases each team can raid per day": 3, "New day starts at (24h clock, raid hours time zone)": "00:00", "Count a whole clan as one team": true }, "Destroyed tool cupboards": { "Leave a ruin when raiders destroy a tool cupboard": false, "Nobody can build within this many meters of a ruin": 16.0 }, "Base history": { "Entries kept per base (0 = off)": 40, "Show attacker names to owners": false, "Minutes without hits that end a raid attempt": 10.0 }, "Discord": { "Webhook URL (blank = off)": "", "Post raids on protected bases": true, "Post raids opening and closing": true, "Post purchases and refunds": false, "Post admin changes": true }, "Other plugins": { "Leave Raidable Bases and Abandoned Bases events alone": true, "Zone Manager zone IDs where Raid Warden does nothing": [], "Notify plugin type for notices set to Notify": 0 }, "Tiers": [ { "Name": "standard", "Priority (highest wins)": 10, "Protection while any owner is online (%)": 0.0, "Protection while all owners are offline (%)": 85.0, "Seconds after the last owner leaves before offline protection starts": 900.0, "Seconds without raid hits needed before offline protection starts": 720.0, "Most minutes raid hits can delay offline protection after owners leave (0 = no limit)": 60.0, "Minutes for offline protection to build up from the online level (0 = straight away)": 0.0, "Cost per hour": 7.0, "Extra cost per hour for each authorized player after the first": 2.0, "Extra cost per hour for every 50 building blocks": 1.0, "Cost per 100 damage blocked": 0.0, "Only charge while protection is blocking damage": true, "Most hours that can be banked (0 = no limit)": 48.0, "Most protected cupboards per player (0 = no limit)": 2, "Allow tugboat protection": true, "Protected bases don't decay": false }, { "Name": "vip", "Priority (highest wins)": 20, "Protection while any owner is online (%)": 30.0, "Protection while all owners are offline (%)": 100.0, "Seconds after the last owner leaves before offline protection starts": 600.0, "Seconds without raid hits needed before offline protection starts": 720.0, "Most minutes raid hits can delay offline protection after owners leave (0 = no limit)": 60.0, "Minutes for offline protection to build up from the online level (0 = straight away)": 0.0, "Cost per hour": 5.0, "Extra cost per hour for each authorized player after the first": 2.0, "Extra cost per hour for every 50 building blocks": 1.0, "Cost per 100 damage blocked": 0.0, "Only charge while protection is blocking damage": true, "Most hours that can be banked (0 = no limit)": 96.0, "Most protected cupboards per player (0 = no limit)": 4, "Allow tugboat protection": true, "Protected bases don't decay": false } ] } Performance Measured on a dev server (Intel i7-13700KF) with Oxide 2.0, Carbon 2.0 and the October 2026 Rust build. 3 µs per hit on a protected base, on Oxide and Carbon 0.06 µs per hit on anything else, like players and animals 0.8 ms once a minute with 300 protected bases (2.5 ms with 1,000) 45 ms at most per server save with 300 bases (53 ms with 1,000), each holding a full 40-entry history 1 ms at most per tick for protection badges with 200 players online (Oxide; about 3 ms on Carbon) 2.2 ms a second for 20 cupboard panels open at once (Oxide; about 4.7 ms on Carbon) Busy-server figures come from 200 players in 50 bases, ten of them with 192 blocks and 16 locked doors. Badge updates are spread across ticks, and an open panel only rebuilds when something on it changes. Nothing is drawn per hit, and the admin panel costs nothing until an admin opens it. For developers API float API_GetProtection(BaseEntity entity) Percent blocked right now, 100 while raids are closed bool API_RaidsOpen() Whether raids are open double API_RaidsChangeAt() Unix time of the next open or close, 0 if none double API_GetBalance(BaseEntity entity) Banked balance in the server's currency double API_GetHoursLeft(BaseEntity entity) Hours of protection left at the current price bool API_AddBalance(BaseEntity entity, double amount) Adds to the balance and switches protection on. Added time is free time and isn't refunded. Returns false for 0, or for a base with no tier or a free tier bool API_IsOwner(BaseEntity entity, ulong userId) Whether the player counts as an owner int API_GetRaidsLeft(ulong userId) Raids the player's team has left today, -1 when raid limits are off Hooks object CanRaidWardenProtect(BaseEntity entity) Before Raid Warden handles a base. Return false and it leaves that base alone. void OnRaidWardenProtectionBought(BasePlayer player, BaseEntity cupboard, double hours, int price) After a player buys protection void OnRaidWardenRaidsOpened(), void OnRaidWardenRaidsClosed() When raid hours open or close void OnRaidWardenRuinCreated(ContainerCorpse ruin, ulong ownerId) When raiders destroy a cupboard and it leaves a ruin void OnRaidWardenRuinRebuilt(BuildingPrivlidge cupboard, ulong ownerId) When an owner repairs a ruin void OnRaidWardenRaidStarted(BaseEntity cupboard, ulong attackerId, float percent) When a raid attempt on a base starts void OnRaidWardenRaidCounted(ulong attackerId, BaseEntity cupboard, int used, int limit) When a raid counts toward a team's daily limit void OnRaidWardenProtectionEnded(BaseEntity cupboard) When a base runs out of protection time void OnRaidWardenProtectionStarted(BaseEntity cupboard, string reason) When a base's protection switches on, once per change. Reason: bought, starter, added, activated, resumed, rebuilt, merged, tier or admin void OnRaidWardenProtectionStopped(BaseEntity cupboard, string reason) When it switches off, once per change. Reason: ranout, paused, released, refunded, removed, destroyed, tier or admin. With destroyed the cupboard may already be gone entity can be the cupboard or any part of the base. The started and stopped hooks fire on changes only, not when the server or plugin loads, so read API_GetProtection when your plugin starts. FAQ Can raiders get protection by authorizing on the cupboard mid-raid? No. Anyone who authorizes within the raider window after a raid hit is flagged. They don't count as owners, can't manage protection and can't hold the base at its offline level. Clearing the cupboard list drops them at once, they're still flagged if they come back later, and an admin can clear the flags from the panel. A teammate refunded our protection. Can I fix it? Yes. The other owners are told in chat when it happens, and the base history shows who did it and when. raidwarden.undo puts the time back as free time, so it can't be refunded again, and tells you how much the refund paid out so you can take it back from them. Protection drained because of a bad price in my config. Can I give it back? Yes. raidwarden.rollback 2h shows how much protection time bases used in the last two hours. Add confirm to give it all back as free time. The same window can't be given back twice. What happens when raiders destroy a protected cupboard? With ruins on, the balance is kept and comes back when an owner repairs the ruin. With ruins off, the protection is gone with the cupboard. Is twig protected? Is decay blocked? Twig isn't protected by default, and you can change that. Decay keeps working unless you turn on Protected bases don't decay for a tier. Does it work on Softcore servers? Raid Warden is built for normal servers. On Softcore, Rust already runs raid windows and cupboard ruins, so leave those two features off and use the rest. Can players pay with something other than scrap? Yes. Keep scrap (or Economics, or Server Rewards) as the main currency and add any items you like, each with its own value. Players choose what to pay with at the cupboard. Prices are set in the main currency, and refunds go back in the items each base was paid with. Do I have to edit the config file? No. Every setting is in the admin panel (/rw admin) and applies straight away. The config file is still there if you prefer it, and the panel can reload it after you edit it by hand. Does it need ImageLibrary or any other plugin? No. Everything in the list above is optional. Raid Warden uses only Rust's built-in icons and never touches ImageLibrary, so it has nothing to clash with if your other plugins use it. I set notices to Notify but players see chat or nothing. Why? With UI Notify, players need the uinotify.see permission (give it to the default group), otherwise UI Notify sends the message to chat. The Notify type number in Raid Warden's config has to exist in UI Notify's config: 0 is its blue notification, 1 its red error. If no Notify plugin is loaded at all, Raid Warden falls back to Rust's own toast. UI Notify's popups sit in the top right like Raid Warden's raid timer, so move one of them with the timer anchor and offset or UI Notify's Y Indent. Will an update reset my settings or data? No. New settings are added with their defaults, and your settings, bases, balances, history and your own edits to the language files are kept. Updates are tested by upgrading a running server with real bases on Oxide and Carbon, and by rolling back again. What happens on a map wipe? Protection data resets with the map. Players' raid timer setting is kept. Do owners need Rust+ for raid alerts? No. Owners who are online get an alert in game. Owners who are offline get a phone alert if they've paired your server in the Rust+ app and the server has the companion app enabled. Will raid limits cut a raid off halfway? No. A base the team already started raiding today doesn't count again, so they can finish. Only new bases are off limits once the team hits its limit. Which languages does it speak? English, Russian, Ukrainian, Polish, German, French, Spanish, Portuguese (Brazil), Chinese (Simplified) and Turkish, picked from each player's Rust language. Every message, button and label is in the lang files, so you can change any of them. Notes Raid Warden charges in-game currency. If you sell VIP tiers for real money, make sure that follows Facepunch's rules for server monetization. Support is through the Support tab on this page.

Livestock Genetics 1.0.1 — Oxide/uMod Rust plugin Stand within 10 metres and look directly at a living adult cow, bull, sheep, or ram. Run the chat command: -/animalgenes Opens the name and genetics editor. -/animaledit Type a new name in the name field and press Enter to stage it. Names must be 1-24 characters. The "Name to save" line confirms the staged name. Click either copy of a gene to cycle Good / Ok / Bad, or choose ALL GOOD.Choose APPLY CHANGES to save the staged name and genes together.CANCEL or X discards all staged changes. The editor stays attached to the animal selected when it opened. You must remain within 10 meters. Permission and target validity are checked again for every editing action. If another command or admin changes its nameor genes while the editor is open, saving is refused; reopen it to refresh. DIRECT CHAT COMMANDS-/animalgenes goodSets all five genes to Good/Good. -/animalgenes okSets all five genes to Ok/Ok. -/animalgenes badSets all five genes to Bad/Bad. -/animalgenes good ok good good badSets the five genes in this order: Dung, Longevity, Yield, Fertility, Hardiness. -/animalgenes good/bad ok good good badSets Dung to Good/Bad; single values set both inherited copies. -/animalgenes show Displays the game's detailed genetics report for the targeted animal.ACCESSServer admins can use the command automatically.To allow a specific non-admin, use the server console: oxide.grant user STEAMID livestockgenetics.useTo revoke that permission: oxide.revoke user STEAMID livestockgenetics.use

Allows players to subscribe and unsubscribe to broadcast messages sent by other plugins. This helps manage notification fatigue in servers with multiple plugins sending frequent messages. Works on both Oxide and Carbon servers. Features Personalization: Each player can subscribe or unsubscribe to specific broadcast topics. Flexible Categorization: Topics can be defined by server admins to match broadcast messages using regular expressions, allowing for flexible categorization. This also means that this plugin is non-intrusive and works with existing and future plugins without modification. Message Support: Supports broadcasted (Server.Broadcast) and direct (Player.Reply) messages sent from other plugins. Chat Commands /topic - Shows usage information for the plugin. /topic list - Lists all available broadcast topics along with the player's current subscription status. /topic subscribe <topic name|number> - Subscribes the player to the specified topic. Aliases for subscribe: sub, enable, on /topic unsubscribe <topic name|number> - Unsubscribes the player from the specified topic. Aliases for unsubscribe: unsub, disable, off /topic toggle <topic name|number> - Toggles the player's subscription status for the specified topic. Console Commands broadcastpreferences.testbroadcast [message] - Sends a test broadcast message to the console and all players. If no message is provided, a default test message is used. Can be useful for testing your topic regex configurations. broadcastpreferences.testreply [message] - Sends a test direct reply message to all players. If no message is provided, a default test message is used. Can be useful for testing your topic regex configurations. Configuration The config file is oxide/config/BroadcastPreferences.json on Oxide and carbon/configs/BroadcastPreferences.json on Carbon. Player preferences are saved in oxide/data/BroadcastPreferences.json on Oxide and carbon/data/BroadcastPreferences.json on Carbon. { "Topics": [ { "Topic ID": "raidable_bases", "Display Name": "Raidable Bases", "Enabled": true, "Description": "Raidable Bases notifications", "Subscribe By Default": true, "User ID Match (0=Ignore)": 0, "Message Regex Match (empty=Ignore)": [ "raidable base event has opened", "Destroyed a left over raid base at", "Next automated raid in" ], "Override Steam Avatar User ID": 0, "Stop On Match": false, "Ignore Styles": true }, { "Topic ID": "death_notes", "Display Name": "Death Notes", "Enabled": true, "Description": "Player death notifications", "Subscribe By Default": true, "User ID Match (0=Ignore)": 0, "Message Regex Match (empty=Ignore)": ["^\\[DeathNotes\\]"], "Override Steam Avatar User ID": 0, "Stop On Match": false, "Ignore Styles": true }, { "Topic ID": "inbound", "Display Name": "Inbound Events", "Enabled": true, "Description": "Heli, Cargo, Drops and other inbound events", "Subscribe By Default": true, "User ID Match (0=Ignore)": 0, "Message Regex Match (empty=Ignore)": [ "^Patrol Helicopter inbound", "^Cargo Ship inbound", "^Cargo Ship is approaching the harbor", "^Cargo Ship has docked at the harbor", "^Chinook inbound", "^Bradley APC inbound", "^Travelling Vendor inbound", "^Hackable Crate has spawned", "Cargo Plane inbound", " has activated The Excavator", " has requested a supply drop", " is hacking a locked crate", " has deployed a supply signal", "Supply Drop has (dropped|landed)" ], "Override Steam Avatar User ID": 0, "Stop On Match": false, "Ignore Styles": true } ], "Version": { "Major": 0, "Minor": 3, "Patch": 0 } } Topics: An array of topic objects defining the broadcast categories. The order of topics only matters if the Stop On Match option is used. Topics are evaluated in the order they are listed. Topic ID: A unique identifier for the topic. Display Name: The name displayed in chat to players for this topic. Enabled: Whether the topic is active. Description: A brief description of the topic that players will see in the /topic list command. Subscribe By Default: Default subscription status for players who have not explicitly set their preference. User ID Match: If set to a specific user ID, only messages from that user will be considered for this topic. Set to 0 to ignore user ID filtering. This can be useful that allow you to configure the user ID used when sending messages. You can specify a random user ID that will match the topic, then override the avatar using the Override Steam Avatar User ID setting. Message Regex Match: An array of regular expressions used to match broadcast messages for this topic. You may specify multiple regex patterns for a single topic. The first matching pattern will trigger the topic. Override Steam Avatar User ID: If set, this user ID's avatar will be used in notifications for this topic. Particularly useful when combined with the User ID Match setting. Stop On Match: If true, no further topics will be checked after a match is found for this topic. In practice, you shouldn't really need this option unless you've got two topics with overlapping regex patterns. Scenario: Topic A: ^\\[Important\\] with Stop On Match set to true Topic B: Important Message: [Important] Server will restart in 10 minutes. Player is unsubscribed to Topic A but subscribed to Topic B. Result: The message matches Topic A and stops looking for more topics, so the player does not receive the message, even though they are subscribed to Topic B, because Topic A stopped further processing. Ignore Styles: If true, the plugin will strip any <color> and <size> tags from messages before processing them for this topic. Localization The English lang file is oxide/lang/en/BroadcastPreferences.json on Oxide and carbon/lang/en/BroadcastPreferences.json on Carbon. { "TestMessage": "This is a <color=#ff00ff>test message</color> for <color=yellow>Broadcast Subscriptions</color> <color=#f0f>plugin</color>.", "Usage": "Usage:", "Usage.Description": "Listen or mute broadcasted messages by topic.", "Usage.Command": "<color=#f0761f>{0}</color> - {1}", "Usage.List": "Lists available topics", "Usage.Subscribe": "Subscribes to a topic by name or list number", "Usage.Unsubscribe": "Unsubscribes from a topic by name or list number", "Usage.Toggle": "Toggles subscription to a topic by name or list number", "List.AvailableTopics": "Broadcast Preferences (<color=#bcc2c2>Unsubscribed</color> / <color=#62ed53>Subscribed</color>):", "Topic.NotFound": "Topic '{0}' not found.", "Topic.AlreadySubscribed": "You are already subscribed to '{0}'.", "Topic.NotSubscribed": "You are not subscribed to '{0}'.", "Topic.Subscribed": "Subscribed to <color=#62ed53>{0}</color>.", "Topic.Unsubscribed": "Unsubscribed from <color=#bcc2c2>{0}</color>.", "Topic.ListItemSubscribed": "{0}. <color=#62ed53>{1}</color>{2}", "Topic.ListItemUnsubscribed": "{0}. <color=#bcc2c2>{1}</color>{2}" } Guidelines You can test your regex patterns using online tools like Regexr. Check your regex patterns for ReDoS vulnerabilities using tools like Devina's ReDoS Checker. ReDoS vulnerabilities can lead to server performance issues or crashes. Remember about localization: you may (or may not) want to add translated versions of your regex patterns for different server languages. The plugin obviously cannot translate english regexes into other languages automatically.

AntiWipeBP: is a persistence-focused Rust plugin that ensures players retain their blueprint progression across server wipes. It maintains a structured data file containing each player’s unlocked blueprints and restores them automatically on server initialization or player connection. The plugin includes administrative commands for manual saving, restoration, and statistical reporting. Its design emphasizes reliability, minimal overhead, and seamless integration with Rust’s blueprint system, making it a practical solution for servers that want to avoid blueprint resets without modifying core game behavior.

Track resource gathering, compare players, and see who's been farming the most on your Rust server. Resource Ranks is a resource-gathering statistics and leaderboard plugin for Rust. It tracks resources collected by individual players and provides an in-game interface for viewing personal statistics, comparing players, and browsing resource-specific rankings. Players can check their lifetime gathering totals, see how much they've collected recently, and compete for a place on the server's farming leaderboard. Features Resource Tracking — Records resources gathered from trees, ore nodes, animals, ground collectibles, and harvested crops. Player Leaderboards — Ranks players by the amount of resources they've gathered. Multiple Time Periods — View all-time totals, the last hour, or the last 24 hours. Individual Player Statistics — Browse a player's gathering history and resource totals. Resource-Specific Rankings — Compare players across individual resource types. Search and Pagination — Find players or resources without scrolling through long lists. Discord Integration — Post resource rankings to Discord using a webhook, manually or at configurable intervals. Persistent Statistics — Keeps lifetime gathering totals between server restarts, with optional map-wipe resets. Compact Data Storage — Uses an efficient JSON format to reduce storage requirements. Configurable Tracking — Enable or disable gathering sources, exclude specific items, or add custom harvestable resources. Permission Controls — Restrict access to the interface and Discord reporting commands. In-Game Interface The /farm command opens a menu containing four main sections: Farm Summary View the number of tracked farmers, total resources gathered across the server, and available resource types. My Harvest Review your personal gathering statistics, including lifetime totals and recent activity. Top Farmers Browse player rankings, switch between all-time and recent gathering totals, search for players, and open individual player statistics. Crop & Ore Index Browse and search available resources to view rankings for specific items. Commands /farm — Open the Resource Ranks interface. /farm top — Open the player leaderboard. /farm me — View your personal gathering statistics. /farm help — Display command help. /farm discord — Manually send resource rankings to Discord. Server Console resourceranks.discord — Send resource rankings to the configured Discord webhook. Permissions resourceranks.use — Allows players to access Resource Ranks. resourceranks.discord — Allows manual Discord reporting. resourceranks.admin — Registered administrative permission. Server administrators can also access the interface and Discord reporting functions. Configuration Resource Ranks provides settings for: Discord webhook URL and automatic reporting interval Discord report title Dispenser gathering and bonus hits Ground collectibles and harvested crops Quarry tracking setting Optional statistics reset on map wipe Automatic data-saving interval Excluded resource shortnames Additional harvestable item shortnames Note: Quarry output cannot reliably be attributed to an individual player, so it is not included in personal rankings. Statistics and Data Storage Resource Ranks stores permanent lifetime gathering totals alongside separate five-minute activity records used for the rolling one-hour and 24-hour statistics. Lifetime totals are preserved when old activity records expire. Statistics are stored locally in compact JSON format and do not require an external database. Installation Download ResourceRanks.cs. Place it in your server's oxide/plugins directory. Allow the plugin to compile and load. Grant resourceranks.use to the appropriate players or groups. Optionally configure Discord reporting and resource tracking. Requirements: Rust server running Oxide/uMod. No additional plugins or external database required. NOTE: A lot of AI was used in the creation of this plugin

A simple in-game clock and weather forecast for Rust. Nebulous Time gives players an easy way to check the current in-game time and see what weather is coming next, all with a single chat command. Instead of guessing how much daylight is left or waiting for the weather to change, players can quickly check the conditions without opening the console. Features In-Game Clock — Displays the current Rust server time in an easy-to-read 12-hour format with AM/PM. Current Weather — Shows the current weather state reported by Rust's climate system. Upcoming Weather — Displays the next scheduled weather state so players can prepare for changing conditions. Automatic Updates — Refreshes weather information every 20 seconds. Clean Chat Output — Uses simple, color-coded formatting that's easy to read without cluttering chat. Built-In Weather Detection — Reads Rust's native climate system without requiring another weather plugin. Graceful Fallbacks — If weather information isn't available on a particular server build, the plugin displays a clear message rather than reporting incorrect conditions. Lightweight Design — No database, external API, or additional plugin dependencies. Chat Command /time Displays the current in-game time, current weather, and upcoming weather. No additional commands are necessary. Example Chat Output TIME & WEATHER In-game time: 3:42 PM Current weather: Clear Upcoming weather: Light rain The values above are examples. Actual results reflect your server's current conditions. Weather Conditions Nebulous Time recognizes and displays readable names for Rust's weather presets, including: Clear Overcast Light rain Heavy rain Storm Fog Dust Other weather preset names can also be displayed when available. How It Works Nebulous Time reads the server's in-game clock directly from Rust's day/night system. For weather information, it accesses Rust's native climate component to retrieve the active weather target and the next scheduled weather preset. Weather information is refreshed automatically every 20 seconds, so players receive recently updated conditions whenever they use /time. Note: Upcoming weather refers to the next scheduled weather state, not an estimated time until that weather begins. Weather information depends on the climate data available in the installed Rust server build. Installation Download NebulousTime.cs. Upload it to your server's oxide/plugins directory. Allow Oxide/uMod to compile and load the plugin. Type /time in-game to check the time and weather. No additional setup is required. Compatibility & Dependencies Game: Rust (PC) Framework: Oxide/uMod Additional Plugin Dependencies: None External APIs: None Database: Not required Configuration: No configuration required Why Use Nebulous Time? Nebulous Time is useful for players planning a trip, preparing for nighttime, or checking the weather before heading out. It provides a small quality-of-life improvement without changing Rust's weather, day/night cycle, or gameplay balance. One command. Current time. Current weather. Upcoming weather. NOTE: A lot of AI was used in the creation of this plugin

Fair KD is a customizable PvP statistics and leaderboard plugin for Rust. It tracks player kills, deaths, and K/D ratios while providing configurable anti-farming protection to keep leaderboard rankings fair and meaningful. Unlike basic kill/death trackers, Fair KD separates total PvP kills from eligible kills. This allows server owners to prevent kill farming without losing track of players' overall PvP activity. Players can check their statistics, look up other players, and browse an in-game leaderboard. Optional Discord integration allows server owners to publish leaderboard results automatically or on demand. FEATURES • Tracks total PvP kills, eligible PvP kills, and deaths • Calculates K/D ratios and eligible-kill percentages • Ranks players by eligible K/D ratio • In-game leaderboard displaying 20 players per page • Player lookup by name or Steam64 ID • Configurable anti-farming restrictions • Support for Rust's native teams and clans • Excludes suicides from death statistics • Optional exclusion of sleeping and disconnected players • Configurable protection against repeated kill farming • Optional Discord webhook integration • Automatic Discord leaderboard posting at configurable intervals • Manual Discord leaderboard posting • Permission-controlled player commands and administrative functions • Persistent statistics with optional map-wipe resets • Compact JSON data storage ANTI-FARMING PROTECTION Fair KD includes several independently configurable restrictions designed to prevent players from artificially increasing their K/D ratios. • Team Kills — Exclude kills between members of the same native Rust team. • Clan Kills — Exclude kills between members of the same native Rust clan. • Spawn Protection — Exclude kills against players who recently respawned. • Naked Victims — Exclude kills against players without clothing. • Unarmed Victims — Exclude kills against players without qualifying weapons. • Sleeping Players — Exclude kills against sleeping or disconnected players. • Repeat Opponents — Apply a configurable cooldown to repeated kills involving the same pair of players. • Excluded Weapons — Prevent kills made with specified weapons from qualifying. • Suicides — Exclude self-inflicted deaths from death statistics. These restrictions can be enabled or disabled individually, allowing server owners to customize how strictly PvP statistics are calculated. STATISTICS AND RANKINGS Fair KD maintains separate statistics for total PvP activity and eligible PvP activity. Total PvP Kills: The total number of recorded PvP kills, including kills that may not qualify under the enabled anti-farming restrictions. Eligible PvP Kills: Kills that pass the configured anti-farming checks. These are used when calculating eligible K/D statistics. Deaths: Tracks player deaths while excluding suicides and other configured exceptions. K/D Ratio: Calculated using eligible kills and deaths. Leaderboard rankings prioritize K/D ratio rather than simply the total number of kills. Eligible Kill Percentage: Shows the percentage of a player's total PvP kills that qualify under the configured restrictions. IN-GAME LEADERBOARD Fair KD includes an in-game leaderboard that allows players to compare their PvP performance. • Displays 20 players per page • Supports multiple pages with navigation controls • Ranks players by K/D ratio • Displays relevant PvP statistics • Supports permission-controlled access Players can also view their own statistics or look up another player's record using a display name or Steam64 ID. COMMANDS /kd View your own PvP statistics. /kd <player> View another player's statistics by name or Steam64 ID. /kd top Display the ranked PvP leaderboard. /kdui Open the in-game leaderboard interface. /kd discord Manually post the leaderboard to Discord. /kd reset <Steam64 ID> Reset the specified player's stored statistics. Server Console Command: fairkd.discord Manually post the leaderboard to the configured Discord webhook. PERMISSIONS fairkd.use Allows players to use the /kd command. fairkd.viewothers Allows players to view other players' statistics and access leaderboard information. fairkd.ui Allows players to open the in-game leaderboard interface. fairkd.discord Allows manual Discord leaderboard posting. fairkd.admin Allows administrative statistics resets. Example permission commands: oxide.grant group default fairkd.use oxide.grant group default fairkd.viewothers oxide.grant group default fairkd.ui oxide.grant group admin fairkd.discord oxide.grant group admin fairkd.admin DISCORD INTEGRATION Fair KD supports optional Discord webhook integration for publishing leaderboard results. • Customizable Discord webhook URL • Configurable leaderboard title • Automatic leaderboard posting • Configurable posting interval in minutes • Manual posting through an in-game command • Manual posting through the server console • Support for sending larger leaderboards across multiple Discord messages Automatic posting can be disabled by setting the posting interval to 0. Discord integration is entirely optional. Fair KD does not require Discord to function. CONFIGURATION The plugin automatically generates its configuration file when first loaded. Configuration location: oxide/config/FairKD.json Configuration options include: • Suicide exclusion • Map-wipe statistics resets • Team kill restrictions • Clan kill restrictions • Spawn protection duration • Naked victim restrictions • Unarmed victim restrictions • Sleeping player restrictions • Repeat-opponent cooldowns • Excluded weapon lists • Discord webhook settings • Discord leaderboard title • Automatic Discord posting interval DATA STORAGE Fair KD uses compact JSON storage to preserve player statistics while minimizing unnecessary disk usage. • Persistent statistics across server restarts • Compact data representation • Support for migration from older supported data formats • Optional statistics resets on map wipes • No external database required INSTALLATION Download FairKD.cs. Upload the file to your server's oxide/plugins directory. Allow Oxide to compile and load the plugin. Open oxide/config/FairKD.json to review the settings. Grant the appropriate permissions to players or groups. Optionally configure a Discord webhook. Use /kd in-game to view your statistics. COMPATIBILITY AND DEPENDENCIES Game: Rust (PC) Framework: Oxide/uMod Additional Plugin Dependencies: None Discord Extension: Not required External Database: Not required Native Rust teams and clans are supported without requiring an additional clan-management plugin. Fair KD is designed for server owners who want meaningful PvP statistics, fair leaderboard rankings, configurable anti-farming protection, and straightforward administration without unnecessary complexity. NOTE: A lot of AI was used in the creation of this plugin

Carry an Invisible Parachute at all times. Does not take any inventory, Wear a backpack and still parachute. Does not dupe empty parachute. It cleans up the mess after. No repacking or leaving useless items all over the world. Ai assisted

This plugin gives ability to your players to post in better way than just on default chat. With that plugin players can post whatever they want as anonymous and with share location option that sends grid in their ad. For you as a server owner there are many configuration & monetization options. You can set rank-specific ad color, cooldown, time on screen, cost, max characters! Plugin is fully written by me- this is plugin is made with heart of rust player and server owner that knows what can cause lag, and what is important for server owners. Plugin is also very good optimised and using only 7 imports from other libraries without heavy ones - systems from heavy libraries has been replaced by my own to avoid using them. playersads.use - gives player ability to show ad form Other permissions are made rank specific, and you can create your own perms by rank name - you can see how it is set in default config /ad - opens an advertisement creation form (click to see)

APMenuButtons - is a lightweight HUD host for server menus. Instead of every plugin drawing its own floating button, you collect them in one clean expandable panel. Players tap the open button → see a grid of icons → each button runs a command (`chat.say /shop`, console, etc.). Admins set up everything in game: move the panel, resize buttons, edit the list, lock buttons behind permissions, and save layouts for later. Permissions apmenubuttons.use — use the HUD menu apmenubuttons.admin — open the admin editor apmenubuttons.btn.<name> — optional per-button access Commands /apmenu.open — toggle expanded menu (use) /apmenu.close — close menu (use) /apmenu — open admin editor (admin) /apmenu.settings — same as /apmenu (admin) /apmenu.reloadimages — reload PNG icons (admin) API (for developers) bool API_AddButton(string id, string text, string command, string imageName = "", string color = "", int order = 0, string permission = ""); bool API_RemoveButton(string id); void API_Refresh(BasePlayer player);

Yorixx Hub is a free companion plugin that opens every Yorixx plugin from one panel, shows update notices with changelogs, manages the permissions of every plugin on your server and shares one accent color and Discord webhook. FREE COMPANION PLUGIN All your Yorixx plugins in one place One panel to open every Yorixx plugin, see when an update is out, manage the permissions of every plugin on your server, and share one accent color and one Discord webhook between them. 100% free. Plugins: every Yorixx plugin installed, with its logo and version, opened in one click Update alerts: automatic checks, a chat message for admins, changelog and download link Discover: browse the other Yorixx plugins as cards (can be turned off) Permissions for every plugin: not only Yorixx: search, grant or revoke for any group or player Shared settings: one accent color and one Discord webhook for every Yorixx plugin Journal: a log of what your plugins did while you were away Commands /yox: Open the hub (the command can be renamed) Permissions yorixxhub.admin: Open the hub Network use To show update notices and the Discover tab, the hub reads a public catalog file (a plain JSON list of Yorixx plugins, versions and changelogs) from pastebin.com, at startup and every 6 hours by default. It only downloads that file: no server, player or usage data is ever sent. You can turn it off in the settings (Updates tab), or point it to your own URL. Plugin logos and cards are images hosted on imgur.com, loaded by the players' game client like any Rust UI image. Configuration Everything below can also be edited in game. { "General: Chat command": "yox", "General: Chat prefix": "<color=#A45BC7>[Yorixx]</color>", "Shared: Use one accent color for every Yorixx plugin": false, "Shared: Accent color (hex)": "#A45BC7", "Shared: Discord webhook used by plugins that have none": "", "Updates: Check for updates": true, "Updates: Check every X hours": 6, "Updates: Tell admins when they connect": true, "Updates: Show plugins you don't have yet": true, "Updates: Catalog URL": "https://pastebin.com/raw/rdNwxCzn", "Journal: Entries kept": 200, "UI: Show credit": true, "General: Debug logs": false } Support English and French included. Questions or ideas: join our Discord.