In-game admin panel   Oxide & Carbon   Our Discord Everything you open RCON for, without leaving the game. PowerfulAdmin is an admin panel that lives inside Rust. Fourteen pages in the sidebar cover players, permissions, plugins, the live console, ConVars, a working server map and your own buttons. Four more tools work out in the world, on whatever you happen to be looking at. Every page and every action has a permission of its own, so a junior moderator gets what you hand them and nothing else. /padmin   opens it. After that it is point and click, or a key you bound yourself.   00 New in 1.2.0 Five things this version adds Config editor Open any plugin from the Plugins page and edit its config as a form. Booleans become switches, numbers and strings become fields, an object becomes a group, an array opens in its own window. Save writes the file and can reload the plugin for you. Lang editor The same form for language files. Copy the open language into a new code to start a translation, delete one you no longer need, or add a key and push it into every localization at once. Map objects Cupboards, bags and stashes on the map used to be dots. Click one and a menu opens with the owners and their avatars, a teleport, a remote inventory, and a destroy behind a confirmation. Economy If you run Economics, ServerRewards or IQEconomic, the player card shows the balance and lets you add to it, take from it or set it. Reading and changing are separate permissions. Hammer & hints The hammer edits container contents instead of only listing them, its action menu moved to a radial you open by holding E, and its HUD can be dragged. Tooltips were added across the sidebar, the actions and the toggles.   01 The sidebar Fourteen pages, plus whatever docks in The panel reopens on the page you left. Add-ons appear in the same sidebar, use the same permission system and follow the theme the admin picked. Dashboard Live console Players Vanish ESP Server map Binds Permissions Logs Plugins ConVars Quick buttons Appearance Settings Bans DLC Freeze DLC Whitelist DLC Your own sections land here too, through the API at the bottom of this page   02 Out in the world Walk up to it and deal with it Most moderation starts with you standing in front of a base, a player or a locked crate, not in a menu. Four tools cover that, and none of them asks the admin to install anything on their client. Vanish You leave the world properly: networking, colliders, entity queries and the game's own AI target list. NPCs stop shooting and forget you were standing there. Radiation, cold, wetness, hunger, thirst and drowning stop touching you, and everything is restored the way it was when you switch Vanish off. A silhouette for other admins, auto vanish on connect, opening locks and noclip riding along are all optional, and each has a permission. Admin hammer Hold a hammer, look at anything, and the HUD reads out the owner, position, health, upkeep, power, who is authorized, the code lock codes and what is in the container. Hold E to pick an action from the radial menu, then Shift+LMB runs it: delete, delete with gibs, delete the whole linked structure, edit the container contents, or on a hackable crate unlock it now and set its timer to any value you type. Inspect Look at a player and act on them without typing a name. E opens their inventory, RMB opens their full card. A hint on screen keeps telling you which key does what. Server ESP The server draws it with the engine's own debug draw and sends it only to admins who hold the permission. Players and sleepers carry their name, HP and held item. Loot, boxes, cupboards, bags, traps, stashes, NPCs, scientists, turrets and vehicles each get their own colour. You set the radius, the opacity and the text size, and enemy, team and admin are coloured apart.   03 The player card One card per player, awake or asleep A searchable, paginated roster of everyone the server has ever seen. The card holds the SteamID, live status, current session and total playtime, total Rust hours from the Steam API, groups, first and last seen, the balance if you run an economy plugin, and the IP behind a permission of its own. Under that sit the actions. Heal Kill Strip Kick Ban Freeze Mute Teleport Inventory Spectate Give Blueprints Modifiers Vitals Permissions Notes Show on map Each of these has its own permission Give is a cart, not a single item. Search the item list, stack up what you want, edit any quantity by clicking the number, then send the lot. Vitals reads the real limits off the prefab, so a raised max HP or a frozen metabolism survives death, respawn, reconnect and wipe.   04 The map The server map, drawn inside the panel The island and the Deep Sea, with zoom. Layers go on one at a time, so you look at what you came for and nothing else. Layers Players, sleepers, cupboards, bags, stashes, cars, horses, air, shops, events and map notes. Cars, boats, submarines, trains, horses and player helicopters each have their own icon and an arrow showing where they are heading. The cargo ship, the cargo plane and the chinook are on the map with the rest. Click an object Cupboards, bags and stashes open a menu that names the owners and shows their Steam avatars. From there you can teleport to it, open its inventory from where you are standing, or destroy it behind a confirmation. Each of the three actions has a separate permission, so a moderator can be allowed to look without being allowed to delete. Heat PVP and raid heat build up from kills that actually happened and explosive damage that actually landed, over a window you set. It shows where the server is loud right now rather than guessing. Side panel A player search next to the map, and a card for whoever you picked with the same actions as the full player card. Hold Shift and place a map note to teleport straight to it.   05 Server control The parts you used to need RCON for Live console Server output as it happens, filtered by category, with a command line and history. It can be switched off entirely for everyone in Settings. Permissions Every permission on the server, grouped under the plugin that owns it. Toggle per user or per group, create and delete groups, set a parent group, and search across thousands of entries. PowerfulAdmin's own permissions can be locked so nobody edits them from inside the panel. Plugins Load, unload and reload anything on the server, then open its config and language files as a form and edit them without touching the filesystem. Editing is a separate permission from reloading, so an admin can restart a plugin without being able to rewrite it. ConVars Edit the server ConVars that matter, grouped and searchable. The panel keeps them in its own cfg file and applies them again on boot, so a restart does not quietly undo your work. Logs Commands, chat, joins, leaves, errors and warnings, colour coded and capped at a number you choose. Companion plugins write into the same log through the API.   06 Make it yours Bend it to how your team works Quick buttons Your own console commands as buttons, each with an icon, a colour, an optional confirmation and a permission of its own. You decide where a button shows up: the player card, the map, the dashboard or the floating widget. Binds Ready bind lines for the panel, Vanish, god mode, noclip, ESP, the hammer, inspect and the map. Type the key you want, select the generated line, Ctrl+C, paste into F1. One key toggles both ways. Appearance Three themes, Rust, Midnight and Plum, chosen per admin. Fonts are picked per slot, the window can be dragged, and the ESP text size is adjustable. Fonts without Cyrillic are marked in the picker. Notifications Panel messages go through Notify or NCP if you have either installed, or through chat, or nowhere at all. You pick the provider in Settings and the add-ons follow it. Storage SQLite by default, and it needs no setup. MySQL is there for networks that share data between servers, JSON for people who prefer files. Moving between them is one click in Settings and the data comes along. Discord An optional companion plugin ships in the same archive. Two way chat relay, feeds for bans, actions and errors, a bot with a live status line, and roles that decide who may run commands from Discord. It is set up in game, not in a config file.   07 Permissions Twenty seven of them, and that is the point A trial moderator can be given Vanish, the player card and nothing else. A head admin gets the lot. The panel greys out what an admin cannot reach instead of hiding it, so nobody has to guess why a page is missing. powerfuladmin.use Open the panel at all powerfuladmin.players Player page and player cards powerfuladmin.map Map page powerfuladmin.map.teleport Teleport to an object on the map powerfuladmin.map.loot Open an object's inventory from the map powerfuladmin.map.remove Destroy an object from the map powerfuladmin.esp ESP page and the overlay itself powerfuladmin.vanish Vanish powerfuladmin.vanish.unlock Open locked doors and boxes while vanished powerfuladmin.hammer Admin hammer powerfuladmin.hammer.codes See code lock codes in the hammer HUD powerfuladmin.hammer.loot Edit container contents with the hammer powerfuladmin.plugins Plugin page, load and reload powerfuladmin.plugins.edit Edit plugin configs and language files powerfuladmin.economy See a player's balance powerfuladmin.economy.edit Change a player's balance powerfuladmin.console Live console page powerfuladmin.perms Permission manager powerfuladmin.logs Logs page powerfuladmin.convars ConVar editor powerfuladmin.quickbuttons Create and edit quick buttons powerfuladmin.settings Settings, storage and Discord powerfuladmin.godmode God mode toggle powerfuladmin.noclip Noclip toggle powerfuladmin.viewip Reveal player IP addresses powerfuladmin.candisablevitals Edit player vitals and metabolism powerfuladmin.countableondashboard Counts toward the admins online figure On top of that, every action in the player card carries powerfuladmin.player.NAME, and every quick button you create carries powerfuladmin.quickbtn.NAME. You do not have to grant them one by one on day one: pa.setup <steamid or name> in the server console hands a player the whole set at once.   08 Commands One in chat, three in console There is nothing else to memorise. The console ones exist mainly so you can bind them to keys. /padmin Open the panel pa.open <page> Open the panel straight on a page, for example pa.open map pa.toggle <feature> Flip vanish, god, noclip, ESP, hammer or inspect. Called without a value it toggles, so one key does both directions pa.setup <steamid|name> Grant the full permission set to a player, once, on install Install 1 Drop the plugin into your scripts folder. It loads and writes a clean config on its own. Oxide and Carbon both work. 2 Run pa.setup with your name or steamid once in the server console. 3 Type /padmin in game. You are in. 4 Optional, later, in Settings: switch to MySQL, connect Discord, add a Steam API key for Rust hours, and copy your binds out of the Binds page.   09 Add-ons Bans, Freeze and Whitelist, sold separately Three companion plugins drop into the sidebar and share the card, the permissions and the storage backend. They are extras rather than missing pieces: everything above this line works without them. PowerfulBans Timed and permanent bans in their own database, reason templates, per role duration caps, ban history and login enforcement. Runs standalone too. PowerfulFreeze Freeze a player where they stand while you talk to them, from the card, the map or the world, with live countdowns and three freeze modes. PowerfulWhitelist Closed server whitelisting with JSON, SQLite or MySQL storage and its own standalone commands.   10 Before you buy The questions that actually get asked Will it lag my server? It is built not to. Objects are pooled and buffers reused, only the element that changed repaints instead of the whole panel, saves are debounced, state is cached behind signatures, and ESP, inspect and the map run on intervals you can tune. Nothing runs for an admin who is not looking at it. Is the ESP a cheat? There is no client mod involved. The server draws it through the engine's own debug draw and sends it only to admins holding powerfuladmin.esp. Take the permission away and it stops existing for that admin. Can a junior moderator abuse it? Only as far as you let them. Every page has a permission, every action in the player card has one, every quick button you make has one, and the plugin's own permissions can be locked so they cannot be edited from inside the panel. Do I need a database? No. SQLite is the default and needs no configuration. MySQL is there for networks that want shared data, JSON for people who like plain files, and moving between them is one click in Settings. Do I have to set up Discord or a Steam API key? Neither. Discord is optional and configured in game when you want it. The Steam key only fills in the total Rust hours figure on player cards. Without it that one line reads n/a and nothing else changes. Can I manage players who are offline? Yes. Teleport to a sleeper, heal them, strip them, edit the inventory, mute, change permissions. Only the actions that need a live connection are disabled while a player is away. Oxide or Carbon? Both. On Carbon the panel's internal commands are protected on top of that, so nothing outside the panel can call them, while the public ones stay open for your binds. What language does it speak? English and Russian out of the box, and every string lives in a language file. Adding another locale is a translation rather than a code change, and you can now do it from inside the panel. I write plugins. Can I hook into it? Yes, and the section below shows how.   11 For developers Your plugin, inside the panel Any plugin can register its own sidebar section and draw inside the panel, in the player's language and in whichever theme the admin picked. Bans, Freeze and Whitelist are built on this same public API, so it gets exercised on every release. [PluginReference] private Plugin PowerfulAdmin; var definition = new Dictionary<string, object> {     ["id"]            = "mystats",     ["icon"]          = "assets/icons/star.png",     ["category"]      = "nav.cat.tools",     ["permission"]    = "myplugin.view",     ["title"]         = (Func<BasePlayer, string>)(p => "My Stats"),     ["hint"]          = (Func<BasePlayer, string>)(p => "Kills, deaths, playtime"),     ["open"]          = (Action<BasePlayer>)OpenSection,     ["cardRows"]      = (Func<string, List<string[]>>)CardRows,     ["settings"]      = (Action<BasePlayer, CuiElementContainer, string, int>)DrawSettings,     ["settingsHeight"] = (Func<BasePlayer, int>)(p => 180),     ["popupActions"]   = new Dictionary<string, Action<BasePlayer, ulong, string>>     {         ["ban"] = OnBan     } }; PowerfulAdmin.Call("API_AddSection", definition); Only id is required. Every other key is optional, and the permission is registered for you if no plugin has claimed it yet. Read API_SectionContext on every render to get the parent layer, the body size, the padding, the player's language and the full theme palette, because the admin can switch themes while your page is open. API_AddSection(def) Register or replace a section API_RemoveSection(id) Unregister, call it in Unload API_OpenSection(player, id) Send a player to your section API_SectionContext(player) Geometry, language and palette for rendering API_ReopenPanel(player) Reopen the panel where it was API_RefreshPlayerCard(steamId) Repaint a player card after your data changes API_RefreshSettings(player) Repaint the settings page after saving a value API_Notify(player, message, isError) Notify through the admin's chosen provider API_Log(message, category) Write a line into the Logs page API_KnownPlayers() Every player the server has seen API_RustHours(steamId) Total Rust playtime from the Steam API, cached   Support, updates and feature requests Bugs get fixed and requests get read. LR Development Discord

