Search the Community

SimplePVE is exactly what it says. An easy simple PVE plugin for your server to modify or change PVE rules individually & now also have a Simple Cui to control PVE rules and Create or edit Schedules. Control PVE Rules from in-game or in the config Easy to understand each individual Rules Create PVP Schedules Discord Embed Messages on PurgeStart or End Many more features are added every update /simplepve - Use to enable or disable pve toggle (Chat & Console command) /simplepve on or off - Use to enable disable pve (Chat & Console command) /sprules - Use to Open a Cui to control PVE Rules & Creating Schedules (Chat command) simplepve.admin - Required to enable or disable SimplePVE simplepve.adminloot - Required to view Loots simplepve.admindamage - Required for Admin damages to any entity void OnSPVEPurgeStarted() void OnSPVEPurgeEnded() TimeSpan GetPVPStartTimeRemaining() TimeSpan GetPVPEndTimeRemaining() Check Out My Other plugins as Well

UI Loot Tables Editor for Raidable Bases plugin by Nivex. Features Import/Export loot table json file Complete database of game items (Categorized, friendly names and pics) Add/Delete loot table items Edit loot table items spawn details Bulk edit/delete items Bulk multiply items values (min amount, max amount, stack size) How to Download and extract RustRBLootEditor-v***.zip Run RustRBLootEditor.exe (having trouble running?, make sure you download .NET 6.0) Click Load, and locate your desired loot table file to be modified in "oxide\data\RaidableBases\.." (not familiar with loot tables? please refer to original Raidable Bases documentation) Now you can easily move game items into your loot table or remove them easily using mouse right click (you can use search box for filtering) Edit loot table item Amount Min/Max and Skin id using mouse left click, change amounts, then click anywhere outside the modal to collapse Click Save and replace your file, and you're done (or save as draft with a new name)

