FEATURES Map size: 4500; Prefab count: ~54k; A lot of attention was paid to nature, and each section of the map was designed in detail; Most of the rocks are hand-crafted, which makes them look much better. The custom config for the BetterNpc plugin is set up so that bots are present at all points of interest; Compatible with BetterNPC plugins (Config for bots in the file),  Train Homes and Raidable bases; Underground railway; A large number of small settlements/single buildings not marked on the road map by road; Double-track surface railway with 1 entrance to the metro with separate branches for spawn trains; Ring road (compatible with event plugins); There are custom trawlers; Evenly spaced monuments to spread the FPS load of client; A lot custom building places (X on the minimap); Custom places for building in the subway (XU on the minimap); Bridges are designed for easy tugboat access; A large number of points with access to fresh water for farms. ( Rivers inside the island work like regular game rivers ) CUSTOM MONUMENTS Oil Refinery; Destroyed satellite dishes; Heli towers (1-5); Construction Site; Abandoned Oil Tanks; Oil Tanks; Crash Site; Oil Platform; Deep Seeker ( Trawler ); Northwind ( Trawler ); Storm Trawler ( Trawler ); Sea Wolf ( Trawler ); Silver Catch ( Trawler ); Bering Beauty ( Trawler ); Underwater caves (x2 ) ( Zones for underwater farm ); Sunken Containers (x2 ) ( Zones for underwater farm ); A lots custom places to build a base. ( "X"/"XU"  on map  ); Train Station ( For Train homes plugin ) A lots unmarked buildings. FACEPUNCH MONUMENTS Combined Outpost; Apartment Complex; Military Tunnel; Harbour (2/2); Ziggurat; Ferry Terminal; Radtown; Abandoned Supermarket; Nuclear Missile Silo; Oxum's Gas Station; Airfield; Lighthouse; The Dome; Water treatment plant; Trainyard; Power Plant; Arctic Research Base; Desert Military Base; Giant Excavator Pit; Stone, Sulfur & HQM quarries; Satellite Dish; Small & Large Oil Rig; Large Underwater Lab. My Discord: shemov Discord Server: https://discord.gg/UpUXuxs4Vx A password is attached to the map.  You can edit it.  

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

Automated chat messages based on chat keywords, timer or various other triggers. Plugin comes with an easy to use  Admin UI for complete setup, and supports special localization for your messages. You can define messages to be sent only to specific Groups or Permissions, and you can allow players to toggle on/off messages if they do not find them useful.   SUPPORTED TRIGGERS  If what you need is not here and still falls under the scope of the plugin description, reach out to me Timed | ChatCommand | AutoReply | NewPlayerJoined | PlayerConnected | PlayerDisconnected | PermissionGranted | PermissionRevoked | AddedToGroup | RemovedFromGroup | PlayerDead | CrateHacked | EnteredDeepSea | LeftDeepSea | EnteredZone | LeftZone | EnteredMonument | LeftMonument   COMMANDS /am.edit - (Admin UI for complete setup) - requires automatedmessages.admin permission /tips -  (Player command for toggling on/off messages) command can be changed in the config file   MESSAGES LOCALIZATION You can switch between languages in Admin UI to setup localized replies for every language the game supports. Check config section below for how to add languages.   Game Tips You can utilize Rust's native game tip UI to show specific messages instead or along with sending it to chat.   VARIABLES Variables can be included in the messages text to show further info based on the trigger or player. The plugin also supports  https://umod.org/plugins/placeholder-api  with the extensive list of variables it brings.   {playername} {playerid} - Player steam id {playercountry} {hacklocation} - Specific to messages with type CrateHacked {wipetimeremaining} - Days/Hours till wipe (based on rust convar settings if a missile silo monument is present) {online} - # of players online {sleeping} - # of players sleeping {joining} - # of players joining   CONFIG SETTINGS  Below are  only settings not currently available in Admin UI, highly recommended to edit triggers or actions using /am.edit Chat Icon (Steam Id)  - Icon that will be used for all messages sent by the plugin, must be a steam id. Toggle Chat Command  - "tips" - Chat command that allows a player to toggle on/off messages. AutoReply Cooldown (in seconds)  - Per action cooldown timer when  players type a keyword set. ChatCommand Cooldown (in seconds) - Per player cooldown timer when a player types a  chat command. ZoneManager Cooldown (in seconds)  - Per player cooldown timer on enter or exit zone. MonumentWatcher Cooldown (in seconds) - Per player cooldown timer on enter or exit monument. Replies Server Languages  - Languages your server will support. Available options:  af, ar, ca, cs, da, de, el, en-PT, en, es-ES, fi, fr, hu, it, ja, ko, nl, no, pl, pt-PT, pt-BR, ro, ru, sr, sv, tr, uk, vi, zh-CN, zh-TW Default Server Language -  Fallback language if player client  language had no available replies, you must have at least one reply for this language for the action to function. AutoReply `Broadcast to all` option to broadcast to team only if keywords sent from team chat - true/false