Basements lets players build underground rooms beneath their bases. Place a hatch on your foundation and dig straight down into a hidden basement with walls, ceilings, and full building privileges. Great for stashing loot, setting up secret bunkers, or just adding extra space. Readme Link - Click Here for Instruction and Documentation 👆Highly recommend reading the FAQ section! BUILD Build basements easily from your tool cupboard. Just place an entrance to get started.  EXPAND Expand your basement by drilling underground. But don't forget to bring a headlamp - its dark down there! TRAVERSE Place multiple entryways, building out your labyrinth of tunnels beneath your base.  DECORATE All deployables, electricity, and storage items can be placed in your basement. Take advantage of your new space! RAID Nothing is safe in Rust, including your basement. If all the entrances are destroyed, then the basement is too. Any loot below will float to the surface. Protect the entrance at all costs! API METHODS (For Plugin Developers) // Returns true if the given entityId is part of a basement. bool IsBasementEntity(ulong entityId) // Returns the building ids of the basements connected to a given surface building id. uint[] GetBasementBuildingIds(uint surfaceBuildingId) // Returns the building ids of the surface buildings connected to a given basement building id. uint[] GetSurfaceBuildingIds(uint basementBuildingId) Extension Plugins These are free plugins that add additional functionality to Basements. BasementsManager Provides a UI for admins to view and manage the basements on the server. Useful for debugging & fixing issues. Use with the /bm command, requires the basements.admin permission to use. BasementsManager.cs