Plugin for Real PvE servers, featuring damage prevention, anti-griefing measures, customizable PvP zones, an automatic loot queue in radtowns and raid zones, and much more. P.S. Since the previous implementation with DynamicPVP was not correct and had some issues, I have added universal hooks(Developer API section) for general access from all PvP plugins, which are currently missing in DynamicPVP. I have requested the author to add them(3 lines), but for now, you will need to use the modified version of DynamicPVP.cs The ability to set "server.pve" to "true", which allows the server to have a "PvE" flag; Damage from NPC's are enabled when server.pve is true; The ability to inflict damage to one's own structures with "server.pve true"; The ability to destroy(including external walls) or rotate one's structures without any time constraints; The ability to force the decay of building blocks with Twigs grade, even if there is wood in the Tool Cupboard; The ability to toggle the gather resource restriction in someone else's Building Privileges; No one, except the owner or their friends, will be able to open their loot containers (chests, storages, bodies, etc.); Administrators can bypass loot restrictions; The ability to schedule the killing of players if they disconnect within someone else's Building Privilege; Disabling backpack and active item drop upon death, even if backpack is full; The ability to disable 'Give' messages; The ability to modify the items given at spawn on the beach; The ability to create an unlimited number of custom permissions; The ability to allow players to bypass the queue; The ability to set limits on sleeping bags, shelters and auto turrets for each permission; The ability to set a multiplier for the prices of monuments and events for each permission; The ability to customize the price and amount of vehicles for each of your custom permissions; The ability to assign vehicles to each player; The ability to customize the assigned price and available amount of vehicles for each of your custom permissions; An assigned vehicle can't be damaged, looted or pushed by other players, but it can be pushed if it is within someone else's Building Privilege; The ability to loot monuments through a queue system; The ability to configure monuments, setting their looting price and time, and adjusting status bars for each monument; The ability to acquire the privilege to loot events (helicopters, bradleys, and raidable bases) through a purchase; The ability to customize the price of each event types and loot attempts (lives); NPCs only aggress against players who are looting monuments, events or raidable bases; Only players who are looting monuments, events or raidable bases can inflict damage to NPCs; RaidableBases are protected from griefing(no damage, no loot and etc). Only the owner can interact with the raid; Neutral RaidableBases can be purchased; Prices for purchasing neutral raids are configurable for each difficulty level; Configurable raid limits (currently available) along with discount multipliers for purchases, for each permission. File location: *SERVER*\oxide\data\RealPVE\PermissionConfig.json Default: https://pastebin.com/5VtWZZVr All permissions are created and configured in the config file under the "List of permissions" section. You can create as many permissions as needed and customize them flexibly. It is recommended to use the prefix "realpve" in the permission's name, for example: "realpve.vip". NOTE: The first permission will serve as the default permission for those who do not have any permissions. { "List of permissions. NOTE: The first permission will be used by default for those who do not have any permissions.": [ { "Permission Name": "realpve.default", "Bypass Queue": false, "Limit of beds": 15, "Limit of shelters": 1, "Limit of auto turrets": 12, "Seconds that will be skipped when opening HackableLockedCrate. Range from 0 to 900": 0.0, "Monuments price multiplier": 1.0, "Events price multiplier": 1.0, "Limit of RaidableBases(at the time)": 1, "RaidableBases price multiplier": 1.0, "Vehicles settings": { "Horse": { "Limit": 1, "Price": 10.0 }, "Bike": { "Limit": 1, "Price": 5.0 }, "MotorBike": { "Limit": 1, "Price": 20.0 }, "Car": { "Limit": 1, "Price": 25.0 }, ... } }, { "Permission Name": "realpve.vip", "Bypass Queue": true, "Limit of beds": 20, "Limit of shelters": 2, "Limit of auto turrets": 15, "Seconds that will be skipped when opening HackableLockedCrate. Range from 0 to 900": 450.0, "Monuments price multiplier": 0.9, "Events price multiplier": 0.9, "Limit of RaidableBases(at the time)": 2, "RaidableBases price multiplier": 0.9, "Vehicles settings": { "Horse": { "Limit": 5, "Price": 9.0 }, "Bike": { "Limit": 5, "Price": 4.5 }, "MotorBike": { "Limit": 5, "Price": 18.0 }, "Car": { "Limit": 5, "Price": 22.5 }, ... } } ], "Version": { "Major": 0, "Minor": 1, "Patch": 1 } } An example of a monument/event/rb multipliers using default permissions. For example, if you set the price for the Harbor at $1000, a player with the default permission(1.0) will pay $1000 * 1 = $1000. Meanwhile, a player with a VIP permission(0.9) will pay $1000 * 0.9 = $900. However, if a player possesses a misbehaving permission with a value of 1.1, they will need to pay $1000 * 1.1 = $1100. { "Chat admin command": "adminpve", "Chat command": "realpve", "Is it worth forcibly implementing PvE for a server?": true, "Is it worth enabling GameTips for messages?": true, "Is it worth preventing the sending of 'Give' messages?": true, "Is it worth preventing resource gathering in someone else's building privilege area?": false, "Is it worth preventing the pickup of plants spawned by the server in someone else's building privilege zone?": false, "Is it worth assigning portals(Halloween and Christmas) to the first player?": true, "Is it worth preventing players from handcuffing others?": true, "Is it worth preventing a backpack from dropping upon player death?": true, "Is it worth preventing damage to the laptop of the Hackable Crate?": true, "Is it worth removing the penalties for recyclers in safe zones?": true, "Which currency symbol and format will be utilized?": "${0}", "Vehicles - Time(in seconds) to display the marker when searching for a vehicle. A value of 0 disables the marker": 15.0, "Anti-Sleeper - Time in seconds after which a player will be killed if they disconnect while inside someone else's Building Privilege. Set to 0 to disable": 1200.0, "PatrolHelicopterAI - Monument Crash. If set to true, the helicopter will attempt to crash into the monument": false, "PatrolHelicopterAI - Use Danger Zones. If set to false, the helicopter will function as it did before the April update": false, "PatrolHelicopterAI - Flee Damage Percentage. A value of 1 or above will make the helicopter behave as it did before the April update": 1.0, "Is Npc Random Raids enabled?": true, "PvP - Is friendly fire enabled by default when creating a team?": false, "PvP - Is it worth adding map markers for PvP zones?": true, "PvP - Name of the map maker": "PvP Zone!", "PvP - Settings for the status bar": { "Order": 9, "Height": 26, "Main_Color(Hex or RGBA)": "1 0.39 0.28 0.7", "Main_Transparency": 0.8, "Main_Material": "", "Image_Url": "https://i.imgur.com/oi5vIkk.png", "Image_Local(Leave empty to use Image_Url)": "RealPVE_PvP", "Image_Sprite(Leave empty to use Image_Local or Image_Url)": "", "Image_IsRawImage": false, "Image_Color(Hex or RGBA)": "1 0.39 0.28 1", "Image_Transparency": 1.0, "Is it worth enabling an outline for the image?": false, "Image_Outline_Color(Hex or RGBA)": "0.1 0.3 0.8 0.9", "Image_Outline_Transparency": 0.0, "Image_Outline_Distance": "0.75 0.75", "Text_Size": 12, "Text_Color(Hex or RGBA)": "1 1 1 1", "Text_Font(https://umod.org/guides/rust/basic-concepts-of-gui#fonts)": "RobotoCondensed-Bold.ttf", "Is it worth enabling an outline for the text?": false, "Text_Outline_Color(Hex or RGBA)": "#000000", "Text_Outline_Transparency": 1.0, "Text_Outline_Distance": "0.75 0.75", "SubText_Size": 12, "SubText_Color(Hex or RGBA)": "1 1 1 1", "SubText_Font": "RobotoCondensed-Bold.ttf", "Is it worth enabling an outline for the sub text?": false, "SubText_Outline_Color(Hex or RGBA)": "0.5 0.6 0.7 0.5", "SubText_Outline_Transparency": 0.0, "SubText_Outline_Distance": "0.75 0.75" }, "PvP - Settings for the progress status bar": { "Main_Color(Hex or RGBA)": "1 1 1 0.15", "Main_Transparency": 0.15, "Progress_Reverse": true, "Progress_Color": "#FF6347", "Progress_Transparency": 0.7, "Progress_OffsetMin": "0 0", "Progress_OffsetMax": "0 0" }, "Wipe ID": null, "Version": { "Major": 0, "Minor": 1, "Patch": 13 } } ENG: https://pastebin.com/ZMUL6pYL RUS: https://pastebin.com/Mx8cbMts Main commands(/realpve ) : autobuy - Toggle autobuy for monuments, vanilla events and raid bases with a total price greater than 0; pickup - Toggle access to pick up your items from the ground for all players; share - Manage access to looting your entities by other players(outside of the team): status *entityID*(optional) - Display information about the settings of the entity you are looking at or the one you specified; add *nameOrID* *entityID*(optional) - Add the specified player to the entity list you are looking at or the one you specified; remove *nameOrID* *entityID*(optional) - Remove the specified player from the entity list you are looking at or the one you specified; toggle *entityID*(optional) - Toggle the entity list you are looking at or the one you specified; delete *entityID*(optional) - Delete the settings for the entity you are looking at or the one you specified; clear - Delete the settings for all your entities. team - Manage your team: ff - Toggle the ability to damage your teammates. vehicle - Manage your vehicles: list - List of IDs for all your vehicles; find *vehicleID*(optional) - Help finding the vehicle you are looking at or the one you specified; unlink *vehicleID*(optional) - Unlink the vehicle you are looking at or the one you specified; clear - Unlink all your vehicles. Admin commands(/adminpve). Permission "realpve.admin" required: autobuy - Manage autobuy for monuments, vanilla events and raid bases: *nameOrId* - Toggle autobuy for the specified player; force monument/event/rb - Toggle forced autobuy. If enabled, player settings will be ignored; clear - Disable autobuy for everyone. config - Manage settings for values in the configuration file: forcepve *boolValue*(optional) - Is it worth forcibly implementing PvE for a server? gametips *boolValue*(optional) - Is it worth enabling GameTips for messages? givemsg *boolValue*(optional) - Is it worth preventing the sending of 'Give' messages? resource_privilege *boolValue*(optional) - Is it worth preventing resource gathering in someone else's building privilege area? plant_privilege *boolValue*(optional) - Is it worth preventing the pickup of plants spawned by the server in someone else's building privilege zone? heli_damage *boolValue*(optional) - Is it worth forcibly blocking damage from the patrol helicopter to building blocks and deployables? handcuffs *boolValue*(optional) - Is it worth assigning portals(Halloween and Christmas) to the first player? portals *boolValue*(optional) - Is it worth preventing players from handcuffing others? backpack_drop *boolValue*(optional) - Is it worth preventing a backpack from dropping upon player death? laptop_damage *boolValue*(optional) - Is it worth preventing damage to the laptop of the Hackable Crate? recycler_safezone *boolValue*(optional) - Is it worth removing the penalties for recyclers in safe zones? item_pickup *boolValue*(optional) - Is it worth allowing all players to pick up items dropped by others? If enabled, personal settings will be ignored; priceformat *stringValue* - The format that will be used for prices; vehicle_marker_time *floatValue* - Vehicles - Time in seconds to display the marker when searching for a vehicle. A value of 0 disables the marker; antisleeper *floatValue* - Anti-Sleeper - Time in seconds after which a player will be killed if they disconnect while inside someone else's Building Privilege. Set to 0 to disable; randomraids *boolValue*(optional) - Is it worth enabling support for the 'Npc Random Raids' plugin? teamff *boolValue*(optional) - Is friendly fire enabled by default when creating a new team? pvpmarkers *boolValue*(optional) - PvP - Is it worth adding map markers for PvP zones? pvpmarkersname *stringValue* - PvP - Name of the map maker. loot - Manage player access to entities without restrictions: *nameOrId* - Toggle unrestricted access for the specified player; self - Toggle unrestricted access for yourself; clear - Revoke unrestricted access for all players. monument - Manage monuments: list - List of available monuments; *monumentID*/this - Instead of the monumentID, you can use the word "this", but you must be inside the monument: suffix *boolValue*(optional) - Toggle the suffix display in the monument's name; broadcast *boolValue*(optional) - Toggle notifications about monument occupancy/release; time *intValue* - Set the looting time limit for the monument in seconds; price *floatValue* - Set the cost for looting rights. A value of 0 makes the monument free; offer *floatValue* - Set the offer duration for purchasing the monument in seconds; map_mode *intValue* - Set the marker display mode on the map. 0 - disabled, 1 - enabled, 2 - enabled during PvP mode; map_circle *boolValue*(optional) - Toggle the display of the monument's circle marker on the map; pvp *boolValue*(optional) - Toggle PvP mode for the monument; pvp_delay *floatValue* - Set the PvP mode duration in seconds for players after leaving the PvP monument; bar_progress *boolValue*(optional) - Toggle between TimeProgressCounter and TimeCounter bars for the monument. perm - Manage permissions: add *permName* - Adds a new permission to the list by copying values from the first(default) permission in the list. If the permission name starts with 'realpve', it will also register a new permission; add *permName* *sourcePermName* - Adds a new permission to the list by copying values from an existing permission in the list; remove *permName* - Removes an existing permission from the list; edit *permName* - Edits a permission: queue - Toggle the permission to bypass the server queue; beds *intValue* - Restriction on the number of available beds; shelters *intValue* - Restriction on the number of available shelters; turrets *intValue* - Restriction on the number of available turrets; hackable *floatValue* - Number of seconds(0-900) to skip when opening a hackable crate; monuments *floatValue* - Price multiplier for monuments; events *floatValue* - Price multiplier for vanilla events; rb_limit *intValue* - Restriction on the number of raid bases available simultaneously; rb_mult *floatValue* - Price multiplier for raid bases; vehicles *vehType* - Vehicles settings: limit *intValue* - Limit on the number of available vehicles by type; price *floatValue* - Price for registering a vehicle by type. clear - Removes all permissions from the list except the first one. pickup - Manage access to picking up another player's items from the ground: *nameOrId* - Toggle access to picking up a specific player's items from the ground; clear - Revoke access for all players to pick up items from the ground. share - Manage access to looting entities by other players(outside of the team): status *entityID*(optional) - Display information about the settings of the entity you are looking at or the one you specified; add *nameOrID* *entityID*(optional) - Add the specified player to the entity list you are looking at or the one you specified; remove *nameOrID* *entityID*(optional) - Remove the specified player from the entity list you are looking at or the one you specified; toggle *entityID*(optional) - Toggle the entity list you are looking at or the one you specified; delete *entityID*(optional) - Delete the settings for the entity you are looking at or the one you specified; clear *nameOrID*(optional) - Delete the settings for all entities or all entities of the specified player. vehicle - List of all available vehicle types: types - List of available vehicle types. Example: /realpve pickup /realpve vehicle find *netID* /realpve team ff /adminpve perm add realpve.vip2 /adminpve perm add realpve.vip2 realpve.vip /adminpve perm edit realpve.vip2 queue true /adminpve perm edit realpve.vip2 vehicles horse limit 5 /adminpve monument list /adminpve monument *monumentID* pvp /adminpve monument *monumentID* price 7.5 /adminpve loot iiiaka /adminpve pickup iiiaka /adminpve vehicle types This plugin provides the ability to claim vehicles, thereby preventing theft and griefing from other players. In permissions, you can set the price and quantity restrictions for each type of vehicle, ensuring flexible customization according to your preferences. An assigned vehicle can't be damaged, looted or pushed by other players, but it can be pushed if it is within someone else's Building Privilege. File location: *SERVER*\oxide\data\RealPVE\MonumentConfig.json Default: https://pastebin.com/XY1d9YaM This plugin introduces queue system and loot purchases for monuments. You can customize the price and time for looting for each monument. Within monuments, only the "Looter" and his friends have the ability to loot, pick up items or damage entities. Additionally, NPCs and animals within monuments do not aggress against other players and do not receive damage from them. If a player dies within the monument, they will have a grace period to return. This allows players to safely loot monuments without fear of griefing. Example of monument configuration: "ferry_terminal_1": { "Type(This parameter is just a hint. Changes won’t have any effect)": "RadTown", "Time in seconds(1-15) given to respond for purchasing monument looting": 5.0, "ShowSuffix": true, "Broadcast": true, "PvP - Is PvP enabled at this monument? If so, players will be able to kill each other, and loot will be publicly accessible": false, "PvP - Sets the delay in seconds that a player remains in PvP mode after leaving a PvP monument. 0 disables the delay": 10.0, "PvP - Is it worth adding map markers for monuments if they are PvP zones?": true, "LootingTime": 900, "Price": 15.0, "Is it worth using a progress bar for bars with a counter?": true, "Settings for the status bar": { "Order": 10, "Height": 26, "Main_Color(Hex or RGBA)": "#FFBF99", "Main_Transparency": 0.8, "Main_Material": "", "Image_Url": "https://i.imgur.com/awUrIwA.png", "Image_Local(Leave empty to use Image_Url)": "RealPVE_ferry_terminal_1", "Image_Sprite(Leave empty to use Image_Local or Image_Url)": "", "Image_IsRawImage": false, "Image_Color(Hex or RGBA)": "#FFDCB6", "Image_Transparency": 1.0, "Is it worth enabling an outline for the image?": false, "Image_Outline_Color(Hex or RGBA)": "0.1 0.3 0.8 0.9", "Image_Outline_Transparency": 0.0, "Image_Outline_Distance": "0.75 0.75", "Text_Size": 12, "Text_Color(Hex or RGBA)": "1 1 1 1", "Text_Font(https://umod.org/guides/rust/basic-concepts-of-gui#fonts)": "RobotoCondensed-Bold.ttf", "Is it worth enabling an outline for the text?": false, "Text_Outline_Color(Hex or RGBA)": "#000000", "Text_Outline_Transparency": 1.0, "Text_Outline_Distance": "0.75 0.75", "SubText_Size": 12, "SubText_Color(Hex or RGBA)": "1 1 1 1", "SubText_Font": "RobotoCondensed-Bold.ttf", "Is it worth enabling an outline for the sub text?": false, "SubText_Outline_Color(Hex or RGBA)": "0.5 0.6 0.7 0.5", "SubText_Outline_Transparency": 0.0, "SubText_Outline_Distance": "0.75 0.75" }, "Settings for the progress status bar": { "Main_Color(Hex or RGBA)": "1 1 1 0.15", "Main_Transparency": 0.15, "Progress_Reverse": true, "Progress_Color": "#FFBF99", "Progress_Transparency": 0.7, "Progress_OffsetMin": "0 0", "Progress_OffsetMax": "0 0" } } Type - This field serves only as an indicator for you. The changes won't have any impact; ShowSuffix - Suffix display. Some monuments (for example Warehouses) have suffixes in the name, like "Warehouse #12"; Broadcast - Enabling or disabling broadcasts when a monument is occupied or vacated; LootingTime - Time allocated for looting the monument; Price - The price for which you can start looting the monument. 0 means looting is free; BarSettings - Settings for the Advanced Status Bar. You can also choose the types of monuments by specifying them under the "List of tracked types of monuments" section. A list of all available types can be viewed on the MonumentsWatcher's page in the "Developer API" section. "List of tracked types of monuments": [ "RadTown", "RadTownWater", "RadTownSmall", "TunnelStation", "Custom" ] Events, similar to monuments, offer the opportunity to claim events. All events are configured in the config file under the "Settings for the events" section. You can customize the price of looting and looting attempts(deaths, including friends). Just like in monuments, only the "Looter" and his friends have the ability to loot and damage entities. Additionally, in events, NPCs do not aggress against other players. If a player(including friends) exceeds the death limit, the event became free, thereby providing other players with the opportunity to claim the event. Example of event configuration: { "Settings for the PatrolHelicopter events": { "IsEnabled": true, "Time in seconds (1-15) given to respond for purchasing this event. Note: This is shown to everyone who deals damage, and the first person to buy it will claim it": 5.0, "Is it worth removing fire from crates?": true, "The price to capture the event. 0 means the event is free": 50.0, "The number of deaths after which the event becomes public": 5 }, "Settings for the BradleyAPC events": { "IsEnabled": true, "Time in seconds (1-15) given to respond for purchasing this event. Note: This is shown to everyone who deals damage, and the first person to buy it will claim it": 5.0, "Is it worth removing fire from crates?": true, "The price to capture the event. 0 means the event is free": 50.0, "The number of deaths after which the event becomes public": 5 }, "Version": { "Major": 0, "Minor": 1, "Patch": 0 } } Price - The price to claim the event. 0 means looting is free; DeathLimit - Limit of deaths after which the event becomes free. File location: *SERVER*\oxide\data\RealPVE\NewbieConfig.json Default: https://pastebin.com/QHZCqpji An example of an item list given for the main inventory: "List of items for the main inventory": [ { "ShortName": "note", "Slot": 0, "Amount": 1, "SkinID": 0, "Text": "MsgNoteText" } ] P.S. In the Text field, you need to specify the language key. Or, you can just write any text, but there won't be a translation of the text. File location: *SERVER*\oxide\data\RealPVE\RaidableBasesConfig.json Default: https://pastebin.com/rpDng7Fd Integration with the RaidableBases plugin does not restrict its functionality in any way. On the contrary, it adds an anti-grief system that protects bases from malicious players. In raid bases, NPCs and other entities can only receive damage from the raid owner or their friends; Turrets and traps do not aggress against outsiders; You can customize the price of claiming to each difficulty and set individual discounts for each permission. You can still purchase raid bases using the /buyraid command. Raid bases without owners(buyable, maintained, manual and scheduled) can be bought for a price set in the configuration file or assigned to the first player who enters its radius, if the final price(price * discount) less or equals to 0. Additionally, as a bonus, upon buying this plugin, you receive 5 free bases for 3 difficulty levels, along with configured loot for them. [PluginReference] private Plugin RealPVE; There are 6 universal hooks that the plugin is subscribed to, the use of which allows interaction with PVP in various PVE plugins: OnPlayerEnterPVP OnPlayerExitPVP OnEntityEnterPVP OnEntityExitPVP CreatePVPMapMarker DeletePVPMapMarker OnPlayerEnterPVP: Used to add a player to PVP mode/zone. To call the OnPlayerEnterPVP hook, you need to pass 2 parameters: <BasePlayer>player - The player to add to PVP; <string>zoneID - A unique identifier for your PVP zone. This parameter is very important because a player can be in multiple PVP zones at the same time and passing the zoneID in this case allows for correct processing of the player's location within them. Interface.CallHook("OnPlayerEnterPVP", player, "*Your unique zone identifier*");//Calling the OnPlayerEnterPVP hook to tell PVE plugins that the player needs to be added to the specified PVP zone. OnPlayerExitPVP: Used to remove a player from PVP mode/zone. Calling this hook guarantees the player’s removal from the specified PVP zone, but does not guarantee the removal from PVP mode, as there may be other zones in addition to yours. Also, when a player dies, they are automatically removed from all PVP zones. To call the OnPlayerExitPVP hook, you need to pass 3 parameters, 1 of which is optional: <BasePlayer>player - The player to remove from PVP; <string>zoneID - A unique identifier for your PVP zone; <float>pvpDelay - Optional. When the player exits your PVP zone, you can also pass the PVP delay time. However, if the player still has other active PVP zones, your PVP delay will not take effect. Interface.CallHook("OnPlayerExitPVP", player, "*Your unique zone identifier*", 10f);//Calling the OnPlayerExitPVP hook to tell PVE plugins that the player needs to be removed from the specified PVP zone, with the pvpDelay(10 seconds) specified if the player no longer has any active PVP zones. OnEntityEnterPVP: Used to add an entity to PVP mode/zone. In the case of RealPVE, this hook is only necessary to add entities with an owner(player) to a PVP, allowing other players to interact with them, such as a player's corpse after death(PlayerCorpse) or a backpack after the corpse disappears(DroppedItemContainer). To call the OnEntityEnterPVP hook, you need to pass 2 parameters: <BaseEntity>entity - The entity to add to PVP; <string>zoneID - A unique identifier for your PVP zone. Interface.CallHook("OnEntityEnterPVP", entity, "*Your unique zone identifier*");//Calling the OnEntityEnterPVP hook to tell PVE plugins that the entity needs to be added to the specified PVP zone. OnEntityExitPVP: Used to remove an entity from PVP mode/zone. When an entity dies, it is automatically removed from all PVP zones. To call the OnEntityExitPVP hook, you need to pass 3 parameters, 1 of which is optional: <BaseEntity>entity - The entity to remove from PVP; <string>zoneID - A unique identifier for your PVP zone; <float>pvpDelay - Optional. When the entity exits your PVP zone, you can also pass the PVP delay time. However, if the entity still has other active PVP zones, your PVP delay will not take effect. Interface.CallHook("OnEntityExitPVP", entity, "*Your unique zone identifier*", 10f);//Calling the OnEntityExitPVP hook to tell PVE plugins that the entity needs to be removed from the specified PVP zone, with the pvpDelay(10 seconds) specified if the entity no longer has any active PVP zones. CreatePVPMapMarker: Used to create a map marker for the PVP zone. To call the CreatePVPMapMarker hook, you need to pass 5 parameters, 2 of which is optional: <string>zoneID - A unique identifier for your PVP zone; <Vector3>pos - The position of your PVP zone; <float>radius - The radius of the circle for your PVP zone; <string>displayName - Optional. The display name for the map marker; <BaseEntity>entity - Optional. The entity to which the map marker should be attached. Interface.CallHook("CreatePVPMapMarker", "*Your unique zone identifier*", pos, 25f, "ATTENTION! This is a PVP zone!");//Calling the CreatePVPMapMarker hook to tell PVE plugins to create a map marker for the specified zone, at the specified position with the given radius, but without specifying a parent entity. DeletePVPMapMarker: Used to delete a map marker for the PVP zone. To call the DeletePVPMapMarker hook, you need to pass only 1 parameter: <string>zoneID - A unique identifier for your PVP zone. Interface.CallHook("DeletePVPMapMarker", "*Your unique zone identifier*");//Calling the DeletePVPMapMarker hook to tell PVE plugins to delete a map marker for the specified zone. There are 5 hooks that the plugin calls: OnPlayerPVPDelay OnPlayerPVPDelayed OnPlayerPVPDelayRemoved OnZoneStatusText CanRedeemKit OnPlayerPVPDelay: Called when a player exits the last active PVP zone, allowing other plugins to overwrite the value for pvpDelay. Returning a float value allows changing the pvpDelay for the player. A value less than zero disables the pvpDelay. When calling the OnPlayerPVPDelay hook, 3 parameters are passed: <BasePlayer>player - The player to whom the pvpDelay is applied; <float>pvpDelay - The initial value of pvpDelay; <string>zoneID - A unique identifier of PVP zone. object OnPlayerPVPDelay(BasePlayer player, float pvpDelay, string zoneID) { Puts($"Attempting to set a PvP delay of {pvpDelay} seconds for player {player.displayName} in zone {zoneID}!"); if (zoneID == "*Your unique zone identifier*") { return 15f;//Overriding the values for pvpDelay } return null;//Leave unchanged } OnPlayerPVPDelayed: Called after the PVP delay has been set for the player. When calling the OnPlayerPVPDelayed hook, 3 parameters are passed: <BasePlayer>player - The player to whom the pvpDelay is applied; <float>pvpDelay - The value of pvpDelay; <string>zoneID - A unique identifier of PVP zone. void OnPlayerPVPDelayed(BasePlayer player, float pvpDelay, string zoneID) { Puts($"A PvP delay of {pvpDelay} seconds has been set for player {player.displayName} in zone {zoneID}!"); } OnPlayerPVPDelayRemoved: Called when the PVP delay is removed from the player after they enter a PVP zone with an active PVP delay. When calling the OnPlayerPVPDelayRemoved hook, only 1 parameter is passed: <BasePlayer>player - The player from whom the PVP delay has been removed. void OnPlayerPVPDelayRemoved(BasePlayer player) { Puts($"PVP delay has been removed for player {player.displayName} as they entered a PVP zone!"); } OnZoneStatusText: Called when the text with the nice name for the specified zone is needed, to be displayed in the status bar. When calling the OnZoneStatusText hook, 2 parameters are passed: <BasePlayer>player - The player for whom the nice name for the zone is being requested; <string>zoneID - A unique identifier of PVP zone. object OnZoneStatusText(BasePlayer player, string zoneID) { Puts($"Text for the status bar is required for zone {zoneID}"); if (zoneID == "*Your unique zone identifier*") { return lang.GetMessage("*langKey*", this, player.UserIDString);//<string>Overriding the value for the status bar text } return null;//Leave unchanged } CanRedeemKit: Called before giving the starter kit, in the OnDefaultItemsReceive hook. A non-zero value cancels this action. When calling the CanRedeemKit hook, only 1 parameter is passed: <BasePlayer>player - The player to whom the kit is being attempted to be given. object CanRedeemKit(BasePlayer player) { Puts($"Attempting to give the kit to player {player.displayName}!"); if (player.IsAdmin) { return false;//Cancel the action } return null;//Leave unchanged }

