pineapple

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