Manage your Rust server easier and more efficiently with the AdminMenu plugin. Track players, interact with them, edit their data and permissions, as well as change server convars and manage plugins. Features: Menu retains its state after closing, you won't lose everything you did before. Ability to fully translate the menu into any language.   Large range of permissions for each action, will allow you to flexibly customize the admin menu for each group of administrators. Quick menu that allows you to perform quick actions Full list of players with the ability to filter by online, offline, admins and moderators. Also has a frame of different colors depending on the level of authorization. Wide range of information and actions for the selected player. Editing convars with search. Has a complete list of editable convars with descriptions for some of them. Extensive issue menu by category, with easy management of name, skin and amount (manual, +1, +100, +1000, +10000). Plugin management menu. It is possible to reload, unload or load a plugin easily and quickly. Updates occur in real time. Ability to create your own custom buttons that execute several commands Quick Start: You install the plugin in the plugins folder. Give yourself the adminmenu.fullaccess permission.   Commands, use one of your choice, one for the player and one for the admin group:   o.grant user [name or steamid] adminmenu.fullaccess   o.grant group admin adminmenu.fullaccess Press the X button (swap  seat button) or type adminmenu in the console. Enjoy   Useful stuff: You can quickly open a player in the admin menu. To do this, point at the player and press X. You don't have to hover over the player exactly, you will be able to open players within a certain radius of the place you are looking at.   CUSTOM BUTTONS Custom buttons are buttons that when pressed will execute commands on behalf of the administrator, commands can be several, below will be the details. At the moment, custom buttons can be created in two places: in the quick menu and in the menu when selecting a player. These places are separated in the config. Button Fields: "Execution as server" - Call the command on behalf of the server, not the administrator "Label"  - Text that will be on the button, for each such inscription creates a field in the lang file, accordingly you can translate this text into several languages. "Commands" - Array of commands that will be executed on behalf of the administrator. Chat commands require a special entry, see examples. "Permission"- permission to display and use the button. You need to write the permission that will be after  "adminmenu.". Example: if you enter the permission "test"  the permission will be adminmenu.test "Position"  - The location for the button, the first number is responsible for the row number, the second for the position within the row, starts from 0.There are limits of locations, if you have gone beyond the limit - the button will not be displayed. Common Tags: {adminUID} - administrator's id. {position} - administrator coordinates (underfoot) {view_position} - the position where the administrator is looking (can be used for spawning or something similar) {view_direction_forward} - forward view direction of the administrator {view_direction_backward} - the direction the administrator is looking backwards {view_direction_left} - direction of the administrator’s view to the left {view_direction_right} - administrator’s view direction to the right Tags for target only: {steamid}, {steamID}, {userID}, {STEAMID}, {USERID} - mean the same thing, namely the id of the selected player. {target_position} - target coordinates (underfoot)   Example of commands: chat.say \"/{chat command}\" vanish ban {steamID} teleport {steamID} {adminUID}     More information about the grant menu: The grant menu includes the full list of items including hidden items as well as custom items created by the CustomItemDefinitions library. The menu can be accessed from the navigation or from the menu of the selected player. When issuing itself has categories. Search works in any registry by any part of the name or short name.   Has a page system at any stage. More information about the buttons in the Quick Menu: [Teleport to 0 0 0] - Teleport to coordinates 0 0 0. Requires  adminmenu.quickmenu.teleportto000 permission [Teleport to Deathpoint] - Teleport to your deathpoint. Requires adminmenu.quickmenu.teleporttodeath  permission [Teleport to Spawn point] - Teleport to a random spawn point. Requires adminmenu.quickmenu.teleporttospawnpoint  permission [Kill Self] - Kill Self, kills even when immortal. Does not require permission. [Heal Self] - Fully heal yourself. Requires  adminmenu.quickmenu.healself  permission   [Call Heli] - Call Helicopter to yourself (arrives in time). Requires adminmenu.quickmenu.helicall  permission [Spawn Bradley] - Spawn bradley on yourself. Requires adminmenu.quickmenu.spawnbradley  permission More information about the buttons in the menu of the selected player: [Teleport Self To] - Teleport yourself to the selected player. Requires adminmenu.userinfo.teleportselfto permission [Teleport To Self] - Teleport the selected player to yourself. Requires adminmenu.userinfo.teleporttoself  permission [Teleport To Auth] - Teleportation to random authorization (TC). Requires adminmenu.userinfo.teleporttoauth permission [Teleport to Deathpoint] - Teleportation to a player's deathpoint. Requires adminmenu.userinfo.teleporttodeath  permission [Heal] - Full healing, including metabolism. Requires adminmenu.userinfo.fullheal  permission [Heal 50%] - Half healing. Requires adminmenu.userinfo.halfheal permission. [View Inventory] - View and edit player's inventory. Requires adminmenu.userinfo.viewinv  permission [Strip Inventory] - Clear player's inventory. Requires adminmenu.userinfo.stripinventory permission [Unlock Blueprints] - Unlock all Blueprints. Requires adminmenu.userinfo.unlockblueprints  permission [Revoke Blueprints] - Reset all Blueprints. Requires adminmenu.userinfo.revokeblueprints permission.   [Kill] - Kill a player. Requires adminmenu.userinfo.kill  permission [Kick] - Kick a player. Requires adminmenu.userinfo.kick permission [Ban] - Ban a player. Requires adminmenu.userinfo.ban  permission More information about the buttons in the menu of the selected group: [Remove Group] - Remove group, has confirmation. Requires adminmenu.groupinfo.removegroup  permission [Clone Group] - Clone group with the ability to copy users. Requires adminmenu.groupinfo.clonegroup permission Permissions: adminmenu.use - Ability to use admin menu with basic set. Open tab quick menu (each button has its own permission, without permissions is present only kill yourself button) and the list of players. adminmenu.fullaccess - Full access to all functions without the need for each permission, includes also adminmenu.use. It is recommended to give only to the main administrators. adminmenu.quickmenu.teleportto000 - Access to the button in the quick menu, teleportation to coordinates 0 0 0 0. adminmenu.quickmenu.teleporttodeath - Access to the button in the quick menu, teleportation to the point of your death. adminmenu.quickmenu.teleporttospawnpoint - Access to the button in the quick menu, teleportation to a random spawn point. adminmenu.quickmenu.healself - Access button in quickmenu, heal yourself completely. adminmenu.quickmenu.helicall - Access to the button in the quick menu, call a helicopter to yourself (arrives in time). adminmenu.quickmenu.spawnbradley - Access button in quickmenu, spawn bradley. adminmenu.userinfo.teleportselfto - Access to the button in the menu of the selected player, teleportation to the selected player. adminmenu.userinfo.teleporttoself - Access to the button in the menu of the selected player, teleport the selected player to himself. adminmenu.userinfo.teleporttoauth - Access to the button in the menu of the selected player, teleportation to random authorization (TC). adminmenu.userinfo.teleporttodeath - Access to the button in the menu of the selected player, teleportation to the place of death of the player. adminmenu.userinfo.fullheal - Access to the button in the menu of the selected player, full healing, including metabolism. adminmenu.userinfo.halfheal - Access to the button in the menu of the selected player, half healing. adminmenu.userinfo.viewinv - Access to the button in the selected player's menu, view and edit the player's inventory. adminmenu.userinfo.stripinventory - Access to the button in the menu of the selected player, clear the player's inventory. adminmenu.userinfo.unlockblueprints - Access the button in the menu of the selected player, unlock all drafts. adminmenu.userinfo.revokeblueprints - Access to the button in the menu of the selected player, reset all drafts. adminmenu.userinfo.kill - Access the button in the selected player's menu to kill the player. adminmenu.userinfo.kick - Access the button in the selected player's menu to kick the player. adminmenu.userinfo.ban - Access to the button in the menu of the selected player, ban the player. adminmenu.groupinfo.removegroup - Access to the button in the menu of the selected group, the ability to remove the group. adminmenu.groupinfo.clonegroup - Access to the button in the menu of the selected group, the ability to clone the group. adminmenu.convars - View and edit convars. adminmenu.permissionmanager - View and edit permissions in groups, player groups, create, delete and clone groups (requires additional permissions from these buttons). adminmenu.pluginmanager - Access to plugin management, reloading, unloading, loading plugins. adminmenu.give - Access to give resources, as well as yourself and the selected player.