NoEscape stands out as a robust solution to control rust players raiding & combat actions. As an innovative plugin for Rust, offering a range of unique features along with a visually appealing overlay. It provides 10 different colors for customization and a visible dome adjuster, enhancing user interaction. This plugin is designed to deliver optimal performance while maintaining backward compatibility with the free NoEscape from umod ensuring a smooth transition. Features Twig Building Ignorance: The plugin intelligently ignores twig buildings, preventing griefers from exploiting the raid/combat block system during simple base construction. Door Shooting Logic: Shooting a door outside the predefined radius won't trigger a raid block, even if the door is destroyed. Reliability and Compatibility Reload Behavior: Reloading NoEscape clears all existing raid/combat blocks. Team and Clan Support: Compatible with Teams & Clans, especially beneficial when used with the Auto Team plugin(umod clans). Removal Tools Support: Fully compatible with remove tools within the game or plugins. Command Blocking: Offers optional command blocking. Commands can be specified to block only for raids ("shop": 1) or combat ("shop": 2), or both ("shop": 3). Health/Regen Logic for Raids: Optional feature to manage health and regeneration of building blocks during raids / base building. Sound Effects: Option to include sound effects for enhanced user experience. UI System: Implements a user interface specifically for raid & combat scenarios that includes complete customization support. Hud Preset Positions: ( 0 Left Top | 1 Left Bottom | 2 Right Top | 3 Right Bottom | 4 Custom ) Combat-Blocking Logic: Combat-blocking is only active when not in a raid-blocked state. This not only saves on performance but also improves the gameplay experience. Raid-Block Self-Ignorance: Prevents raid-blocking on one's own buildings. MLRS Support: Yes, but only the vanilla ones launched by the vehicle on the map are supported, 3rd party plugins are not. Fire Damage Logic: If a wooden (but not twig) base takes fire damage, it triggers a raid. Damage Source Ignorance: Ignores non-player damage and buildings set to owner ID 0 by third-party plugins. Visual Enhancements: Color Support for Spheres: Adds color customization options for the visible spheres. Visualization Level Setter: Allows users to set the level of visualization for easier navigation and interaction. In conclusion, NoEscape provides a comprehensive and robust solution for Rust players, offering a blend of unique features, compatibility, and visual enhancements to elevate the gaming experience. Permissions noescape.admin Allows you to use the console / F1 command "newcolor" for changing the Raid overlay settings in game. Also allows you to use the console / F1 command "noescape" for allowing to raid your self or trigger combat block on npcs. Command newcolor <1-10> <0-8> -- first number is the color setting, second number is the sphere darkness level. noescape or noescape steamID Need to trigger raids on your self or combat block for NPCs? For testing! Use the new noescape command! Example: F1 menu Type "noescape" in game to toggle for your self. Example: F1 menu or server-console Type "noescape steamID" to toggle for someone else. Requires the noescape.admin perm to use in game. Configuration { "Specify commands to block ( 3 = Block Both | 1 = Block Raid | 2 = Block Combat )": { "shop": 3, "tp": 3 }, "User Interface": { "Switch to sprite instead of Icon?": false, "Sprite string Default: assets/icons/explosion.png": "assets/icons/explosion.png", "Sprite Color Default: 0.95 0 0.02 0.67": "0.95 0 0.02 0.67", "Enable Raid UI": true, "Raid Icon (Item ID Default: 1248356124) 0 = None": 1248356124, "Raid Skin ID (Skin ID Default: 0) 0 = None": 0, "Enable Combat UI": true, "Combat Icon (Item ID Default: 1545779598) 0 = None": 1545779598, "Combat Skin ID (Skin ID Default: 0) 0 = None": 0, "Hud Preset Positions: ( 0 Left Top | 1 Left Bottom | 2 Right Top | 3 Right Bottom | 4 Custom )": 0, "Hud Transparency Default: #, 0.1f": { "Hex": "#", "Rgb": "0 0 0 0.1" }, "Text Color Default: #09ff00": { "Hex": "#46ff36", "Rgb": "0.0352941176470588 1 0 1" }, "Text Font Size Default: 13": 13, "Hex or RGB toggle (Default is Hex)": false, "Custom UI POS: Key is anchorMin | Value is anchorMax": { "Hud": { "Key": "0.345 0.11", "Value": "0.465 0.14" }, "Icon": { "Key": "0 0", "Value": "0.13 1" }, "Text": { "Key": "0.15 0", "Value": "1 1" } } }, "Combat Block": { "Enable Combat Block?": true, "Block Time (Min)": 1, "Exclude Steam 64IDs": [] }, "Raid Block": { "Enable Raid Block?": true, "Raid Block player until death instead of distance checks or zones. + 'Optional' timer setting in seconds Default: 0.0 = disabled.": { "Die": false, "Time": 0.0 }, "Block Time (Sec)": 300.0, "Block Radius": 100.0, "Damaged Health Percentage on an entity to trigger a raid (0 = disabled)": 0, "Sphere Visibility (Recommend 3 or 5, 0 = disabled)": 3, "Sphere Color (0 = none, 1 = Blue, 2 = Cyan, 3 = Green, 4 = Pink, 5 = Purple, 6 = Red, 7 = White, 8 = Yellow, 9 = Turquoise, 10 = Brown)": 4, "Enable Random Sphere Colors? (Randomly selects a new color each time a raid block is triggered)": false, "Allow Upgrade or Block?": true, "Override facepunches default repair wait time after being attacked? Default: 30sec": 30, "Enable Base Building Block Features": true }, "Building (None = Doors, VendingMachine, ShopFront)": { "None": { "Raid Blocked Building Spawned Health Percentage": 35, "Health Regen Rate (Sets how fast it gens the health every x(Sec)": 1.0, "Regen Amount (0 = Disabled Sets how much to regen every x(Sec)": 20.0, "After Being Attacked Regen Time (Sec)": 30.0 }, "Twigs": { "Raid Blocked Building Spawned Health Percentage": 10, "Health Regen Rate (Sets how fast it gens the health every x(Sec)": 1.0, "Regen Amount (0 = Disabled Sets how much to regen every x(Sec)": 1.0, "After Being Attacked Regen Time (Sec)": 30.0 }, "Wood": { "Raid Blocked Building Spawned Health Percentage": 20, "Health Regen Rate (Sets how fast it gens the health every x(Sec)": 1.0, "Regen Amount (0 = Disabled Sets how much to regen every x(Sec)": 20.0, "After Being Attacked Regen Time (Sec)": 30.0 }, "Stone": { "Raid Blocked Building Spawned Health Percentage": 30, "Health Regen Rate (Sets how fast it gens the health every x(Sec)": 1.0, "Regen Amount (0 = Disabled Sets how much to regen every x(Sec)": 25.0, "After Being Attacked Regen Time (Sec)": 30.0 }, "Metal": { "Raid Blocked Building Spawned Health Percentage": 40, "Health Regen Rate (Sets how fast it gens the health every x(Sec)": 1.0, "Regen Amount (0 = Disabled Sets how much to regen every x(Sec)": 30.0, "After Being Attacked Regen Time (Sec)": 30.0 }, "TopTier": { "Raid Blocked Building Spawned Health Percentage": 50, "Health Regen Rate (Sets how fast it gens the health every x(Sec)": 1.0, "Regen Amount (0 = Disabled Sets how much to regen every x(Sec)": 40.0, "After Being Attacked Regen Time (Sec)": 30.0 } }, "Upgrading only works for BuildingBlocks": { "Twigs": { "Raid Blocked Upgrading Spawned Health Percentage": 10, "Health Regen Rate (Sets how fast it gens the health every x(Sec)": 1.0, "Regen Amount (0 = Disabled Sets how much to regen every x(Sec)": 1.0, "After Being Attacked Regen Time (Sec)": 30.0 }, "Wood": { "Raid Blocked Upgrading Spawned Health Percentage": 20, "Health Regen Rate (Sets how fast it gens the health every x(Sec)": 1.0, "Regen Amount (0 = Disabled Sets how much to regen every x(Sec)": 20.0, "After Being Attacked Regen Time (Sec)": 30.0 }, "Stone": { "Raid Blocked Upgrading Spawned Health Percentage": 30, "Health Regen Rate (Sets how fast it gens the health every x(Sec)": 1.0, "Regen Amount (0 = Disabled Sets how much to regen every x(Sec)": 25.0, "After Being Attacked Regen Time (Sec)": 30.0 }, "Metal": { "Raid Blocked Upgrading Spawned Health Percentage": 40, "Health Regen Rate (Sets how fast it gens the health every x(Sec)": 1.0, "Regen Amount (0 = Disabled Sets how much to regen every x(Sec)": 30.0, "After Being Attacked Regen Time (Sec)": 30.0 }, "TopTier": { "Raid Blocked Upgrading Spawned Health Percentage": 50, "Health Regen Rate (Sets how fast it gens the health every x(Sec)": 1.0, "Regen Amount (0 = Disabled Sets how much to regen every x(Sec)": 40.0, "After Being Attacked Regen Time (Sec)": 30.0 } }, "Sound Effects": { "RaidStart": "assets/bundled/prefabs/fx/takedamage_hit.prefab", "CombatSart": "assets/bundled/prefabs/fx/kill_notify.prefab", "RaidEnd": "assets/prefabs/building/door.hinged/effects/vault-metal-close-end.prefab", "CombatEnd": "assets/prefabs/building/door.hinged/effects/vault-metal-close-end.prefab", "Denied": "assets/prefabs/weapons/toolgun/effects/repairerror.prefab" }, "Message Responses": { "ChatIcon": 0, "RaidBlocked": "You are now <color=#00FF00>raid blocked</color>! For <color=#00FF00>{0}</color>!", "UnRaidBlocked": "You are <color=#00FF00>no longer</color> raid blocked.", "CombatBlocked": "You are <color=#00FF00>combat blocked</color> For <color=#00FF00>{0}</color>.", "UnCombatBlocked": "You are <color=#00FF00>no longer</color> combat blocked.", "CommandBlocked": "Access Denied: Cannot use <color=#FFA500>'{0}'</color> command during <color=#FFA500>{1}</color>: <color=#FFA500>{2}</color>", "ActionBlocked": "Denied: Cannot <color=#FFA500>{0}</color> while <color=#FFA500>raid blocked</color>", "RepairBlocked": "Unable to repair: Recently damaged. Repairable in: " } } API Hooks Useful to force quit 3rd party plugin actions when players trigger Combat/Raid Blocks. private void OnCombatBlock(BasePlayer player) private void OnRaidBlock(BasePlayer player) Useful for checking commands, etc, before allowing a player to do something private bool IsCombatBlocked(BasePlayer player) | IsCombatBlocked(string player) | IsCombatBlocked(ulong player) private bool IsRaidBlocked(BasePlayer player) | IsRaidBlocked(string player) | IsRaidBlocked(ulong player) private bool IsEscapeBlocked(BasePlayer player) | IsEscapeBlocked(string player) | IsEscapeBlocked(ulong player)