Offline Raid Limiter Stop Unfair Offline Raids in Their Tracks Tired of seeing your Rust server overrun by offline raid abuse? Offline Raid Limiter steps in to restore balance and fair play. With powerful tracking and immediate damage blocking, your players can enjoy a more authentic Rust experience—and you can enjoy worry-free server management. Key Benefits Prevent Offline Raid Abuse Daily + Per-Wipe raid limits Run daily limits, wipe limits, or both at the same time (fully configurable). Proximity-Based Tracking: Only counts raids when attackers are within range of a Tool Cupboard (TC), ensuring offline raid limits don’t trigger prematurely. Smart Raid Session Management Team & Additional Raider Tracking: Keeps tabs on individual players as well as entire teams—even if they leave and rejoin. Plus, if additional players jump into the same raid, their involvement is recorded. Edge Case Handling: No more confusion or gaps in coverage if a defender goes offline mid-raid or when multiple attackers are involved. Offline Raid Limiter’s robust logic sorts out these scenarios seamlessly. Instant Damage Blocking Enforce Fair Play: Once a team or individual hits their daily offline raid quota, further damage is blocked automatically. That means no more sneaky workarounds or unstoppable raids. Modded Server UI In-Game Control: For modded servers, gain access to a simple in-game UI that displays raid history, player statistics, and real-time session data. Player-Friendly Features: Grant permissions so your players can check their offline raid counts with the /orl.mystats command—helping everyone stay within the rules. Detailed Alerts & Reporting Discord Integration: Offline Raid Limiter sends comprehensive alerts to Discord, making admin oversight a breeze. Export & Clear Sessions: Use /orl.export to log and share your entire raid history for deeper analysis, then wipe all sessions with a simple console command if you need a fresh start. Designed for Vanilla & Modded Servers Flexible Configuration: If you set your server to "Vanilla,” the plugin automatically disables UI and direct damage blocks, limiting itself to Discord notifications so admins can monitor raiding behind the scenes. Seamless Integration: Works hand-in-hand with Rust’s existing frameworks and requires only the Simple Status & Image Library for certain UI elements. Why Choose Offline Raid Limiter? Enhanced Fairness: Players can’t take shortcuts with offline raids for easy loot. Clear Oversight: Admins see exactly who’s raiding and how often, helping you enforce balanced gameplay. Configurable & User-Friendly: Tailor the plugin to your server’s needs in just a few clicks, with plenty of documentation to guide you. If you’re ready to level the playing field and protect your community from unfair offline raids, Offline Raid Limiter has you covered. Bring your Rust server to new heights of balance, transparency, and peace of mind!   Commands & Usage Player Commands (permission based) /orl.mystats — Shows your overall stats (daily + wipe, plus active limits). /orl.mydaily — Shows your daily offline raids and daily limit. /orl.mywipe — Shows your wipe offline raids and wipe limit. Admin Commands /orl.disable <hours> — Temporarily disables enforcement for X hours. /orl.enable — Re-enables immediately. /orl.clearall — Clears all stored raid sessions (and fully resets tracking). /orl.clearplayer <SteamID64 or name> — Clears raids for a specific player/team. /orl.export — Exports raid sessions to JSON via the debug webhook. /orl.dailyall [top] — Shows a “top raiders” list for daily scope. /orl.wipeall [top] — Shows a “top raiders” list for wipe scope. /orl.dailyplayer <name/id> — Check a player’s daily count. /orl.wipeplayer <name/id> — Check a player’s wipe count.   Damage / Raid Logic OfflineRaidLimiter checks incoming damage to building blocks, doors, external walls, and more. If a team or player has exceeded the daily offline raid limit, all further damage to offline bases is blocked—and you can optionally broadcast an alert to Discord. Key Points to Note About Commands Some commands differ depending on your permissions and server setup. For instance, if a player types /exportraidsessions in chat, it won’t work unless they have OfflineRaidLimiter.admin. For "Vanilla” servers (as set in the config), UI, damage blocking, and certain other features may be disabled—so commands like clearraidsessions and clearraidsforplayer will still work, but may only be visible to server admins via console. When Commands Might Defer Cleanup Commands: If the plugin detects that some raid sessions are still "cooling down” (meaning the raid window hasn’t fully expired), the system may defer clearing them until the next pass. This prevents conflicts with currently active raids. Blocking Logic: After the daily limit is reached, the blocking triggers immediately and remains in place until the next server reset or cleanup routine (depending on how you configure it).  

