SoftArmy's Wishlist

Create fully automated raidable bases with NPCs in Rust
NOT compatible with server.pve when set to true. Use a PVE plugin like TruePVE if you want PVE protection.

This is the premium version of Raidable Bases. The differences between this and the free version are too many to list. A few key differences are: five (5) difficulties and associated loot table functionality instead of one (1), buyable events, lockouts for players. Requires latest version of CopyPaste. This plugin does NOT come with any bases. Packages are sold separately that include bases. Check out my packages for this plugin for tier1, tier2, and tier3 which contain everything you need to get the plugin working in minutes with all bases and loot already configured for you! Packages are sold separately.
📄Facepunch TOS
Disclaimer: The Facepunch Terms of Service have been updated to explicitly prohibit servers from enabling players to access Facepunch-approved DLC content or cosmetic skins through any method other than those officially provided by vanilla Rust (e.g., legitimate crafting or ownership-based unlocking mechanisms).
This plugin includes built-in configuration options—enabled by default—that are designed to assist servers in maintaining compliance with this policy.
Modification, disabling, or circumvention of these safeguards may place the server in breach of Facepunch's Terms of Service. By using this plugin, server operators acknowledge and accept full responsibility for any alterations made to its configuration, and the developer assumes no liability for any misuse, policy violations, or enforcement actions resulting therefrom.
You should independently ensure that any prohibited content—such as unauthorized DLC items or restricted skins—is removed from your server files. Do not rely solely on this plugin or any third-party tool for compliance. The developer assumes no liability for servers found in violation due to misconfiguration, oversight, or failure to remove such content manually.
You can add unapproved (non-paid) skins manually to your ImportedWorkshopSkins.json file found in the Profiles directory, which has an example provided already. 
Profiles in Oxide are located in the folder: oxide/data/RaidableBases/Profiles
Profiles in Carbon are located in the folder: carbon/data/RaidableBases/Profiles
ninco90 has created a tool to help with this. At the time of this posting, he’s still actively working on this, so please be patient while he fixes issues with it.
https://app.rustspain.com/facepunch/checkitems
📄RBE DEBUG
This command exists to aid with issues regarding your configuration, profiles and/or map by displaying information, both good and bad, related to finding spawn points and spawning of bases. It is your responsibility to use this command before asking for help.
📄Loot Table Editor by @beee😎
https://codefling.com/tools/raidable-bases-loot-table-editor
 heya, I can't say without your config file.