Transform your Rust map with dynamic wormholes that open up thrilling new possibilities for players! This plugin introduces randomly spawning, paired wormholes that create instant portals between two locations on the map. Randomized Spawns: Wormholes appear at random intervals, based on configurable timer ranges. Paired Portals: Each wormhole is linked to another, allowing seamless teleportation between the two. Customizable Settings: Time Limits: Control how long wormholes remain active. Usage Limits: Set how many times a wormhole can be used before it despawns. Condition Restrictions: Prevent players from using wormholes when they are Bleeding Starving Dehydrated Cold/Hot Wounded Irradiated Escape/Raid/Combat blocked Spice up gameplay, encourage exploration, and create chaotic or strategic opportunities for your players to interact with the world in new ways. Perfect for servers looking to add a touch of unpredictability and fun! Command: wormhole.spawn <grid coordinate> <grid coordinate> Type: Chat Permission: wormholes.admin Description: Forces a pair of wormholes to spawn in each grid coordinate. For example wormhole.spawn b2 c5 would spawn a wormhole in a random location in b2, with the other side of the wormhole at a random location in c5. Both coordinates need to contain valid spawn points. Command: whgrid Type: Chat Permission: wormholes.admin Description: Draws all valid spawn positions that the plugin has cached to the user. Requires level 1 auth. Command: dbwh Type: Chat Permission: wormholes.admin Description: Debugs all active wormholes on the map. Draws lines between each wormhole pair.