An excellent plugin for remote trading between players with extensive functionality.   The ability to log successful trades; The ability to create new permissions; The ability to customize permissions flexibly, including both new and existing ones; The ability to limit slots in trade; The ability to configure the method(Personal, CommonMinimum, CommonMaximum) for limiting the number of slots; The ability to set a cooldown on sending trade requests; The ability to configure the method(InitiatorOnly, TargetOnly, Both) for applying cooldown to players; The ability to purchase a bypass for the trade request cooldown; The ability to set a daily limit on sending trade requests; The ability to purchase additional trade requests after reaching the daily limit; The ability to forbid trading when wounded; The ability to forbid trading while swimming; The ability to forbid trading while mounted on certain seats; The ability to forbid trading in specified monuments, by name or by monument type; The ability to forbid trading in someone else's building privileges; The ability to forbid trading when taking damage; The ability to forbid trading during a combat block; The ability to forbid trading during a raid block; The ability to forbid certain items from being traded; The ability to automatically generate language files for specified languages(with content filled in English); The ability to set an effect upon receiving a trade request; The ability to change the effect upon a successful trade completion; The ability to display a status bar while waiting for a trade; The ability to choose between bar types(TimeCounter and TimeProgressCounter); The ability to specify the order of the bar; The ability to change the height of the bar; The ability to customize the color and transparency of the background; The ability to set a material for the background; The ability to switch between CuiRawImageComponent and CuiImageComponent for the image; The ability to get images from the local folder(*SERVER*\oxide\data\AdvancedStatus\Images); The ability to set own image and customize the color and transparency of the image; The ability to set sprite instead of the image; The ability to customize the color, size and font of the text.   { "Chat command": "trade", "List of 'accept' commands": [ "accept", "yes" ], "List of 'cancel' commands": [ "cancel", "no" ], "Is it worth enabling GameTips for messages?": true, "Is it worth using Notify plugins for messages instead of the vanilla UI?": false, "Specify the regular message type for notify": 0, "Specify the warning message type for notify": 1, "Is it worth using the AdvancedStatus plugin?": true, "Is it worth saving trade logs to a file?": true, "List of language keys for creating language files": [ "en" ], "Slot limit calculation mode(Personal, CommonMinimum, CommonMaximum)": "CommonMaximum", "Trade cooldown apply mode(InitiatorOnly, TargetOnly, Both)": "InitiatorOnly", "Is it worth checking the target's trade cooldown?": false, "Time in seconds given to respond to a trade request": 15.0, "Price to skip 60 seconds of the trade request cooldown": 10.0, "The prefab name for the effect triggered when a trade request is received": "assets/bundled/prefabs/fx/invite_notice.prefab", "The prefab name for the effect triggered when a trade is successfully completed": "assets/prefabs/building/wall.frame.shopfront/effects/metal_transaction_complete.prefab", "List of mount names where trading is prohibited": [ "horsesaddle", "horsesaddlerear", "bikedriverseat", "bikepassengerseat", "motorbikedriverseat", "motorbikepassengerseat", "modularcardriverseat", "modularcarpassengerseatleft", "modularcarpassengerseatright", "modularcarpassengerseatlesslegroomleft", "modularcarpassengerseatlesslegroomright", "modularcarpassengerseatsidewayleft", "miniheliseat", "minihelipassenger", "transporthelipilot", "transporthelicopilot", "attackhelidriver", "attackheligunner", "submarinesolodriverstanding", "submarineduodriverseat", "submarineduopassengerseat", "snowmobiledriverseat", "snowmobilepassengerseat", "snowmobilepassengerseat tomaha", "workcartdriver", "locomotivedriver", "craneoperator", "batteringramseat", "ballistagun.entity" ], "Status. Bar - Display time in seconds. A value of 0 keeps it visible until the cooldown ends": 15.0, "Status. Bar - Type(TimeProgressCounter or TimeCounter)": "TimeCounter", "Status. Bar - Height": 26, "Status. Bar - Order": 10, "Status. Background - Color(Hex or RGBA)": "#EFC570", "Status. Background - Transparency": 0.7, "Status. Background - Material(Leave empty to disable)": "", "Status. Image - Url": "https://gitlab.com/IIIaKa/images/-/raw/main/StatusBars/Trader_Request.png", "Status. Image - Local(Leave empty to use Image_Url)": "Trader_Request", "Status. Image - Sprite(Leave empty to use Image_Local or Image_Url)": "", "Status. Image - Is raw image": false, "Status. Image - Color(Hex or RGBA)": "#EFC570", "Status. Image - Transparency": 1.0, "Status. Image Outline - Color(Hex or RGBA)": "0.1 0.3 0.8 0.9", "Status. Image Outline - Transparency": 1.0, "Status. Image Outline - Distance(Leave empty to disable). Example '0.75 0.75'": "", "Status. Text - Size": 12, "Status. Text - Color(Hex or RGBA)": "#FFFFFF", "Status. Text - Transparency": 1.0, "Status. Text - Font(https://umod.org/guides/rust/basic-concepts-of-gui#fonts)": "RobotoCondensed-Bold.ttf", "Status. Text - Offset Horizontal": 0, "Status. Text Outline - Color(Hex or RGBA)": "#000000", "Status. Text Outline - Transparency": 1.0, "Status. Text Outline - Distance(Leave empty to disable)": "", "Status. SubText - Size": 12, "Status. SubText - Color(Hex or RGBA)": "#FFFFFF", "Status. SubText - Transparency": 1.0, "Status. SubText - Font": "RobotoCondensed-Bold.ttf", "Status. SubText Outline - Color(Hex or RGBA)": "0.5 0.6 0.7 0.5", "Status. SubText Outline - Transparency": 1.0, "Status. SubText Outline - Distance(Leave empty to disable)": "", "Status. Progress - Background Color(Hex or RGBA)": "1 1 1 0.15", "Status. Progress - Background Transparency": 0.15, "Status. Progress - Reverse": true, "Status. Progress - Color(Hex or RGBA)": "#EFC570", "Status. Progress - Transparency": 0.7, "Status. Progress - OffsetMin": "0 0", "Status. Progress - OffsetMax": "0 0", "List of trade permissions": [ { "Permission Name": "trader.default", "Number of available trade slots": 3, "Cooldown time(in seconds) before next trade": 600.0, "Daily trade request limit. A value of 0 disables the limit": 50, "Price to purchase a trade after exceeding the daily limit. A value of 0 disables the purchase": 5.0, "Is it worth forbidding trade if the player is in a wounded state?": true, "Is it worth forbidding trade if the player is swimming?": true, "Is it worth forbidding trade if the player is mounted?": true, "Is it worth forbidding trade if the player is in someone else's building privilege area?": true, "Is it worth forbidding trade if the player has taken damage?": true, "Is it worth forbidding trade if the player has combat block?": true, "Is it worth forbidding trade if the player has raid block?": true, "List of monuments where trade is forbidden": null, "List of monument categories where trade is forbidden": [ "RadTown", "RadTownWater", "RadTownSmall", "TunnelStation", "Custom" ], "List of forbidden trade items": [ "rock" ] }, { "Permission Name": "trader.vip", "Number of available trade slots": 6, "Cooldown time(in seconds) before next trade": 450.0, "Daily trade request limit. A value of 0 disables the limit": 100, "Price to purchase a trade after exceeding the daily limit. A value of 0 disables the purchase": 2.5, "Is it worth forbidding trade if the player is in a wounded state?": true, "Is it worth forbidding trade if the player is swimming?": true, "Is it worth forbidding trade if the player is mounted?": true, "Is it worth forbidding trade if the player is in someone else's building privilege area?": true, "Is it worth forbidding trade if the player has taken damage?": true, "Is it worth forbidding trade if the player has combat block?": true, "Is it worth forbidding trade if the player has raid block?": true, "List of monuments where trade is forbidden": null, "List of monument categories where trade is forbidden": [ "RadTown", "RadTownWater", "TunnelStation" ], "List of forbidden trade items": [ "rock" ] }, { "Permission Name": "realpve.vip", "Number of available trade slots": 9, "Cooldown time(in seconds) before next trade": 300.0, "Daily trade request limit. A value of 0 disables the limit": 0, "Price to purchase a trade after exceeding the daily limit. A value of 0 disables the purchase": 0.0, "Is it worth forbidding trade if the player is in a wounded state?": false, "Is it worth forbidding trade if the player is swimming?": false, "Is it worth forbidding trade if the player is mounted?": false, "Is it worth forbidding trade if the player is in someone else's building privilege area?": false, "Is it worth forbidding trade if the player has taken damage?": false, "Is it worth forbidding trade if the player has combat block?": false, "Is it worth forbidding trade if the player has raid block?": false, "List of monuments where trade is forbidden": [ "oilrig_1" ], "List of monument categories where trade is forbidden": null, "List of forbidden trade items": [ "rock" ] } ], "Version": { "Major": 0, "Minor": 1, "Patch": 4 } }   EN: { "CmdNotAllowed": "You do not have permission to use this command!", "CmdPlayerNotFound": "Player '{0}' not found! You must provide the player's name or ID.", "CmdMultiplePlayers": "Multiple players found: {0}", "CmdEconomicsNotEnough": "Not enough funds!", "CmdMain": "Available trade commands:\n\n<color=#D1CBCB>/trade</color> <color=#D1AB9A>bars *boolValue*(optional)</color> - Toggle status bar display\n<color=#D1CBCB>/trade</color> <color=#D1AB9A>*nameOrId*</color> - Send a trade request to the specified player\n<color=#D1CBCB>/trade</color> <color=#83BA7C>accept/yes</color> - Accept a pending trade request\n<color=#D1CBCB>/trade</color> <color=#DE5757>cancel/no</color> - Decline a pending or active trade\n<color=#D1CBCB>/trade</color> <color=#D1AB9A>limits</color> - View your trade limits\n<color=#D1CBCB>/trade</color> <color=#D1AB9A>buy limits *amount*(optional)</color> - Purchase additional trade requests\n<color=#D1CBCB>/trade</color> <color=#D1AB9A>buy cd *amount*(optional)</color> - Purchase a 60 second(* by amount) cooldown skip\n\n--------------------------------------------------", "CmdBarsEnabled": "Status bar display enabled!", "CmdBarsDisabled": "Status bar display disabled!", "CmdDailyLimitExtra": "You have exceeded the daily limit({0}) for sending trade requests!\n<size=10>However, you can buy additional requests using the <color=#D1AB9A>/trade buy limits</color> command for <color=#D1CBCB>${1}</color></size>", "CmdDailyLimit": "You have exceeded the daily limit({0}) for sending trade requests!", "CmdCooldownSkip": "You must wait {0} seconds before sending another trade request!\n<size=10>However, you can skip the cooldown using the <color=#D1AB9A>/trade buy cd</color> command for <color=#D1CBCB>${1}</color> per 60 seconds</size>", "CmdCooldown": "You must wait {0} seconds before sending another trade request!", "CmdWoundBlock": "You can't trade while wounded!", "CmdSwimming": "You can't trade while swimming!", "CmdMountBlock": "You can't trade while mounted here!", "CmdBuildingBlock": "You can't trade inside someone else's base!", "CmdDamageBlock": "You can't trade while taking damage!", "CmdCombatBlock": "You can't trade during combat block!", "CmdRaidBlock": "You can't trade during a raid block!", "CmdAcceptEmpty": "You have no pending trade requests!", "CmdAcceptOngoing": "You already have an active trade with player '<color=#D1AB9A>{0}</color>'!", "CmdDeclineEmpty": "You have no pending or active trades!", "CmdDecline": "Trade between you and player '<color=#D1AB9A>{0}</color>' has been canceled!", "CmdDeclineOther": "Player '<color=#D1AB9A>{0}</color>' canceled the trade with you!", "CmdSendSelf": "You cannot send a trade request to yourself!", "CmdSendNoRespond": "Player '<color=#D1AB9A>{0}</color>' has not responded to your trade request!", "CmdSendAlredyHave": "You already have a pending or active trade with player '<color=#D1AB9A>{0}</color>'!\n<size=10><color=#83BA7C>/trade yes</color> - Accept the pending trade request\n<color=#DE5757>/trade no</color> - Decline the pending or active trade</size>", "CmdSendTargetNotAllowed": "Player '<color=#D1AB9A>{0}</color>' does not have permission to use trading!", "CmdSendTargetAlredyHave": "Player '<color=#D1AB9A>{0}</color>' already has a pending or active trade with player '<color=#D1AB9A>{1}</color>'!", "CmdSendTargetHasCooldown": "Player '<color=#D1AB9A>{0}</color>' has an active cooldown, {1} seconds remaining!", "CmdSendTo": "Trade request successfully sent to player '<color=#D1AB9A>{0}</color>'.", "CmdSendFrom": "Player '<color=#D1AB9A>{0}</color>' has sent you a trade request.\n<size=10><color=#83BA7C>/trade yes</color> - Accept the pending trade request\n<color=#DE5757>/trade no</color> - Decline the pending or active trade</size>", "CmdPurchaseNotLimited": "You haven't reached your daily limit yet!", "CmdPurchaseHaveExtra": "You still have {0} additional trade requests! Use them before purchasing more.", "CmdPurchaseLimitsNotAllowed": "Purchasing additional trade requests is unavailable!", "CmdPurchasedLimits": "You have successfully purchased <color=#D1CBCB>{0}</color> trade requests!\n<size=10>Now you have <color=#D1CBCB>{1}</color> additional trade requests</size>", "CmdPurchaseNoCooldown": "You don't have a cooldown for sending trade requests!", "CmdPurchaseCooldownNotAllowed": "Purchasing a cooldown skip for trade requests is not available!", "CmdPurchasedCooldown": "You have successfully purchased a cooldown skip for <color=#D1CBCB>{0} seconds</color> for trade requests!\n<size=10>Now you need to wait <color=#D1CBCB>{1} seconds</color></size>", "CmdMyLimits": "Your trade request limits:\n\n<color=#D1CBCB>Cooldown</color> - <color=#D1AB9A>{0} sec</color>\n<color=#D1CBCB>Daily Limit</color> - <color=#D1AB9A>{1}</color>\n\n--------------------------------------------------", "BarInitiator": "Trade to: {0}", "BarTarget": "Trade from: {0}", "BarCooldown": "Trade cooldown:", "MsgStarted": "You have started a trade with player '<color=#D1AB9A>{0}</color>'!", "MsgCompleted": "Trade with player '<color=#D1AB9A>{0}</color>' completed successfully!", "MsgCanceled": "Player '<color=#D1AB9A>{0}</color>' canceled the trade!" } RU: { "CmdNotAllowed": "У вас недостаточно прав для использования этой команды!", "CmdPlayerNotFound": "Игрок '{0}' не найден! Вы должны указать имя или ID игрока.", "CmdMultiplePlayers": "Найдено несколько игроков: {0}", "CmdEconomicsNotEnough": "Не достаточно средств!", "CmdMain": "Доступные команды для трейда:\n\n<color=#D1CBCB>/trade</color> <color=#D1AB9A>bars *булевоеЗначение*(опционально)</color> - Переключение отображения статус баров\n<color=#D1CBCB>/trade</color> <color=#D1AB9A>*имяИлиАйди*</color> - Отправить запрос на трейд указанному игроку\n<color=#D1CBCB>/trade</color> <color=#83BA7C>accept/yes</color> - Принять ожидающий запрос на трейд\n<color=#D1CBCB>/trade</color> <color=#DE5757>cancel/no</color> - Отклонить ожидающий или активный трейд\n<color=#D1CBCB>/trade</color> <color=#D1AB9A>limits</color> - Узнать свои лимиты\n<color=#D1CBCB>/trade</color> <color=#D1AB9A>buy limits *количество*(опционально)</color> - Докупить дополнительное количество трейд запросов\n<color=#D1CBCB>/trade</color> <color=#D1AB9A>buy cd *количество*(опционально)</color> - Купить пропуск 60 секунд(* на количество) задержки перед отправкой трейд запросов\n\n--------------------------------------------------", "CmdBarsEnabled": "Отображение статус баров включено!", "CmdBarsDisabled": "Отображение статус баров выключено!", "CmdDailyLimitExtra": "Вы превысили допустимую дневную норму({0}) на отправку трейд запросов!\n<size=10>Но вы можете купить дополнительные запросы с помощью команды <color=#D1AB9A>/trade buy limits</color> за <color=#D1CBCB>{1}$</color></size>", "CmdDailyLimit": "Вы превысили допустимую дневную норму({0}) на отправку трейд запросов!", "CmdCooldownSkip": "Перед отправкой нового запроса на трейд вам необходимо подождать {0} секунд!\n<size=10>Но вы можете купить пропуск задержки с помощью команды <color=#D1AB9A>/trade buy cd</color> за <color=#D1CBCB>{1}$</color> за каждые 60 секунд</size>", "CmdCooldown": "Перед отправкой нового запроса на трейд вам необходимо подождать {0} секунд!", "CmdWoundBlock": "Вам запрещено пользоваться трейдом в предсмертном состоянии!", "CmdSwimming": "Вам запрещено пользоваться трейдом в воде!", "CmdMountBlock": "Вам запрещено пользоваться трейдом сидя в данном месте!", "CmdBuildingBlock": "Вам запрещено пользоваться трейдом в чужой базе!", "CmdDamageBlock": "Вам запрещено пользоваться трейдом при получении урона!", "CmdCombatBlock": "Вам запрещено пользоваться трейдом во время боя!", "CmdRaidBlock": "Вам запрещено пользоваться трейдом во время рейда!", "CmdAcceptEmpty": "У вас нет ожидающих запросов на трейд!", "CmdAcceptOngoing": "У вас уже есть активный трейд с игроком '<color=#D1AB9A>{0}</color>'!", "CmdDeclineEmpty": "У вас нет ожидающих или активных трейдов!", "CmdDecline": "Трейд между вами и игроком '<color=#D1AB9A>{0}</color>' отменён!", "CmdDeclineOther": "Игрок '<color=#D1AB9A>{0}</color>' отменил трейд с вами!", "CmdSendSelf": "Нельзя отправить трейд запрос самому себе!", "CmdSendNoRespond": "Игрок '<color=#D1AB9A>{0}</color>' не ответил на ваш трейд запрос!", "CmdSendAlredyHave": "У вас уже есть ожидающий или активный трейд с игроком '<color=#D1AB9A>{0}</color>'!\n<size=10><color=#83BA7C>/trade yes</color> - Принять ожидающий запрос на трейд\n<color=#DE5757>/trade no</color> - Отклонить ожидающий или активный трейд</size>", "CmdSendTargetNotAllowed": "У игрока '<color=#D1AB9A>{0}</color>' недостаточно прав для использования обмена!", "CmdSendTargetAlredyHave": "У игрока '<color=#D1AB9A>{0}</color>' уже есть ожидающий или активный трейд с игроком '<color=#D1AB9A>{1}</color>'!", "CmdSendTargetHasCooldown": "У игрока '<color=#D1AB9A>{0}</color>' имеется активный кулдаун, осталось {1} секунд!", "CmdSendTo": "Игроку '<color=#D1AB9A>{0}</color>' был успешно отправлен запрос на трейд.", "CmdSendFrom": "Игрок '<color=#D1AB9A>{0}</color>' отправил вам запрос на трейд.\n<size=10><color=#83BA7C>/trade yes</color> - Принять ожидающий запрос на трейд\n<color=#DE5757>/trade no</color> - Отклонить ожидающий или активный трейд</size>", "CmdPurchaseNotLimited": "Вы ещё не исчерпали свой дневной лимит!", "CmdPurchaseHaveExtra": "У вас ещё есть {0} дополнительных трейд запросов! Используйте их прежде, чем покупать новые.", "CmdPurchaseLimitsNotAllowed": "Покупка дополнительных трейд запросов недоступна!", "CmdPurchasedLimits": "Вы успешно докупили <color=#D1CBCB>{0}</color> трейд запросов!\n<size=10>Теперь у вас <color=#D1CBCB>{1}</color> дополнительных трейд запросов</size>", "CmdPurchaseNoCooldown": "У вас нет задержки на отправку трейд запросов!", "CmdPurchaseCooldownNotAllowed": "Покупка пропуска задержки на трейд запросы недоступна!", "CmdPurchasedCooldown": "Вы успешно купили пропуск на <color=#D1CBCB>{0} секунд</color> задержки для трейд запросов!\n<size=10>Теперь вам нужно подождать <color=#D1CBCB>{1} секунд</color></size>", "CmdMyLimits": "Ваши лимиты трейд запросов:\n\n<color=#D1CBCB>Время задержки</color> - <color=#D1AB9A>{0} сек</color>\n<color=#D1CBCB>Дневной лимит</color> - <color=#D1AB9A>{1}</color>\n\n--------------------------------------------------", "BarInitiator": "Трейд с: {0}", "BarTarget": "Трейд от: {0}", "BarCooldown": "Задержка трейда:", "MsgStarted": "Вы начали трейд с игроком '<color=#D1AB9A>{0}</color>'!", "MsgCompleted": "Трейд с игроком '<color=#D1AB9A>{0}</color>' успешно завершён!", "MsgCanceled": "Игрок '<color=#D1AB9A>{0}</color>' отменил трейд!" }   bars *boolValue*(optional) - Toggle status bar display. *nameOrId* - Send a trade request to the specified player. accept/yes - Accept a pending trade request. cancel/no - Decline a pending or active trade. limits - View your trade limits. buy limits *amount*(optional) - Purchase additional trade requests. buy cd *amount*(optional) - Purchase a 60 second(* by amount) cooldown skip. Example: /trade bars true /trade iiiaka /trade yes /trade limits /trade buy limits 1 /trade buy limits 0.5

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            