Optimize A stylishly designed plugin that boosts player FPS and includes a wide range of performance optimizations. 15+ optimization settings Oxide & Carbon English · Russian Supports Community Servers Depending on the hardware, client FPS either goes up or becomes noticeably more stable. Goals Before developing any plugin, we define the goals it should achieve when running on your game server. Improve players FPS Make your project stand out Improve the overall quality Features and Capabilities We provide extensive functionality for both server owners who purchase the plugin and the players who use it. General Polished and thoughtfully designed interface Extensive plugin customization Players One time notification when low FPS is detected Numerous optimization settings Optimization Settings Players enable exactly what they need — every option is toggled individually, and choices are saved automatically. World Around You Draw distance The server stops sending buildings, boxes and other objects that are far away. Distant trees Trees load only around you instead of the whole map — as you move, they stream in on their own. Saves memory and speeds up joining the server. Images and drawings Drawings on signs, photos, paintings and spray art stop loading. Saves memory and bandwidth. Unapproved Skins Disables skins that have not been accepted into the game but may still be used by other players. Fire, Light & Animations Destruction debris No debris flies around when walls and structures collapse. The difference is most noticeable during raids. Flames Furnaces, campfires, and torches will no longer display flames. The difference is especially noticeable in large, heavily built-up bases. Wind turbine rotation Wind turbines stop spinning. They generate power just like before. Turret lasers Laser sights on turrets and SAM sites are turned off. Falling trees A chopped tree simply disappears — no falling animation, no cracking sounds. Construction smoke Smoke and effects from placing, upgrading and repairing structures are no longer shown. Lights Lamps and searchlights will no longer emit light. The difference is especially noticeable in large, heavily built-up bases. Electricity & Industrial Items in industrial pipes Item animation inside industrial conveyors and pipes is turned off. The conveyors themselves keep working as usual. Recyclers and quarries Recyclers, quarries and pumpjacks stop shaking and animating. They keep on working. Water flow Water inside hoses and pipes is no longer rendered. Sprinklers and water supply work as usual. Effects & Sounds Distant effects Explosions, muzzle flashes and smoke from other players' distant fights are hidden. Everything happening near you stays visible as usual. Voice chat You won't hear other players' voice chat, or will hear it only at a reduced range. Frequently Asked Questions We have anticipated your questions and answered the most common ones below. You can ask any additional questions in the plugin's discussion section. Do you accept suggestions for improving the plugin? Sure! To submit an idea, join our Discord Server obtain the required role, and post your suggestion in the #suggestions channel. What should I do if the plugin is not working? Create a support ticket on our Discord Server and we will help you resolve the issue. Does the plugin require a powerful game server? No. The plugin is well optimized and will not place a significant load on your server, even on low-end hardware or with a high player count. Permissions and Commands Below is a list of the permissions and commands available in the plugin. Permissions optimize.use Grants players access to the plugin Commands /fps Opens the plugin menu Console Commands optimize.wipe Clears the player settings database Join our Click on this text to join our server, get support, updates, and more. Developed in Authors Code by DezLife Design by Illumination

DemoPro: The Anti Cheat That Works 🎥 DemoPro turns F7 reports into a single evidence bundle with timeline markers + jump points, so you can jump straight to the key moments fast. It captures footage  Before / during / after the f7 report is made Cheaters can’t hide from this system — no more relying on outdated anti-cheat plugins. This is clear video evidence that makes decisions easier, faster, and fairer. 100% accurate, No False Positives  Key Features 🎥      ✅ Converts **F7 reports** into a  single evidence bundle      ✅ Records BEFORE, DURING, and AFTER every F7 report. You NEVER miss what happens.      ✅ Saves you and your admins loads of time. No more wasting hours spectating players      ✅ Smart sorts demos with Timeline markers + jump points  to reach key moments fast      ✅ Private portal access for you and your admins with **Steam sign-in**      ✅ Assignments, notes, outcomes  (keeps reviews organised)      ✅ Server-friendly: all data is stored off-site on your account, not on your game server, keeping things lightweight and smooth.      ✅ Can be use as a content tool,  you can make cinematic videos from the demos you receive.      ✅ Fully compatible with all Rust server setups.   Proof it works: 🔍 join our Discord and check out the #cheater-clips channel  https://discord.gg/2DCfVFFgvW   7-day free trial: https://rustdemopro.com   RustAdmin Integration: https://www.rustadmin.com Visual snippet of recoil mapping with each attack in timeline Shareable filtered portal links Discord ban feed + global portal search Redesign the portal + dashboard for a more modern and fluid feel  New portal is now live Future Updates AI Integration 🧠 Introduce an AI/ML system that analyses demo files to learn the difference between normal players behaviour vs a cheaters behaviour All Seeing Eye  👁️ An AI powered monitoring layer that automatically flags suspicious players and triggers evidence capture without relying on F7 reports.   Set Up Guide   Step 1 — Create Your DemoPro Space Sign in at https://rustdemopro.com using your Steam account Create your community space Choose monthly or annual billing (includes a 7-day free trial)   Step 2 — Install the Harmony Mod Copy the DLL into: server_root/HarmonyMods/ Start the server once to generate: server_root/HarmonyConfig/ (this contains the config) After editing the config, run: rdm.reloadcfg to apply changes   Step 3 — Connect Your Server In the portal, generate a Server Key Paste the key into the plugin config Make sure uploads are enabled in the config Reload the config, enter this command in your console rdm.reloadcfg    Step 4 — Reports Create Cases When an in-game report (F7) happens, DemoPro automatically builds an evidence bundle The bundle is uploaded to your portal as a case for review   Step 5 — Review & Decide Open the case, assign it, and add notes Download the bundle, jump to the timeline markers Mark the outcome as Reviewed (Clear) or Reviewed (Cheating) with notes for your team If you need any help setting up DemoPro, please open a ticket on our Discord.         How it works  🎥 Server records players in 15-minute chunks with ~30 minutes rolling history. When someone is F7 reported, Demo Pro grabs the “before” buffer and keeps recording. 15 minutes later it adds the “after” clip and uploads everything to the portal. If a player disconnects/reconnects, chunk lengths can be shorter than 15 minutes—that’s normal. Portal statuses 🎥 Players reported → Clip uploaded → Needs Review → Admin downloads → Admin reviews → Mark result Needs Review — new or reset incidents. Downloaded (Needs Review) — someone pulled the bundle but hasn’t finished. Reviewed — Clear / Reviewed — Cheating — finished decisions. Opening & assigning a report 🎥 Click Open on a card to see details. Assign it to yourself immediately and add notes as you investigate. Set the review state to Reviewed (Clear) or Reviewed (Cheating) when done. Assignments and outcomes keep other moderators from duplicating work. Finding the action fast 🎥 Timeline dots: hits/shots, kills, report moment. Use the event feed to jump to notable damage or kill events. Report marker shows where the F7 report landed inside the clip. Downloading the bundle Use Download bundle for a ZIP containing .dem files and a README. The README points to the first demo and the timestamp to jump to—start there. Clip lengths can vary if players disconnect; that’s expected. Load demos into Rust 🎥 Copy the suggested .dem into C:\Program Files (x86)\Steam\steamapps\common\Rust\demos. If the demos folder doesn’t exist, create it (restart Rust once if needed). Playing + controls From Rust main menu, open the Demo browser, refresh, pick the file, and play. Use Alt to toggle cursor, Tab for UI, and debugcamera to free-fly. Cycle nearby players with Spacebar; pause/rewind/fast-forward as needed. Review guidance 🎥 Use the README timestamps as a starting point; check other demos if nothing obvious. If cheating is confirmed: capture proof, upload to the usual place, mark Reviewed (Cheating), and leave clear notes. If clean: mark Reviewed (Clear) and add a quick note (e.g., desync, valid prefire). long story short, when someone f7 reports, you can get a clip, you replay in rust of exactly why, and it shows footage before and during the report. For tips and useful keybinds to help you get the most out of DemoPro, check out the dedicated channels in our Discord.    Discord: https://discord.gg/2DCfVFFgvW Website: https://rustdemopro.com/ Youtube: https://www.youtube.com/@RustDemoPro Cheater Videos            