Set sail and conquer the waves with our thrilling Ship Bases package! Immerse yourself in a unique Rust experience with our floating bases designed to challenge even the most daring players From majestic galleons to fearsome pirate ships, each base offers a new adventure waiting to be discovered in the vast ocean of possibilities. Our RustBase package offers you a wide range of challenges and thrills as you explore the turbulent waters and fight to establish your dominance on the high seas. With key features like unique designs, strategic challenges, and a variety of difficulties, this package is designed to take your Rust gaming experience to the next level. In addition to providing hours of entertainment, our floating bases are the perfect setting for exciting showdowns and clever strategies. From surprise ambushes to epic naval battles, every encounter at sea offers an opportunity to prove your worth as the ultimate leader. Are you ready to brave the storms and claim your place as the undisputed master of the oceans in Rust? Get our RustBase package today and make your empire in Rust legendary! 3 Easy bases 3 Medium bases 5 Hard bases 5 Expert bases 2 Nightmare bases ++ all instructions for setting it up indoors If you need to contact me send me a private message or write me on Discord. rustbases_11012 .

Offline Raid Limiter Stop Unfair Offline Raids in Their Tracks Tired of seeing your Rust server overrun by offline raid abuse? Offline Raid Limiter steps in to restore balance and fair play. With powerful tracking and immediate damage blocking, your players can enjoy a more authentic Rust experience—and you can enjoy worry-free server management. Key Benefits Prevent Offline Raid Abuse Daily Raid Limit: Automatically restrict how many offline raids each player (or team) can perform per day. Proximity-Based Tracking: Only counts raids when attackers are within range of a Tool Cupboard (TC), ensuring offline raid limits don’t trigger prematurely. Smart Raid Session Management Team & Additional Raider Tracking: Keeps tabs on individual players as well as entire teams—even if they leave and rejoin. Plus, if additional players jump into the same raid, their involvement is recorded. Edge Case Handling: No more confusion or gaps in coverage if a defender goes offline mid-raid or when multiple attackers are involved. Offline Raid Limiter’s robust logic sorts out these scenarios seamlessly. Instant Damage Blocking Enforce Fair Play: Once a team or individual hits their daily offline raid quota, further damage is blocked automatically. That means no more sneaky workarounds or unstoppable raids. Modded Server UI In-Game Control: For modded servers, gain access to a simple in-game UI that displays raid history, player statistics, and real-time session data. Player-Friendly Features: Grant permissions so your players can check their offline raid counts with the /myraids command—helping everyone stay within the rules. Detailed Alerts & Reporting Discord Integration: Offline Raid Limiter sends comprehensive alerts to Discord, making admin oversight a breeze. Export & Clear Sessions: Use /exportraidsessions to log and share your entire raid history for deeper analysis, then wipe all sessions with a simple console command if you need a fresh start. Designed for Vanilla & Modded Servers Flexible Configuration: If you set your server to “Vanilla,” the plugin automatically disables UI and direct damage blocks, limiting itself to Discord notifications so admins can monitor raiding behind the scenes. Seamless Integration: Works hand-in-hand with Rust’s existing frameworks and requires only the Simple Status & Image Library for certain UI elements. Why Choose Offline Raid Limiter? Enhanced Fairness: Players can’t take shortcuts with offline raids for easy loot. Clear Oversight: Admins see exactly who’s raiding and how often, helping you enforce balanced gameplay. Configurable & User-Friendly: Tailor the plugin to your server’s needs in just a few clicks, with plenty of documentation to guide you. If you’re ready to level the playing field and protect your community from unfair offline raids, Offline Raid Limiter has you covered. Bring your Rust server to new heights of balance, transparency, and peace of mind! OfflineRaidLimiter_FullDocumentation_Updated.zip Commands & Usage Damage Blocking & Clearing Sessions clearraidsessions Console command: clearraidsessions Usage: Immediately removes all saved offline raid sessions. Purpose: Useful for resetting the entire raid history if you’ve made big changes or just need a fresh start. clearraidsforplayer <SteamID64> Console command: clearraidsforplayer <SteamID64> Usage: Removes every offline raid session associated with a specific player (and their team). Notes: Handy for admins who need to give a particular player or group a second chance. simulatecleanup Console command: simulatecleanup Usage: Triggers the plugin’s internal cleanup routine on demand to remove expired sessions. Notes: Essentially forces the “scheduled” cleanup to run right away for testing or maintenance. Exporting Raid Data exportraidsessions Console command: exportraidsessions Usage: Exports a JSON file of all existing raid sessions and sends it to the Discord debug webhook for easy admin review. Notes: Great for deeper analysis or archiving raid history. Damage / Raid Logic OfflineRaidLimiter checks incoming damage to building blocks, doors, external walls, and more. If a team or player has exceeded the daily offline raid limit, all further damage to offline bases is blocked—and you can optionally broadcast an alert to Discord. Key Points to Note About Commands Some commands differ depending on your permissions and server setup. For instance, if a player types /exportraidsessions in chat, it won’t work unless they have OfflineRaidLimiter.admin. For “Vanilla” servers (as set in the config), UI, damage blocking, and certain other features may be disabled—so commands like clearraidsessions and clearraidsforplayer will still work, but may only be visible to server admins via console. When Commands Might Defer Cleanup Commands: If the plugin detects that some raid sessions are still “cooling down” (meaning the raid window hasn’t fully expired), the system may defer clearing them until the next pass. This prevents conflicts with currently active raids. Blocking Logic: After the daily limit is reached, the blocking triggers immediately and remains in place until the next server reset or cleanup routine (depending on how you configure it).

Create fully automated raidable bases with NPCs in Rust 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 or bases 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. 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. 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 There are just a few steps required to get bases spawn on your server within minutes. 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. 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 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) 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 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 (0 = easy, 1 = medium, 2 = hard, 3 = expert, 4 = nightmare) (0) - 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 - DO NOT GIVE THIS TO THE DEFAULT GROUP LOL 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: 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 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 will populate specific loot tables with every item in the game (items are disabled by default as their amounts are set to 0) Arguments: rb.populate easy medium hard expert nightmare loot all Arguments: rb.populate 0 1 2 3 4 loot all easy - Populates oxide/data/RaidableBases/Editable_Lists/Easy.json medium - Populates oxide/data/RaidableBases/Editable_Lists/Medium.json hard - Populates oxide/data/RaidableBases/Editable_Lists/Hard.json expert - Populates oxide/data/RaidableBases/Editable_Lists/Expert.json nightmare - Populates oxide/data/RaidableBases/Editable_Lists/Nightmare.json loot - Populates oxide/data/RaidableBases/Editable_Lists/Default_Loot.json all - Populates ALL above loot tables Configure the items to your liking then copy the files contents into a loot table that you would like to use (for example Difficulty Loot/Easy.json) You cannot use loot tables in the config file anymore. Use the data directory (oxide/data/RaidableBases) 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 bases for you. 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.

Are you looking to expand your Raidable Bases TrapBox collection with Easy Bases? We have the perfect solution for you! Introducing our set of 40 easy-difficulty bases, specifically designed to enhance your collection. Perfect for beginners and those who enjoy a more relaxed experience ! rb.config add "Easy Bases" e-1 e-2 e-3 e-4 e-5 e-6 e-7 e-8 e-9 e-10 e-11 e-12 e-13 e-14 e-15 e-16 e-17 e-18 e-19 e-20 e-21 e-22 e-23 e-24 e-25 e-26 e-27 e-28 e-29 e-30 e-31 e-32 e-33 e-34 e-35 e-36 e-37 e-38 e-39 e-40

Here is some bases i made that can be used in Raidable Bases.. Noob bases - 5 Easy bases - 7 Medium bases - 15 Hard bases - 15 Extreme bases - 10 Total - 52 Bases.

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.

20 Easy Raidable Bases – Perfect for Beginners! This pack includes 20 pre-built bases designed to provide a fun and straightforward raiding experience. Perfect for players looking for an easy challenge or practice runs! Mix yourself – find more bases on my profile! Features: Wooden doors and wooden walls for a classic, simple design. Ready to use and ideal for both new and experienced raiders. Need help or have suggestions? Join the community on Discord: discord.gg/4j3FvSYAFd

Defend your home.. well.. defend what's left of it! Welcome to an epic new event where the players will defend their bases against waves of Frankenraiders! They will use any weapons they have available to try to raid your base. Some will come with whatever they can swing at you and your base, some will just try to defend their kin, some have found some heavy weaponry too! I think that one has a rocket launcher?! Description To launch the event first you must find a flare bright enough to attract their attention. You'll be able to find flares bright enough to attract an Easy Frankenraid in Bradley, Elite, Military, and Supply crates. When you've found a flare just toss it on or near the base within Tool Cupboard range. Once you successfully defend an Easy Frankenraiding party, you will be rewarded with a flare bright enough for a Medium party. Then upon defending successfully against a Medium raid, well if you really want to risk your wipe being wiped by a full Frankenraider party, then you will have earned a flare bright enough to attract a Hard Frankenraid! When you complete any difficulty level and are able to defend your base, a chinook will be sent to your location with rewards for your service to the island in clearing out the threat! If your base is destroyed, the event ends, chat notifications are sent, and there you stand in shame. Hopefully you're on a low pop server and not too many people noticed. It's okay champ, happens to the best of us some days! Just keep an eye on the in game UI like the timer and wave information to give yourself the best shot at keeping your base standing! There are various ways to configure this plugin to customize it for your server, for any level and number of players. The creativity is in your hands with the configuration file as well as your communities wants or needs. The loot table, the flare spawns, the different enemy types and their setups, everything is there for you to customize this if you so choose. Dependencies (optional, not required) True PVE GUI Announcements Notify AlphaLoot CustomLoot Base Repair Chat commands /defstop - in game command to end event in your current Tool Cupboard range (be near the event you are trying to end) - only for administrators! /checkfoundations - checks all the foundations of the house for the event (it is necessary to be inside the Cupboard area of the house) ⊘ - you or your friends are not the owner of the foundation ⊝ - the foundation does not match in height/depth ⊛ - the foundation does not match the topology (prohibited topologies: Cliff, Cliffside, Decor, Building, Monument, Clutter, Mountain) ◉ - the foundation is located within a radius of 40 meters from the custom monument Console commands (RCON only) giveflare {skinid} {steamid} - Console command to give a custom flare with a Steam Workshop SkinID ({skinid}) to a player using their SteamID ({steamid}) Plugin Config en - example of plugin configuration in English ru - example of plugin configuration in Russian My Discord: KpucTaJl#8923 Join the Mad Mappers Discord here! Check out more of my work here! Creator of the default configuration – jtedal Help in creating a plugin description – Jbird

Copypaste raid base usable via raidable bases plugins.