🥇Ready to level up your server's raiding experience? This premium pack contains 210 unique, handcrafted raidable bases divided into 5 distinct difficulty tiers (Easy, Medium, Hard, Expert, and Nightmare). Each tier comes with its own custom, balanced loot tables —the bigger the challenge, the better the reward! Everything is 100% Plug & Play. You don’t need to spend hours editing configurations; just copy, paste, and you're good to go! 🕹️What makes this pack unique: Easy & Medium Bases: Built to be starter-friendly, utilizing a massive variety of awesome skins to make your server look incredibly alive and high-quality. Hard, Expert & Nightmare Bases: Features complex layouts, multiple entrances, clever trap placements, and a heavy challenge loaded with top-tier rewards. Plug & Play Setup: Comes with everything pre-configured—loot tables, difficulty profiles, and the main plugin settings are all included. No setup required! 🎮How to Install (Step-by-Step) As detailed in the README.txt.txt file, setting this up on your server takes less than 2 minutes: Base Files: Extract all .json files from the copypaste/ folders and place them directly into: oxide/data/copypaste/ (Do not copy the subfolders, only the files inside them!) Loot Tables: Copy all files from Difficulty_Loot/ into: oxide/data/RaidableBases/Loot/ Profiles: Copy all files from Profiles/ into: oxide/data/RaidableBases/Profiles/ Plugin Config (Optional): If you want to use the included custom config, copy RaidableBases.json from the config/ folder into: oxide/config/ (Note: This will overwrite your existing config!) Reload: Run o.reload RaidableBases in your server console. Note: This pack requires the paid Raidable Bases plugin (by nivex) and the CopyPaste plugin installed on an Oxide/uMod Rust server.     IMPORTANT: Remove Stone Walls (Enclosures): By default, the plugin spawns a giant stone wall around bases. To remove it: Open oxide/config/RaidableBases/Profiles/Easy.json Find "Spawns Enclosure": true and change it to false. Run command: rb.reload in console. In Case that you feel that it's too much loot: Open oxide/config/RaidableBases/Profiles/Easy.json or any tother Difficulty "Amount Of Items To Spawn": 45, Change the  Amount Of Items to a lower number. Modifying Base Despawn Timers: If you want to change how long a base stays on the map before disappearing, find these lines under "Raid Management" in config:  "Minutes Until Despawn After Looting (min: 1)": 15, "Minutes Until Despawn After Inactive (0 = disabled)": 45 Controlling Automatically Maintained Events: It's spawning 6 bases at every 30 mins - 1h 30 mins, randomly. Easy & Medium got higher chances to spawn. Takes 30 seconds per base to spawn so it's not going to make the server to lag. "Always Maintain Max Events": true, "Max Maintained Events": 6 Auto-Cooking & Sorting (Furnace & Base Sorting): If you want to know how the pack automatically moves resources or food into the right containers when a base spawns, look for these options under "Raid Management" in config: "Move Cookables Into Ovens": true, "Move Food Into BBQ Or Fridge": true, "Move Resources Into Tool Cupboard": true, "Move Items Into Lockers": true Turning Lights and Furnaces On Automatically: "Turn Lights On At Night": true, "Turn Lights On Indefinitely": true, "Furnace Starting Fuel": 1000 Automatic Chat Announcements: If you want the entire server to know when a new raid has appeared on the map, look for "Event Messages" in config: "Announce Buy Base Messages": false, "Show Opened Message For PVE Bases": true, "Show Opened Message For PVP Bases": true If you already have other bases installed and don't want to use the included Profiles, you can register all 210 bases directly into your difficulty profiles by running the commands below in your server console (F1 or RCON). After pasting all commands, reload the plugin with o.reload RaidableBases. rb.config add "Easy Bases" easy1 easy2 easy3 easy4 easy5 easy6 easy7 easy8 easy9 easy10 rb.config add "Easy Bases" easy11 easy12 easy13 easy14 easy15 easy16 easy17 easy18 easy19 easy20 rb.config add "Easy Bases" easy21 easy22 easy23 easy24 easy25 easy26 easy27 easy28 easy29 easy30 rb.config add "Easy Bases" easy31 easy32 easy33 easy34 easy35 easy36 easy37 easy38 easy39 easy40 rb.config add "Easy Bases" easy41 easy42 easy43 easy44 easy45 easy46 easy47 easy48 easy49 easy50 rb.config add "Easy Bases" easy51 easy52 easy53 easy54 easy55 easy56 easy57 easy58 easy59 easy60 rb.config add "Medium Bases" medium1 medium2 medium3 medium4 medium5 medium6 medium7 medium8 medium9 medium10 rb.config add "Medium Bases" medium11 medium12 medium13 medium14 medium15 medium16 medium17 medium18 medium19 medium20 rb.config add "Medium Bases" medium21 medium22 medium23 medium24 medium25 medium26 medium27 medium28 medium29 medium30 rb.config add "Medium Bases" medium31 medium32 medium33 medium34 medium35 medium36 medium37 medium38 medium39 medium40 rb.config add "Medium Bases" medium41 medium42 medium43 medium44 medium45 medium46 medium47 medium48 medium49 medium50 rb.config add "Medium Bases" medium51 medium52 medium53 medium54 medium55 medium56 medium57 medium58 medium59 medium60 rb.config add "Hard Bases" hard1 hard2 hard3 hard4 hard5 hard6 hard7 hard8 hard9 hard10 rb.config add "Hard Bases" hard11 hard12 hard13 hard14 hard15 hard16 hard17 hard18 hard19 hard20 rb.config add "Hard Bases" hard21 hard22 hard23 hard24 hard25 hard26 hard27 hard28 hard29 hard30 rb.config add "Expert Bases" expert1 expert2 expert3 expert4 expert5 expert6 expert7 expert8 expert9 expert10 rb.config add "Expert Bases" expert11 expert12 expert13 expert14 expert15 expert16 expert17 expert18 expert19 expert20 rb.config add "Expert Bases" expert21 expert22 expert23 expert24 expert25 expert26 expert27 expert28 expert29 expert30 rb.config add "Nightmare Bases" nightmare1 nightmare2 nightmare3 nightmare4 nightmare5 nightmare6 nightmare7 nightmare8 nightmare9 nightmare10 rb.config add "Nightmare Bases" nightmare11 nightmare12 nightmare13 nightmare14 nightmare15 nightmare16 nightmare17 nightmare18 nightmare19 nightmare20 rb.config add "Nightmare Bases" nightmare21 nightmare22 nightmare23 nightmare24 nightmare25 nightmare26 nightmare27 nightmare28 nightmare29 nightmare30   You will see photos only with 5 bases per Difficulty, beacause I am aware of people stealing my designs. In the pack you will se a file named: RaidableBases_Testing_cfg (this is another config for the pack, that makes the bases to spawn without any cooldown, while the main configuration in  the pack makes the bases to spawn between 30 min up to 1h 30 mins) 🛡️ Optimized NPCs The number of NPCs is fully optimized for each difficulty tier. You can find and tweak these balanced guard configurations inside the Profiles/ folder! A Note From Me 👋 Hello and welcome! I’ve put my heart and countless hours into creating this professional, 100% plug-and-play pack. Everything was built by me from absolute scratch on my local server. I am incredibly proud of it, especially the loot tables—honestly, you won't find a better-balanced reward system out there! Why only $30? A massive pack like this usually costs around $70–$80. But as a former server owner myself, I know how hard and expensive it is to find high-quality setups that don't break the bank. I wanted to give back and support the Rust community with a top-tier pack at an affordable price. ⭐ Support the Work If you love this pack, please consider leaving a 5-star review! Your feedback means the world to me and motivates me to keep building and improving the configurations for you! Thank you for your support, and happy raiding! 🚀