TL;DR, it's likely your config as your map has an abundance of available spawn points given how flat some of the areas on your map are. you've likely changed the biome settings, or have forced everything elsewhere.
📄Map Terrain and it's importance with this plugin (maps must be designed appropriately for use with this plugin)
Flat terrain only:
I do not support spawning bases on bumpy terrain—design them on flat terrain only. Fortify on Steam is perfect for this, and there are plenty of bases available there. Be careful when downloading bases from ANY source: vet them first, and remember that bases are not all designed equally. Stability can be shaky in some, causing them to crumble as they paste in. Inventories may contain items the designer forgot to remove. Worst of all, some bases aren’t copied properly from their centermost foundation—copying at the wrong height can make them spawn below the map or way above it. If you look at the ground, paste it in, and it appears elsewhere, it was not copied properly. Recopy it—don’t rely on ANY height settings in profiles! Those settings are for MINOR adjustments, not for bases that got yeeted halfway around the world. If the plugin is ignoring terrain, it's usually due to one of three reasons:
The terrain is not flat enough for bases to spawn on- bases should be designed on unobstructed flat and equal terrain. You've modified a setting in your config or profiles, use compare in Notepad++ or diff on the default config file, and your config file, and see what changes are different. This is the EASIEST way to see what you've changed! The spawn point is blocked by a visible or invisible entity. Just because you can't see it does not mean it's not there. RBE DEBUG (see documentation) exists solely so you can spot issues like this on-the-fly. Understand that debug contains GOOD and BAD information, use your common sense to narrow it down weighing the highest number occurrences of BAD debug at the most likely causes. Easier than it sounds. No worries. If your map’s terrain is bad, you’ve still got options: the beach, the water, or custom spawn points. Shagadelic, baby. Custom spawn points
Spawns Database plugin
Create spawn points yourself, and put the name of the file (e.g: nivexspawnpoints10 - note that .json is NOT appended to the end of the filename, do not append it, using the filename without its path or extension as I've shown) in your config OR profile (not both, highly recommend profile only). Allow Raid Bases On Beaches
in the config, not the profiles. This is for the beach and all beach terrain under the water within its vicinity, usually a very short distance out from the shore. Water Settings - In the profiles, not the config. Highly recommended: Water is abundant in the ocean, surprise! Enable within your profiles, force them on top of the waters surface. Highly recommended for maps with bad terrain.
Allow Bases To Float Above Water: true
Chance For Underwater Bases To Spawn: 100
Spawn On The Surface Of Water: true
Ignore Land Level On Seabed: true
Prevent Bases From Floating Above Water By Also Checking Surrounding Area: false
Maximum Water Depth Level Used For Float Above Water Option: 1
Minimum Water Depth Level Used For Seabed Option: -20 (negative twenty, forcing the spawn points AWAY from the shoreline) Keep these settings enabled (true), knowing that changing them can and will break the plugin depending on the maps you use. Some maps may embrace these changes, while others will feel like a distant echo—terrain reduced to nothing, the memory abandoned entirely, lost to the abyss for all eternity. Just kidding—use the damn water settings and quit pouting. Bad spawns are notoriously brutal on custom maps.
Allow Raid Bases On Beaches Allow Raid Bases Inland Allow Raid Bases On Building Topology Enable (true) these settings if you're in desperate need of more spawn points:
Allow Raid Bases On Roads Allow Raid Bases On Rivers Do not use these options if you have high traffic on railroads
Allow Raid Bases On Railroads Do not modify Allow Raid Bases In Biomes without understanding that disable a biome will prevent all bases from spawning within that biome!
Allow Raid Bases In Biomes
Arctic: true
Arid: true
Temperate: true
Tundra: true or false
Jungle: true or false Last but not least, the most important of them all for anyone not using custom spawn points from Spawns Database plugin (see documentation):
The number of potential spawn points is displayed when the grid loads. First, the plugin must initialize, then it generates potential spawn points across your map. Once this process is complete—usually within a few minutes—it will output the results to your server console.
If potential points are under 1000, the map has poor terrain, or you’ve disabled too many options in the config. If potential points are above 1500, you’ll have a reliable amount of spawns. This number will naturally decline as players build more bases on the server. If potential points are above 2500 but nothing spawns, your config and/or profiles are set up incorrectly. Read the documentation. Do not disable biome options in the config. Doing so blocks all spawns in those biomes.  
📄There are just a few steps required to get bases spawn on your server within minutes (3 minutes for experts, 30 minutes for a novice, and 60 to 120 minutes for beginners. Total time to configure the plugin beyond these steps is infinite, you'll never stop making changes so long as you continue building your base catalog into a massive collection of artwork).
👉 You must have the CopyPaste plugin installed. (Disclaimer: Configuring this to your servers specific needs will require a lot of time and effort) 👈
Step 1: Obtain Your Bases
You can get bases by:
Downloading them from Fortify Purchasing a tier package from me Buying a base package from third-party sellers (be wary that some sellers include items in their CopyPaste files!) Creating your own bases Step 2: Set Up Profiles
Profiles are located in:
oxide/data/RaidableBases/Profiles/ carbon/data/RaidableBases/Profiles/ There are five different profiles. You can add the filenames of your CopyPaste bases manually, or by using the command:
For example (You must use straight double quotes. Curly double quotes are not supported!):
Step 3: Edit the Configuration
The configuration file is located in:
oxide/config/RaidableBases.json carbon/configs/RaidableBases.json Make the following changes:
Always Maintain Max Events: Set this to true. Max Maintained Events: Set this to the number of bases you want to spawn. Minimum Required Players Online: If you want bases to spawn even when no players are online, set this to 0. Step 4: Save and Reload
After making your changes:
Save your files. Reload the plugin. The bases will now start spawning automatically. They will use the Default Loot table, located in:
oxide/data/RaidableBases/Default_Loot.json carbon/data/RaidableBases/Default_Loot.json Step 5: Customize Loot Tables
Refer to the documentation to learn how to set up your own custom loot tables.
Additional Information
If you want buyable events using the /buyraid command, you can set a cost under the Buyable Event Costs section. This includes:
Economics Buy Raid Costs ServerRewards Buy Raid Costs Custom Buy Raid Costs Tips for Customizing Your Setup
The plugin has many settings to customize. No guide can cover everything, so you will need to go through each setting and adjust it to meet your server’s needs.
Important:
Make backups as you configure the settings. Don’t rush—take it one step at a time. 📄Dynamic difficulties (added in 3.0.0):
Easily add or remove your own difficulties.
You should reload the plugin whenever you make changes!
Add a difficulty:  
rb.difficulty add "Sky" This will create the profile "Sky Bases.json" and set the difficulty to "Sky" rb.config add "Sky Bases" sky1 sky2 sky3 sky4 sky5 Reload the plugin! This will create language messages in the EN and RU language files which you can copy to other language files.   If your messages do not update after a reload then you must restart your Rust server to reset Oxide cache. This will create all relevant settings for "Sky" within the config file where you must set them all as desired You need your own copypaste files and loot tables using their new respective names. Base Loot folder - add a loot table with the filename "Sky Bases.json" to match the profile name. Difficulty Loot folder - add a loot table with the filename "Sky.json" to match the difficulty name. Remove a difficulty:  
rb.difficulty remove "Sky" This will remove all settings for this difficulty from the config file - and disable the profile - only. No files are deleted! Edit or change a difficulty name:  
This is not supported and will not be - some hosts restrict System.File.IO namespace Please avoid trying to do this unless you are an expert user - you must rename EVERYTHING yourself Configuration errors are shown in rcon when the plugin loads If you make a mistake, you can use the add command a second time which will re-add any missing settings. ❤️  ❤️❤️ If you feel overwhelmed or frustrated, take a break and return to it later. I am always here to answer your questions and help you (even if it takes some hours for me to respond). ❤️❤️❤️
📄Tutorial

This is not your run-of-the-mill plugin. DO NOT INSTALL WITHOUT READING THIS DOCUMENTATION FIRST. This plugin is extremely advanced and requires utmost attention to detail to configure properly. Jumping around in the configuration file or profiles will lead to more problems than it's worth. Take your time to understand each option before enabling or disabling its functionality.
Raidable Bases is an independent expansion of Dangerous Treasures. You may learn how to enable the expansion mode below. It does not require Dangerous Treasures for any other purpose.
Configuration
🔧Loot Tables
The plugin comes with some very basic items (Default_Loot.json) that only serve as a demo loot list for you to either delete or expand upon. In order to make any use of the plugin (beyond demonstration) you will have to create your own loot lists instead.
It will take a very long time to configure your loot tables, and fine-tune each to your specific needs. To start, I recommend that you use the rb.populate all command. This creates files in the Editable_Lists folder for each difficulty that contain every item in the game. Edit each file and set the amounts for the items that you want to spawn, and remove those that you do not want to spawn. It may look intimidating editing a list of 660 items, but don't underestimate how easy it is to delete items from a list compared to adding each one manually.
Items that have their amount AND amountMin set to 0 will not spawn. So you may either delete these items from the list, or come back to them later. If you set amountMin to 0 then chance will determine if the item spawns or not, and another item will not replace it unless there are extra items available (as of 1.7.3).
You can set the item skin that you want to use, but I suggest using the Skins settings in the configuration file to use random skins, or none at all.
The rb.populate command which populates the Editable_Lists folder also includes items already inside of your Difficulty_Loot folder. This allows you to easily repopulate lists in order to re-evaluate which items spawn at a later date.
Files inside of the Editable_Lists folder must be copied into an existing loot file in order to use the loot table. As the name implies, it is for editing only.
- If you want to use Editable_Lists/Easy.json for your Easy bases then copy the contents of the file into the Difficulty_Loot/Easy.json file.
- If you want to use Editable_Lists/Expert.json for the Expert Bases.json profile, then you must copy the contents of the Expert.json file into the Bases_Loot/Expert Bases.json file
probability - the chance that the item can spawn. value must be between 0.0 and 1.0 where 1.0 is 100% chance

🔧Loot Priority
Loot is pulled from all datafiles within the oxide/data/RaidableBases/ folder with the exception of the Profiles folder which is used to configure bases.
oxide/data/RaidableBases/Base Loot - If a loot table exists in this folder with the same name as a profile then all of the bases in that profile will use this loot table. If you want items in this loot table to always spawn then you must enable Always Spawn Base Loot Table in the respective profile.
oxide/data/RaidableBases/Difficulty Loot - Items will be chosen from these files based on the difficulty of each profile.
If Use Day Of Week Loot is enabled then it will choose the loot table for that specific day. Otherwise, it will pick from Default_Loot.json. This is the default list, and is only used when all other loot tables do not have a sufficient amount of loot to spawn based on the Amount Of Items To Spawn setting.

🔧Loot Settings
Block paid and restricted content to comply with Facepunch TOS (true) – removes paid content on NPC death, prevents pickup of DLC/paid deployables, resets skins on pickup, and blocks paid loot in boxes. Future update may allow pickup for content owners. Allow Duplicate Items - This is useful when you do not have enough items in your loot tables , and you want to spawn Amount Of Items To Spawn by using the same items more than once. Amount Of Items To Spawn - This is the number of items that you want to spawn. If you do not have enough items in your loot tables then it will only spawn the amount that you have available. It will not spawn items if the container does not have enough space. Drop Tool Cupboard Loot After Raid Is Completed (false) Divide Loot Into All Containers - This allows you to divide loot evenly from all of your loot lists into all containers when enabled. You MUST increase or decrease Amount Of Items To Spawn respective to how many items you want in each container. This includes large boxes, small boxes, coffins and storage barrels. Optional settings include (in order of priority) cupboard, bbq, oven, fridge and lockers. Allow Players To Pickup Deployables (false) - As name implies, overridden by Entities Not Allowed To Be Picked Up Allow Players To Deploy A Cupboard (true) - Block players from placing a TC after destroying the TC in the base. Drop Container Loot X Seconds After It Is Looted (false) - Prevent players from cherry picking items and leaving the rest, in order to despawn the raid quicker. Drop Container Loot Applies Only To Boxes And Cupboards (true) - As name implies Empty All Containers Before Spawning Loot (true) - Useful if using CopyPaste files that contain loot already - I suggest leaving this true as it can complicate how many items spawn if there are too few inventory slots remaining. Ignore Containers That Spawn With Loot Already (false) - Useful if you want specific loot to spawn from a copypaste file. Require Cupboard Access To Loot (false) - Prevent all players from looting until they reach the TC, or destroy it. Skip Treasure Loot And Use Loot In Base Only (false)" - Useful if you want all loot to spawn from a copypaste file - not recommended - will allow players to memorize which boxes to raid and ignore the rest. Always Spawn Base Loot Table (false) - Very useful if you want items in the Base_Loot file to always spawn (such as C4, rockets, ammo, etc) 🔧 Advanced Loot Configuration
📦 Loot Behavior in Tool Cupboards
Stacked Items Combine
Items that spawn into the Tool Cupboard (TC) automatically combine into single stacks. For example, two separate 500-stone stacks will merge into one 1,000-stone stack.
This is reflected in the Status UI. TC Always Counts Toward Remaining Loot In Status UI
The contents of the TC are always included in the loot remaining total shown in the Status UI — even if looting the TC is not required for event completion. There is no reason players should not be aware of the TC amount. Making the TC a Requirement
By default, players do not need to loot the TC to complete the raid.
To require TC and boxes to be looted before the event can be completed, enable:
Require Cupboard To Be Looted Before Completion
To require only the TC to be looted before the event can be completed, enable:
Destroying The Cupboard Completes The Raid ⚙️ Stack Size Options
Stack-Split Items Reduce Remaining Loot
When using stack size options, the split stacks are counted individually, which reduces the number of remaining items needed to meet the Amount Of Items To Spawn requirement.
Optional Setting To Change This Behavior:
Amount Of Items To Spawn Increased By Item Splits
When enabled, one item will still count as one, even if it becomes split into multiple smaller stacks. An option exists in the configuration file for all items: 
Use Stack Size Limit For Spawning Items An option exists in the loot tables for each individual item, and will override the above option: 
stacksize 📦 Additional Containers
Only TC and Boxes are counted in the Status UI by default
Other containers (e.g., furnaces, lockers) are not included in the remaining loot count by default.
To include others, add the prefab short name (not item shortname) found with /tpve_prod to: Additional Containers To Include As Boxes Settings
Blacklisted Commands (none) - prevents players from using these commands inside of a raid base Automatically Teleport Admins To Their Map Marker Positions (true) - right-click map to teleport (requires raidablebases.mapteleport permission) Block Wizardry Plugin At Events (false) - Block players from using wands Chat Steam64ID (0) - The steam profile icon to show in chat messages Expansion Mode (Dangerous Treasures) (false) - Allow Dangerous Treasures to take over a random box for its event Remove Admins From Raiders List (false) - Allows admins to help players without receiving any rewards Show X Z Coordinates (false) - Show X Z coordinates alongside grid location Buy Raid Command (buyraid) - Opens the buyable UI to purchase raids for each difficulty Event Command (rbe) - Specify command name Hunter Command (rb) - Specify command name Server Console Command (rbevent) - Specify command name Remove Paid Content Command - Name is generated randomly on load. This command will edit your loot tables and all copypaste files. Backup your files before using this command. The edit will remove any restricted content from these files. Block paid and restricted content to comply with Facepunch TOS (true) – removes paid content on NPC death, prevents pickup of DLC/paid deployables, resets skins on pickup, and blocks paid loot in boxes. Future update may allow pickup for content owners.
Raid Management
Allow Teleport (false) - Allow/prevent players from teleporting Allow Cupboard Loot To Drop (true) - Allows loot to drop when TC is destroyed by a player Allow Players To Build (true) Allow Players To Use Ladders (true) Allow Players To Deploy Barricades (true) Allow Players To Upgrade Event Buildings (false) - Prevent players from upgrading buildings with no TC to prevent this otherwise Allow Player Bags To Be Lootable At PVP Bases (true) - Bypasses Prevent Looting plugin Allow Player Bags To Be Lootable At PVE Bases (true) - Bypasses Prevent Looting plugin Allow Traps To Drop Loot (false) - Allow traps such as guntraps and turrets to drop loot on death Allow Players To Loot Traps (false) - Allows players to loot traps such as guntrap and turrets with TC access Allow Raid Bases On Roads (true) Allow Raid Bases On Rivers (true) Allow Raid Bases On Building Topology (true) - Specifically added for custom map makers Allow Vending Machines To Broadcast (false) - Prevents vending machines from showing on the map Allow Bases To Float Above Water (false) - Keyword: FLOAT Allow Bases To Spawn On The Seabed (false) Prevent Bases From Floating Above Water By Also Checking Surrounding Area (false) - Keyword: FLOAT Maximum Water Depth Level Used For Float Above Water Option (1.0) - Keyword: FLOAT, but allows you to prevent on water if the value is low enough Backpacks Can Be Opened At PVE Bases (true) Backpacks Can Be Opened At PVP Bases (true) Backpacks Drop At PVE Bases (false) - Will drop a backpack on death, even if explicity disabled in Backpack configuration (requires Backpacks 3.4.0 ) Backpacks Drop At PVP Bases (false) Block Mounted Damage To Bases And Players (false) - Prevent players from dealing damage while on mini, scrap heli, etc Block RestoreUponDeath Plugin For PVP Bases (false) Block RestoreUponDeath Plugin For PVE Bases (false) Bypass Lock Treasure To First Attacker For PVE Bases (false) - Do not set an owner for PVE bases Bypass Lock Treasure To First Attacker For PVP Bases (false) - Do not set an owner for PVP bases Despawn Spawned Mounts (true) - Allows mounts such as mini or scrap heli to remain if not abandoned when raid despawns Do Not Destroy Player Built Deployables (true) - Loot is not lost if the plugin destroys a player's box with this option - it is dropped on the ground in a grey loot container just as if they destroyed the box themselves Do Not Destroy Player Built Structures (true) Divide Rewards Among All Raiders (true) Draw Corpse Time (Seconds) (300.0) - The amount of time the players corpse location is drawn on their screen Eject Sleepers Before Spawning Base (true) Extra Distance To Spawn From Monuments (0.0) Flame Turrets Ignore NPCs (false) - Can help with performance on some servers Maximum Land Level (2.5) - The allowed height of the surrounding terrain for spawning bases (this should never be changed) Move Cookables Into Ovens (true) Move Food Into BBQ Or Fridge (true) Move Resources Into Tool Cupboard (true) Move Items Into Lockers (true) Lock Treasure To First Attacker (true) - Sets the first attacker as the owner of a raid. You must set eject enemies settings in each profile if you do not want players entering private raids Lock Treasure Max Inactive Time (Minutes) (20.0) - Resets the raid as public after this time Assign Lockout When Lock Treasure Max Inactive Time Expires (false) - useful those who partially raid bases in order to avoid the lockout timer Lock Players To Raid Base After Entering Zone (false) - Forces players to be locked to a raid once they enter it, even on accident Only Award First Attacker and Allies (false) Minutes Until Despawn After Looting (min 1) (15) - The time until the base despawns after being raided Minutes Until Despawn After Inactive (0 = disabled) (45) - The time until the base despawns after being inactive Minutes Until Despawn After Inactive Resets When Damaged (true) - Resets the time until the base despawns when it is damaged by a player Mounts Can Take Damage From Players (false) Mounts Can Take Damage From SamSites (true) Player Cupboard Detection Radius (100.0) - Extra layer of protection to prevent raid bases from spawning too closely to player bases (this should never be under 100 and never too high either, 100-200 at most) Players With PVP Delay Can Damage Anything Inside Zone (false) - Applies specifically to PVP raid bases Players With PVP Delay Can Damage Other Players With PVP Delay Anywhere (false) PVP Delay Between Zone Hopping (10.0) - The amount of time players can take damage while on a PVE server after stepping outside of a PVP zone - prevents exploiting - recommended value: 120 Prevent Fire From Spreading (true) - Helps with server performance by preventing forest fires, err, fire from spreading after initial spawn Prevent Players From Hogging Raids (true) - Prevents players from tagging multiple raids at once Require Cupboard To Be Looted Before Despawning (false) Destroying The Cupboard Completes The Raid (false) Require All Bases To Spawn Before Respawning An Existing Base (false) - Rotate through all bases specific to each difficulty before reusing an existing base Turn Lights On At Night (true) Turn Lights On Indefinitely (false) Traps And Turrets Ignore Users Using NOCLIP (false) Use Random Codes On Code Locks (true) Wait To Start Despawn Timer When Base Takes Damage From Player (false) - Prevents the inactive despawn timer from starting until it is damaged by a player. Combos well when inactive resets is disabled by giving players a limited time to finish a raid once they start it Additional Containers To Include As Boxes (none) - example: vendingmachine
Eject Mounts
Boats (false) - Set any true to prevent them from entering a raid base Cars (Basic) (false) Cars (Modular) (false) Campers (true) Chinook (false) Flying Carpet (false) Horses (false) HotAirBalloon (true) MiniCopters (false) Pianos (true) Scrap Transport Helicopters (false) All Other Mounts (false) All Controlled Mounts (false) - Mounts controlled via another plugin Max Amount Of Players Allowed To Enter Each Difficulty (0 = infinite, -1 = none) (infinite)
Easy Difficulty => Amount (0) Medium Difficulty => Amount (0) Hard Difficulty => Amount (0) Expert Difficulty => Amount (0) Nightmare Difficulty => Amount (0)
Max Amount Allowed To Automatically Spawn Per Difficulty (0 = infinite) -1 = disabled)
Easy (0) - Specifies how many of each difficulty can be spawned at any given time Medium (0) Hard (0) Expert (0) Nightmare (0)  
Player Lockouts (0 = ignore) - this is for PUBLIC raids where buyable events use the Buyable Cooldowns and these are not shared - players may still do 1 public and 1 buyable event if these are both enabled
Time Between Raids In Minutes (Easy) (0.0) - Set a cooldown before the player can enter another raid base Time Between Raids In Minutes (Medium) (0.0) Time Between Raids In Minutes (Hard) (0.0) Time Between Raids In Minutes (Expert) (0.0) Time Between Raids In Minutes (Nightmare) (0.0) Block Clans From Owning More Than One Raid (false) - Prevent clans from hogging multiple raid bases Block Friends From Owning More Than One Raid (false) Block Teams From Owning More Than One Raid (false)
Easy|Medium|Hard|Expert|Nightmare Raids Can Spawn On
Monday (true) Tuesday (true) Wednesday (true) Thursday (true) Friday (true) Saturday (true) Sunday (true)  
Difficulty Colors (Border)
Easy (000000) Medium (000000) Hard (000000) Expert (000000) Nightmare (000000)
Difficulty Colors (Inner)
Easy (00FF00) Medium (FFEB04) Hard (FF0000) Expert (0000FF) Nightmare (000000)
Map Markers
Marker Name (Raidable Base Event) Radius (0.25) Use Vending Map Marker (true) Show Owners Name on Map Marker (true) Use Explosion Map Marker (false) Create Markers For Buyable Events (true) Create Markers For Maintained Events (true) Create Markers For Scheduled Events (true) Create Markers For Manual Events (true)
Buyable Events
Do Not Reward Buyable Events (false) Refunds > Refund Despawned Bases (false) Refunds > Refund Percentage (100.0) Refunds > Refund Resets Cooldown Timer (false) Refunds > Block Refund If Base Is Damaged (true) Cooldowns (0 = No Cooldown) VIP Permission (raidablebases.vipcooldown (300.0) Admin Permission (raidablebases.allow (0.0) Server Admins (0.0) Normal Users (600.0) Allow Players To Buy PVP Raids (false) - If all of your profiles have PVP enabled then players will NOT be able to buy any raids! Convert PVE To PVP (false) Convert PVP To PVE (false) Distance To Spawn Bought Raids From Player (500.0) Lock Raid To Buyer And Friends (true) Ignore Player Entities At Custom Spawn Locations (false) Ignore Safe Checks (false) - if enabled will prevent the plugin from checking the area for a TC, buildings, or deployables Max Buyable Events (1) Reset Purchased Owner After X Minutes Offline (10.0) Spawn Bases X Distance Apart (100.0) - most maps cannot support this being above 200 ! Spawns Database File (Optional) (none) - Useful if you want buyable raids to spawn in specific locations using spawn files from the Spawns Database plugin
Maintained Events
Always Maintain Max Events (false) - Spawn another raid soon after one despawns Ignore Player Entities At Custom Spawn Locations (false) - spawn regardless of what player entities are built in the area Chance To Randomly Spawn PVP Bases (0 = Ignore Setting) (0.0) - Overrides all PVP Allow profile settings for a chance to make the raid PVE or PVP Convert PVE To PVP (false) Convert PVP To PVE (false) Include PVE Bases (true) Include PVP Bases (true) Ignore Safe Checks (false) - Bypass checks that ensure no buildings or other objects are blocking the spawn Minimum Required Players Online (1) - Max Maintained Events (1) - How many bases you want available at any given time Spawn Bases X Distance Apart (100.0) - most maps cannot support this being above 200 ! Spawns Database File (Optional) (none) - Useful if you want maintained raids to spawn in specific locations using spawn files from the Spawns Database plugin Time To Wait Between Spawns (15.0) - Wait a specific time frame between each paste (can be set to 0)
Manual Events
Convert PVE To PVP (false) Convert PVP To PVE (false) Max Manual Events (1) Spawn Bases X Distance Apart (100.0) Spawns Database File (Optional) (none) - Useful if you want manually spawned raids to spawn in specific locations using spawn files from the Spawns Database plugin
Scheduled Events
Enabled (false) - Spawn raids on a timer specific to random amount of time between Every Min and Every Max Seconds Ignore Player Entities At Custom Spawn Locations (false) - spawn regardless of what player entities are built in the area Chance To Randomly Spawn PVP Bases (0 = Ignore Setting) (0.0) - Overrides all PVP Allow profile settings for a chance to make the raid PVE or PVP Convert PVE To PVP (false) Convert PVP To PVE (false) Every Min Seconds (3600.0) Every Max Seconds (7200.0) Include PVE Bases (true) Include PVP Bases (true) Ignore Safe Checks (false) - Bypass checks that ensure no buildings or other objects are blocking the spawn Max Scheduled Events (1) Max To Spawn At Once (0 = Use Max Scheduled Events Amount) (0) Minimum Required Players Online (1) Spawn Bases X Distance Apart (100.0) - most maps cannot support this being above 200 ! Spawns Database File (Optional) (none) - Useful if you want scheduled raids to spawn in specific locations using spawn files from the Spawns Database plugin Time To Wait Between Spawns (15.0) - Wait a specific time frame between each paste (can be set to 0)
Economics Buy Raid Costs (0 = disabled) - if you do not configure at least one cost for Buyable Events then players will not be able to buy any raids
Easy (0.0) - How much each raid costs, use the /buyraid command to see the UI Medium (0.0) Hard (0.0) Expert (0.0) Nightmare (0.0)
ServerRewards Buy Raid Costs (0 = disabled) - if you do not configure at least one cost for Buyable Events then players will not be able to buy any raids
Easy (0) - How much each raid costs, use the /buyraid command to see the UI Medium (0) Hard (0) Expert (0) Nightmare (0)  
Custom Buy Raid Costs (false = disabled) - if you do not configure at least one cost for Buyable Events then players will not be able to buy any raids
Easy (50 scrap) - How much each raid costs, use the /buyraid command to see the UI Medium (100 scrap) Hard (150 scrap) Expert (200 scrap) Nightmare (250 scrap) All are disabled by default. All can require its own specific item.
Allowed Zone Manager Zones
List: pvp, 99999999 - the list of zones where raid bases may spawn at - Zone Manager is not required to use this plugin. Use Grid Locations In Allowed Zone Manager Zones Only - forces all spawns into zones by Zone Manager. Adding flags to your zones may conflict with this plugin. Use of Spawns Database plugin is advised instead
Event Messages
Notify Plugin (-1 = disabled) Notification Interval (1 second) Announce Raid Unlocked (false) Announce Buy Base Messages (false) Announce Thief Message (true) Announce PVE/PVP Enter/Exit Messages (true) Show Destroy Warning (true) Show Opened Message (true) Show Opened Message For Paid Bases (true) Show Prefix (true) Show Messages To Player (true) - set false if you do not want players to receive CHAT messages, other messages from notifications will still show GUIAnnouncements and Advanced Alerts plugins can be used instead of CHAT messages  
Advanced Alerts
Enabled (true) Anchor Min and Max Time Shown (5) Panel Alpha (0.98) Background Color Title Background Color GUIAnnouncements
Enabled (false) Banner Tint Color (Grey) Maximum Distance (300.0) Text Color (White)
Lusty Map
Enabled (false) Icon File (http://i.imgur.com/XoEMTJj.png) Icon Name (rbevent) Icon Rotation (0.0)
Ranked Ladder (based on points system)
Award Top X Players On Wipe (3) - Set 0 to disable permissions and groups from being created. Every wipe the top 3 players are awarded the raidablebases.th permission and raidhunter group. Used with plugins that give titles based on permissions/groups, such as BetterChat Enabled (true) Difficulty Points (for each difficulty) Assign To Owner Of Raid Only (false) Assign Rank After X Completions
-     Players that complete the required amount of completions will receive the relevant above permission and group automatically
-     Set value above 0 to enable this feature for any given difficulty as it is disabled for all difficulties by default Permissions and groups are given to players for being top 3 in each difficulty at the end of a wipe
Set Award Top X Playrs On Wipe to 0 to disable these permissions and groups from being created.
permissions: raidablebases.ladder.easy, raidablebases.ladder.medium, raidablebases.ladder.hard, raidablebases.ladder.expert, raidablebases.ladder.nightmare, raidablebases.th groups: raideasy, raidmedium, raidhard, raidexpert, raidnightmare, raidhunter
Skins (Boxes, Loot Items, Npcs all have there own settings) (skin settings revamped in 2.7.4)
Use Identical Skins Include Workshop Skins (true) Use Random Skin (true) Use Imported Workshop Skins File (true) - copy existing Imported Workshop Skins section from Skinbox to the Imported Workshop Skins json file to apply. Boxes (including above Skins options)
Preset Skins - you can add any box skin here and it will randomly apply to any relevant box this skin can be used with Loot Items (including above Skins options)
Use Identical Skins For Stackable Items Use Identical Skins For Non-Stackable Items
Deployables (including above Skins options)
List: Partial Names (door, barricade, chair, fridge, furnace, locker, reactivetarget, rug, sleepingbag, table, vendingmachine, waterpurifier, skullspikes, skulltrophy, summer_dlc, sled) Skin Everything (true) - if true then the Partial Names list will not be used Preset Door Skins - you can add any door skin here and it will randomly apply to any relevant door this skin can be used with Ignore If Skinned Already (false)
Treasure
Resources Not Moved To Cupboards (skull.human, battery.small, bone.fragments, can.beans.empty, can.tuna.empty, water.salt, water, skull.wolf) Use Day Of Week Loot (false) Do Not Duplicate Base Loot (false) Do Not Duplicate Difficulty Loot (false) Do Not Duplicate Default Loot (false) Use Stack Size Limit For Spawning Items (false)  
Status UI - Shows PVE/PVP, time left, amount of loot left and the status of owner
Details UI - Shows owner and active status
Delay UI - Shows UI for PVP delay
Buyable Cooldowns UI - Shows UI for the Buyable Cooldowns option
Buyable Events UI - Shows players a UI for buying events including the primary cost
Lockouts UI - Shows UI for the Player Lockouts option
Enabled Offset Min Offset Max Panel Alpha Font Size Background Color Title Background Color etc
Weapons
Fog Machine Allows Motion Toggle (true) Fog Machine Requires A Power Source (true) SamSite Repairs Every X Minutes (0.0 = disabled) (5.0) SamSite Range (350.0 = Rust default) (75.0) Test Generator Power (100.0) Tesla Coil settings in profiles
Infinite Ammo
AutoTurret (true) FlameTurret (true) FogMachine (true) GunTrap (true) SamSite (true)
Ammo
AutoTurret (256) FlameTurret (256) FogMachine (5) GunTrap (128) SamSite (24)
Tesla Coil (profiles)
Requires A Power Source (true) Max Discharge Self Damage Seconds (0 = None) 120 = Rust default) (0.0) Max Damage Output (35.0)
Profiles
Difficulty - very first setting. If your raids show as NORMAL then you're using the free plugin. If all bases show as EASY then this setting is not configured. Entities Not Allowed To Be Picked Up (List: generator.small, generator.static autoturret_deployed - overrides Allow Players To Pickup Deployables) Additional Bases For This Difficulty (default) - A list of bases to use within this profile Paste Options (default) - Paste options specific to the profiles filename if it is also a base Profile Enabled (true)- Useful for disabling a profile instead of deleting it Add Code Lock To Unlocked Or KeyLocked Doors (true) Add Code Lock To Boxes (false) Add Code Lock To Tool Cupboards (false) Close Open Doors With No Door Controller Installed (true) Allow Duplicate Items (false) - [Explained above] Allow Players To Pickup Deployables (false) - [Explained above] Allow Players To Deploy A Cupboard (true)- [Explained above] Allow PVP (true) Allow Friendly Fire (Teams) (true) Amount Of Items To Spawn (30) - [Explained above] Minimum Amount Of Items To Spawn (0 = Use Max Value) (0) Flame Turret Health (300.0) Block Plugins Which Prevent Item Durability Loss (false) - Force items to take condition losses Block Damage Outside Of The Dome To Players Inside (false) - Prevent damage from outside of the dome to players inside of the dome Block Damage Outside Of The Dome To Bases Inside (false) - Prevent damage from outside of the dome to the base inside Block Damage Inside From Npcs To Players Outside (false) Building Blocks Are Immune To Damage (false) Boxes Are Invulnerable (false) Spawn Silently (No Notifcation, No Dome, No Map Marker) (false) Divide Loot Into All Containers (true) - [Explained above] Drop Container Loot X Seconds After It Is Looted (0.0) - [Explained above] Drop Container Loot Applies Only To Boxes And Cupboards (true) - [Explained above] Create Dome Around Event Using Spheres (0 = disabled, recommended = 5) (5) - A visible dome for players to distinguish raid bases from player bases Empty All Containers Before Spawning Loot (true) - [Explained above] Eject Corpses From Enemy Raids (Advanced Users Only) (true) - Prevents corpses from remaining inside of a raid when it becomes private and prevents the user from looting it Eject Enemies From Purchased PVE Raids (true) - Useful when Lock Raid To Buyer And Friends is enabled Eject Enemies From Purchased PVP Raids (false) Eject Enemies From Locked PVE Raids (true) - Useful when Lock Treasure To First Attacker is enabled Eject Enemies From Locked PVP Raids (false) Explosion Damage Modifier (0-999) (100.0) - Modify the damage of all explosives Force All Boxes To Have Same Skin (true) Ignore Containers That Spawn With Loot Already (false) - [Explained above] Penalize Players On Death In PVE (ZLevels) (true) Penalize Players On Death In PVP (ZLevels) (true) Loot Amount Multiplier (1.0) - useful to scale loot amounts without having to adjust them all individually Protection Radius (50.0) - This options controls every single option and feature that relies explicity on distance or radius in one regard or another. Setting an incorrect value, either too low, or too high, will break the functionality of the plugin. It's best to leave it alone. Require Cupboard Access To Loot (false) - [Explained above] Minimum Respawn Npc X Seconds After Death (0.0) - Useful in simulating a real raid where players respawn Maximum Respawn Npc X Seconds After Death (0.0) Skip Treasure Loot And Use Loot In Base Only (false) - [Explained above] Always Spawn Base Loot Table (false) - [Explained above] -

Arena Walls
Enabled (true) Extra Stacks (1) - How many times you want walls to stack on top of one another Use Stone Walls (true) - set false to use wooden walls instead Use Iced Walls (false) - not advised to use this as it can cause client lag (not a plugin issue) Use Least Amount Of Walls (true) Use UFO Walls (false) - Walls spawn horizontally instead of vertically Radius (25.0)
NPC Levels
Level 2 - Final Death (false) - Respawns all npcs when raid is completed
NPCs
Enabled (true) Spawn Inside Bases (Options: Spawn On Floors, Spawn On Rugs, Spawn On Beds) Murderer Items Dropped On Death (none) Scientist Items Dropped On Death (none) Murderer (Items) (metal.facemask, metal.plate.torso, pants, tactical.gloves, boots.frog, tshirt, machete) Scientist (Items) (hazmatsuit_scientist, rifle.ak) Murderer Kits (murderer_kit_1, murderer_kit_2) - Kits have priority over these lists of items Scientist Kits (scientist_kit_1, scientist_kit_2) Random Names (none) - Spawn with a custom random name instead of a provided random name Amount To Spawn (3) Aggression Range (70.0) - Aggression range is increased by 250 meters when engaged Despawn Inventory On Death (true) Health For Murderers (100 min, 5000 max) (150.0) Health For Scientists (100 min, 5000 max) (150.0) Minimum Amount To Spawn (1) Use Dangerous Treasures NPCs (false) - Tells Dangerous Treasures to control and outfit the NPCs instead Spawn Murderers And Scientists (true) Scientist Weapon Accuracy (0 - 100) (30.0) - These bots are meant to be savages. 30% is average for highly skilled players, while the average player has 10-20% accuracy Spawn Murderers (false) Spawn Random Amount (false) Spawn Scientists Only (false)
Rewards
Economics Money (0.0) - How much is rewarded after a raid. Overridden by Divide Rewards Among All Raiders ServerRewards Points (0) Change Building Material Tier To
Wooden (false) - Useful for upgrading or downgrading buildings automatically Stone (false) Metal (false) HQM (false) Change Door Type To
Wooden (false) - Useful for upgrading or downgrading doors automatically Metal HQM Player Building Restrictions
Wooden (false) Stone (false) Metal (false) HQM (false) Auto Turrets
Aim Cone (5.0) - shots fired will spread into a cone pattern based on this radius. Lowering this value will group the shots closer together. Minimum Damage Modifier (1.0) Maximum Damage Modifier (1.0) Start Health (1000.0) Sight Range (30.0) Set Hostile (False = Do Not Set Any Mode) (true) Requires Power Source (false) Remove Equipped Weapon (false) Weapon To Equip When Unequipped (null = Do Not Equip) (rifle.ak)
📄Permissions
raidablebases.allow -- Allows player to use the available ADMIN commands. This is NOT recommended as players can use the commands 'buyraid' and 'rb' already. raidablebases.canbypass permission (or to be flying) to bypass dome restrictions (this previously worked for admins, but now requires the permission instead) raidablebases.blockbypass permission to bypass Owning More Than One Raid settings for Clans/Friends/Teams raidablebases.mapteleport Teleporting to map marker now simply requires this permission and to be enabled in config raidablebases.ddraw allows support for FauxAdmin users raidablebases.config allows use of the rb.config command in-game (server console does not require this permission) raidablebases.banned bans the user from entering any raids - If you grant this by accident, use /rb unban name|id to revoke it. Do not grant this to any groups, especially not the default group... raidablebases.durabilitybypass to bypass `Block Plugins Which Prevent Item Durability Loss` raidablebases.notitle permission to exclude users from ranked title rewards See other permissions using Permissions Manager Players do not require any permissions by default.
📄Grid
This plugin creates it's own spawn points automatically, which cover the entirety of your server's map when the plugin is loaded. This is created one-time when the plugin loads. The grid maintains itself without requiring any input.
You may view the grid by typing /rb grid in-game to view detailed drawings of all locations on the grid.
X - green - possible spawn point
X - Red - currently in use
C - Cyan - construction detected nearby
TC - yellow - TC detected nearby
W - blue - water depth is too high - refreshes on ocean level change
Each location on the grid is checked a second time before spawning a base to insure it does not spawn the base on players or their buildings.
You can disable using the grid by providing a valid spawn file for each raid type (buyable, maintained, scheduled and manual).

📄Commands
buyraid - buys a raid, eg: buyraid easy, buyraid easy steamid, buyraid 0, buyraid 0 steamid. I suggest typing the command and using the UI to buy bases. rb - for players to see the ladder (also for admins to see the status of each raid going on, which includes showing the allies and owners of each raid) rb ui [lockouts|status] - COMMAND REMOVED rbe despawn - despawns a players purchased base if they have raidablebases.despawn.buyraid permission   For admins, or players with the admin permission raidablebases.allow: rb.config stability true/false - sets stability in every profile rbe debug - toggles debug messages shown every second to server console for maintained and scheduled warning messages rb grid - see the grid and all monument names rb resettime - reset the time for the next scheduled event rb savefix - to cancel a server save that has become stuck - requires authlevel 2 rb prod - to gather information from a raid base entity for debugging purposes - requires admin or raidablebases.allow rbe - spawns a base at the position you are looking at. You cannot spawn a base on a player (including yourself) rbe draw - draw the raids radius rbe despawn - despawn a base near you (can be used by players with raidablebases.despawn.buyraid permission to despawn a base they purchased) rbe despawnall - despawn all bases rbe [basename] [difficulty] - spawn a raid at the location you are looking at rbe expire steamid|playername - removes a lockout for a specific player rbe expireall rbe active - shows status for each event rbevent [basename] [difficulty] - spawn a raid randomly on the map - and teleport to it if using the command in-game rb.reloadconfig - allows you to reload the config without needing to reload the plugin. Some changes are not applied immediately, and no changes are retroactive to bases that are already spawned. rb.config - allows you to edit the config by adding, removing, and listing bases. Requires the permission raidablebases.config when not being used from the server console. rb.toggle - toggles Maintained Events and Scheduled Events on/off, if enabled in the config, until plugin reloads rbe setowner name - Sets the player as the owner of the raid rbe clearowner - Clears the owner of the raid Additional Bases allows you to add additional files to an existing base so that all bases in that list share the same configuration as the primary base/profile. This is great for setting up a list of bases for easy, medium, hard, expert and nightmare.
Command rb.populate all will add every item in the game to specific loot tables under the oxide/data/RaidableBases/Editable_Lists folder, with each disabled by default (amount is 0)
Arguments:
-     rb.populate easy medium hard expert nightmare loot all
-     rb.populate 0 1 2 3 4 loot all
-     easy - Populates oxide/data/RaidableBases/Editable_Lists/Easy.json
-     all - Populates ALL diifficulty loot tables Configure the items to your liking then copy the files contents into a loot table that you would like to use Example:
-     Difficulty_Loot/Easy.json to match the difficulty
-     Base_Loot/Easy Bases.json to match the profile name
📄API
No return behavior:
void OnRaidableBaseStarted(Vector3 raidPos, int mode, bool allowPVP) void OnRaidableBaseEnded(Vector3 raidPos, int mode, bool allowPVP) void OnPlayerEnteredRaidableBase(BasePlayer player, Vector3 raidPos, bool allowPVP, int mode) void OnPlayerExitedRaidableBase(BasePlayer player, Vector3 raidPos, bool allowPVP, int mode) OnRaidableBaseDespawn, OnRaidableBaseDespawned, OnRaidableBasePrivilegeDestroyed, OnRaidableBaseCompleted   find more hooks and arguments by searching for CallHook in the plugin file
📄Tips
Players will be considered raiders after looting, killing an npc, using explosives, eco raiding, destroying a building block/high wall/door or dealing damage from INSIDE of the dome You must change easybase1, mediumbase2, expertbase3, etc to the name of your CopyPaste files, or vis-versa. This plugin doesn't create or come with any bases. You can use the rb.config command (rb.config add "easy bases" easybase1 easybase2 0) in the server console to make this process easier. You can rename all profiles or additional base filenames. When copying a base with CopyPaste, make certain that you copy the base from eye level of the CENTER foundation within the base, or slightly clipped into this foundation with noclip. Whichever provides better results for you. You must verify that the base pastes down correctly (with /paste command) after you've copied it. I would not change autoheight from false to true. height is the distance the base is spawned off of the ground. elevation determines how flat the surrounding terrain must be in order for bases to spawn on it Scheduled Events is how often you want a random base to spawn on the map. This is disabled by default. This randomness comes from Every Min Seconds and Every Max Seconds Maintain Events will always spawn the Max Events amount of bases on your map. This is disabled by default. When one despawns, another will take its place shortly after. Allow Teleport will prevent players from teleporting when disabled. Compatible with NTeleportation or any plugin that uses the CanTeleport hook. 📄Help
This plugin does NOT use Zone Manager - it creates and manages everything on its own. If you are having issues with too few locations on the grid, or each attempt to spawn a base returns a manual spawn was already requested then it is likely because of how you have setup Zone Manager. You either have far too many zones, or you have zones which are far too large. Raidable Bases will not spawn in these zones unless the ZoneID is added to Allowed Zone Manager Zones in the config file. Do not put this plugin in your store/shop. It simply is not designed to work with it. There are far too many cooldowns to make this idea plausible, and the plugin cannot function properly without them. Using /buyraid will open a UI designed specifically for this issue. This plugin requires CopyPaste plugin to work. It also requires that you have copypaste files already made. Raidable bases will be spawned using the CopyPaste plugin. This plugin does NOT come with any bases. PvE server friendly with TruePVE and other plugins that support the hooks CanEntityTakeDamage, CanEntityBeTargeted, and CanEntityTrapTrigger. Bases can have 5 difficulty settings: 0 for easy, 1 for medium, 2 for hard, 3 for expert, and 4 for nightmare. This is configurable per profile. Bases can spawn on roads and other areas that do not allow building by Rust. Building ladders in these areas is allowed by the plugin. I will add support for building twig later. My bases often spawn in the same biome If you're having issues with spawn points being repeatedly used, or with a biome being favored consistently over other biomes then this is an elevation issue with the terrain on your map. You can fix this by increasing the Elevation in the configuration. For example, if your Elevation is 1.0 then set it to 1.5 and try again. This will also increase the height the base is allowed to spawn off of the ground. With certain maps you'll just have to make do with this issue. Corpses appear outside of the dome as backpacks This is intended, and it is optional. The location is drawn on the players screen to notify them that their corpse moved. This allows players to retrieve their backpack in the event that the raid becomes locked privately to another player, and prevents them from entering. Players do not drop their active item when they die. 📄Bases Stop Spawning On Linux Machine
          [Error] Exception while calling NextTick callback (DllNotFoundException: libgdiplus.so.0)
          If you see this error after bases spawn then you need to install libgdiplus on your machine. This will mimic the below issue but it is NOT a bug like the below issue is.
          A quick google search shows the install command is:  sudo apt-get install -y libgdiplus
          This happens when images in the CopyPaste file are being rendered by converting the byte array to bitmap.
📄Paste/Spawn/Despawn FPS/Rubberbanding Issues:
Upgrade your servers hardware (please don't tell me how good your hardware is-- if it's having issues or is overloaded with plugins then it's not) Use copypaste files under 3MB Reduce the amount of bases that you are spawning Remove plugins - if you have too many resource hogs then you're going to have issues! Reduce Amount of entities to paste per batch. Use to tweak performance impact of pasting in your CopyPaste config to between 1 and 5 Restart your server daily to mitigate server degradation issues It could be as simple as a bad copypaste file. Note the base(s) that spawned around the time that the lag started, go to each of those bases and despawn them (/rbe despawn). If the lag disappears, then the base is the cause. Remove it from rotation (rb.config remove badbase1) until you can figure out what's wrong with it. RaidableBases is a large plugin, with a lot of functionality, and that functionality demands hook time. I constantly strive to improve performance and provide high quality products.

The ultimate base protection plugin that allows players to pay a resource in exchange for configurable protection for their base or tugboat. This plugin has been rewritten from the ground up for performance, quality, and integrating community suggested features.
 
Features

 
There are many different ways you can configure this plugin to fit the needs of your server. Many features can be modified or disabled entirely through the plugin configuration file. These include:
Both online and/or offline base protection Trade currency for protection or provide it for free Players can turn on/off protection Permission based protection tiers Configure what gets protected and who it is protected from Set limits on how long protection lasts Indicator(s) for displaying base protection Option for allowing raiders to bypass protection if they can drain the protection balance with damage Options for making protection more expensive for larger bases/clans and cheaper for small groups. UI that blends in seamlessly with vanilla Rust. Disclaimer
This plugin will be updated at the owners discretion. Before purchasing any plugin, I recommend checking the date of the last update and refer to support tickets to see if there might be any issues with the latest Rust game version. If a game update breaks this plugin, please open a support ticket (if it doesn't already exist) and direct message me on Discord (link found below).
How to Use
Configure the plugin and load it Once loaded, assign yourself (or your group) one of the protection level permissions. Place a new tool cupboard, or find one that YOU have previously placed. Open the tool cupboard inventory, at the top you should see two tabs: "Upkeep" and "Protection". Select the protection tab to view the raid protection info. On this screen, you will be able to spend the configured currency in order to purchase hours of protection. By default, this currency is scrap. Use the buttons on the right to add some hours of protection, you should see that status change to show the time you are protected. Your base will now be protected for the amount of time specified. Notes
You can use the Clear button to withdraw all balance, and stop protection The Pause/Resume button can be used to start/stop protection without changing the balance. The Info button will reveal a panel which displays additional information on protection. The +Max button will deposit the maximum amount of time that you can afford  
Quick Start Presets
There is a lot of documentation for this plugin because there is a lot you can do with it! However, it doesn't have to be complicated. If you have a simple use case in mind, you can use one of these preset configurations to get what you need or use as a starting point without having to figure it out yourself!
Important:  You will want to assign your default permission group the  raidprotection.level.1  permission for any of these configurations.
 Always Free Provides free raid protection for all players with the level 1 permission Protection for tugboat bases Recommended for PvE or light PvP servers Offline Only Same as the default config, but only offers offline protection Has a limit of 48 hours of protection for level 1 Includes a level 2 permission with unlimited hours of protection (VIP) Protection for tugboat bases Recommended for PvP servers Hardcore Offline only protection Two protection levels, one with a 48 hour limit and one with no limit Additional costs that scale with number of owners and building size Raiders can damage a structure and cause it to "bleed" protection balance to attempt to disable the protection with enough damage Significant delay for activating protection No protection for tugboat bases Recommended for hardcore PvP servers Upgrading Versions
When a new version is released, you may need delete your config and lang files and reload them to accommodate the new changes. You do NOT need to delete the data file, unless specifically instructed. As long as you do not delete the data file, then all of your protection balances will persist, even between versions. Not all updates will require this process, but if it does, you will be notified with a message like this:
To resolve this, simply delete the config and lang files and reload the plugin. You will need to manually update these files to align with what you want.
As of v3.4.0 you no longer need to delete your config files when upgrading from a previous version. However, you still should check the config after the update is installed to verify no unintended changes have occurred.
Protection Levels

Protection levels are how you assign a particular set of rules to a player. These protection levels are added in the configuration file, and are then assigned to an auto-generated permission.
Each protection level needs a unique Rank property, this rank determines the order of precedence when a player is assigned multiple protection levels. In this event, a player's protection level will always be the highest ranked protection level they are granted.
Protection levels are managed in the configuration file, here is some information on some of the properties:
Cost per damage protected    - This amount will be deducted from the protection balance for each point of damage that was protected. So if this value is set to 1 and  someone attempts to deal 100 damage to a protected structure, and that structure has 100% protection, then 100 balance will be deducted. If in that same example it was only 50% protection, then only 50 balance would be deducted. Entity resistances are taken into account as well (twig will take more damage than metal, ect). Hourly base  cost  - This is a fixed cost that is charged per hour of protection. Hourly cost per authorized player  - This amount will be charged for each owner every hour. Can be used to charge players more if they have a larger clan. Hourly cost per floor  - This amount will be charged for each floor  every hour. Can be used to charge players more for protecting a larger base. Max protection time  - The max number of hours protection can be applied for. If set to null, then there will be no limit. Offline protection percent  - The percent of protection a structure will receive when all the owners are offline. A value of 0 will be unprotected, and a value of 100 will be fully protected. Online protection percent  - The percent of protection a structure will receive when at least one owner is online. A value of 0 will be unprotected, and a value of 100 will be fully protected. Rank  - A number value indicating the order of importance when a player is assigned multiple protection ranks. Higher values indicate a greater importance. For example, if a player is assigned both protection rank 1 and protection rank 2, then tool cupboards they place will be of protection rank 2 instead of 1.   These ranks must be unique  DO NOT  create protection levels with the same rank. This value needs to be 1 or higher, it cannot be 0. Delay after taking damage  - The number of seconds before protection may begin after a structure has taken unprotected damage. It is recommended to set this to a higher amount on PvP servers. Delay for offline protection  - The number of seconds before offline protection kicks in after the last owner has gone offline. It is recommended to set this to a higher amount on PvP servers. Damage resets timer when owner is offline  - If this is set to true, then if a raid has already started on a structure that has offline only protection, but the protection hasn't kicked in yet (due to a delay timer) then the attackers can continue to raid indefinitely as long as they continue to do damage while the owner(s) are offline. If this is set to false, then the attackers will only have a certain amount of time to continue their raid if the owner(s) are offline. Allow tugboat protection  - If this is set to true, then players with this protection level may receive protection for tugboat bases. For these tugboat bases the protection panel can be accessed in the fuel inventory of the boat. The founder of a tugboat base is whomever is the FIRST player to authorize on a tugboat. Founder Limit  - The number of tool cupboards that a player can be a Founder of and receive raid protection. If a player exceeds this limit, then future tool cupboards will not receive protection until enough previously placed ones have been destroyed in order to be within the limit. If a player places a tool cupboard, and they have exceeded the limit, once they are no longer exceeding the limit they can "activate" that tool cupboard in the info panel to have it gain raid protection. If this value is set to null then there is no limit.  
Founders and Owners

When a tool cupboard is placed, the player who places it is permanently labeled as the "Founder" of that tool cupboard and building privilege. The protection level of that building privilege is derived soley from the founder's protection level, and therefore won't change unless the founder's protection level changes.
Whenever a player is authorized on a tool cupboard, they will be permanently branded as an "Owner" of that tool cupboard. Owners are all the players, including the founder, who have EVER been authorized on the tool cupboard. This means that players will still be listed as an owner even if they deauthorize themselves. Owners are important because they affect how Online/Offline protection will be triggered. A base will only be granted offline protection if ALL the owners are offline, otherwise online protection (if available) will be granted if at least one owner is online.
For tugboat bases, the founder is whomever is the first player to authorize themselves on the tugboat.
 
Permissions
raidprotection.admin raidprotection.level.x - these permissions are autogenerated based on your protection level settings in the config, they will show up in the server console when the plugin is loaded (unless you have  Enable Console Messages  set to  false) raidprotection.ignore - raid protection will not count any player with this permission towards being an owner. They will not show up in the owner list and will not count toward team member count for offline protection. They also will not receive protection on bases they build even if they have a protection level assigned. This is useful for admin groups so that you don't have to remember to deauth on tool cupboards. However, if this permission is ever revoked, that player will be retroactively counted as an owner on ALL tool cupboards they are currently authed on.  
Commands
Player Commands
These commands require no permissions and can be used by any player.
/pro -  displays the raid protection information panel, requires authorization on the tool cupboard in the current area. /lev -  displays a screen that tells the player their personal assigned protection level and explains the benefits that comes with it. Admin Commands
These commands require the  raidprotection.admin  permission to use.
/tc -  displays a screen with all the available admin commands /tc help - same as /tc Use the above commands to see a full command list in game.  
Configuration
The default config file:  
Here is an explanation for some of the fields:
Enable Logging  - Set to true to keep logs of tool cupboards protection activity. Logs will be saved to the oxide/logs/RaidProtection folder.   It is recommended only to enable this only for debugging purposes, as it will take a significant amount of storage space if you have a larger server. Enable Ledger  - Set to true to keep track of protection balance changes for tool cupboard. These ledger files are stored in oxide/data/RaidProtection/Ledgers. It is recommended to keep this enabled, as it will help you roll back balances if a player has an issue. This does not take up as much storage space as logging does as it only keeps track of balances. Enable Console Messages  - Set to false to disable the info messages upon plugin reload. Commands  - You can change the prefix for the commands this plugin uses here. Chat Message Icon ID  - A steam id for the portrait of chat messages. Protection Tabs Offset  - This value will adjust the vertical placement of the Protection Tabs in the tool cupboard menu. Positive values will move it up, negative values will move it down. Useful for making it so those tabs don't conflict with other UI plugins that use that area. Image Settings  - Links for the images the plugin uses. Indicator Settings  - Settings for the indicator that (by default) appears in the top right when you attack a protected structure. You can change its size and position or disable it. Plugin Integration  - Set any of these to  true  if you want this plugin to take advantage of the features of another supported plugin. Custom Status Framework Settings  (Ignore if you do not have Custom Status Framework integration enabled) Popup Attack Indicator  - If set to true, a status will briefly appear when a player attacks a protected structure. Persistent Status For Owners  - If set to true, a status will appear while a player is in a protected area that they are an owner for. Slight performance cost when enabled. Persistent Status For Non Owners  - If set to true, a status will appear while a player is in a protected area that they are NOT an owner for. Slight performance cost when enabled. Popup Status When Hammer Equipped  - If set to true, a status indicating the protection level of the area they are in will appear while they are holding a hammer. This will appear regardless of if you are an owner of that area or not. Protection Settings Admin owners removed when deauthorized - Normally, you cannot remove an owner even if they deauthorize. But if this setting is enabled, it allows admins to remove themselves as owners when they deauthorize from a tool cupboard. They can also achieve this with commands. Allow balance withdraw  - If set to true, then players will see a "Clear" button in the tool cupboard panel that allows them to withdraw any protection balance. Allow max deposit  - If set to true, there will be a "+Max" button that will purchase the maximum number of protection hours a player can afford. Award remaining balance when cupboard is destroyed  - If set to true, whomever destroys a tool cupboard will be awarded whatever amount was in the protection balance. Currency item  - The item that will be used as currency for protection, this will only be overridden if you are using Server Rewards or Economics for your currency. If you want it to be a custom item that has a skin, you can put # followed by the skin id after the item name. For example "scrap#12345" would only accept scrap items with the skin 12345. Protected entities  - If any of these are set to true, then that type of entity will be covered under Raid Protection. If you are using other protection plugins like TruePvE, then you will want to configure these to not overlap with what other plugins are protecting. Protected from  - If these are set to true, then damage from that type of source will be protected. By default Authed Players  is set to false, which means that players will be able to damage their own structures, but enemy players cannot. Protection levels  - See the section about protection levels for information. Protect twig  - If set to true, then twig building blocks will receive raid protection. If set to false, then twig building blocks will not receive raid protection, even if placed by an owner of the base. Ledgers
As of Raid Protection v3.2.0, you can optionally configure ledgers to be enabled. When enabled, the plugin will keep logs protection balance changes for all tool cupboards. These logs will be saved to oxide/data/RaidProtection/Ledgers. There is a ledger file for each tool cupboard, and it's filename will make the entity ID of that tool cupboard. You can use the /tc id command to see what the ID of a tool cupboard is (see commands section). The benefit of ledgers is that each balance change has a specific GUID identifier attached to it that can be used to restore a tool cupboard's balance to that exact state in the event that a player has an issue. An example of a ledger file might look like this:
Ledger file for tool cupboard with ID 2250729
[ "05/26/2023 16:17:56,ad87f16e-52eb-4689-887f-ecc53cd3ff13,0,Withdraw", "05/26/2023 16:18:20,108e54c0-98c4-46df-9eb3-e17192c37bb3,0,CollectionStopped", "05/26/2023 16:18:23,a2f03162-200c-47ce-948e-b0c703435e51,0,CollectionStarted", "05/26/2023 16:18:28,5c83390e-bbd2-4049-8ec9-8f2951746159,0,Withdraw", "05/26/2023 16:19:29,cd892a3f-249b-4cad-8949-abf904656288,20,Added", "05/26/2023 16:19:31,6e710dfc-23c2-4375-8c4f-07017d4d44c6,40,Added", "05/26/2023 16:19:31,bc51f8c7-3f3a-4abc-8fd2-8bb4c47fe454,60,Added", "05/26/2023 16:20:25,f08cfa34-a623-4de3-9027-7c3acb3e3ec3,60,CollectionStarted", "05/26/2023 16:20:52,a849be59-899c-4779-bba6-2f5f1b0ffb8d,59.93055,CollectionStopped" ] The format of each row goes as follows, from left to right separated by commands.
Date and Time of balance activity GUID identifier, used by the /tc restore command to roll back a balance The protection balance of the tool cupboard at that given time A brief descriptive reason as to what changed about that balance For example, using the ledger file listed above, if we wanted to rollback the tool cupboard to before the collection started (the last "Added" one), we could run the following command.
/tc restore 2250729 bc51f8c7-3f3a-4abc-8fd2-8bb4c47fe454 Running this command will set the balance of the tool cupboard with ID  2250729 back to its balance of 60.
As of v3.2.3 you can also mass restore all tool cupboards to a specific time or date.
For example, using the ledger file listed above, if we wanted to rollback the tool cupboard to the time 16:19:00. We could run the following command.
 
/tc ledger rollback 16:19 This will rollback ALL TOOL CUPBOARDS to the first ledger entry that comes BEFORE the given time.   In this case that entry would be GUID=5c83390e-bbd2-4049-8ec9-8f2951746159 at time 16:18:28 because that is the latest entry before 16:19:00. Thus the balance will be 0.
Rollbacks can also accept a date in addition to a time. For example, if you wanted to rollback to noon the following day you could run the following command.
 
/tc ledger rollback "5/25/2023 12:00" Notice that there is no ledger entry for this tool cupboard that goes back that far. In this case, the balance of the cupboard will be set to ZERO. Please note that if you include a date and time the value MUST be enclosed in quotes (see the example above).
Tugboat Bases
As of v3.3.0, Raid Protection can optionally be allowed for tugboat bases. This is configurable per protection level. Tugboat bases can utilize all the features of a normal tool cupboard base. You can access the protection panel for tugboat bases in the fuel inventory in the drivers seat. For tugboat bases, the founder of the base is considered to be the FIRST player to authorize on the tugboat.
Plugin Integration
Clans
This plugin provides built-in support for Clans. If a player is in a Clan, it will automatically treat all clan members as owners. This of course means that the owners will not be removed even when a member is kicked from a clan.
True PVE
This plugin is compatible with True PVE as long as both plugins are configured in a non-conflicting way. For example, if you use True PVE to provide protection to players, then in your Raid Protection config file under the  Protected entities  section you should set  Authed Players  and  Unauthed  Players  both to  false  to avoid hook conflict errors. If you do see hook conflicts, see the section of this documentation about how to resolve hook conflict errors.
Zone Manager
This plugin is compatible with ZoneManager without any extra configuration. ZoneManager will take priority if the zone has the "undestr" flag.
Custom Status Framework
If you have CustomStatusFramework installed and want to take advantage of the status indicators (that appear in the bottom right) in your Raid Protection config file under the  Plugin Integration  section set  Custom Status Framework  to  true.
Simple Status
Simple Status is a plugin that is still being developed, and will be an alternative, more performance friendly option to Custom Status Framework. This plugin is not yet available, but as of v3.4.0, configuration options have been added to support this plugin when it releases.
Preview of indicators:

 
Economics and Server Rewards
If you wish to use economics balance or server rewards points as a currency instead of an item, you can set ONE of these to true in the plugin integration section of the config. It is important to set ONLY ONE of these to true, or else both will be disabled and you will get a warning in the console.
Protection panel with Economics:

NoDecay
This plugin is compatible with NoDecay without any extra configuration.
Notify
If you want to use Notify as your source of indicators you can enable the flag for it in the Raid Protection config.
Abandoned Bases
If you enable Abandoned Bases in the integration config, then bases that are labeled as Abandoned will not receive raid protection.
Raidable Bases
Bases spawned by Raidable Bases will be ignored by Raid Protection. They should not show up in ledgers and players cannot add balance to them.
Skill Tree
If Skill Tree is enabled in the integration config then it will prevent players with the lockpicking skill from picking locks in raid protected areas.
Other Plugins
Should be compatible with most other plugins given they don't use the onEntityTakeDamage hook. If they do use this hook, it just means you have to change your configuration settings, see the hook conflicts section for more info.
Images
If you experience any issues with the default images provided by this plugin I recommend hosting them yourself. The urls can be changed in the config. Here is a zip file containing all the images.
icons.zip
Carbon
As of 8/19/2023 I can confirm that this plugin is compatible with Carbon. Please open a support ticket if you experience any Carbon related issues.
Hook Conflicts
If you're getting messages in the server console that looks similar to this:
OnEntityTakeDamage resulted in a conflict between the following plugins: NoDecay - True (Boolean), RaidProtection (False (Boolean)) That means that another plugin is conflicting with Raid Protection. In most cases this is an easy fix, and it just means that you need to update your Raid Protection config file to not protect the same entities that another plugin is already protecting. So for example, if you have a plugin already that makes it so player's cannot attack each other, then there is no need for Raid Protection to do that job, and therefore in the  Protected entities  section of the config you should set  Authed players  and  Unauthed  players  to false to avoid conflicts.
Previous Versions
You may have seen the free version of this plugin available on uMod. That version (2.X.X) will stay available for free on umod, but is no longer supported.
If you are upgrading from the free version, you must first delete the config/lang/data files before installing v3.0.0 and above. If you do not delete these files, you will likely run into issues, as despite having the same name, the plugin has been completely rewritten, and therefore is completely incompatible with the free version.
 
Developer API
/* * Returns 0 if entity unprotected and 100 if entity fully protected */ private float GetProtectionPercent(BaseEntity entity) /* * Returns a list of the owners of the structure associated with the given entity */ private List<BasePlayer> GetOwners(BaseEntity entity) /* * Returns the player who is the founder of the structure associated with the given entity. Can be null. */ private BasePlayer GetFounder(BaseEntity entity) /* * Returns the protection balance of the structure associated with the given entity */ private float GetProtectionBalance(BaseEntity entity) /* * Returns the hours of protection remaining of the structure associated with the given entity */ private float GetProtectionHours(BaseEntity entity) Discord
If you want to report a bug, require support, have a suggestion or want to be notified when I release an update you can join my plugin development discord with this link:
Plugin Development Discord Link

Donate
Writing and maintaining these plugins takes a tremendous amount of work. Donating is one way to give some positive feedback which helps me continue making them!
Buy me a coffee here!
 
FAQ
Please check out this section before opening a support ticket, it may save us both some time!
Q: I don't see the status indicators in the bottom right.
A: The status indicators come from another plugin called CustomStatusFramework, you must install it and enable it in the config file to get the indicators.
Q: I have protection time, but I am able to damage my own structure.
By default "Authed players" are able to damage their own structures. You can change this in the config file.
Q: The add hours buttons aren't showing for me in the tool cupboard panel.
A: The hours buttons will not show if the protection has 0 cost.
Q: I have a max protection time set, but it says "protected for forever"
A: If the protection cost is 0, then there cannot be a max protection time.
Q: I deauthorized myself from the tool cupboard, but I am still listed as an owner.
A: Owners are not removed after deauthorization. Only admins can remove owners.
Q: How are overlapping tool cupboards handled?
A: If a player has a base with overlapping tool cupboards, then each cupboard will need its own protection. Which entities are protected depend upon which tool cupboard governs that entity.
Q: Can player's exploit offline only protection by deauthorizing?
A:Deauthorizing will not help players looking to exploit offline only protection because they will still be considered an Owner even if they deauthorize.
Q: Can a player exploit offline only protection by never authorizing?
A: If a player is never authorized on a cupboard, then they will not count toward being online, and therefore offline protection can occur. However, players cannot add or manage protection balance unless they are authorized, and therefore the protection balance will run out, especially if a max protection time is set.
Q: I have protection for horses on, but now the horses never poop
A: If horses don't lose health, they will never eat and therefore never poop, this is a side effect of protection for horses.
Q: Why does protection say "pending" in the bottom right?
A: Pending either means that you have offline only protection or your structure has recently taken damage and therefore protection is delayed. See the tool cupboard protection panel for more info.
Q: I'm seeing conflict warnings in my console between Raid Protection and True PvE
A: Please refer to the sections of documentation for TruePvE and Hook Conflicts
Q: I'm seeing Image failed to download! Error: HTTP/1.1 429 Too Many Requests
A: Refer to the Images section of the documentation.
 
 

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

Rust Tebex Template – Outpost
Stand out from the competition with this Rust-themed Tebex template!
 
Features
Rust Themed
The template is heavily inspired by the Rust in-game UI, so people will instantly recognize what they’re used to. It is kept in a darkish style to stand out from all the other default-white templates out there!
Fully Customizable
Everything is directly integrated into Tebex. If you are already running a shop with them, it will integrate in a few minutes. If you are new to setting everything up do not worry – it is pretty straight forward!
Comes with product images
Product images make you stand out and allow to get attention from your players. The template comes with a few basic product images so you can focus on getting everything set up!
Perfect addition to the Rust Website Template
If you didn’t already know, I have published a Rust-themed website template before.  Check it out over here. The Tebex template is heavily based on that, so if you plan to extend your existing website, try to give it a go!
 
Requirements
! You need to have the paid Tebex Plus plan to be able to use custom themes! We do not refund payments if you don’t have the plan available. !
Installation Instructions
Installation instructions can be found on our Discord
Troubleshooting
If you have any open questions or problems while setup, check out the troubleshoot guide on our Discord
Contact and Support
If you need additional assistance or got any open questions before purchasing, join us on Discord:  https://promeus.io/discord

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 | 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