The Offline Raid Protection plugin is a comprehensive solution designed to protect players' structures and vehicles while they are offline. It offers a range of customisable protection levels based on real-time or the length of time a player has been offline, and integrates with the Clans plugin and the in-game teams feature to determine protection status based on the online status of all clan or team members and authorised players. Key Features Configurable Protection Levels: Set protection levels based on real time or the amount of time since a player went offline. For example, a building can have 100% protection one hour after a player goes offline, and 50% protection after two hours. This feature is highly configurable. Clan/Team Integration: The plugin integrates with the Clans plugin and the in-game teams feature. The protection status of a structure or vehicle is determined by the online status of all clan or team members and authorised players. Penalty System: An optional penalty system is implemented to prevent abuse of the protection feature. For example, if a player leaves a clan or team, a penalty can be applied to all members and protection can be disabled for a configurable period of time. Game Tip Messages: The plugin displays game tip messages to players when they hit a protected structure or vehicle. The message includes the percentage of protection and is colour coded according to the level of protection. It supports all the languages available in Rust. Commands: Players with permission can use commands to check the protection status of other players, change the offline time of other players, and change the penalty status. Cache System: The plugin uses a caching system to optimise performance and keep the impact on the server to a bare minimum. Configuration: The plugin includes a configuration file that allows you to customise the behaviour of the plugin. Commands All commands can be configured. /orp or /ao <steam id or full name> — Check a player's offline protection status. You can type the command without a name when looking at a player's structure. /raidprot — Display offline raid protection information. /orp.fill.onlinetimes — Fill all players offline times. (Chat & Console command) /orp.test.offline <steam id or full name> <hours> — Change a player's offline time. /orp.test.online <steam id or full name> — Change a player's offline time to the current time. /orp.test.penalty <steam id or full name> <hours> — Change the duration of a player's penalty. A negative value or zero would disable the penalty. /orp.update.permission — Update the permissions status (offlineraidprotection.protect) for all players. orp.update.prefabs <true> - Updates the 'Prefabs to protect' list in the configuration. Overwrites the list with the 'true' argument. (Console command) orp.dump.prefabs - Clears the 'Prefabs to protect' list in the configuration. (Console command) Permissions All permissions can be configured. offlineraidprotection.protect — Allows a player to be protected from raids. offlineraidprotection.check — Allows a player to check the offline protection status of other players. offlineraidprotection.admin — Allows a player to use all admin commands of the plugin. To grant a permission, use carbon/oxide.grant <user or group> <steamname or ID> <permission>. To revoke a permission, use carbon/oxide.revoke <user or group> <steamname or ID> <permission>. Configuration The configuration is to a large extent self-explanatory. Raid Protection Options Only mitigate damage caused by players: Choose whether or not to only mitigate damage caused directly by players. Protect players that are online: Choose whether or not to protect the bases of the players who are online. Works when "Scale of damage depending on the current hour of the real day" is configured. Scale of damage depending on the current hour of the real day: Defines the protection levels based on the current hour of the real day. The key is the hour of the day (0-23), and the value is the protection scale (0 — 340282300000000000000000000000000000000). Example: "0": 0.0, "1": 0.0, "2": 0.0, "3": 0.0 This means that the protection level is 100% from midnight to 3am. Scale of damage depending on the offline time in hours: Defines the protection levels based on the time since the player went offline. The key is the number of hours since the player went offline, and the value is the protection scale (0 — 340282300000000000000000000000000000000). The value of the hours can also be a decimal number. Example: "12": 0.25, "24": 0.5, "48": 1.0, "96": 2.0 This means that 12 hours after the player goes offline, the protection level will be 75%. After 24 hours it will be 50% and after 48 hours it will be 0%. After 96 hours, the damage is increased by 200%. Cooldown in minutes: During this time, damage levels will remain vanilla. Raids are possible. Scale of damage between the cooldown and the first configured time: During this time, the level of damage between the cooldown and the first configured time can be set to a specific value, such as 0.0 Online time to qualify for offline raid protection in minutes: Time to qualify for offline raid protection after a player connects Protect all prefabs: Choose whether to protect all prefabs or only specific ones. This will protect anything in the TC range. Protect AI (animals, NPCs, Bradley and attack helicopters etc.) if 'Protect all Prefabs' is enabled: Choose whether or not to protect AI entities if "Protect all Prefabs" is enabled. May cause high hook times if set to true. Protect vehicles: Choose whether to protect vehicles or not. Vehicle authorisation always has priority. If you want to exclude certain vehicles from protection, add them to the blacklist. Protect twigs: Choose whether to protect twigs or not. Prefabs to protect: List of prefabs that will be protected. Make sure you remove the prefabs you don't want to protect, some of them are pointless. Prefabs blacklist: List of prefabs that will not be protected. Prefabs in the blacklist will always have priority to be unprotected. Timezone Options The fallback timezone is UTC if you leave it blank in the configuration, or if your configured timezone doesn't exist. The timezone identifiers are different for Windows and Linux. You can check the appendices to find your preferred timezone. Conclusion: The Offline Raid Protection plugin provides a comprehensive solution for protecting players' structures and vehicles when they are offline. This plugin is essential for any Rust server owner who wants to provide a fair and enjoyable gaming experience for their players. Acknowledgments Special thanks to @Kulltero for his valuable feedback and suggestions during the development of this plugin. Windows_Timezones.txt Linux_Timezones.txt Prefabs.txt

In the "Bases" Folder you will find 60 bases total that you can add to your server. They are ranked easy, medium, hard, expert and nightmare. They are all Unique and fun to raid. There are simple raid bases like you would see on a normal rust server. But there are alot of maze / puzzle bases in there, with secret loot rooms and hidden tc's. Watch out for the special traps that are placed, on places you wouldn't care to look! Never a doll moment when you see one of my raidbases, they are all tested on an active server and everyone loves to see my raidbases. You can't go wrong with this pack! 6 Easy 9 Medium 18 Hard 16 Expert 11 Nightmare Loot Tables: As said on Raidable Bases plugin you need your own 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. These are al made on Enchanted.gg server. Made with for pluggins: https://umod.org/plugins/copy-paste

hello this pack of base contain all types of base from the easy to the hard (bunker, 2x1 ...etc) to expert ( with turret and electricité) some bases contain the new skin designe there is about 36 base bightmare and 30 metal and other stone if you need any help contacte me on discord just put the files in copypaste folder and you could spawn it with this command /paste name height number name ---> name of file base height ---> height of the base from map

Warning: To use this bases pack, you need to purchase the paid Raidable Bases plugin if you do not already own it: https://codefling.com/plugins/raidable-bases This package is produced by the fullwiped & xrust.co servers. This is a configuration file that contains 110 bases designed by us, ranging from easy to nightmare difficulty levels. Warning: This package does not include loot tables. If you need bases + loot tables, you may want to check out the higher-tier package: Raibable Bases + Loot Tables package This Raidable Bases package includes: - 30 Easy Bases - 30 Medium Bases - 30 Hard Bases - 10 Expert Bases - 10 Nightmare Bases With a total of 110 bases, this package focuses on simplicity and optimization. Most bases are protected by turrets and traps, and each base is designed with player PC performance and server stability in mind. Additional Features: A configuration JSON file (optional for your use, at your discretion) Five profile configuration JSON files located in data/RaidableBases/Profiles (optional, but saves time by adding all 110 bases without needing individual console commands) If you need a more comprehensive package that includes loot tables along with the bases pack, you may want to check out this product as well: INSTALLATION INSTRUCTIONS: I recommend two installation options: 1) First Option: If you have never installed Raidable Bases before, you can simply copy all the files from the downloaded "oxide" folder to your server. I strongly recommend this method because I have made several adjustments to prevent issues, such as bases embedding underground, ensuring they spawn at sea level, and removing Arena walls and NPCs. If you want to use your own configuration, check the second option below. 2) Second Option: If you already have existing Raidable Bases or wish to avoid modifying your configuration and profile files, you’ll need to add the new bases using commands. Open the console with F1 and use these commands to save the new bases to your existing profile configuration in /serverfiles/oxide/data/RaidableBases/Profiles. Example command: rb.config add "Easy Bases" fullwipedeasy1 Second example command: rb.config add "Easy Bases" fullwipedeasy2 Summary of Commands to Add New Bases: rb.config add "Easy Bases" fullwipedeasy1 fullwipedeasy2 fullwipedeasy3 fullwipedeasy4 fullwipedeasy5 fullwipedeasy6 fullwipedeasy7 fullwipedeasy8 fullwipedeasy9 fullwipedeasy10 fullwipedeasy11 fullwipedeasy12 fullwipedeasy13 fullwipedeasy14 fullwipedeasy15 fullwipedeasy16 fullwipedeasy17 fullwipedeasy18 fullwipedeasy19 fullwipedeasy20 fullwipedeasy21 fullwipedeasy22 fullwipedeasy23 fullwipedeasy24 fullwipedeasy25 fullwipedeasy26 fullwipedeasy27 fullwipedeasy28 fullwipedeasy29 fullwipedeasy30 rb.config add "Medium Bases" fullwipedmed1 fullwipedmed2 fullwipedmed3 fullwipedmed4 fullwipedmed5 fullwipedmed6 fullwipedmed7 fullwipedmed8 fullwipedmed9 fullwipedmed10 fullwipedmed11 fullwipedmed12 fullwipedmed13 fullwipedmed14 fullwipedmed15 fullwipedmed16 fullwipedmed17 fullwipedmed18 fullwipedmed19 fullwipedmed20 fullwipedmed21 fullwipedmed22 fullwipedmed23 fullwipedmed24 fullwipedmed25 fullwipedmed26 fullwipedmed27 fullwipedmed28 fullwipedmed29 fullwipedmed30 rb.config add "Hard Bases" fullwipedhard1 fullwipedhard2 fullwipedhard3 fullwipedhard4 fullwipedhard5 fullwipedhard6 fullwipedhard7 fullwipedhard8 fullwipedhard9 fullwipedhard10 fullwipedhard11 fullwipedhard12 fullwipedhard13 fullwipedhard14 fullwipedhard15 fullwipedhard16 fullwipedhard17 fullwipedhard18 fullwipedhard19 fullwipedhard20 fullwipedhard21 fullwipedhard22 fullwipedhard23 fullwipedhard24 fullwipedhard25 fullwipedhard26 fullwipedhard27 fullwipedhard28 fullwipedhard29 fullwipedhard30 rb.config add "Expert Bases" fullwipedexp1 fullwipedexp2 fullwipedexp3 fullwipedexp4 fullwipedexp5 fullwipedexp6 fullwipedexp7 fullwipedexp8 fullwipedexp9 fullwipedexp10 rb.config add "Nightmare Bases" fullwipednight1 fullwipednight2 fullwipednight3 fullwipednight4 fullwipednight5 fullwipednight6 fullwipednight7 fullwipednight8 fullwipednight9 fullwipednight10 If you do not want to add 110 bases one by one, you can perform a clean installation using the first method. However, this will overwrite all config settings in your existing Profiles folder, from "easy" to "nightmare" bases. Be sure to back up your files before proceeding. About Base Spawn Locations: If you are using the optional profile config we provide, Easy and Medium bases are configured to spawn near the map's center, while Hard, Expert, and Nightmare bases are set to spawn near coastal areas. This is intended to ensure bases spawn on flatter terrain, avoiding issues with the new rock mechanics that can embed bases into the ground. However, as bases spawning near water may occasionally cause issues in some coastal areas, this setting is left to personal preference for customization. If you'd like to adjust this, you can edit the profiles located in: /home/serverfiles/oxide/data/RaidableBases/Profiles Change "Force All Bases To Spawn At Height Level (0 = Water)" from 0.0 to -1.0 using a text editor. "Force All Bases To Spawn At Height Level (0 = Water)": -1.0, If you're confident that you've successfully uploaded all the files, enter the following command in RCON to restart the plugin and apply the changes. Good luck: o.reload RaidableBases Support: FULLWIPED DISCORD