XDQuest: A comprehensive and customizable quest system for your RUST server! XDQuest is a powerful and flexible plugin that introduces a comprehensive and dynamic quest system into your game world. With 31 different types of missions available for players, the possibilities are almost limitless. Players receive various rewards for completing missions, adding even more incentive to accomplish tasks. At the moment, this is the largest and only quest system available! XDQuest is your key to creating endless adventures in the world of RUST. List of features: (The description briefly outlines the functionality and includes screenshots.) Interactive website for creating quests: XDQuest-Creater - On my website, you can easily and quickly create quests. Forget about manually editing JSON files — my user-friendly interface will make the quest creation process simple and enjoyable! The plugin offers four types of rewards: Items Blueprints Custom items Commands It integrates perfectly with various economic systems, and also supports Skill Tree and ZLevels. List of missions Mission setup Reward setup Detailed instructions and settings on the website: XDQuest-Creater - My website features clear and informative instructions that will help you configure the plugin and master all types of missions. You will gain access to it immediately after purchasing the plugin. Discover the simplest and most effective way to configure using my guide! Beautiful and modern UI: The stylish and intuitive interface makes using XDQuest simple and enjoyable. There is a mini-quest list that allows your players to remotely track the progress of their missions. UI UI Mini quest list Example of UI customization (Rusty Wasteland PvE) Capabilities and NPC settings: NPCs have their own voice-overs; currently, they can respond to the user on 4 triggers: 1.Greetings 2.Farewells 3.Task acceptance 4.Task completion You can also upload and use your own sounds for any of these 4 triggers, and the website will assist you with this as well. Dress your NPC however you like and create a unique appearance for them. There is an option to change the location of the NPC. Your NPC resides in a unique dwelling created in accordance with their character and backstory. Available types of missions: Currently, there are 24 different types of tasks available: (The types of missions are constantly being updated) (16 pre-set quests included) Command: Chat commands: /quest.saveposition - saves a custom position (available only to administrators). /quest.saveposition.outpost - saves a custom position within the bounds of a peaceful town (available only to administrators). /quest.tphouse - teleport to a building (available only to administrators). Console commands: xdquest.stat - publishes statistics. xdquest.player.reset [steamid64] - Clears all of a player's missions and everything associated with them. Configuration: Discord  -  DezLife Website editor  -  xdquest.skyplugins.ru