📝 Description: Custom Event Manager is a lightweight Rust plugin that automatically manages and rotates through server events. Instead of manually starting events, this plugin will periodically trigger them for you, picking randomly from multiple event lists and ensuring they don't repeat until all events have been cycled through. Disable timer starts in your plugins, and use the start command in the config, to avoid having multiple events run at the same time. This keeps gameplay fresh and dynamic for your players without requiring constant admin attention, and now includes Discord webhook integration to notify your community when events start! NEW in v2.3.0: Take full control of Rust's vanilla events! Disable automatic spawns of patrol helicopters, cargo planes, cargo ships, CH47s, Bradley APCs, and supply drops. Then optionally schedule them manually through the plugin's rotation system for complete server event control. ✨ Features Multiple event lists with independent rotation schedules Configurable delays between different event lists to prevent overlap Automatic event rotation at configurable intervals Smart rotation logic ensures no event repeats until all have been used Discord webhook integration with customizable notifications Vanilla event control - Enable/disable individual vanilla Rust events Manual vanilla event scheduling - Schedule vanilla events through the rotation system when disabled Admin commands to start, stop, and check the rotation status Simple JSON configuration for adding your own events Full permission system support Configuration ⚙️ Configuration The config file will be generated at: oxide/config/CustomEventManager.json Example:   { "EnableOnServerStart": true, "PreventDuplicateEvents": true, "MaxRerollAttempts": 5, "EventCooldownSeconds": 60, "DiscordWebhookUrl": "https://discord.com/api/webhooks/YOUR_WEBHOOK_URL", "DiscordSettings": { "EnableNotifications": true, "BotName": "Event Manager", "BotAvatarUrl": "", "EmbedColor": 3447003, "NotifyOnEventStart": true, "NotifyOnRotationStart": true, "NotifyOnRotationStop": true, "NotifyOnCycleComplete": true }, "VanillaEventSettings": { "EnablePatrolHelicopter": true, "EnableCargoPlane": true, "EnableCargoShip": true, "EnableCH47": true, "EnableBradleyAPC": true, "EnableSupplyDrop": true }, "EventLists": [ { "Name": "MainEvents", "IntervalMinutes": 30, "RandomizeOrder": true, "DelayAfterMainEvent (minutes)": 0, "Enabled": true, "Events": [ { "Name": "extraevents", "Command": "extraevents start", "Enabled": true }, { "Name": "guardedcrate", "Command": "gcrate start", "Enabled": true }, { "Name": "guessthenumber", "Command": "gtn start", "Enabled": true } ] }, { "Name": "SecondaryEvents", "IntervalMinutes": 45, "RandomizeOrder": true, "DelayAfterMainEvent (minutes)": 5, "Enabled": true, "Events": [ { "Name": "roamtasks", "Command": "RoamTask start", "Enabled": true }, { "Name": "skilltreexpevents", "Command": "startxpevent", "Enabled": true }, { "Name": "convoy", "Command": "convoystart", "Enabled": true } ] }, { "Name": "VanillaEvents", "IntervalMinutes": 60, "RandomizeOrder": true, "DelayAfterMainEvent (minutes)": 0, "Enabled": false, "Events": [ { "Name": "PatrolHelicopter", "Command": "spawnheli", "Enabled": true }, { "Name": "CargoPlane", "Command": "spawnplane", "Enabled": true }, { "Name": "CargoShip", "Command": "spawncargoship", "Enabled": true }, { "Name": "CH47", "Command": "spawnch47", "Enabled": true } ] } ] } Options General Settings EnableOnServerStart → Automatically start event rotation when the server starts. Default: true PreventDuplicateEvents → Prevents the same event from running across different event lists simultaneously. Default: true MaxRerollAttempts → Number of attempts to find a non-duplicate event before giving up. Default: 5 EventCooldownSeconds → Time (in seconds) before an event is removed from the global active list. Default: 60 DiscordWebhookUrl → Your Discord webhook URL for notifications. Leave empty to disable Discord integration. Discord Settings EnableNotifications → Master switch for all Discord notifications. Default: true BotName → The name displayed for the webhook bot. Default: "Event Manager" BotAvatarUrl → URL to an avatar image for the bot (optional) EmbedColor → Decimal color code for Discord embeds. Default: 3447003 (blue) NotifyOnEventStart → Send notification when an event starts. Default: true NotifyOnRotationStart → Send notification when rotation starts. Default: true NotifyOnRotationStop → Send notification when rotation stops. Default: true NotifyOnCycleComplete → Send notification when all events in a list complete. Default: true Vanilla Event Settings Control whether vanilla Rust events spawn automatically: EnablePatrolHelicopter → Allow automatic patrol helicopter spawns. Default: true EnableCargoPlane → Allow automatic cargo plane spawns. Default: true EnableCargoShip → Allow automatic cargo ship spawns. Default: true EnableCH47 → Allow automatic CH47 spawns. Default: true EnableBradleyAPC → Allow automatic Bradley APC spawns. Default: true EnableSupplyDrop → Allow automatic supply drop spawns. Default: true Important: When you disable a vanilla event (set to false), the plugin will block its automatic spawns. To schedule these events manually, enable the "VanillaEvents" list in your EventLists configuration and customize the interval and events as needed.   Event List Settings Each event list supports: Name → Friendly name for the event list IntervalMinutes → Time (in minutes) between each event in this list. Default: 30 RandomizeOrder → Whether to randomize event selection. Default: true DelayAfterMainEvent (minutes) → Additional delay before starting this list's events (useful for preventing overlap). Default: 0 Enabled → Whether this event list is active. Default: true Events → Array of event definitions: Name → Friendly name for the event (used in status tracking and Discord notifications) Command → The console command to trigger the event Enabled → Whether this specific event is active. Default: true   🛠️ Permissions customeventmanager.admin Required to use the admin commands.   💻 Commands /cem start - Starts the event rotation /cem stop - Stops the event rotation /cem status - Shows current status, how many events have run, and when the next one is scheduled /cem reload - Reloads the configuration and restarts rotation /cem list - Lists all configured event lists and their events /cem active - Shows currently active events globally /cem vanilla - shows the status of vanilla event settings ⌨️ Console Commands All chat commands can also be used from the F1 console by replacing /cem with cem: cem start cem stop cem status cem reload cem list cem active cem vanilla 🔧 How it works Multiple Event Lists: You can configure multiple independent event lists (e.g., "MainEvents" and "SecondaryEvents") that run on their own schedules Smart Scheduling: Each list tracks its interval and optional delay to prevent events from overlapping No Repeats: Events won't repeat until all events in that list have been triggered Discord Integration: Get real-time notifications in your Discord server when events start, cycles complete, or rotation status changes Duplicate Prevention: Prevents the same event from running simultaneously across different lists Vanilla Event Control: Block automatic vanilla event spawns and optionally schedule them through the plugin's rotation system   🔧 Vanilla Event Scheduliing To take full control of vanilla Rust events: Disable automatic spawns by setting the vanilla events to false in VanillaEventSettings: "VanillaEventSettings": { "EnablePatrolHelicopter": false, "EnableCargoPlane": false, "EnableCargoShip": false, "EnableCH47": false, "EnableBradleyAPC": false, "EnableSupplyDrop": false } 2. Enable manual scheduling by setting the VanillaEvents list to true   { "Name": "VanillaEvents", "IntervalMinutes": 60, "RandomizeOrder": true, "DelayAfterMainEvent (minutes)": 0, "Enabled": true, "Events": [...] } 3. Customize the schedule by adjusting IntervalMinutes, adding/removing events, or changing the order This gives you complete control over when and how often vanilla events occur on your server! 📌 Tips Disable built-in timers in your event plugins to prevent conflicts Use the DelayAfterMainEvent setting to stagger different event lists Set RandomizeOrder to false if you want events to run in a specific sequence Customize Discord notifications to match your server's style with the EmbedColor and BotAvatarUrl settings Use PreventDuplicateEvents to avoid the same event running twice at once across different lists Disable vanilla events and use the VanillaEvents list for complete control over server events Use /cem vanilla to quickly check which vanilla events are enabled or disabled    