Raidable Bases Pack 3 Features 10 Medium Bases All bases have boxes, furnaces, lockers, bags, drop boxes, vending machines, and more inside so you don't have to populate the loot locations yourself! Installation Instructions 1. Extract the files in the `Bases` folder into your `oxide/data/copypaste` folder. Do not copy the folder itself into the copypaste folder, just the files. 2. Run the following commands in your console. This will import the files into your Raidable Bases plugin with the appropriate difficulty levels. Run each line below as its own command. If you have purchased any of my other packs, there is no reason to rename any of the files as each file has a unique name associated with the base. rb.config add "Medium Bases" BCF-Medium-1 BCF-Medium-2 BCF-Medium-3 BCF-Medium-4 BCF-Medium-5 BCF-Medium-6 BCF-Medium-7 BCF-Medium-8 BCF-Medium-9 BCF-Medium-10 For a more detailed guide on how to use Raidable Bases please visit Rust Admin Academy's YouTube video which can be found here: https://www.youtube.com/watch?v=KgWgtnmOXiw

Raidable Bases Pack 2 Features 10 Easy Bases All bases have boxes, furnaces, lockers, bags, drop boxes, vending machines, and more inside so you don't have to populate the loot locations yourself! Installation Instructions 1. Extract the files in the `Bases` folder into your `oxide/data/copypaste` folder. Do not copy the folder itself into the copypaste folder, just the files. 2. Run the following commands in your console. This will import the files into your Raidable Bases plugin with the appropriate difficulty levels. Run each line below as its own command. If you have purchased any of my other packs, there is no reason to rename any of the files as each file has a unique name associated with the base. rb.config add "Easy Bases" BCF-Easy-1 BCF-Easy-2 BCF-Easy-3 BCF-Easy-4 BCF-Easy-5 BCF-Easy-6 BCF-Easy-7 BCF-Easy-8 BCF-Easy-9 BCF-Easy-10 For a more detailed guide on how to use Raidable Bases please visit Rust Admin Academy's YouTube video which can be found here: https://www.youtube.com/watch?v=KgWgtnmOXiw

Features So many turrets it'll make your head spin! Theres a ton of weird and unique features to this base to ensure that your players have the maximum amount of fun! The Castle has boxes, furnaces, lockers, bags, drop boxes, vending machines, and more inside so you don't have to populate the loot locations yourself! Installation Instructions 1. Extract the files in the `Bases` folder into your `oxide/data/copypaste` folder. Do not copy the folder itself into the copypaste folder, just the files. 2. Run the following commands in your console. This will import the files into your Raidable Bases plugin with the appropriate difficulty levels. Run each line below as its own command. If you have purchased any of my other packs, there is no reason to rename any of the files as each file has a unique name associated with the base. rb.config add "Nightmare Bases" Nightmare-The-Castle For a more detailed guide on how to use Raidable Bases please visit Rust Admin Academy's YouTube video which can be found below! https://www.youtube.com/watch?v=KgWgtnmOXiw

Features 5 Easy Bases 5 Medium Bases 5 Hard Bases All bases have boxes, furnaces, lockers, bags, drop boxes, vending machines, and more inside so you don't have to populate the loot locations yourself! Installation Instructions 1. Extract the files in the `Bases` folder into your `oxide/data/copypaste` folder. Do not copy the folder itself into the copypaste folder, just the files. 2. Run the following commands in your console. This will import the files into your Raidable Bases plugin with the appropriate difficulty levels. Run each line below as its own command. If you have purchased any of my other packs, there is no reason to rename any of the files as each file has a unique name associated with the base. ``` rb.config add "Easy Bases" BCF-Easy-1 BCF-Easy-2 BCF-Easy-3 BCF-Easy-4 BCF-Easy-5 rb.config add "Medium Bases" BCF-Medium-1 BCF-Medium-2 BCF-Medium-3 BCF-Medium-4 BCF-Medium-5 rb.config add "Hard Bases" BCF-Hard-1 BCF-Hard-2 BCF-Hard-3 BCF-Hard-4 BCF-Hard-5 ``` For a more detailed guide on how to use Raidable Bases please visit Rust Admin Academy's YouTube video which can be found below! https://www.youtube.com/watch?v=KgWgtnmOXiw

Raidable Base Medium Pack include 40 Raidable Bases with traps bases include all necessary items to have a Good Raid, don't wait and Boost your Raidable Base Rotation with these nice medium bases Rb.config add "Medium Bases" M-1 M-2 M-3 M-4 M-5 M-6 M-7 M-8 M-9 M-10 M-11 M-12 M-13 M-14 M-15 M-16 M-17 M-18 M-19 M-20 M-21 M-22 M-23 M-24 M-25 M-26 M-27 M-28 M-29 M-30 M-31 M-32 M-33 M-34 M-35 M-36 M-37 M-38 M-39 M-40