Gather & loot rates Rates that belong to the player, not to the server Server-wide multipliers give everyone the same wipe. This plugin attaches rates to permissions instead: a default tier, a VIP tier, as many tiers as you sell. Every gather source is covered — nodes, quarries, the excavator, the metal detector, farming, tea, even NPC corpses — and every loot container is multiplied per item category, or per exact item. All of it edited in a UI, applied the moment you type the number. 14 Item categories, each with its own rate 7 Production sources with their own multiplier 4 Fields on every per-item override 0 Dependencies ✓ Unlimited permission tiers — a different wipe for every rank you sell ✓ Every source, not just trees and nodes — quarries, excavator, metal detector, farming, tea, NPC corpses ✓ Guaranteed drops per item — "always 5 scrap, 10% chance of 20" without touching a loot table ✓ Loot and junk pile respawn speed — separately, live, no map restart ✓ Edited in-game — type a number, it's live and saved   01 — Tiers One server, as many rate sets as you sell A tier is a permission plus a full set of rates. Two come preconfigured — a 2x/3x default and a 3x/5x VIP — and you add as many as your shop needs. No permission, no change Players outside every tier play vanilla rates, untouched. Nothing is applied server-wide, so you can run the plugin on a 1x server and sell 2x as a rank. Stack tiers, or don't By default a player with several tiers gets one of them. Flip a single switch and every rate they hold is summed instead — so a booster permission can add on top of a rank rather than replace it. Everything from one screen Page through your tiers with two arrows. Global rates, every production source, all 14 categories and the per-item list are on the same screen, each an input field. Type a value and it's active and written to the config — no reload, no o.reload, no file editing.   02 — Loot Containers that pay what you decide Barrels, crates, elite crates, hackable crates, supply drops — anything with loot in it goes through a global rate multiplied by the rate of that item's category. 14 categories, 14 dials Triple the components but leave weapons alone. Halve ammunition while resources stay at 5x. Weapons, construction, items, resources, attire, tools, medical, food, ammunition, traps, misc, components, electrical and fun each carry their own multiplier on top of the global one. NPC corpses count the killer Scientists, tunnel dwellers and every other NPC drop loot scaled to the rates of whoever killed them — tracked from the kill to the corpse, so a VIP's kill pays VIP rates even if someone else opens the body. Shot open or opened by hand Barrels broken with a rock and crates opened normally both go through the same multipliers, credited to the player who did it — and each container is processed exactly once, never twice. Respawn speed, live Two multipliers — one for junk piles, one for crates and barrels — and the world's spawn timers are rebuilt the moment you change them. No wipe, no restart, and the vanilla values are put back when the plugin unloads. An exclusion list for the things you don't touch Name a container prefab and it stays vanilla — useful for event crates and custom loot that another plugin already fills.   03 — Gathering Every way a player earns a resource Most rate plugins stop at trees and ore. This one follows the resource wherever it comes from, and gives the slow, expensive sources their own multiplier on top. Nodes, trees and the finishing bonus Every hit, the bonus for finishing a node, and the leftovers that spill when it breaks — all three are scaled, so the numbers stay consistent instead of the bonus quietly staying at 1x. Quarries and the excavator pay their operator A mining quarry, a survey-charge pump jack and the Giant Excavator each have their own production multiplier — and the output is scaled by the rates of the player who switched it on, not by a server-wide number. Jackhammer, chainsaw and the metal detector Power tools get a multiplier of their own, so you can make them worth their fuel — or deliberately not. Metal-detector digs are boosted too, which almost nothing else covers. Tea strength as a rate The tea multiplier scales the effect value of the tea itself, not the number of leaves. A VIP's ore tea simply works harder than everyone else's. Farming and hand-picked resources Harvested plants and everything picked up off the ground — hemp, mushrooms, corn, wood piles — run through the same rates as everything else.   04 — Per item One item out of step with the rest Category rates handle the broad strokes. When a single item needs its own rule, it overrides everything above it. Its own multiplier, ignoring everything else Run resources at 10x and keep sulfur at 2x. An item with an override takes its own number and nothing else — no compounding surprises. Guaranteed amounts with a jackpot chance For loot, set a minimum and a maximum with a percentage chance for the big one. Every barrel gives exactly 5 scrap, and 10% of them give 20 — a flat, predictable economy you can actually price your shop against. Added by clicking an icon The picker filters by all 15 categories and searches display names and shortnames as you type. Click an item to add it, type its rate under the icon, click the red cross to drop it. Long lists paginate at 29 per page.   Reliability Built to be left alone ✓ No dependencies — nothing to install alongside it ✓ Vanilla respawn timings are restored on unload — the plugin remembers what they were before it touched them ✓ Every UI change is written to the config immediately — a crash can't lose the tier you just built ✓ A bad shortname tells you in chat instead of failing silently or throwing errors into console ✓ Respawn boosting is opt-in — off by default, with the safe range stated in the config   Command & permissions One command, and the tiers you invent The command name and the setup permission are both configurable. Admins have access regardless. /rs Open the rate editor gatherlootmultiplier.setup Access to the editor gatherlootmultiplier.default Preconfigured tier — 2x loot, 3x gather gatherlootmultiplier.vip Preconfigured tier — 3x loot, 5x gather. Rename both, or add ten more   Questions Before you buy What happens to players with no permission? Nothing at all — they get vanilla rates. That's the point: grant the default tier to the default group for a server-wide rate, or keep it for ranks only. A player has two tiers. Which one wins? The one further down the config list — so keep your tiers in ascending order and the highest rank ends up last. Alternatively, turn on rate summing and every tier they hold is added together instead. Do I have to restart or reload after changing a rate? No. Values from the UI take effect immediately and are saved to the config as you type them. Even loot respawn timing is rebuilt live. Whose rates apply to a quarry or the excavator? The player who switched it on. A VIP's quarry produces at VIP rates while it runs. Can I make a resource drop a fixed amount instead of a multiplied one? Yes, for loot: give the item a minimum, an optional maximum and a chance for the maximum. The multiplier is then ignored for that item and the amount is rolled between the two. Is faster loot respawn safe for my server? It's off by default and it scales the game's own spawn timings rather than spawning extra entities. Stay near the suggested values — extremely low numbers mean more entities alive at once, which costs frames on any server. Will it fight with my other loot plugin? Add that plugin's container prefabs to the ignore list and they pass through untouched.