The Monument Events plugin creates amazing events on the monument from preconfigured presets from config. It creates CustomNPCs around the monument which will roam the monument during the event. Then it will spawn CH47 Helicopter which will drop Hackable crates & spawn configured Patrol Helicopters which will roam the monument vicinity. When players try to unlock the Hackable Crate there will be a  CH47 Helicopter which will carry NPC and drop on the monument and will give players an amazing raged experience. ⭐ Key Features 10+ Monument  preset preconfigured (Radtown, Oxum's Gas Station, Abandoned Supermarket, Water Treatment Plant, Power Plant, Ferry Terminal, Small Harbor, Large Harbor, Junkyard, The Dome, Airfield, Train Yard, Satellite Dish, Sewer Branch, Launch Site) PVE/PVP support  Easy setup everything is pre-configured, so drag and drop and it will auto start from the selected time Massive configure option for individual  monuments (Except a few not added) Monument Owner control based on damage Editable Monument Setting, Npc Settings, Npc Loottable Amazing event for engaging players with monuments NEW • CUSTOM VITAL STATUS 📌 Commands /mestart Preset_Name | monumentID - Starts any specific event  (Console & Chat command) /mestop Preset_Name | monumentID - Stops the event  (Console & Chat command) /melist - Shows all available monument events on the map /mestartrandom - Starts a random from presets (Console & Chat command) /meadd edit  PRESET_NAME -  Select a monument for editing spawn points (Chat command) /meadd  npcspawn -  Creates NPC spawn points for the selected monument  (Chat command) /meadd  wavespawn -  Creates Wave Npc spawn points for the selected monument  (Chat command) /meadd  cratespawn -  Creates Crates  spawn points for the selected monument  (Chat command) /meadd stopedit -  Deselect the current editing monument  (Chat command) NEW /mestart <preset> [steamid]" now starts the event and assigns that player as the Event Owner (works with all existing Event Owner settings) 📜 Permissions MonumentEvents.admin - Permission required for using commands 🎬 Video Showcase   ⚙️ Configuration 🗃️Monument Settings 🗃️Npc Setting 🗃️Npc Loottable 🗃️Lang  🚀 API & Hooks 💬 Support  

Team HUD  ·  Rust  ·  Oxide Rust tells you who your teammates are, and nothing about what is happening to them BetterTeams puts a live panel on screen with every mate's health, state, held weapon and grid square. It adds a team-only voice channel that ignores distance, a map ping on one key, and automatic authorization on every cupboard, lock, turret and SAM site your team builds. Every part is a config switch, and every player decides what they use. See it What it looks like on the server       How it goes From dropping the file in to the night the server dies MINUTE ONE Nothing to set up The panel is already there Drop the file in and anyone who is in a team sees their mates on screen. Where it sits, how large it is and how many rows before it starts a second column are config values. Everything else is each player's own choice. Health as a bar, not a number. It slides toward red as they lose health, and it redraws the moment their health actually changes rather than on a timer. State takes over when it matters. WOUNDED, DEAD and OFFLINE replace the bar on that row, so a mate who is down is unmistakable without reading anything. What they are holding. The active item's icon, with its skin, sits at the end of every row and follows each weapon swap. Grid square, on your own refresh rate. Five seconds by default. A player who would rather not broadcast theirs switches it off for themselves. The leader keeps a star. One glance tells you who can change the team's settings, and offline mates stay listed instead of vanishing. IN A FIGHT Nobody types grids Talk across the map, ping what you are looking at Team voice replaces the vanilla proximity channel for the players who switch it on. Distance stops mattering, nobody outside the team hears it, and a speaker icon lights up on the row of whoever is talking. bind h ftmark Voice at any range, team only. Off per player until they enable it, so nobody has their voice chat changed without asking for it. One key, no binoculars. Bind the command once and the ping lands wherever you are aiming, up to fifty metres by default. The ping knows what it hit. An enemy player, an ore node, a storage box and a dropped gun each get their own marker icon and colour. Anything else drops a plain point. On a cooldown you set. Ten seconds by default, and the time left comes back as a game tip instead of the key doing nothing. SOMEONE JOINS One shared list Authorized everywhere, in one pass The moment an invite is accepted that player is added to every cupboard, code lock, turret and SAM site the rest of the team owns, and everyone else is added to theirs. Leaving or being kicked takes all of it back in the same pass. Five places, five switches. Tool cupboards, code locks, key locks, auto turrets and SAM sites, each turned on or off for the whole server. Key locks without the key. A teammate opens a key-locked door because they are on the team, not because you handed them anything. SAM sites check who is aboard. A teammate's SAM holds fire on a helicopter with an authorized member in a seat, instead of shooting down your own minicopter. Bases that already exist are picked up on boot. Everything placed before the install is registered when the plugin loads, so this works on a server mid-wipe and not only on what gets built next. THE LEADER Decided in game The random you just invited is not automatically trusted Taking a stranger into the team is where convenience turns into risk, so the whole authorization list is editable per ally from the menu. No config file, no restart. Revoke without breaking the rest. A blocked ally loses access everywhere except the locks and cupboards they placed themselves, and the team keeps access to those. Kick from the same screen. Pick the ally, kick, and every authorization they were given through the team is pulled as they go. Friendly fire off with one toggle. Only the leader can flip it; everyone else sees it locked and is told why rather than wondering if it is broken. A team skin per item type. The leader picks it, and anything a mate picks up gets it automatically. Thirty-five item types ship in the config with their own skin lists, and both are yours to cut or extend. AFTER A CRASH Teams survive it A bad shutdown should not disband half the server Rust loses teams when a server goes down badly, and the tickets land on you. This one writes the roster and the leader to disk and puts them back on start. Rosters restored on boot. Members and leader are recreated, including the players who are offline at the time, so nobody logs in teamless. Optional leader hand-off. If the leader disconnects the next online member is promoted, and the original takes it back when they return. Off by default, because not every server wants it. A wipe clears it properly. A new wipe id drops the saved teams and skin choices rather than dragging last wipe's data onto a fresh map.   While you are not looking Built to be left alone The parts you will never notice unless they are missing. ✓  ImageLibrary is the only dependency, and Clans is used if you have it   ✓  A missing dependency is named in console and the plugin unloads, instead of half-running ✓  Switching a feature off unsubscribes its hooks rather than leaving them running   ✓  Panel updates are batched into one message per team per tick, not one per player ✓  Grid squares only redraw for the players who actually changed square   ✓  A burst of joins and kicks collapses into a single data file write ✓  Every player choice is stored by Steam ID and survives restarts and reloads   ✓  Clan tags are stripped from names in the panel when the Clans plugin is loaded   Reference One command in chat, one to bind Each permission is only enforced if you switch its requirement on. All four are off by default, which means the feature is simply available to everyone. Chat /bt Open the menu: info, allies, skins, settings. The command name is a config value. Console ftmark Drop a team ping where you are looking. Meant to be bound to a key. Permission betterteams.hud The on-screen panel Permission betterteams.voice Team voice chat Permission betterteams.skins Choosing the team skin. One player in the team holding it is enough for the whole team. Permission betterteams.marker Easy team markers   Straight answers The questions people ask before buying Do my players have to install anything? No. It runs entirely on the server and the panel is drawn through the normal game UI. The only install is ImageLibrary, on the server, once.   Does team voice take over normal voice chat? Only for a player who turns it on themselves, and it is off by default. Everyone else keeps vanilla proximity voice untouched. Can a random I invite loot everything I own? Only if you leave them authorized. The leader can revoke any of the five places for one specific ally from the menu, and they keep access to nothing but what they placed themselves.   Will the panel sit on top of my other UI? Its offset from the top and left, its scale and how many rows it stacks before starting a new column are all config values, so it can be moved out of the way. What if I do not want half of these features? Panel, voice, skins, markers, friendly-fire toggle, grid positions, team restore and each of the five authorization places are separate switches. Turning one off also stops the hooks behind it.   What happens if ImageLibrary is missing? It waits and retries a few times in case load order put it second, then prints the download link in server console and unloads itself rather than throwing errors on every hook.   5 authorization places covered 35 item types with team skins 50m default ping range, configurable 1 dependency, ImageLibrary

Weather & time control Own the sky — from a GUI, not a config file Vanilla weather is a coin flip you don't get to influence. This plugin shuts it off and hands you the whole sky: build your own presets, tune every value with plain-English names, chain them on a schedule, or mirror the real weather of any city on Earth. Everything is editable in-game and applies instantly. 33 Tunable parameters 24 Schedulable hours 6 Presets preloaded 0 Dependencies ✓Every parameter named in plain English — no cryptic engine values ✓Real lightning strikes — not just thunder sounds ✓Live weather synced from any real location on Earth ✓Separate day and night length — plus vote-based night skip ✓Personal weather — let chosen players pick their own sky while the server weather stays for everyone else Video See it in action 01 — Presets Weather presets you actually control All six vanilla presets are imported automatically on first load, so you start from a working base instead of a blank slate. From there, nothing is off limits. Everything is a dial Rain, wind, thunder, rainbow and ocean wave height · cloud coverage, size, opacity and scattering · fog density · atmosphere brightness and contrast, day and night separately · full volumetric cloud control Named in plain English "Waves in the sea" instead of "OceanScale" · "Fog density" · "Sun glow size". No guessing what a value does before you drag it. Real lightning, not a sound effect Any preset with Thunder above zero fires actual strike effects for every online player, across three intensity tiers, with frequency scaling off the Thunder value. ✓Smooth transitions — set a transition time per preset and weather eases in over seconds or minutes instead of snapping ✓Weighted random — make Storm rare and Clear common with a single number ✓Duration per preset — when one ends, the next rolls automatically 02 — Time Time and nights on your terms Long days, short nights, or no nights at all — and if you'd rather let the server decide, hand the choice to your players. Day and night length, separately A 45-minute day with a 10-minute night is one number each. Sunrise and sunset hours are configurable, and /setday and /setnight change time instantly. Skip nights automatically One toggle and nights are skipped the moment they start. Ideal for PvP servers and low-population wipes. Or let players vote A vote opens at an hour you choose and the night is skipped only if your required percentage agrees. Vote window, sound effect and every message are customizable. An anti-abuse limit locks voting after a set number of consecutive skipped nights, so your server still has nights. 03 — Automation Automation that runs the sky for you Set it once and never touch it again — either on a schedule you design, or synced to the real world. Rust-time schedule Assign presets to any of the 24 in-game hours. A preset holds until the next scheduled one, so filling three slots already covers a whole day. No two days alike Put several presets in one slot — "Storm,Dust" — and one is picked at random by weight every time that hour comes around. Real-world weather sync Give it coordinates and an OpenWeatherMap key and your server mirrors the live weather of that location, rechecked every in-game hour. Map each real condition — Clear, Rain, Snow, Thunderstorm, Fog — to whichever preset you like. 04 — Personal weather Personal weather for the players you choose Give a group its own sky. Anyone with the permission sets weather for themselves alone, while everyone else keeps whatever the server is running. A natural VIP perk that costs the rest of your players nothing. Their own sky, on command /myweather opens a small menu. The player picks a preset and it applies to them alone, instantly, on top of whatever the server weather is. You pick what they can choose Limit the menu to a handful of presets in the config, or leave it open to all of them. Only the presets you allow ever show up. One click back to normal A Server Weather button drops them back to the shared sky at any time, and their choice is remembered across reconnects and restarts. Reliability Built to be left alone ✓Weather survives restarts — the active preset and how long it has been running are saved, so a reboot doesn't reset the sky to a random state ✓Active preset is highlighted in the UI — you always know what's running ✓Optional console announcement whenever a new preset starts ✓Clean unload — vanilla weather chances are restored exactly as they were Commands Three admin commands, two for players Admin commands require the weather.use permission. Personal weather requires weather.personal. /wsetupOpen the setup UI /setdaySet time to day /setnightSet time to night /nskipVote to skip the night — configurable, open to all players /myweatherOpen the personal weather menu — needs weather.personal Hooks & API For plugin developers string API_GetCurrentWeatherPreset() Returns the name of the active preset void OnNewPresetStart(string presetName) Called when a new preset begins Questions Before you buy I scheduled a preset at hour 3, but hours 4–9 are empty. What happens?A preset runs until the next scheduled one. Set Rain at 4 and Dust at 9 and you get rain from 4 to 9, then dust from 9 until hour 4 comes back around. Can I put more than one preset on the same hour?Yes — comma-separated, like "Storm,Dust". One is chosen at random each time, weighted by each preset's chance. How do I know which preset is currently active?Open the UI — every preset is listed and the active one is highlighted. A preset you've only selected to edit is not. What happens when the current preset ends?A new one starts at random, weighted by the chance value you gave each preset. Does the weather reset when the server restarts?No. The active preset and its elapsed time are saved, so the sky picks up where it left off. Can players set their own weather?Yes, if you grant them the weather.personal permission. They open /myweather and pick from the presets you allow, and it applies to them alone while everyone else keeps the server weather. Do I need an API key?Only for real-world weather sync. Everything else works out of the box, and a free OpenWeatherMap key is enough.

SimplePVE is exactly what the name suggests: a simple and easy-to-use PVE plugin for Rust servers. It allows server owners to control and customize PVE rules individually, either through the config or with a clean in-game CUI. You can also create, edit, and manage PVE/PVP schedules directly, making it easy to run full PVE servers, purge events, or hybrid PVE/PVP setups. ⭐ Key Features Control PVE rules directly from in-game CUI or through the config Easy-to-understand rule system for managing damage, raiding, looting, and protection Enable or disable PVE/PVP manually with commands Create automatic PVP schedules for purge times Supports weekly schedules, such as Sunday to Friday or weekend-only PVP Supports date-specific schedules, such as January 1 to January 7, holiday events, wipe-weekend events, and custom purge periods Automatic PVE/PVP purge events based on your configured schedule Loot protection system to prevent unauthorized looting Zone Manager support for custom PVE/PVP zones Exclude specific zones from global PVE rules Supports many popular event plugins Works without using `server.pve true` In-game rule manager using `/sprules` Debug command to help check why damage is blocked or allowed Optional PVE/PVP status UI for players Customizable UI position, status text, icons, and colors Discord embed messages when PVP purge starts or ends Optional Discord warning messages before PVE/PVP schedule changes Run custom server commands when PVP purge starts or ends Admin bypass permissions for loot and damage control Supports PVP delay when leaving PVP zones Flexible config for server owners who want full control Designed for simple PVE servers, purge servers, hybrid PVE/PVP servers, and event-based servers NEW • CUSTOM STATUS  NEW • PVE/PVP HUD FOR DISPLAYING PURGE EVENTS 📌 Commands /simplepve - Use to enable or disable pve toggle (Chat & Console command) /simplepve on or off - Use to enable disable pve (Chat & Console command) /sprules - Use to Open a Cui to control PVE Rules & Creating Schedules   (Chat command) /spdebug - Use this for debuging rules /sp_change - Use this to change the SimplePVE hud from ingame (Chat command) 📜 Permissions simplepve.admin - Required to enable or disable SimplePVE simplepve.adminloot - Required to view Loots of other players simplepve.admindamage - Required for Admin damages to any entity                                                                                                                                                                                                     🎉 Game hosting perfected, that's Physgun Join the thousands of server owners using Physgun to take their game server communities to the top.   🎬 Video Showcase 🚀 API & Hooks void  OnSPVEPurgeStarted() void  OnSPVEPurgeEnded() TimeSpan  GetPVPStartTimeRemaining() TimeSpan  GetPVPEndTimeRemaining() ⚙️ Configurations 🗃️ Rules Data file in Oxide/data/SimplePVE 📜 FAQ Question: Does SimplePVE require server.pve to be set to false? Yes, it requires server.pve set to false. Question: Where can I change the rules for my PVE server? You can use the `/sprules` command to open the in-game CUI rule manager. You must have the `simplepve.admin` permission assigned to use this command. Question: PVE/PVP schedules times are not working properly, why is that happening? You may need to adjust the `UTC Time Difference` value in the config. Make sure the UTC offset matches your server’s intended timezone. For more details, please check the Info tab below. Question: How do I enable or disable PVE manually? You can use `/simplepve on` to enable PVE and `/simplepve off` to disable it. You need the `simplepve.admin` permission to use these commands. Question: Can I create automatic PVP purge schedules? Yes. SimplePVE supports scheduled PVP/PVE times, allowing you to automatically enable PVP during purge events and return to PVE when the schedule ends. Question: Can I do Weekly schedules like Sunday To Friday or specific date to another date? Yes. SimplePVE supports both option and you can only use one of them at once. Question: Can admins damage players or entities while PVE is enabled? Yes, but only if the admin damage settings and permissions allow it. The permission `simplepve.admindamage` is used for admin damage access. Question: Why is damage still happening during PVE mode? This usually means one of your rules allows that damage type, or another plugin is modifying damage before or after SimplePVE. Use `/spdebug` to help debug which rule is being applied. Question: What does `/spdebug` do? The `/spdebug` command helps you debug damage rules. It can be useful when you are trying to understand why damage is blocked or allowed. Question: How does loot protection work? Loot protection prevents players from looting protected entities or containers, depending on your config settings. Admins can be allowed to bypass this using the `simplepve.adminloot` permission. Question: Can I exclude specific entities from loot protection? Yes. You can add entity shortnames to the `Loot Protection Excluded Entitys` list in the config. Question: Does SimplePVE support zones? Yes. SimplePVE supports Zone Manager, allowing you to create different PVE/PVP behavior inside specific zones. Question: Can I exclude specific zones from SimplePVE rules? Yes. You can add zone IDs to the `Exclude Zone IDs From Rules` config option. Question: Can SimplePVE send Discord notifications? Yes. SimplePVE can send Discord embed messages when PVP purge starts, ends, or when a scheduled event is approaching, depending on your Discord config settings. Question: Can I run server commands when PVP purge starts or ends? Yes. You can add commands to the config options for commands that run when PVP purge starts or ends. ⚙️ Schedules Settings for your own timezone 🛠️ For Developers           💬 Support   Check Out My Other plugins as Well