Optional Dependency Raidable Bases - https://codefling.com/plugins/raidable-bases Optional Dependency Custom Loot - https://codefling.com/plugins/custom-loot How To Call In Random Raids Randomly calls in npc raids with options for Mlrs and Attack Hele Set a configurable timer and chance to auto call in raid With Raidable bases plugin set a chance with configurable options for the npc's to come back and attack the raiders at one of there bases. After a certain amount of npc kills have a random chance. With item found in loot containers or given in shops by admins. SEE ALL CONFIG SETTINGS! Chat Command - Permission = randomraids.admin /randomraid -- Will display command usage. /randomraid item list - will display list of raid item for admin to give them self. /randomraid item <type> - example config types = easy, medium, hard Server command randomraid <playerid> <type> - Gives player raid item to start a raid. { "Random settings": { "GUI AnchorMin": "0.807 0.96", "GUI AnchorMax": "0.996 0.99", "GUI2 AnchorMin": "0.807 0.92", "GUI2 AnchorMax": "0.996 0.95", "GameTip display time in seconds": 2.0, "Total raids allowed at once": 10, "A player on the tc must be online": true, "Use random raid timer": false, "Random raid timer time": 3600, "Chance of random raid at time (1-100)": 10, "Authorized players Cooldown minutes before random raided again by chance": 1440, "The maximum amount of time a rocket will fly before exploding": 4.0, "Npc spawn damage delay": 2.0, "Display global chat message on raid start": true, "Display global map marker on raid start": true, "Display Gui to base owners": false, "Use GameTip announcement to player": false, "Disable radio chatter": false, "Wait until all NPC are dead before sending in next wave": false, "Player must have randomraids.use inorder to get raided": false, "Use world text to show base location": false, "World text display time": 60.0, "Use discord Webhook": false, "Discord Webhook URL": "", "Discord Avatar URL": "http://images.myvector.xyz/discordimage.png" }, "All Random Raid Types": { "Random raid types": { "easy": { "Total auth players on tc needed": 1, "Total npcs per wave": 10, "How many extra waves": 1, "Seconds untell next wave": 120, "Npc fires Mlrs at base": false, "Send in Attack Copter support": false, "Total event time in seconds": 640, "Npc drop loot on death": true, "Spawn health of the npc": 100.0, "Total rockets npc can fire": 20, "Total explosives npc can toss": 10, "Total AirDrops on event win": 1, "Rocket damage scale": 1.0, "Player damage scale from npc": 1.0, "Auto turret damage scale to npc": 1.0, "Raiders aimConeScale": 2.0, "Throw Explosive item shortnames": [ "explosive.timed", "explosive.satchel" ], "Spawn Attack Heli profile": [ "easy" ], "Spawn kits for the npcs": [], "Names to give the npcs": [ "Cobalt Scientist" ], "CustomLoot config profile name": [], "CustomLoot config profile names for AirDrop": [], "AlphaLoot config profile names": [], "AlphaLoot config profile names for AirDrop": [], "Juggernaut config": [ "easy" ], "Surrender costs": 200 }, "medium": { "Total auth players on tc needed": 2, "Total npcs per wave": 15, "How many extra waves": 1, "Seconds untell next wave": 120, "Npc fires Mlrs at base": false, "Send in Attack Copter support": true, "Total event time in seconds": 900, "Npc drop loot on death": true, "Spawn health of the npc": 200.0, "Total rockets npc can fire": 20, "Total explosives npc can toss": 10, "Total AirDrops on event win": 1, "Rocket damage scale": 1.0, "Player damage scale from npc": 1.0, "Auto turret damage scale to npc": 1.0, "Raiders aimConeScale": 2.0, "Throw Explosive item shortnames": [ "explosive.timed", "explosive.satchel" ], "Spawn Attack Heli profile": [ "easy" ], "Spawn kits for the npcs": [], "Names to give the npcs": [ "Cobalt Scientist" ], "CustomLoot config profile name": [], "CustomLoot config profile names for AirDrop": [], "AlphaLoot config profile names": [], "AlphaLoot config profile names for AirDrop": [], "Juggernaut config": [ "easy" ], "Surrender costs": 400 }, "hard": { "Total auth players on tc needed": 3, "Total npcs per wave": 20, "How many extra waves": 1, "Seconds untell next wave": 120, "Npc fires Mlrs at base": false, "Send in Attack Copter support": true, "Total event time in seconds": 1200, "Npc drop loot on death": true, "Spawn health of the npc": 400.0, "Total rockets npc can fire": 20, "Total explosives npc can toss": 10, "Total AirDrops on event win": 1, "Rocket damage scale": 1.0, "Player damage scale from npc": 1.0, "Auto turret damage scale to npc": 1.0, "Raiders aimConeScale": 2.0, "Throw Explosive item shortnames": [ "explosive.timed", "explosive.satchel" ], "Spawn Attack Heli profile": [ "easy" ], "Spawn kits for the npcs": [], "Names to give the npcs": [ "Cobalt Scientist" ], "CustomLoot config profile name": [], "CustomLoot config profile names for AirDrop": [], "AlphaLoot config profile names": [], "AlphaLoot config profile names for AirDrop": [], "Juggernaut config": [ "easy" ], "Surrender costs": 600 }, "expert": { "Total auth players on tc needed": 4, "Total npcs per wave": 30, "How many extra waves": 1, "Seconds untell next wave": 120, "Npc fires Mlrs at base": false, "Send in Attack Copter support": true, "Total event time in seconds": 1500, "Npc drop loot on death": true, "Spawn health of the npc": 400.0, "Total rockets npc can fire": 20, "Total explosives npc can toss": 10, "Total AirDrops on event win": 1, "Rocket damage scale": 1.0, "Player damage scale from npc": 1.0, "Auto turret damage scale to npc": 1.0, "Raiders aimConeScale": 2.0, "Throw Explosive item shortnames": [ "explosive.timed", "explosive.satchel" ], "Spawn Attack Heli profile": [ "easy" ], "Spawn kits for the npcs": [], "Names to give the npcs": [ "Cobalt Scientist" ], "CustomLoot config profile name": [], "CustomLoot config profile names for AirDrop": [], "AlphaLoot config profile names": [], "AlphaLoot config profile names for AirDrop": [], "Juggernaut config": [ "medium" ], "Surrender costs": 800 }, "nightmare": { "Total auth players on tc needed": 5, "Total npcs per wave": 30, "How many extra waves": 1, "Seconds untell next wave": 120, "Npc fires Mlrs at base": false, "Send in Attack Copter support": true, "Total event time in seconds": 2100, "Npc drop loot on death": true, "Spawn health of the npc": 400.0, "Total rockets npc can fire": 20, "Total explosives npc can toss": 10, "Total AirDrops on event win": 1, "Rocket damage scale": 1.0, "Player damage scale from npc": 1.0, "Auto turret damage scale to npc": 1.0, "Raiders aimConeScale": 2.0, "Throw Explosive item shortnames": [ "explosive.timed", "explosive.satchel" ], "Spawn Attack Heli profile": [ "easy" ], "Spawn kits for the npcs": [], "Names to give the npcs": [ "Cobalt Scientist" ], "CustomLoot config profile name": [], "CustomLoot config profile names for AirDrop": [], "AlphaLoot config profile names": [], "AlphaLoot config profile names for AirDrop": [], "Juggernaut config": [ "medium" ], "Surrender costs": 1000 } } }, "AttackCopter profiles": { "Profile Names": { "easy": { "Heli float health": 1000.0, "Total crates to drop": 2, "Heli strafe cooldown": 50.0, "Heli can strafe x times": 3 } } }, "Block Random raid in colider": { "Blocked": [ "iceberg", "ice_berg", "ice_sheet", "icesheet", "cliff", "cave" ] }, "Raidable Base plugin settings": { "Raid player on Raidable Base Completed": false, "Warn player in chat of upcoming revenge on them": false, "Raidable Base Settings": { "0": { "Total amount of mode complete before ever has chance": 3, "Reset kill count after chance happened": false, "Raidable Base Completed Delay Before Raid chance happens": 320.0, "raid chance (1-100)": 10, "Random raid to send them if chance": [ "easy" ] }, "1": { "Total amount of mode complete before ever has chance": 3, "Reset kill count after chance happened": false, "Raidable Base Completed Delay Before Raid chance happens": 320.0, "raid chance (1-100)": 10, "Random raid to send them if chance": [ "easy", "medium" ] }, "2": { "Total amount of mode complete before ever has chance": 3, "Reset kill count after chance happened": false, "Raidable Base Completed Delay Before Raid chance happens": 320.0, "raid chance (1-100)": 10, "Random raid to send them if chance": [ "easy", "medium" ] }, "3": { "Total amount of mode complete before ever has chance": 3, "Reset kill count after chance happened": false, "Raidable Base Completed Delay Before Raid chance happens": 320.0, "raid chance (1-100)": 10, "Random raid to send them if chance": [ "easy", "medium", "hard" ] }, "4": { "Total amount of mode complete before ever has chance": 3, "Reset kill count after chance happened": false, "Raidable Base Completed Delay Before Raid chance happens": 320.0, "raid chance (1-100)": 10, "Random raid to send them if chance": [ "hard", "expert", "nightmare" ] } } }, "Trigger by npc kills": { "Enable log kills and random raid on kills": false, "Reset npc kills on player raided.": false, "Warn player in chat of upcoming revenge on them": false, "Use total players on tc check on type": false, "Enable combine npc kills list": false, "Combine npc kills list": [ "scientistnpc_patrol", "scientistnpc_oilrig", "scientistnpc_heavy", "sentry.scientist.barge", "sentry.scientist.barge.static", "sentry.scientist.static", "heavyscientist_youtooz.deployed", "ch47scientists.entity", "scientist_corpse", "scientistnpc_arena", "scientistnpc_cargo", "scientistnpc_cargo_turret_any", "scientistnpc_cargo_turret_lr300", "scientistnpc_ch47_gunner", "scientistnpc_excavator", "scientistnpc_full_any", "scientistnpc_full_lr300", "scientistnpc_full_mp5", "scientistnpc_full_pistol", "scientistnpc_full_shotgun", "scientistnpc_junkpile", "sientistnpc_peacekeeper", "scientistnpc_roam", "scientistnpc_roam_nvg_variant", "scientistnpc_roamtethered", "npc_tunneldweller", "npc_tunneldwellerspawned", "npc_underwaterdweller", "scarecrow" ], "Combine Profile to use": { "Total amount of Npc killed before chance can happen": 70, "Reset kill count after chance happened": false, "Delay before chance happens": 320.0, "Raid chance (1-100)": 10, "Cooldown minutes before chance can happen again": 1440, "Random raid to send them if chance": [ "easy" ] }, "Npc kills settings": { "scientistnpc_heavy": { "Total amount of Npc killed before chance can happen": 30, "Reset kill count after chance happened": false, "Delay before chance happens": 320.0, "Raid chance (1-100)": 10, "Cooldown minutes before chance can happen again": 1440, "Random raid to send them if chance": [ "medium" ] }, "scientistnpc_oilrig": { "Total amount of Npc killed before chance can happen": 60, "Reset kill count after chance happened": false, "Delay before chance happens": 320.0, "Raid chance (1-100)": 10, "Cooldown minutes before chance can happen again": 1440, "Random raid to send them if chance": [ "easy" ] }, "scientistnpc_patrol": { "Total amount of Npc killed before chance can happen": 60, "Reset kill count after chance happened": false, "Delay before chance happens": 320.0, "Raid chance (1-100)": 10, "Cooldown minutes before chance can happen again": 1440, "Random raid to send them if chance": [ "easy" ] }, "scientistnpc_junkpile": { "Total amount of Npc killed before chance can happen": 60, "Reset kill count after chance happened": false, "Delay before chance happens": 320.0, "Raid chance (1-100)": 10, "Cooldown minutes before chance can happen again": 1440, "Random raid to send them if chance": [ "easy" ] } } }, "Juggernaut profiles": { "easy": { "Juggernaut spawns on witch Wave number/Total to spawn": { "1": 1 }, "Spawn health of the juggernaut": 500.0, "Player damage scale from the juggernaut": 1.0, "juggernaut aimConeScale": 2.0, "Names to give the juggernaut": [ "Juggernaut Raider" ], "Spawn kits for the juggernaut": [] }, "medium": { "Juggernaut spawns on witch Wave number/Total to spawn": { "1": 2 }, "Spawn health of the juggernaut": 700.0, "Player damage scale from the juggernaut": 1.0, "juggernaut aimConeScale": 2.0, "Names to give the juggernaut": [ "Juggernaut Raider" ], "Spawn kits for the juggernaut": [] } }, "Item profiles": { "easy": { "Raid call item skin": 2893480896, "Raid call item name": "Npc Raid Level 1", "LootContainer Spawn enabled": false, "Can Spawn In LootContainer types": [ "crate_normal", "crate_normal_2" ], "LootContainer Spawn Chance 1-100": 5.0 }, "medium": { "Raid call item skin": 2893480635, "Raid call item name": "Npc Raid Level 2", "LootContainer Spawn enabled": false, "Can Spawn In LootContainer types": [ "crate_normal", "crate_normal_2", "heli_crate" ], "LootContainer Spawn Chance 1-100": 5.0 }, "hard": { "Raid call item skin": 2893481009, "Raid call item name": "Npc Raid Level 3", "LootContainer Spawn enabled": false, "Can Spawn In LootContainer types": [ "bradley_crate", "crate_elite" ], "LootContainer Spawn Chance 1-100": 5.0 }, "expert": { "Raid call item skin": 2893481137, "Raid call item name": "Npc Raid Level 4", "LootContainer Spawn enabled": false, "Can Spawn In LootContainer types": [ "bradley_crate", "crate_elite" ], "LootContainer Spawn Chance 1-100": 5.0 }, "nightmare": { "Raid call item skin": 2893482048, "Raid call item name": "Npc Raid Level 5", "LootContainer Spawn enabled": false, "Can Spawn In LootContainer types": [ "bradley_crate", "crate_elite" ], "LootContainer Spawn Chance 1-100": 5.0 } }, "Version": { "Major": 1, "Minor": 7, "Patch": 7 } }

Featuring two dynamic events, this plugin introduces cargo drones that spawn at random monuments and raid drones that patrol the island, targeting and destroying unprotected bases. Enhance your gameplay with these exciting drone encounters. This plugin also adds C4 Drones and Anti Drone Turrets to the game. Features: Raid Drone Event: Drones patrol the island and attack unprotected bases. Loot Drone Event: Drones with loot boxes appear at random monuments and can be shot down. Player controlled C4 Drone: Players can craft a bomb drone and detonate it remotely through a computer station. Anti-Drone Turret: Players can craft Anti-Drone Turrets to protect their bases from raid drones while offline. Fully customizable Anti Drone Turrets: Can be used to protect your base from raid drones and C4 Drones. They require homing missile ammo to function. C4 Drones: Can be controlled by players and used to raid player bases. They can be detonated from the computer station. Commands: raiddrones - Spawn raid drone swarm at current position lootdrones - Spawn loot drones at current position antidrone.give <?amount> <?player> - Give Anti Drone Turret to the specified player (player and amount can be omitted) bombdrone.give <?amount> <?player> - Give C4 Drone to the specified player (player and amount can be omitted) Permissions: droneraiders.admin - Required to use event commands droneraiders.give - Required to use give commands Items: Anti Drone Turret: Command: antidrone.give <?amount> <?player> Shortname: box.wooden ItemId: -180129657 SkinId: 1220840269 Bomb Drone: Command: bombdrone.give <?amount> <?player> Shortname: drone ItemId: 1588492232 SkinId: 3241799978 This plugin supports the Loot Api and Custom Items Api of https://codefling.com/plugins/loot-table-stacksize-gui