Server HUD  ·  Rust  ·  Oxide  ·  CARBON Your chat is «is heli up?» twelve times an hour Put the answer on screen. Online count, clock, grid square, balance, and a live bar of every event running — Bradley, heli, cargo, airdrop, both oil rigs. Nine events out of the box, set up entirely from a panel in game.   How it goes From install to the event you added yourself MINUTE ONE Install and it's on screen It doesn't wait for the next wipe to be useful Install mid-wipe and the heli that's already flying is on the bar. ImageLibrary is the only other plugin you need. Nine events on by default. Bradley, Patrol Heli, CH47, Cargo Ship, Airdrop, Harbor cargo, both Oil Rigs, Deep Sea. Rigs turn red while the crate is being hacked. Players see the fight starting from across the map. Icons are just URLs. Fetched and cached for you. First install reloads once to pick them up — expected, not a fault. No file to edit first. Defaults draw a finished HUD with your server name in it. FROM THEN ON Every player, every day The numbers your chat keeps asking for Updated as they change. A player standing still costs you nothing. K12    or    X:-1204   Z:842 Grid square or raw coordinates. Your choice, your colour. Online, sleeping, queue. Admins can be left out of the count. Clock in each player's own format. 12- or 24-hour from their game language, or force one. Two balances, side by side. Economics, ServerRewards or ShoppyStock. Only what's live. One switch hides idle events instead of showing a wall of grey. Info messages on rotation. A random line from your list, any corner, any width. IN THE WAY The player decides Four states, and the choice is remembered Your logo is the button: full panel → events only → hidden. One command removes it entirely. Still set that way after a reconnect. Streamers keep coordinates off camera. One permission drops the position readout. CCTV and drones get a clean screen. Hides on mount, back on dismount, switchable. Any corner, any scale. Pixel offsets, one scale value, and a toggle to show it over the inventory. MONTHS LATER All of it, from in game The config file is optional One command opens an admin panel over every setting there is. Change it, it saves, everyone online sees it. Events from other plugins. A name, an icon, and the hooks it fires. Convoy, Sputnik, Armored Train and Harbor come pre-filled. Adding one rewrites a marked block in the plugin file and reloads it. A drop-down of command buttons. Any chat or console command, own icon, own permission, closes itself after use. Updates don't reset your settings. New events land with defaults; a section you deleted comes back. Or edit the file. Auto reload picks it up the moment you save.   The look See it running, then make it yours Every icon is a URL in the config. Take a pack, or draw your own from the blank template.       Free custom HUD icons Free   Custom HUD icons Paid   Server HUD custom icon pack Paid   While you're not looking Built to be left alone ✓  A typo in the config won't take the HUD down — it falls back to defaults and says so   ✓  Switching a counter off stops the work behind it, not just the display ✓  An economy you enabled but never installed shows 0, and the HUD carries on   ✓  Unloading clears every panel off every screen — nothing stuck until relog   Reference One chat command, five words after it Setup is admins only. Menu buttons take whatever permission you name in the config. Chat /h Show the command list Chat /h open Full panel — counters, clock, position, balance, events Chat /h events Event bar only Chat /h hide Hide the panels, keep the logo button Chat /h close Remove it entirely Chat /h setup Settings panel — admins only Perm hud.streamer Hides the position readout from whoever holds it Hook object CanHudChangeState(BasePlayer player, string currentState, string nextState) Fires before a state change. Return non-null to stop it. API string API_PlayerHudState(string playerId) Returns full, events, hidden or closed for a player.   Straight answers Asked before buying Can players turn it off? Full panel, event bar only, or gone entirely — their choice, and it survives a reconnect.   Do I have to edit the config file? No, the in-game panel covers all of it. If you prefer a text editor, auto reload picks the file up as you save. I stream — my coordinates are on screen. Grant yourself the streamer permission. The position readout goes, everything else stays.   Can I add an event from another plugin? Yes — name it, give it an icon, and name the hooks it fires. Most plugins list those in their own description. What if I run no economy plugin? Leave it off and the HUD closes the gap. Enable it without the plugin and you get a 0, not a broken HUD.   Does it block CCTV and drones? It hides itself in a Computer Station and comes back on dismount. One toggle if you'd rather it stayed.   9 events out of the box 4 states, chosen per player 2 economy balances at once 1 dependency — ImageLibrary