Search the Community

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. 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 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 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": 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": 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 command": "realpve", "Chat admin command": "adminpve", "Is it worth forcibly implementing PvE for a server?": true, "Is it worth forcing the tutorial mode support?": true, "Is it worth enabling GameTips for messages?": true, "Is it worth rechecking the limits when removing permissions?": true, "Is it worth preventing death on logout in safe zones?": true, "Is it worth preventing the pickup of plants spawned by the server in someone else's building privilege zone?": false, "Is it worth forcibly blocking damage from the patrol helicopter to building blocks and deployables?": false, "Is it worth preventing players from handcuffing others?": true, "Is it worth assigning portals(Halloween and Christmas) to the first player?": 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, "Is it worth allowing all players to pick up items dropped by others? If enabled, personal settings will be ignored": false, "Is it worth protecting sleeping players from animals?": true, "List of forbidden resource gathering types in someone else's building privilege area. 0 - no restrictions, 1 - trees, 2 - ores, 3 - flesh": [ 1, 2, 3 ], "The format that will be used for prices": "${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, "Is it worth enabling support for the 'Npc Random Raids' plugin?": true, "List of language keys for creating language files(excluding ru)": [ "en" ], "Is friendly fire enabled by default when creating a new 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": 21 } } 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? forcetutorial *boolValue*(optional) - Is it worth forcing the tutorial mode support? gametips *boolValue*(optional) - Is it worth enabling GameTips for messages? perm_limits *boolValue*(optional) - Is it worth rechecking the limits when removing permissions? safe_death *boolValue*(optional) - Is it worth preventing death on logout in safe zones? 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; safe_sleep *boolValue*(optional) - Is it worth protecting sleeping players from animals? loot_privilege *stringValues* - Entities spawned by the server allowed to be looted in someone else's building privilege zone(None, Wood, Ore, Flesh, Collectible, All) ; 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; ignore *nameOrID* *boolValue* - Add or remove a player from the monument entry ignore list; *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; unlockRespawn - Toggle the availability of the Outpost respawn point; 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. tc - Manage building privilege: add self/*entityID* *nameOrID*(optional) - Add yourself or a specified player to the building privilege of the area you or the specified entity are in; remove self/*entityID* *nameOrID*(optional) - Remove yourself or a specified player from the building privilege of the area you or the specified entity are in; clear self/*entityID* - Clear the list of authorized players in the building privilege of the area you or the specified entity are in; info self/*entityID* - Get information about the building privilege of the area you or the specified entity are in. vehicle - List of all available vehicle types: types - List of available vehicle types. Example: /realpve pickup /realpve vehicle find *netID* /realpve team ff /adminpve config loot_privilege wood, ore /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 tc info self /adminpve tc info 6959689 /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 and NPCs 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", "Is it worth displaying the suffix(if any) in the monument's name?": true, "Is it worth notifying all players about the occupation/release of the monument?": true, "The cost for the right to loot the monument. A value of 0 makes the monument free": 15.0, "The time in seconds(1-3600) given for looting the monument": 900, "The time in seconds(1-15) given to make a decision to purchase the monument": 5.0, "Map marker display mode: 0 - disabled, 1 - enabled, 2 - enabled during PvP mode": 1, "Is it worth creating a circle in the map marker?": 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 - The time in seconds(0-60) during which the player retains PvP mode after leaving the PvP monument": 10.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: { "Is it worth enabling forced auto-buy for vanilla events where the final price is greater than 0?": false, "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 claim the event. A value of 0 means it's free": 50.0, "The number of deaths after which the event becomes public. A value of 0 disables the limit": 5, "The time in seconds for which the event is locked to the player. A value of 0 disables the time limit": 1800.0 }, "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 claim the event. A value of 0 means it's free": 50.0, "The number of deaths after which the event becomes public. A value of 0 disables the limit": 5, "The time in seconds for which the event is locked to the player. A value of 0 disables the time limit": 1800.0 }, "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 }

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. Key Features Control PVE Rules from in-game or in the config Easy to understand each rule Create PVP Schedules Loot prevention Automatic PVE/PVP purge events Zone Manager support Most event plugins support Works without "server.pve true" Discord Embed Messages on PurgeStart or End Many more features are added with every update Commands /simplepve - Use to enable or disable pve toggle (Chat & Console command) /simplepve on or off - Use to enable disable pve (Chat & Console command) /sprules - Use to Open a Cui to control PVE Rules & Creating Schedules (Chat command) /spdebug - Use this for debuging rules Permissions simplepve.admin - Required to enable or disable SimplePVE simplepve.adminloot - Required to view Loots of other players simplepve.admindamage - Required for Admin damages to any entity Video Showcase API & Hooks void OnSPVEPurgeStarted() void OnSPVEPurgeEnded() TimeSpan GetPVPStartTimeRemaining() TimeSpan GetPVPEndTimeRemaining() Configurations Support Check Out My Other plugins as Well

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. Modular Boat and Tugboat protection: These can optionally be protected just like player bases. 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. Enable this to prevent players from causing base damage by baiting patrol helicopters, etc. 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. Set this to a positive value to discourage defenders from interrupting raids by logging off. 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 Set this to a positive value to discourage players from quickly logging on and back off solely to reset protection. 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. Set to false to reduce hook times, and to avoid protecting wild animals that wander by offline bases. Protect modular and tug boats: Choose whether to protect modular boats and tugboats and their deployables. Checks wheel authorisation list, plus optionally lock authorisation lists. Protect vehicles: Choose whether to protect vehicles or not. Vehicle lock authorisation always has priority. If you want to exclude certain vehicles from protection, add them to the blacklist. Tugboats and modular boats are separate from this. Protect twigs: Choose whether to protect twigs or not. Protect decaying buildings: Choose whether to protect buildings that are either decaying, or have at least 50% of building blocks below 90% health. Ignore decay if due solely to twig: Choose whether to ignore decay state caused solely due to the presence of twig building blocks combined with a lack of wood in the TC. Set to true to ensure raiders cannot disable protection by building twig onto an offline base. 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. 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

Create fully automated raidable bases with NPCs in Rust NOT compatible with server.pve when set to true. Use a PVE plugin like TruePVE if you want PVE protection. This is the premium version of Raidable Bases. The differences between this and the free version are too many to list. A few key differences are: five (5) difficulties and associated loot table functionality instead of one (1), buyable events, lockouts for players. Requires latest version of CopyPaste. This plugin does NOT come with any bases. Packages are sold separately that include bases. Check out my packages for this plugin for tier1, tier2, and tier3 which contain everything you need to get the plugin working in minutes with all bases and loot already configured for you! Packages are sold separately. Facepunch TOS Disclaimer: The Facepunch Terms of Service have been updated to explicitly prohibit servers from enabling players to access Facepunch-approved DLC content or cosmetic skins through any method other than those officially provided by vanilla Rust (e.g., legitimate crafting or ownership-based unlocking mechanisms). This plugin includes built-in configuration options—enabled by default—that are designed to assist servers in maintaining compliance with this policy. Modification, disabling, or circumvention of these safeguards may place the server in breach of Facepunch's Terms of Service. By using this plugin, server operators acknowledge and accept full responsibility for any alterations made to its configuration, and the developer assumes no liability for any misuse, policy violations, or enforcement actions resulting therefrom. You should independently ensure that any prohibited content—such as unauthorized DLC items or restricted skins—is removed from your server files. Do not rely solely on this plugin or any third-party tool for compliance. The developer assumes no liability for servers found in violation due to misconfiguration, oversight, or failure to remove such content manually. You can add unapproved (non-paid) skins manually to your ImportedWorkshopSkins.json file found in the Profiles directory, which has an example provided already. Profiles in Oxide are located in the folder: oxide/data/RaidableBases/Profiles Profiles in Carbon are located in the folder: carbon/data/RaidableBases/Profiles ninco90 has created a tool to help with this. At the time of this posting, he’s still actively working on this, so please be patient while he fixes issues with it. https://app.rustspain.com/facepunch/checkitems RBE DEBUG This command exists to aid with issues regarding your configuration, profiles and/or map by displaying information, both good and bad, related to finding spawn points and spawning of bases. It is your responsibility to use this command before asking for help. Loot Table Editor by @beee https://codefling.com/tools/raidable-bases-boats-loot-editor/ heya, I can't say without your config file. TL;DR, it's likely your config as your map has an abundance of available spawn points given how flat some of the areas on your map are. you've likely changed the biome settings, or have forced everything elsewhere. Shop Plugins TL;DR: A shop/store plugin will not be supported unless they sell at zero cost. Otherwise players can pay and get blocked by RB cooldowns/restrictions with no possible refund. Price at 0, run the command, let RB charge/refund. The buyraid command handles all payments from players and purchases from plugins. RaidableBases has multiple cooldowns and restrictions that can make a purchase invalid and block it. If a shop plugin handles payment, and RaidableBases then blocks the purchase due to a cooldown or restriction, the player will not be refunded: The shop plugin does not know the purchase failed, so it cannot refund. RaidableBases did not see or handle the payment, so it cannot refund either. Because of that, the shop must sell the event for free (0) and only trigger the purchase command. RaidableBases must handle charging and refunds internally without exception. If a shop plugin cannot sell at zero cost it will not be supported. Supported method: Set the cost in the RaidableBases config Set the shop price to free/0 (if a shop plugin cannot sell for free/0, it will not be supported) Shop command: buyraid 0 <steamid> <steamid> must use the placeholder syntax your shop plugin requires. Example: if your shop uses %steamid%, then use: buyraid 0 %steamid% By default, 0 is the difficulty level (0=Easy, 1=Medium, 2=Hard, 3=Expert, 4=Nightmare) Map Terrain and it's importance with this plugin (maps must be designed appropriately for use with this plugin) Flat terrain only: I do not support spawning bases on bumpy terrain—design them on flat terrain only. Fortify on Steam is perfect for this, and there are plenty of bases available there. Be careful when downloading bases from ANY source: vet them first, and remember that bases are not all designed equally. Stability can be shaky in some, causing them to crumble as they paste in. Inventories may contain items the designer forgot to remove. Worst of all, some bases aren’t copied properly from their centermost foundation—copying at the wrong height can make them spawn below the map or way above it. If you look at the ground, paste it in, and it appears elsewhere, it was not copied properly. Recopy it—don’t rely on ANY height settings in profiles! Those settings are for MINOR adjustments, not for bases that got yeeted halfway around the world. If the plugin is ignoring terrain, it's usually due to one of three reasons: The terrain is not flat enough for bases to spawn on- bases should be designed on unobstructed flat and equal terrain. You've modified a setting in your config or profiles, use compare in Notepad++ or diff on the default config file, and your config file, and see what changes are different. This is the EASIEST way to see what you've changed! The spawn point is blocked by a visible or invisible entity. Just because you can't see it does not mean it's not there. RBE DEBUG (see documentation) exists solely so you can spot issues like this on-the-fly. Understand that debug contains GOOD and BAD information, use your common sense to narrow it down weighing the highest number occurrences of BAD debug at the most likely causes. Easier than it sounds. No worries. If your map’s terrain is bad, you’ve still got options: the beach, the water, or custom spawn points. Shagadelic, baby. Custom spawn points Spawns Database plugin Create spawn points yourself, and put the name of the file (e.g: nivexspawnpoints10 - note that .json is NOT appended to the end of the filename, do not append it, using the filename without its path or extension as I've shown) in your config OR profile (not both, highly recommend profile only). Allow Raid Bases On Beaches in the config, not the profiles. This is for the beach and all beach terrain under the water within its vicinity, usually a very short distance out from the shore. Water Settings - In the profiles, not the config. Highly recommended: Water is abundant in the ocean, surprise! Enable within your profiles, force them on top of the waters surface. Highly recommended for maps with bad terrain. Allow Bases To Float Above Water: true Chance For Underwater Bases To Spawn: 100 Spawn On The Surface Of Water: true Ignore Land Level On Seabed: true Prevent Bases From Floating Above Water By Also Checking Surrounding Area: false Maximum Water Depth Level Used For Float Above Water Option: 1 Minimum Water Depth Level Used For Seabed Option: -20 (negative twenty, forcing the spawn points AWAY from the shoreline) Keep these settings enabled (true), knowing that changing them can and will break the plugin depending on the maps you use. Some maps may embrace these changes, while others will feel like a distant echo—terrain reduced to nothing, the memory abandoned entirely, lost to the abyss for all eternity. Just kidding—use the damn water settings and quit pouting. Bad spawns are notoriously brutal on custom maps. Allow Raid Bases On Beaches Allow Raid Bases Inland Allow Raid Bases On Building Topology Enable (true) these settings if you're in desperate need of more spawn points: Allow Raid Bases On Roads Allow Raid Bases On Rivers Do not use these options if you have high traffic on railroads Allow Raid Bases On Railroads Do not modify Allow Raid Bases In Biomes without understanding that disable a biome will prevent all bases from spawning within that biome! Allow Raid Bases In Biomes Arctic: true Arid: true Temperate: true Tundra: true or false Jungle: true or false Last but not least, the most important of them all for anyone not using custom spawn points from Spawns Database plugin (see documentation): The number of potential spawn points is displayed when the grid loads. First, the plugin must initialize, then it generates potential spawn points across your map. Once this process is complete—usually within a few minutes—it will output the results to your server console. If potential points are under 1000, the map has poor terrain, or you’ve disabled too many options in the config. If potential points are above 1500, you’ll have a reliable amount of spawns. This number will naturally decline as players build more bases on the server. If potential points are above 2500 but nothing spawns, your config and/or profiles are set up incorrectly. Read the documentation. Do not disable biome options in the config. Doing so blocks all spawns in those biomes. There are just a few steps required to get bases spawn on your server within minutes (3 minutes for experts, 30 minutes for a novice, and 60 to 120 minutes for beginners. Total time to configure the plugin beyond these steps is infinite, you'll never stop making changes so long as you continue building your base catalog into a massive collection of artwork). You must have the CopyPaste plugin installed. (Disclaimer: Configuring this to your servers specific needs will require a lot of time and effort) Step 1: Obtain Your Bases You can get bases by: Downloading them from Fortify Purchasing a tier package from me Buying a base package from third-party sellers (be wary that some sellers include items in their CopyPaste files!) Creating your own bases CopyPaste files belong in the oxide/data/copypaste/ folder for Oxide users, and the carbon/data/copypaste/ folder for Carbon users. Note that the folder name must be in all lowercase. Step 2: Set Up Profiles Profiles are located in: oxide/data/RaidableBases/Profiles/ carbon/data/RaidableBases/Profiles/ There are five different profiles. You can add the filenames of your CopyPaste bases manually, or by using the command: For example (You must use straight double quotes. Curly double quotes are not supported!): Step 3: Edit the Configuration The configuration file is located in: oxide/config/RaidableBases.json carbon/configs/RaidableBases.json Make the following changes: Always Maintain Max Events: Set this to true. Max Maintained Events: Set this to the number of bases you want to spawn. Minimum Required Players Online: If you want bases to spawn even when no players are online, set this to 0. Step 4: Save and Reload After making your changes: Save your files. Reload the plugin. The bases will now start spawning automatically. They will use the Default Loot table, located in: oxide/data/RaidableBases/Default_Loot.json carbon/data/RaidableBases/Default_Loot.json Step 5: Customize Loot Tables Refer to the documentation to learn how to set up your own custom loot tables. Additional Information If you want buyable events using the /buyraid command, you can set a cost under the Buyable Event Costs section. This includes: Economics Buy Raid Costs ServerRewards Buy Raid Costs Custom Buy Raid Costs Tips for Customizing Your Setup The plugin has many settings to customize. No guide can cover everything, so you will need to go through each setting and adjust it to meet your server’s needs. Important: Make backups as you configure the settings. Don’t rush—take it one step at a time. Dynamic difficulties (added in 3.0.0): Easily add or remove your own difficulties. You should reload the plugin whenever you make changes! Add a difficulty: rb.difficulty add "Sky" This will create the profile "Sky Bases.json" and set the difficulty to "Sky" rb.config add "Sky Bases" sky1 sky2 sky3 sky4 sky5 Reload the plugin! This will create language messages in the EN and RU language files which you can copy to other language files. If your messages do not update after a reload then you must restart your Rust server to reset Oxide cache. This will create all relevant settings for "Sky" within the config file where you must set them all as desired You need your own copypaste files and loot tables using their new respective names. Base Loot folder - add a loot table with the filename "Sky Bases.json" to match the profile name. Difficulty Loot folder - add a loot table with the filename "Sky.json" to match the difficulty name. Remove a difficulty: rb.difficulty remove "Sky" This will remove all settings for this difficulty from the config file - and disable the profile - only. No files are deleted! Edit or change a difficulty name: This is not supported and will not be - some hosts restrict System.File.IO namespace Please avoid trying to do this unless you are an expert user - you must rename EVERYTHING yourself Configuration errors are shown in rcon when the plugin loads If you make a mistake, you can use the add command a second time which will re-add any missing settings. If you feel overwhelmed or frustrated, take a break and return to it later. I am always here to answer your questions and help you (even if it takes some hours for me to respond). Tutorial This is not your run-of-the-mill plugin. DO NOT INSTALL WITHOUT READING THIS DOCUMENTATION FIRST. This plugin is extremely advanced and requires utmost attention to detail to configure properly. Jumping around in the configuration file or profiles will lead to more problems than it's worth. Take your time to understand each option before enabling or disabling its functionality. Raidable Bases is an independent expansion of Dangerous Treasures. You may learn how to enable the expansion mode below. It does not require Dangerous Treasures for any other purpose. Configuration Loot Tables The plugin comes with some very basic items (Default_Loot.json) that only serve as a demo loot list for you to either delete or expand upon. In order to make any use of the plugin (beyond demonstration) you will have to create your own loot lists instead. It will take a very long time to configure your loot tables, and fine-tune each to your specific needs. To start, I recommend that you use the rb.populate all command. This creates files in the Editable_Lists folder for each difficulty that contain every item in the game. Edit each file and set the amounts for the items that you want to spawn, and remove those that you do not want to spawn. It may look intimidating editing a list of 660 items, but don't underestimate how easy it is to delete items from a list compared to adding each one manually. Items that have their amount AND amountMin set to 0 will not spawn. So you may either delete these items from the list, or come back to them later. If you set amountMin to 0 then chance will determine if the item spawns or not, and another item will not replace it unless there are extra items available (as of 1.7.3). You can set the item skin that you want to use, but I suggest using the Skins settings in the configuration file to use random skins, or none at all. The rb.populate command which populates the Editable_Lists folder also includes items already inside of your Difficulty_Loot folder. This allows you to easily repopulate lists in order to re-evaluate which items spawn at a later date. Files inside of the Editable_Lists folder must be copied into an existing loot file in order to use the loot table. As the name implies, it is for editing only. - If you want to use Editable_Lists/Easy.json for your Easy bases then copy the contents of the file into the Difficulty_Loot/Easy.json file. - If you want to use Editable_Lists/Expert.json for the Expert Bases.json profile, then you must copy the contents of the Expert.json file into the Bases_Loot/Expert Bases.json file probability - the chance that the item can spawn. value must be between 0.0 and 1.0 where 1.0 is 100% chance Loot Priority Loot is pulled from all datafiles within the oxide/data/RaidableBases/ folder with the exception of the Profiles folder which is used to configure bases. oxide/data/RaidableBases/Base Loot - If a loot table exists in this folder with the same name as a profile then all of the bases in that profile will use this loot table. If you want items in this loot table to always spawn then you must enable Always Spawn Base Loot Table in the respective profile. oxide/data/RaidableBases/Difficulty Loot - Items will be chosen from these files based on the difficulty of each profile. If Use Day Of Week Loot is enabled then it will choose the loot table for that specific day. Otherwise, it will pick from Default_Loot.json. This is the default list, and is only used when all other loot tables do not have a sufficient amount of loot to spawn based on the Amount Of Items To Spawn setting. Loot Settings Block paid and restricted content to comply with Facepunch TOS (true) – removes paid content on NPC death, prevents pickup of DLC/paid deployables, resets skins on pickup, and blocks paid loot in boxes. Future update may allow pickup for content owners. Allow Duplicate Items - This is useful when you do not have enough items in your loot tables , and you want to spawn Amount Of Items To Spawn by using the same items more than once. Amount Of Items To Spawn - This is the number of items that you want to spawn. If you do not have enough items in your loot tables then it will only spawn the amount that you have available. It will not spawn items if the container does not have enough space. Drop Tool Cupboard Loot After Raid Is Completed (false) Divide Loot Into All Containers - This allows you to divide loot evenly from all of your loot lists into all containers when enabled. You MUST increase or decrease Amount Of Items To Spawn respective to how many items you want in each container. This includes large boxes, small boxes, coffins and storage barrels. Optional settings include (in order of priority) cupboard, bbq, oven, fridge and lockers. Allow Players To Pickup Deployables (false) - As name implies, overridden by Entities Not Allowed To Be Picked Up Allow Players To Deploy A Cupboard (true) - Block players from placing a TC after destroying the TC in the base. Drop Container Loot X Seconds After It Is Looted (false) - Prevent players from cherry picking items and leaving the rest, in order to despawn the raid quicker. Drop Container Loot Applies Only To Boxes And Cupboards (true) - As name implies Empty All Containers Before Spawning Loot (true) - Useful if using CopyPaste files that contain loot already - I suggest leaving this true as it can complicate how many items spawn if there are too few inventory slots remaining. Ignore Containers That Spawn With Loot Already (false) - Useful if you want specific loot to spawn from a copypaste file. Require Cupboard Access To Loot (false) - Prevent all players from looting until they reach the TC, or destroy it. Skip Treasure Loot And Use Loot In Base Only (false)" - Useful if you want all loot to spawn from a copypaste file - not recommended - will allow players to memorize which boxes to raid and ignore the rest. Always Spawn Base Loot Table (false) - Very useful if you want items in the Base_Loot file to always spawn (such as C4, rockets, ammo, etc) Advanced Loot Configuration Loot Behavior in Tool Cupboards Stacked Items Combine Items that spawn into the Tool Cupboard (TC) automatically combine into single stacks. For example, two separate 500-stone stacks will merge into one 1,000-stone stack. This is reflected in the Status UI. TC Always Counts Toward Remaining Loot In Status UI The contents of the TC are always included in the loot remaining total shown in the Status UI — even if looting the TC is not required for event completion. There is no reason players should not be aware of the TC amount. Making the TC a Requirement By default, players do not need to loot the TC to complete the raid. To require TC and boxes to be looted before the event can be completed, enable: Require Cupboard To Be Looted Before Completion To require only the TC to be looted before the event can be completed, enable: Destroying The Cupboard Completes The Raid Stack Size Options Stack-Split Items Reduce Remaining Loot When using stack size options, the split stacks are counted individually, which reduces the number of remaining items needed to meet the Amount Of Items To Spawn requirement. Optional Setting To Change This Behavior: Amount Of Items To Spawn Increased By Item Splits When enabled, one item will still count as one, even if it becomes split into multiple smaller stacks. An option exists in the configuration file for all items: Use Stack Size Limit For Spawning Items An option exists in the loot tables for each individual item, and will override the above option: stacksize Additional Containers Only TC and Boxes are counted in the Status UI by default Other containers (e.g., furnaces, lockers) are not included in the remaining loot count by default. To include others, add the prefab short name (not item shortname) found with /tpve_prod to: Additional Containers To Include As Boxes Settings Blacklisted Commands (none) - prevents players from using these commands inside of a raid base Automatically Teleport Admins To Their Map Marker Positions (true) - right-click map to teleport (requires raidablebases.mapteleport permission) Block Wizardry Plugin At Events (false) - Block players from using wands Chat Steam64ID (0) - The steam profile icon to show in chat messages Expansion Mode (Dangerous Treasures) (false) - Allow Dangerous Treasures to take over a random box for its event Remove Admins From Raiders List (false) - Allows admins to help players without receiving any rewards Show X Z Coordinates (false) - Show X Z coordinates alongside grid location Buy Raid Command (buyraid) - Opens the buyable UI to purchase raids for each difficulty Event Command (rbe) - Specify command name Hunter Command (rb) - Specify command name Server Console Command (rbevent) - Specify command name Remove Paid Content Command - Name is generated randomly on load. This command will edit your loot tables and all copypaste files. Backup your files before using this command. The edit will remove any restricted content from these files. Block paid and restricted content to comply with Facepunch TOS (true) – removes paid content on NPC death, prevents pickup of DLC/paid deployables, resets skins on pickup, and blocks paid loot in boxes. Future update may allow pickup for content owners. Raid Management Allow Teleport (false) - Allow/prevent players from teleporting Allow Cupboard Loot To Drop (true) - Allows loot to drop when TC is destroyed by a player Allow Players To Build (true) Allow Players To Use Ladders (true) Allow Players To Deploy Barricades (true) Allow Players To Upgrade Event Buildings (false) - Prevent players from upgrading buildings with no TC to prevent this otherwise Allow Player Bags To Be Lootable At PVP Bases (true) - Bypasses Prevent Looting plugin Allow Player Bags To Be Lootable At PVE Bases (true) - Bypasses Prevent Looting plugin Allow Traps To Drop Loot (false) - Allow traps such as guntraps and turrets to drop loot on death Allow Players To Loot Traps (false) - Allows players to loot traps such as guntrap and turrets with TC access Allow Raid Bases On Roads (true) Allow Raid Bases On Rivers (true) Allow Raid Bases On Building Topology (true) - Specifically added for custom map makers Allow Vending Machines To Broadcast (false) - Prevents vending machines from showing on the map Allow Bases To Float Above Water (false) - Keyword: FLOAT Allow Bases To Spawn On The Seabed (false) Prevent Bases From Floating Above Water By Also Checking Surrounding Area (false) - Keyword: FLOAT Maximum Water Depth Level Used For Float Above Water Option (1.0) - Keyword: FLOAT, but allows you to prevent on water if the value is low enough Backpacks Can Be Opened At PVE Bases (true) Backpacks Can Be Opened At PVP Bases (true) Backpacks Drop At PVE Bases (false) - Will drop a backpack on death, even if explicity disabled in Backpack configuration (requires Backpacks 3.4.0 ) Backpacks Drop At PVP Bases (false) Block Mounted Damage To Bases And Players (false) - Prevent players from dealing damage while on mini, scrap heli, etc Block RestoreUponDeath Plugin For PVP Bases (false) Block RestoreUponDeath Plugin For PVE Bases (false) Bypass Lock Treasure To First Attacker For PVE Bases (false) - Do not set an owner for PVE bases Bypass Lock Treasure To First Attacker For PVP Bases (false) - Do not set an owner for PVP bases Despawn Spawned Mounts (true) - Allows mounts such as mini or scrap heli to remain if not abandoned when raid despawns Do Not Destroy Player Built Deployables (true) - Loot is not lost if the plugin destroys a player's box with this option - it is dropped on the ground in a grey loot container just as if they destroyed the box themselves Do Not Destroy Player Built Structures (true) Divide Rewards Among All Raiders (true) Draw Corpse Time (Seconds) (300.0) - The amount of time the players corpse location is drawn on their screen Eject Sleepers Before Spawning Base (true) Extra Distance To Spawn From Monuments (0.0) Flame Turrets Ignore NPCs (false) - Can help with performance on some servers Maximum Land Level (2.5) - The allowed height of the surrounding terrain for spawning bases (this should never be changed) Move Cookables Into Ovens (true) Move Food Into BBQ Or Fridge (true) Move Resources Into Tool Cupboard (true) Move Items Into Lockers (true) Lock Treasure To First Attacker (true) - Sets the first attacker as the owner of a raid. You must set eject enemies settings in each profile if you do not want players entering private raids Lock Treasure Max Inactive Time (Minutes) (20.0) - Resets the raid as public after this time Assign Lockout When Lock Treasure Max Inactive Time Expires (false) - useful those who partially raid bases in order to avoid the lockout timer Lock Players To Raid Base After Entering Zone (false) - Forces players to be locked to a raid once they enter it, even on accident Only Award First Attacker and Allies (false) Minutes Until Despawn After Looting (min 1) (15) - The time until the base despawns after being raided Minutes Until Despawn After Inactive (0 = disabled) (45) - The time until the base despawns after being inactive Minutes Until Despawn After Inactive Resets When Damaged (true) - Resets the time until the base despawns when it is damaged by a player Mounts Can Take Damage From Players (false) Mounts Can Take Damage From SamSites (true) Player Cupboard Detection Radius (100.0) - Extra layer of protection to prevent raid bases from spawning too closely to player bases (this should never be under 100 and never too high either, 100-200 at most) Players With PVP Delay Can Damage Anything Inside Zone (false) - Applies specifically to PVP raid bases Players With PVP Delay Can Damage Other Players With PVP Delay Anywhere (false) PVP Delay Between Zone Hopping (10.0) - The amount of time players can take damage while on a PVE server after stepping outside of a PVP zone - prevents exploiting - recommended value: 120 Prevent Fire From Spreading (true) - Helps with server performance by preventing forest fires, err, fire from spreading after initial spawn Prevent Players From Hogging Raids (true) - Prevents players from tagging multiple raids at once Require Cupboard To Be Looted Before Despawning (false) Destroying The Cupboard Completes The Raid (false) Require All Bases To Spawn Before Respawning An Existing Base (false) - Rotate through all bases specific to each difficulty before reusing an existing base Turn Lights On At Night (true) Turn Lights On Indefinitely (false) Traps And Turrets Ignore Users Using NOCLIP (false) Use Random Codes On Code Locks (true) Wait To Start Despawn Timer When Base Takes Damage From Player (false) - Prevents the inactive despawn timer from starting until it is damaged by a player. Combos well when inactive resets is disabled by giving players a limited time to finish a raid once they start it Additional Containers To Include As Boxes (none) - example: vendingmachine Eject Mounts Boats (false) - Set any true to prevent them from entering a raid base Cars (Basic) (false) Cars (Modular) (false) Campers (true) Chinook (false) Flying Carpet (false) Horses (false) HotAirBalloon (true) MiniCopters (false) Pianos (true) Scrap Transport Helicopters (false) All Other Mounts (false) All Controlled Mounts (false) - Mounts controlled via another plugin Max Amount Of Players Allowed To Enter Each Difficulty (0 = infinite, -1 = none) (infinite) Easy Difficulty => Amount (0) Medium Difficulty => Amount (0) Hard Difficulty => Amount (0) Expert Difficulty => Amount (0) Nightmare Difficulty => Amount (0) Max Amount Allowed To Automatically Spawn Per Difficulty (0 = infinite) -1 = disabled) Easy (0) - Specifies how many of each difficulty can be spawned at any given time Medium (0) Hard (0) Expert (0) Nightmare (0) Player Lockouts (0 = ignore) - this is for PUBLIC raids where buyable events use the Buyable Cooldowns and these are not shared - players may still do 1 public and 1 buyable event if these are both enabled Time Between Raids In Minutes (Easy) (0.0) - Set a cooldown before the player can enter another raid base Time Between Raids In Minutes (Medium) (0.0) Time Between Raids In Minutes (Hard) (0.0) Time Between Raids In Minutes (Expert) (0.0) Time Between Raids In Minutes (Nightmare) (0.0) Block Clans From Owning More Than One Raid (false) - Prevent clans from hogging multiple raid bases Block Friends From Owning More Than One Raid (false) Block Teams From Owning More Than One Raid (false) Easy|Medium|Hard|Expert|Nightmare Raids Can Spawn On Monday (true) Tuesday (true) Wednesday (true) Thursday (true) Friday (true) Saturday (true) Sunday (true) Difficulty Colors (Border) Easy (000000) Medium (000000) Hard (000000) Expert (000000) Nightmare (000000) Difficulty Colors (Inner) Easy (00FF00) Medium (FFEB04) Hard (FF0000) Expert (0000FF) Nightmare (000000) Map Markers Marker Name (Raidable Base Event) Radius (0.25) Use Vending Map Marker (true) Show Owners Name on Map Marker (true) Use Explosion Map Marker (false) Create Markers For Buyable Events (true) Create Markers For Maintained Events (true) Create Markers For Scheduled Events (true) Create Markers For Manual Events (true) Buyable Events Do Not Reward Buyable Events (false) Refunds > Refund Despawned Bases (false) Refunds > Refund Percentage (100.0) Refunds > Refund Resets Cooldown Timer (false) Refunds > Block Refund If Base Is Damaged (true) Cooldowns (0 = No Cooldown) VIP Permission (raidablebases.vipcooldown (300.0) Admin Permission (raidablebases.allow (0.0) Server Admins (0.0) Normal Users (600.0) Allow Players To Buy PVP Raids (false) - If all of your profiles have PVP enabled then players will NOT be able to buy any raids! Convert PVE To PVP (false) Convert PVP To PVE (false) Distance To Spawn Bought Raids From Player (500.0) Lock Raid To Buyer And Friends (true) Ignore Player Entities At Custom Spawn Locations (false) Ignore Safe Checks (false) - if enabled will prevent the plugin from checking the area for a TC, buildings, or deployables Max Buyable Events (1) Reset Purchased Owner After X Minutes Offline (10.0) Spawn Bases X Distance Apart (100.0) - most maps cannot support this being above 200 ! Spawns Database File (Optional) (none) - Useful if you want buyable raids to spawn in specific locations using spawn files from the Spawns Database plugin Maintained Events Always Maintain Max Events (false) - Spawn another raid soon after one despawns Ignore Player Entities At Custom Spawn Locations (false) - spawn regardless of what player entities are built in the area Chance To Randomly Spawn PVP Bases (0 = Ignore Setting) (0.0) - Overrides all PVP Allow profile settings for a chance to make the raid PVE or PVP Convert PVE To PVP (false) Convert PVP To PVE (false) Include PVE Bases (true) Include PVP Bases (true) Ignore Safe Checks (false) - Bypass checks that ensure no buildings or other objects are blocking the spawn Minimum Required Players Online (1) - Max Maintained Events (1) - How many bases you want available at any given time Spawn Bases X Distance Apart (100.0) - most maps cannot support this being above 200 ! Spawns Database File (Optional) (none) - Useful if you want maintained raids to spawn in specific locations using spawn files from the Spawns Database plugin Time To Wait Between Spawns (15.0) - Wait a specific time frame between each paste (can be set to 0) Manual Events Convert PVE To PVP (false) Convert PVP To PVE (false) Max Manual Events (1) Spawn Bases X Distance Apart (100.0) Spawns Database File (Optional) (none) - Useful if you want manually spawned raids to spawn in specific locations using spawn files from the Spawns Database plugin Scheduled Events Enabled (false) - Spawn raids on a timer specific to random amount of time between Every Min and Every Max Seconds Ignore Player Entities At Custom Spawn Locations (false) - spawn regardless of what player entities are built in the area Chance To Randomly Spawn PVP Bases (0 = Ignore Setting) (0.0) - Overrides all PVP Allow profile settings for a chance to make the raid PVE or PVP Convert PVE To PVP (false) Convert PVP To PVE (false) Every Min Seconds (3600.0) Every Max Seconds (7200.0) Include PVE Bases (true) Include PVP Bases (true) Ignore Safe Checks (false) - Bypass checks that ensure no buildings or other objects are blocking the spawn Max Scheduled Events (1) Max To Spawn At Once (0 = Use Max Scheduled Events Amount) (0) Minimum Required Players Online (1) Spawn Bases X Distance Apart (100.0) - most maps cannot support this being above 200 ! Spawns Database File (Optional) (none) - Useful if you want scheduled raids to spawn in specific locations using spawn files from the Spawns Database plugin Time To Wait Between Spawns (15.0) - Wait a specific time frame between each paste (can be set to 0) Economics Buy Raid Costs (0 = disabled) - if you do not configure at least one cost for Buyable Events then players will not be able to buy any raids Easy (0.0) - How much each raid costs, use the /buyraid command to see the UI Medium (0.0) Hard (0.0) Expert (0.0) Nightmare (0.0) ServerRewards Buy Raid Costs (0 = disabled) - if you do not configure at least one cost for Buyable Events then players will not be able to buy any raids Easy (0) - How much each raid costs, use the /buyraid command to see the UI Medium (0) Hard (0) Expert (0) Nightmare (0) Custom Buy Raid Costs (false = disabled) - if you do not configure at least one cost for Buyable Events then players will not be able to buy any raids Easy (50 scrap) - How much each raid costs, use the /buyraid command to see the UI Medium (100 scrap) Hard (150 scrap) Expert (200 scrap) Nightmare (250 scrap) All are disabled by default. All can require its own specific item. Allowed Zone Manager Zones List: pvp, 99999999 - the list of zones where raid bases may spawn at - Zone Manager is not required to use this plugin. Use Grid Locations In Allowed Zone Manager Zones Only - forces all spawns into zones by Zone Manager. Adding flags to your zones may conflict with this plugin. Use of Spawns Database plugin is advised instead Event Messages Notify Plugin (-1 = disabled) Notification Interval (1 second) Announce Raid Unlocked (false) Announce Buy Base Messages (false) Announce Thief Message (true) Announce PVE/PVP Enter/Exit Messages (true) Show Destroy Warning (true) Show Opened Message (true) Show Opened Message For Paid Bases (true) Show Prefix (true) Show Messages To Player (true) - set false if you do not want players to receive CHAT messages, other messages from notifications will still show GUIAnnouncements and Advanced Alerts plugins can be used instead of CHAT messages Advanced Alerts Enabled (true) Anchor Min and Max Time Shown (5) Panel Alpha (0.98) Background Color Title Background Color GUIAnnouncements Enabled (false) Banner Tint Color (Grey) Maximum Distance (300.0) Text Color (White) Lusty Map Enabled (false) Icon File (http://i.imgur.com/XoEMTJj.png) Icon Name (rbevent) Icon Rotation (0.0) Ranked Ladder (based on points system) Award Top X Players On Wipe (3) - Set 0 to disable permissions and groups from being created. Every wipe the top 3 players are awarded the raidablebases.th permission and raidhunter group. Used with plugins that give titles based on permissions/groups, such as BetterChat Enabled (true) Difficulty Points (for each difficulty) Assign To Owner Of Raid Only (false) Assign Rank After X Completions - Players that complete the required amount of completions will receive the relevant above permission and group automatically - Set value above 0 to enable this feature for any given difficulty as it is disabled for all difficulties by default Permissions and groups are given to players for being top 3 in each difficulty at the end of a wipe Set Award Top X Playrs On Wipe to 0 to disable these permissions and groups from being created. permissions: raidablebases.ladder.easy, raidablebases.ladder.medium, raidablebases.ladder.hard, raidablebases.ladder.expert, raidablebases.ladder.nightmare, raidablebases.th groups: raideasy, raidmedium, raidhard, raidexpert, raidnightmare, raidhunter Skins (Boxes, Loot Items, Npcs all have there own settings) (skin settings revamped in 2.7.4) Use Identical Skins Include Workshop Skins (true) Use Random Skin (true) Use Imported Workshop Skins File (true) - copy existing Imported Workshop Skins section from Skinbox to the Imported Workshop Skins json file to apply. Boxes (including above Skins options) Preset Skins - you can add any box skin here and it will randomly apply to any relevant box this skin can be used with Loot Items (including above Skins options) Use Identical Skins For Stackable Items Use Identical Skins For Non-Stackable Items Deployables (including above Skins options) List: Partial Names (door, barricade, chair, fridge, furnace, locker, reactivetarget, rug, sleepingbag, table, vendingmachine, waterpurifier, skullspikes, skulltrophy, summer_dlc, sled) Skin Everything (true) - if true then the Partial Names list will not be used Preset Door Skins - you can add any door skin here and it will randomly apply to any relevant door this skin can be used with Ignore If Skinned Already (false) Treasure Resources Not Moved To Cupboards (skull.human, battery.small, bone.fragments, can.beans.empty, can.tuna.empty, water.salt, water, skull.wolf) Use Day Of Week Loot (false) Do Not Duplicate Base Loot (false) Do Not Duplicate Difficulty Loot (false) Do Not Duplicate Default Loot (false) Use Stack Size Limit For Spawning Items (false) Status UI - Shows PVE/PVP, time left, amount of loot left and the status of owner Details UI - Shows owner and active status Delay UI - Shows UI for PVP delay Buyable Cooldowns UI - Shows UI for the Buyable Cooldowns option Buyable Events UI - Shows players a UI for buying events including the primary cost Lockouts UI - Shows UI for the Player Lockouts option Enabled Offset Min Offset Max Panel Alpha Font Size Background Color Title Background Color etc Weapons Fog Machine Allows Motion Toggle (true) Fog Machine Requires A Power Source (true) SamSite Repairs Every X Minutes (0.0 = disabled) (5.0) SamSite Range (350.0 = Rust default) (75.0) Test Generator Power (100.0) Tesla Coil settings in profiles Infinite Ammo AutoTurret (true) FlameTurret (true) FogMachine (true) GunTrap (true) SamSite (true) Ammo AutoTurret (256) FlameTurret (256) FogMachine (5) GunTrap (128) SamSite (24) Tesla Coil (profiles) Requires A Power Source (true) Max Discharge Self Damage Seconds (0 = None) 120 = Rust default) (0.0) Max Damage Output (35.0) Profiles Difficulty - very first setting. If your raids show as NORMAL then you're using the free plugin. If all bases show as EASY then this setting is not configured. Entities Not Allowed To Be Picked Up (List: generator.small, generator.static autoturret_deployed - overrides Allow Players To Pickup Deployables) Additional Bases For This Difficulty (default) - A list of bases to use within this profile Paste Options (default) - Paste options specific to the profiles filename if it is also a base Profile Enabled (true)- Useful for disabling a profile instead of deleting it Add Code Lock To Unlocked Or KeyLocked Doors (true) Add Code Lock To Boxes (false) Add Code Lock To Tool Cupboards (false) Close Open Doors With No Door Controller Installed (true) Allow Duplicate Items (false) - [Explained above] Allow Players To Pickup Deployables (false) - [Explained above] Allow Players To Deploy A Cupboard (true)- [Explained above] Allow PVP (true) Allow Friendly Fire (Teams) (true) Amount Of Items To Spawn (30) - [Explained above] Minimum Amount Of Items To Spawn (0 = Use Max Value) (0) Flame Turret Health (300.0) Block Plugins Which Prevent Item Durability Loss (false) - Force items to take condition losses Block Damage Outside Of The Dome To Players Inside (false) - Prevent damage from outside of the dome to players inside of the dome Block Damage Outside Of The Dome To Bases Inside (false) - Prevent damage from outside of the dome to the base inside Block Damage Inside From Npcs To Players Outside (false) Building Blocks Are Immune To Damage (false) Boxes Are Invulnerable (false) Spawn Silently (No Notifcation, No Dome, No Map Marker) (false) Divide Loot Into All Containers (true) - [Explained above] Drop Container Loot X Seconds After It Is Looted (0.0) - [Explained above] Drop Container Loot Applies Only To Boxes And Cupboards (true) - [Explained above] Create Dome Around Event Using Spheres (0 = disabled, recommended = 5) (5) - A visible dome for players to distinguish raid bases from player bases Empty All Containers Before Spawning Loot (true) - [Explained above] Eject Corpses From Enemy Raids (Advanced Users Only) (true) - Prevents corpses from remaining inside of a raid when it becomes private and prevents the user from looting it Eject Enemies From Purchased PVE Raids (true) - Useful when Lock Raid To Buyer And Friends is enabled Eject Enemies From Purchased PVP Raids (false) Eject Enemies From Locked PVE Raids (true) - Useful when Lock Treasure To First Attacker is enabled Eject Enemies From Locked PVP Raids (false) Explosion Damage Modifier (0-999) (100.0) - Modify the damage of all explosives Force All Boxes To Have Same Skin (true) Ignore Containers That Spawn With Loot Already (false) - [Explained above] Penalize Players On Death In PVE (ZLevels) (true) Penalize Players On Death In PVP (ZLevels) (true) Loot Amount Multiplier (1.0) - useful to scale loot amounts without having to adjust them all individually Protection Radius (50.0) - This options controls every single option and feature that relies explicity on distance or radius in one regard or another. Setting an incorrect value, either too low, or too high, will break the functionality of the plugin. It's best to leave it alone. Require Cupboard Access To Loot (false) - [Explained above] Minimum Respawn Npc X Seconds After Death (0.0) - Useful in simulating a real raid where players respawn Maximum Respawn Npc X Seconds After Death (0.0) Skip Treasure Loot And Use Loot In Base Only (false) - [Explained above] Always Spawn Base Loot Table (false) - [Explained above] - Arena Walls Enabled (true) Extra Stacks (1) - How many times you want walls to stack on top of one another Use Stone Walls (true) - set false to use wooden walls instead Use Iced Walls (false) - not advised to use this as it can cause client lag (not a plugin issue) Use Least Amount Of Walls (true) Use UFO Walls (false) - Walls spawn horizontally instead of vertically Radius (25.0) NPC Levels Level 2 - Final Death (false) - Respawns all npcs when raid is completed NPCs Enabled (true) Spawn Inside Bases (Options: Spawn On Floors, Spawn On Rugs, Spawn On Beds) Murderer Items Dropped On Death (none) Scientist Items Dropped On Death (none) Murderer (Items) (metal.facemask, metal.plate.torso, pants, tactical.gloves, boots.frog, tshirt, machete) Scientist (Items) (hazmatsuit_scientist, rifle.ak) Murderer Kits (murderer_kit_1, murderer_kit_2) - Kits have priority over these lists of items Scientist Kits (scientist_kit_1, scientist_kit_2) Random Names (none) - Spawn with a custom random name instead of a provided random name Amount To Spawn (3) Aggression Range (70.0) - Aggression range is increased by 250 meters when engaged Despawn Inventory On Death (true) Health For Murderers (100 min, 5000 max) (150.0) Health For Scientists (100 min, 5000 max) (150.0) Minimum Amount To Spawn (1) Use Dangerous Treasures NPCs (false) - Tells Dangerous Treasures to control and outfit the NPCs instead Spawn Murderers And Scientists (true) Scientist Weapon Accuracy (0 - 100) (30.0) - These bots are meant to be savages. 30% is average for highly skilled players, while the average player has 10-20% accuracy Spawn Murderers (false) Spawn Random Amount (false) Spawn Scientists Only (false) Rewards Economics Money (0.0) - How much is rewarded after a raid. Overridden by Divide Rewards Among All Raiders ServerRewards Points (0) Change Building Material Tier To Wooden (false) - Useful for upgrading or downgrading buildings automatically Stone (false) Metal (false) HQM (false) Change Door Type To Wooden (false) - Useful for upgrading or downgrading doors automatically Metal HQM Player Building Restrictions Wooden (false) Stone (false) Metal (false) HQM (false) Auto Turrets Aim Cone (5.0) - shots fired will spread into a cone pattern based on this radius. Lowering this value will group the shots closer together. Minimum Damage Modifier (1.0) Maximum Damage Modifier (1.0) Start Health (1000.0) Sight Range (30.0) Set Hostile (False = Do Not Set Any Mode) (true) Requires Power Source (false) Remove Equipped Weapon (false) Weapon To Equip When Unequipped (null = Do Not Equip) (rifle.ak) Permissions raidablebases.allow -- Allows player to use the available ADMIN commands. This is NOT recommended as players can use the commands 'buyraid' and 'rb' already. raidablebases.canbypass permission (or to be flying) to bypass dome restrictions (this previously worked for admins, but now requires the permission instead) raidablebases.blockbypass permission to bypass Owning More Than One Raid settings for Clans/Friends/Teams raidablebases.mapteleport Teleporting to map marker now simply requires this permission and to be enabled in config raidablebases.ddraw allows support for FauxAdmin users raidablebases.config allows use of the rb.config command in-game (server console does not require this permission) raidablebases.banned bans the user from entering any raids - If you grant this by accident, use /rb unban name|id to revoke it. Do not grant this to any groups, especially not the default group... raidablebases.durabilitybypass to bypass `Block Plugins Which Prevent Item Durability Loss` raidablebases.notitle permission to exclude users from ranked title rewards See other permissions using Permissions Manager Players do not require any permissions by default. Grid This plugin creates it's own spawn points automatically, which cover the entirety of your server's map when the plugin is loaded. This is created one-time when the plugin loads. The grid maintains itself without requiring any input. You may view the grid by typing /rb grid in-game to view detailed drawings of all locations on the grid. X - green - possible spawn point X - Red - currently in use C - Cyan - construction detected nearby TC - yellow - TC detected nearby W - blue - water depth is too high - refreshes on ocean level change Each location on the grid is checked a second time before spawning a base to insure it does not spawn the base on players or their buildings. You can disable using the grid by providing a valid spawn file for each raid type (buyable, maintained, scheduled and manual). Commands buyraid - buys a raid, eg: buyraid easy, buyraid easy steamid, buyraid 0, buyraid 0 steamid. I suggest typing the command and using the UI to buy bases. rb - for players to see the ladder (also for admins to see the status of each raid going on, which includes showing the allies and owners of each raid) rb ui [lockouts|status] - COMMAND REMOVED rbe despawn - despawns a players purchased base if they have raidablebases.despawn.buyraid permission For admins, or players with the admin permission raidablebases.allow: rb.config stability true/false - sets stability in every profile rbe debug - toggles debug messages shown every second to server console for maintained and scheduled warning messages rb grid - see the grid and all monument names rb resettime - reset the time for the next scheduled event rb savefix - to cancel a server save that has become stuck - requires authlevel 2 rb prod - to gather information from a raid base entity for debugging purposes - requires admin or raidablebases.allow rbe - spawns a base at the position you are looking at. You cannot spawn a base on a player (including yourself) rbe draw - draw the raids radius rbe despawn - despawn a base near you (can be used by players with raidablebases.despawn.buyraid permission to despawn a base they purchased) rbe despawnall - despawn all bases rbe [basename] [difficulty] - spawn a raid at the location you are looking at rbe expire steamid|playername - removes a lockout for a specific player rbe expireall rbe active - shows status for each event rbevent [basename] [difficulty] - spawn a raid randomly on the map - and teleport to it if using the command in-game rb.reloadconfig - allows you to reload the config without needing to reload the plugin. Some changes are not applied immediately, and no changes are retroactive to bases that are already spawned. rb.config - allows you to edit the config by adding, removing, and listing bases. Requires the permission raidablebases.config when not being used from the server console. rb.toggle - toggles Maintained Events and Scheduled Events on/off, if enabled in the config, until plugin reloads rbe setowner name - Sets the player as the owner of the raid rbe clearowner - Clears the owner of the raid Additional Bases allows you to add additional files to an existing base so that all bases in that list share the same configuration as the primary base/profile. This is great for setting up a list of bases for easy, medium, hard, expert and nightmare. Command rb.populate all will add every item in the game to specific loot tables under the oxide/data/RaidableBases/Editable_Lists folder, with each disabled by default (amount is 0) Arguments: - rb.populate easy medium hard expert nightmare loot all - rb.populate 0 1 2 3 4 loot all - easy - Populates oxide/data/RaidableBases/Editable_Lists/Easy.json - all - Populates ALL diifficulty loot tables Configure the items to your liking then copy the files contents into a loot table that you would like to use Example: - Difficulty_Loot/Easy.json to match the difficulty - Base_Loot/Easy Bases.json to match the profile name API No return behavior: void OnRaidableBaseStarted(Vector3 raidPos, int mode, bool allowPVP) void OnRaidableBaseEnded(Vector3 raidPos, int mode, bool allowPVP) void OnPlayerEnteredRaidableBase(BasePlayer player, Vector3 raidPos, bool allowPVP, int mode) void OnPlayerExitedRaidableBase(BasePlayer player, Vector3 raidPos, bool allowPVP, int mode) OnRaidableBaseDespawn, OnRaidableBaseDespawned, OnRaidableBasePrivilegeDestroyed, OnRaidableBaseCompleted find more hooks and arguments by searching for CallHook in the plugin file Tips Players will be considered raiders after looting, killing an npc, using explosives, eco raiding, destroying a building block/high wall/door or dealing damage from INSIDE of the dome You must change easybase1, mediumbase2, expertbase3, etc to the name of your CopyPaste files, or vis-versa. This plugin doesn't create or come with any bases. You can use the rb.config command (rb.config add "easy bases" easybase1 easybase2 0) in the server console to make this process easier. You can rename all profiles or additional base filenames. When copying a base with CopyPaste, make certain that you copy the base from eye level of the CENTER foundation within the base, or slightly clipped into this foundation with noclip. Whichever provides better results for you. You must verify that the base pastes down correctly (with /paste command) after you've copied it. I would not change autoheight from false to true. height is the distance the base is spawned off of the ground. elevation determines how flat the surrounding terrain must be in order for bases to spawn on it Scheduled Events is how often you want a random base to spawn on the map. This is disabled by default. This randomness comes from Every Min Seconds and Every Max Seconds Maintain Events will always spawn the Max Events amount of bases on your map. This is disabled by default. When one despawns, another will take its place shortly after. Allow Teleport will prevent players from teleporting when disabled. Compatible with NTeleportation or any plugin that uses the CanTeleport hook. Help This plugin does NOT use Zone Manager - it creates and manages everything on its own. If you are having issues with too few locations on the grid, or each attempt to spawn a base returns a manual spawn was already requested then it is likely because of how you have setup Zone Manager. You either have far too many zones, or you have zones which are far too large. Raidable Bases will not spawn in these zones unless the ZoneID is added to Allowed Zone Manager Zones in the config file. This plugin requires CopyPaste plugin to work. It also requires that you have copypaste files already made. Raidable bases will be spawned using the CopyPaste plugin. This plugin does NOT come with any bases. PvE server friendly with TruePVE and other plugins that support the hooks CanEntityTakeDamage, CanEntityBeTargeted, and CanEntityTrapTrigger. Bases can have 5 difficulty settings: 0 for easy, 1 for medium, 2 for hard, 3 for expert, and 4 for nightmare. This is configurable per profile. Bases can spawn on roads and other areas that do not allow building by Rust. Building ladders in these areas is allowed by the plugin. I will add support for building twig later. My bases often spawn in the same biome If you're having issues with spawn points being repeatedly used, or with a biome being favored consistently over other biomes then this is an elevation issue with the terrain on your map. You can fix this by increasing the Elevation in the configuration. For example, if your Elevation is 1.0 then set it to 1.5 and try again. This will also increase the height the base is allowed to spawn off of the ground. With certain maps you'll just have to make do with this issue. Corpses appear outside of the dome as backpacks This is intended, and it is optional. The location is drawn on the players screen to notify them that their corpse moved. This allows players to retrieve their backpack in the event that the raid becomes locked privately to another player, and prevents them from entering. Players do not drop their active item when they die. Bases Stop Spawning On Linux Machine [Error] Exception while calling NextTick callback (DllNotFoundException: libgdiplus.so.0) If you see this error after bases spawn then you need to install libgdiplus on your machine. This will mimic the below issue but it is NOT a bug like the below issue is. A quick google search shows the install command is: sudo apt-get install -y libgdiplus This happens when images in the CopyPaste file are being rendered by converting the byte array to bitmap. Paste/Spawn/Despawn FPS/Rubberbanding Issues: Upgrade your servers hardware (please don't tell me how good your hardware is-- if it's having issues or is overloaded with plugins then it's not) Use copypaste files under 3MB Reduce the amount of bases that you are spawning Remove plugins - if you have too many resource hogs then you're going to have issues! Reduce Amount of entities to paste per batch. Use to tweak performance impact of pasting in your CopyPaste config to between 1 and 5 Restart your server daily to mitigate server degradation issues It could be as simple as a bad copypaste file. Note the base(s) that spawned around the time that the lag started, go to each of those bases and despawn them (/rbe despawn). If the lag disappears, then the base is the cause. Remove it from rotation (rb.config remove badbase1) until you can figure out what's wrong with it. RaidableBases is a large plugin, with a lot of functionality, and that functionality demands hook time. I constantly strive to improve performance and provide high quality products.

Halloween Raid Islands This is a custom built Halloween Raidable base island. There is no loot spawns on here just a Halloween themed place for your Raid Bases to spawn. There is recycler in 1 of the container buildings for player to recycle there components. There is a total of 183 prefabs for this. For any support contact me on discord @ https://discord.gg/HNhPTPZVmd

Clean & Simple Raid Islands (2 Pack) Need more space for high-action events on your Rust server? This pack gives you two low-entity-count islands that offer a clean, simple, and isolated space perfect for spawning your raidable bases. Optimized Performance: Low entity count ensures minimal impact on your server's performance. Easy Building: Provides a flat, uncluttered area for players to construct their raidable bases. Seamless Addition: A simple, drop-in addition to expand the build space on your map. A perfect and simple addition to your server, giving your players more room to build and raid! sFor any help or support, please contact me on Discord @ https://discord.gg/HNhPTPZVmd

Mini Raid Island 5 Pack Enhance your server's gameplay with this collection of 5 uniquely designed Mini Raid Islands. These compact, high-performance prefabs are designed specifically for Rust server owners looking to provide engaging PvP and PvE raiding experiences without sacrificing server performance. Each island in this pack offers a distinct layout, providing variety for your players and ensuring that no two raids feel the same. When used as automated raid bases, these islands are optimized for seamless integration. ### Key Features High Performance: Optimized with a low prefab count to ensure zero impact on server FPS. Compact Design: Small footprints allow for easy placement in ocean biomes or along coastlines. Diverse Layouts: Five distinct variations including industrial, rocky, and fortified themes. For any Assistance or questions Please contact me on Discord @ https://discord.gg/HNhPTPZVmd

This package contains 40 fully prepared raid bases designed for the Raidable Bases plugin. Each base is created with a focus on gameplay balance, functionality, and variety. All bases have been carefully tested and are ready for immediate deployment on any Rust server. The package also includes preconfigured loot tables adjusted to match the difficulty of each base. Package Contents: Description: Easy: 10 simple bases suitable for beginners Medium: 10 moderately challenging bases with balanced defenses Hard: 10 more advanced and well-defended bases Expert: 10 very challenging raid bases for experienced players Total: 40 raid bases Loot Tables The package includes balanced loot tables, fully compatible with the Raidable Bases plugin. Each difficulty level uses its own loot configuration. All loot tables have been tested in practice to ensure fair gameplay progression — higher difficulty levels offer better rewards without disrupting the server economy. Key Features ➤ 40 ready-to-use raid bases ➤ Difficulty categories: Easy, Medium, Hard, Expert ➤ Separate loot tables for each difficulty ➤ Tested for stability and gameplay balance ➤ Suitable for both PvE and PvP servers ➤ Optimized for performance without server lag ➤ Easy installation and implementation Requirements To use this package, the following plugins must be installed on your server: ➤ RaidableBases ➤ CopyPaste Install Upload all raid base files to the following directory: /oxide/data/copypaste Upload the included loot tables to: /oxide/data/RaidableBases/Base_Loot Register the base packages by difficulty in the server console: rb.config add "Easy Bases" raideasy1 raideasy2 raideasy3 rb.config add "Medium Bases" raidmed1 raidmed2 raidmed3 rb.config add "Hard Bases" raidmed1 raidmed2 raidmed3 rb.config add "Expert Bases" raidmed1 raidmed2 raidmed3 If needed, this package can be customized or extended — for example with custom base designs, additional loot variants, or server economy integration. For more information, please contact us.

xWirelessPower xWirelessPower transforms how players interact with electrical devices (IO Entities). Instead of running back to switches, rewiring circuits, or building complex control rooms, players can directly toggle supported powered entities simply by looking at them and using a command or even with doing a clap gesture - Creating a smoother, more responsive way to manage base systems. In short: You can simply use electrical item (IO Entities) like ceiling light, sprinkler, auto turret etc. without requireing any wire or power. Features Instant Wireless Control Turn configured devices (IO Entities) ON or OFF just by looking at them with using a command or even using the clap gesture - No switches or wiring changes needed. Optional Team Access Let teammates manage shared systems for easier group gameplay. Perfect for Base Management Quickly control turrets, lights, signs, sprinklers, and more without running around your base. Faster Reaction During Raids Activate defenses or adjust systems instantly when every second counts. Fully Customizable Server owners can choose which devices are controllable and how the system behaves through config or even with chatcommadn "whoami". ShortPrefabName gets printed and saves it automatically to the confing with default value "false". Permission Support Grant access to specific groups like VIPs, admins, or trusted players. Optional Auto Power On Devices can automatically turn on when placed for smoother setup. Performance Friendly Runs efficiently with minimal impact on server performance. Plugin Preview Chat Commands /power - Toggle the IOEntity you’re looking at. /powerall - Toggles all IO entities you’re looking at. For example, when powerall is turned on and you look at an auto turret, all auto turrets will be turned off. /whoami - Prints the looked-at entity’s ShortPrefabName and adds it to your IOEntities list in config (default value = true). Permission xwirelesspower.toggle - If 'UsePermission' is true, permission is needed. Config { "ToggleCommand": "power", "PowerAllCommand": "powerall", "GetItemNameCommand": "whoami", "UsePermission": false, "PermissionName": "xwirelesspower.toggle", "AllowTeamToggle": false, "RequireToolCupboard": false, "MaxDistanceToggle": 5.0, "AutoTurnOn": true, "TurnOnOffWithClappingGesture": true, "IOEntities": { "autoturret_deployed": true, "ceilinglight.deployed": true, "neonsigntr.deployed": true, "electric.sprinkler.deployed": true }, "PermissionBasedIOEntities": { "xwirelesspower.vip": [ "fridge.deployed" ], "xwirelesspower.vip2": [ "electricfurnace.deployed", "electricfurnace.io" ] } } - You can add as many IOEntities as you want, to get the correct name of it, just spawn/place it -> Look at it -> Use ChatCommand '/whoami' and add that shortname to your IOEntities list. ToggleCommand - Chat command players use to turn IO Entity on/off. PowerAllCommand - Chat command players can toggle to turn all IO Entities from same name on/off. GetItemNameCommand - Admin command to see the IO Entity internal name (ShortPrefabName), also saves that viewed at IOEntity automatically to config with default value "false". UsePermission - If ON, only players with permission has access to this wireless power system. PermissionName - The permission name. AllowTeamToggle - Lets teammates toggle each other’s IO Entities. RequireToolCupboard - Wirless Power does only work if within a tool cupboard. MaxDistanceToggle - How close you must be to toggle (in meters). AutoTurnOn - Devices turn on automatically when placed. TurnOnOffWithClappingGesture - As the config says, use any gesture to toggle IO Entity. IOEntities - List of devices that wireless power works with (true = enabled). Localization (If you want to disable a message just use empty value "") { "NotAllowed": "You are not allowed to use this command.", "LookAtEntity": "You're not looking at an entity.", "AddedConfigEntries": "Added to config with default value true: {0}", "DetectedShortnames": "Detected shortnames: {0}", "PowerAllNoEntity": "You're not looking at a valid wireless entity, or you lack the required permission.", "PowerAllNoMatches": "No matching IOEntities could be toggled.", "PowerAllResult": "{0}: {1} entities are now {2}.", "NoEnabledEntity": "No enabled wireless IO entity was found for that deployable, or you lack the required permission.", "NotOwner": "You can only toggle your own IOEntity.", "NoEntitiesToggled": "No IOEntities could be toggled.", "ToggleAllResult": "{0}: {1} entities are now {2}.", "ToggleSingleResult": "{0} is now {1}.", "DisabledInConfig": "{0} is disabled in config.", "CupboardRequired": "A nearby tool cupboard is required to use wireless power." }

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

"Hello! This is my Full Pack. Attention: If you already own the previous packs of 38 or 52 bases, do not purchase this! This collection includes all my bases in one place, plus the configuration for normal and balanced loot within the bases. By purchasing this file, you are paying for my hard work—and quality work costs money! If you are wondering if it’s worth it, try building a series of bases yourself, editing them, perfecting them, and then working on the configuration. This is the path I’ve chosen, and the price reflects how much I value my effort. Thank you to those who appreciate and support my projects! As I’ve said before, this is not my last project; there is more to come. Setup Guide for Your New Bases To ensure a clean installation, start by disabling the current plugin. Enter the following command into your server console: o.unload RaidableBases. If you have used this plugin before, it is essential to clear out any old settings. Please delete the following: The configuration file: oxide/config/RaidableBases.json The entire data directory: oxide/data/RaidableBases/ Now, access your server files via FTP and locate the main /oxide/ directory. Inside this download, you will see two folders: config and data. Simply drag and drop these into your server's /oxide/ folder. When prompted by your FTP client, choose "Overwrite" or "Merge" to ensure the new files are correctly placed. Once the transfer is complete, reactivate the plugin by typing: o.reload RaidableBases. You should see the updated loot tables appearing in the console logs. To verify that the bases have been recognized, use the command: rb.config list. This will display all the new schematic files now located in oxide/data/copypaste/. If the list appears empty, please double-check your file paths and try the process again. In the future, we will continue to increase the number of bases and perfect every single one.

Hello everyone! This is already my second project, and I’ve put a lot of heart into it. My team and I have worked hard to make it as interesting as possible and to include even more bases. Inside, you’ll find very cool features and lifehacks, so I can guarantee that once you purchase this package, you’ll truly enjoy using it. We have focused on creating more level 4, 5, and 6 bases, as these are the most popular choices! As mentioned before, this package also includes the acquisition and configuration for the level 6 pack—something brand new that hasn't been seen before. That’s why we highly recommend it! Setup Guide for Your New Bases To ensure a clean installation, start by disabling the current plugin. Enter the following command into your server console: o.unload RaidableBases. If you have used this plugin before, it is essential to clear out any old settings. Please delete the following: The configuration file: oxide/config/RaidableBases.json The entire data directory: oxide/data/RaidableBases/ Now, access your server files via FTP and locate the main /oxide/ directory. Inside this download, you will see two folders: config and data. Simply drag and drop these into your server's /oxide/ folder. When prompted by your FTP client, choose "Overwrite" or "Merge" to ensure the new files are correctly placed. Once the transfer is complete, reactivate the plugin by typing: o.reload RaidableBases. You should see the updated loot tables appearing in the console logs. To verify that the bases have been recognized, use the command: rb.config list. This will display all the new schematic files now located in oxide/data/copypaste/. If the list appears empty, please double-check your file paths and try the process again. Thank you for appreciating our work and for standing by us!

New Plugin: Custom Raidable Bases (Raidable Bases Extension) Hello Rust Community! I'm JaaaaaThomas I'm excited to introduce my first plugin: an exclusive collection of custom raid bases designed to enhance your server's PVE/PVP experience! 37 bases This is just the beginning, but we are ready to bring a fresh breath of air to how players interact with the Raidable Bases plugin. What You Get with This Package This package is not a standalone plugin, but a Content Extension that adds a selection of unique, handcrafted, and optimized Raid Bases directly to your server. Key Features: New Bases, New Challenges: I've included an entirely new difficulty category (ClanBase), featuring smart layouts designed to test even the most experienced raiders. Custom Loot: The bases come with a revised loot scheme, specifically balanced for a clan-level experience. Optimization & Configuration: All bases are designed to work seamlessly with popular difficulty settings. Attention: Required Dependencies For this base pack to function, your server MUST have the following two plugins installed and working: [Oxide/uMod Plugin] Raidable Bases (The main event plugin). [Oxide/uMod Plugin] Copy Paste (Required to correctly import the base structures). Without these two plugins, the base pack will NOT work. Future Vision This is only the first step! In the future, we plan to expand the package by: Adding new difficulty categories (Solo, Duo, Mega-Base). Introducing unique puzzles and traps within the structures. Providing constant updates with new bases for every major wipe. Thank you so much for your support! I hope you enjoy the new bases. I wish you all a good game and successful raids! — Sincerely, JaaaaaThomas.

The plugin allows players to visit a cold atmospheric Space void of gravity and oxygen, and visit an International Space Station! A Space Station appears high in the sky, and is surrounded by Meteorites, Spaceships, and Balloons. There is no gravity in Space, the temperature is very low and there is no oxygen. You can get to Space by a Spaceship or by a Balloon which also spawn near roads or in loot tables. The Space Station is guarded by customizable NPCs and a Space Bradley. Outer Space Meteorites, Crates, NPCs, Balloons and Spaceships will spawn in Outer Space near the Space Station, the number of each can be configured and customized. In order to survive in Outer Space, the player will need a Spacesuit. A Spacesuit can be customized to be any piece of clothing. In the config you can customize items that will perform the functions of the Spacesuit in whole or in part. To make space dark for players at any time of the day, use the NightVision plugin Space Station The Space Station consists of several compartments that are separated from each other by doors. Optionally, the doors can be locked and they will need to be raided. Inside the station there are crates with loot, NPCs, turrets, and fire turrets. At the end of the corridor there are two doors that open with blue cards and one door that opens with red. The spawn of the space station can be disabled. All objects on the space station are configured in the Data file of this station Spaceship The plugin includes spaceships that can spawn near roads, in Space, or can be added to loot tables. The ship has separate settings for flying in the normal atmosphere and in zero gravity in Space. It can shoot torpedoes, which will help the player in capturing the space station. There are two seats in each spaceship. Shuttle Control Guide: Balloon A balloon is an ordinary balloon with which you can ride into outer space. The balloon can spawn near roads, in Space, or can be added to loot tables. Also, this function can be applied to all balloons on the server. If the balloon is in zero gravity, it can be used as an escape capsule! If necessary, the player can enter, press a button, and be taken out of Space into the normal atmosphere. Dependencies Required NpcSpawn Chat commands (only for administrators) /spacestart – launches the event in a random configuration /spacestart <eventPresetName> – launches the event in the <eventPresetName> configuration /spacestop – stops the event /spawnshuttle – spawn the shuttle in your position /spawnaerostat – spawn the aerostat in your position /spacepoint – creates a custom spawn point of the event in your position (after that, you need to enable custom spawn points in the config) Console commands (RCON only) spacestart – launches the event in a random configuration spacestart <eventPresetName> – launches the event in the <eventPresetName> configuration spacestop – stops the event givepurplecard <userId> <amount> – gives a space card to a player giveshuttle <userId> <amount> – gives a shuttle to a player giveaerostat <userId> <amount> – gives a shuttle to a player givespacesuit <space_suit_preset> <userId> <amount> – gives <space_suit_preset> to a player Config plugin_en – example of plugin configuration in English station_en – example of station configuration in English plugin_ru – example of plugin configuration in Russian station_ru – example of station configuration in Russian Dependencies (optional, not required) True PVE PveMode GUI Announcements Notify DiscordMessages AlphaLoot CustomLoot Economics Server Rewards IQEconomic Hooks void OnSpaceEventStop() void OnSpaceEventStart() API bool IsPositionInSpace(Vector3 position) float GetMinSpaceAltitude() bool IsEventActive() My Discord: adem9554 Join the Mad Mappers Discord here! Check out more of my work here!

Features Target Designator System: Players receive a binocular designator. Aim and left-click to mark a target point and call in an airstrike Strike and Nuke Support: Supports both standard F15 Strike and F15 Nuke runs, each with independent settings for planes, shots, rocket speed, delay, cooldown, and more Strike Modes: Includes multiple strike patterns: precise, circle, line, and carpet Custom F15 Flight: Flight altitude, plane speed, and pre-fire distance are fully configurable Aircraft spawn, fly their attack run, fire, and clean up automatically when the strike is complete Rocket Mechanics: Configurable rocket speed, rate of fire, shots per plane, plane stagger, and impact spread Direct Designator Delivery: Admins can deliver Strike or Nuke designators directly to players using the give subcommand In-Game Store: Optional in-game store support for purchasing Strike and Nuke designators. Supports Auto, Economics, and ServerRewards providers Admin Control Panel: Includes an in-game admin panel for managing store settings, strike settings, warnings, and zone restrictions without editing the config manually Combat Alerts: Includes target-marked warnings, inbound warnings, and countdown alerts with map grid support Blocked Use Zones: Can block strike usage while the caller is inside a safe zone, and can also block target points inside safe zones or monument bounds Commands are configurable from the config Permissions f15estrike.strike → allows using Strike designators f15estrike.nuke → allows using Nuke designators f15estrike.strike.give → allows giving Strike designators to other players f15estrike.nuke.give → allows giving Nuke designators to other players f15estrike.admin → full admin access and admin panel access Commands /f15 → opens the in-game F15 store /strike → gives the player an F15 Strike designator /nuke → gives the player an F15 Nuke designator /strike give <name|SteamId64> → gives an F15 Strike designator to another player /nuke give <name|SteamId64> → gives an F15 Nuke designator to another player Config { "Config Version": 3, "Flight altitude (m)": 250.0, "Plane speed (m/s)": 200.0, "Pre-fire distance (m)": 750.0, "Chat prefix": "[F15]", "Commands": { "Strike": { "Enabled": true, "Primary": "strike", "Aliases": [] }, "Nuke": { "Enabled": true, "Primary": "nuke", "Aliases": [] } }, "Blocked use zones": { "Block caller while inside a safe zone": true, "Block target point inside a safe zone": true, "Block target point inside monument bounds": false }, "Global warnings": { "Enabled": true, "Broadcast when target is marked": true, "Broadcast countdown reminders": true, "Countdown warning seconds": 5, "Broadcast when aircraft are inbound": true, "Include map grid": true, "Include world coordinates": true }, "Purchases": { "Enabled": false, "Provider (Auto/Economics/ServerRewards)": "Auto", "Strike": { "Enabled": true, "Cost": 1500.0 }, "Nuke": { "Enabled": true, "Cost": 10000.0 } }, "Strike": { "Planes (count)": 1, "Shots per plane": 10, "Rocket speed (m/s)": 150.0, "Rate of fire (shots/sec)": 2.5, "Stagger between planes (s)": 0.25, "Impact spread radius (m)": 3.0, "Confirm delay (s)": 5.0, "Cooldown (s)": 5.0, "Default mode": "circle", "Designator display name": "F15 Strike" }, "Nuke": { "Planes (count)": 5, "Shots per plane": 10, "Rocket speed (m/s)": 200.0, "Rate of fire (shots/sec)": 1.5, "Stagger between planes (s)": 0.35, "Impact spread radius (m)": 6.0, "Confirm delay (s)": 6.0, "Cooldown (s)": 120.0, "Default mode": "circle", "Designator display name": "F15 Nuke" } } Need Support?

This custom package, created by us, includes 100 handcrafted bases across three difficulty levels, ranging from Easy to Hard. Note: The building skins in the package showcase images may differ from the spawned bases or use the default building skin. If you're looking for a more advanced pack, you can get the upgraded version here, which includes 210 bases ranging from Easy to Nightmare along with the Loot Tables package: https://codefling.com/bases/raidable-bases-mega-pack-loot-tables-210-bases Warning: The Raidable Bases plugin requires the Copy Paste plugin to function. You must install both for this bases pack to work. Raidable Bases (Paid): https://codefling.com/plugins/raidable-bases Copy Paste (Free): https://umod.org/plugins/copy-paste This Raidable Bases package includes: (In addition to the bases, it includes a well-configured config file that can be uploaded to /serverfiles/oxide/config, but its usage is optional. It also contains 5 different profile configs that can be uploaded to /oxide/data/RaidableBases/Profiles. These are also well-configured and optional to use. The usage of both is entirely up to you.) 40 Easy Bases 30 Medium Bases 30 Hard Bases WARNING: TWO DIFFERENT INSTALLATION METHODS (PLEASE READ BOTH AND APPLY ONLY THE ONE THAT FITS YOUR NEEDS) INSTALLATION GUIDE 1 (If you do not have a custom configuration and are not a professional in server configurations, choose this option. However, if you already have your own configuration and profile settings and do not wish to use the optional configs we provide—in other words, if you only need the bases—use the second installation guide instead.) Step 1: Place the Config File From the extracted ZIP files, locate the config folder and find the RaidableBases.json file. Move it to the following directory: /serverfiles/oxide/config Step 2: Place the Bases From the extracted ZIP files, locate the copypaste folder and move it to the following directory: /serverfiles/oxide/data Step 3: Place the Profiles Folder From the extracted ZIP files, locate the profiles folder and move it to the following directory: /serverfiles/oxide/data/RaidableBases Why Are Profiles Important? The profiles folder contains crucial settings that allow you to: Enable/disable the dome Enable/disable NPCs Adjust the number of lootable items These are just a few examples—there are dozens of important settings that directly affect how raid bases function. The config file alone is not enough—these files play a major role in customizing your raid bases. I strongly recommend reviewing each difficulty setting (Easy to Hard) inside the profiles folder and adjusting them based on your needs. Step 4: Restart the plugin via RCON: o.reload RaidableBases INSTALLATION GUIDE 2 (Use this installation method if you do not want to use our configurations and instead prefer to use your own config files and your own /oxide/data/RaidableBases/Profiles configurations.) In this case, you only need to add the bases. To do this, use the following commands in RCON: Step 1: You can add bases one by one or in bulk. After executing the commands in RCON, the bases will be registered inside the Profiles configuration. If you do not want to deal with these adjustments, it is recommended to use Installation Guide 1 instead. A- Example RCON commands: rb.config add "Easy Bases" fullwipedeasy31 rb.config add "Hard Bases" fullwipedhard31 B- Commands to Integrate Raid Bases in Bulk via RCON: rb.config add "Easy Bases" fullwipedeasy31 fullwipedeasy32 fullwipedeasy33 fullwipedeasy34 fullwipedeasy35 fullwipedeasy36 fullwipedeasy37 fullwipedeasy38 fullwipedeasy39 fullwipedeasy40 fullwipedeasy41 fullwipedeasy42 fullwipedeasy43 fullwipedeasy44 fullwipedeasy45 fullwipedeasy46 fullwipedeasy47 fullwipedeasy48 fullwipedeasy49 fullwipedeasy50 fullwipedeasy51 fullwipedeasy52 fullwipedeasy53 fullwipedeasy54 fullwipedeasy55 fullwipedeasy56 fullwipedeasy57 fullwipedeasy58 fullwipedeasy59 fullwipedeasy60 fullwipedeasy61 fullwipedeasy62 fullwipedeasy63 fullwipedeasy64 fullwipedeasy65 fullwipedeasy66 fullwipedeasy67 fullwipedeasy68 fullwipedeasy69 fullwipedeasy70 rb.config add "Medium Bases" fullwipedmed31 fullwipedmed32 fullwipedmed33 fullwipedmed34 fullwipedmed35 fullwipedmed36 fullwipedmed37 fullwipedmed38 fullwipedmed39 fullwipedmed40 fullwipedmed41 fullwipedmed42 fullwipedmed43 fullwipedmed44 fullwipedmed45 fullwipedmed46 fullwipedmed47 fullwipedmed48 fullwipedmed49 fullwipedmed50 fullwipedmed51 fullwipedmed52 fullwipedmed53 fullwipedmed54 fullwipedmed55 fullwipedmed56 fullwipedmed57 fullwipedmed58 fullwipedmed59 fullwipedmed60 rb.config add "Hard Bases" fullwipedhard31 fullwipedhard32 fullwipedhard33 fullwipedhard34 fullwipedhard35 fullwipedhard36 fullwipedhard37 fullwipedhard38 fullwipedhard39 fullwipedhard40 fullwipedhard41 fullwipedhard42 fullwipedhard43 fullwipedhard44 fullwipedhard45 fullwipedhard46 fullwipedhard47 fullwipedhard48 fullwipedhard49 fullwipedhard50 fullwipedhard51 fullwipedhard52 fullwipedhard53 fullwipedhard54 fullwipedhard55 fullwipedhard56 fullwipedhard57 fullwipedhard58 fullwipedhard59 fullwipedhard60 Step 3: Restart the plugin via RCON: o.reload RaidableBases EXTRA IMPORTANT INFORMATIONS: We do not use a dome, NPCs, or arena walls around raid bases on our servers, and in the ZIP file we provided, these features are also disabled by default. If you want to enable them, you will need to adjust the settings accordingly. For example, to enable the dome, follow the steps below: Navigate to: /oxide/data/RaidableBases/Profiles Open the files inside the Profiles folder with a text editor. Locate the following settings: (This is already set to false because it is required for markers to appear on the map.) "Spawn Silently (No Notification, No Dome, No Map Marker)": false, "Create Dome Around Event Using Spheres (0 = disabled, recommended = 5)": 0, Change the value from 0 to 5 as shown below: "Create Dome Around Event Using Spheres (0 = disabled, recommended = 5)": 5, In our setup: - Timed events and purchasable events are disabled. - After a wipe, easy bases will start spawning 30 minutes later. - Nightmare bases will begin spawning 48 hours (2 days) later. Imagine starting the game with just a torch in hand and immediately encountering a nightmare base on the shore. You’d likely quit the game right away—this setting is crucial for us to avoid such scenarios. Configuration Example: serverfiles/oxide/config "Maintained Events": { "Always Maintain Max Events": true, "Max Maintained Events": 30, "Enable X Hours After Wipe (0 = immediately)": { "Easy": 0.5, "Medium": 1.0, "Hard": 3.0, "Expert": 24.0, "Nightmare": 48.0 All of our bases from Easy to Nightmare are equipped with turret protection. If you do not want turrets to spawn in your raidable bases on your server, you can use the following method. Go to the file path /data/RaidableBases/Profiles, open the JSON files inside with a text editor, and apply the following: "Kill These Prefabs After Paste": [ "assets/prefabs/npc/autoturret/autoturret_deployed.prefab", "autoturret_deployed" ], If you need not only these bases but also the loot tables for the items that will spawn inside them, check out our one-of-a-kind, exceptional Raidable Base Loot Tables at the link below: https://codefling.com/customizations/raidable-bases-loot-tables-pack (Our loot tables are designed to cater to different server types, including Vanilla (1x) servers as well as 2x, 3x, 5x, 10x, and higher multipliers to match various loot requirements.) If you are satisfied with this package, you can support us by leaving a 5-star review on the site where you purchased it. Your feedback motivates us to continue improving and providing even better configurations for dedicated server owners like you. Thank you! Support: FULLWIPED DISCORD

This is a custom package created by us, featuring 110 handcrafted bases across five difficulty levels, ranging from Easy to Nightmare. Note: The building skins in the package showcase images may differ from the spawned bases or use the default building skin. (This package does not include loot tables. If you need bases + loot tables, you may want to check out the higher-tier package: 110 Raibable Bases + Loot Tables package) Warning: The Raidable Bases plugin requires the Copy Paste plugin to function. You must install both for this bases pack to work. Raidable Bases (Paid): https://codefling.com/plugins/raidable-bases Copy Paste (Free): https://umod.org/plugins/copy-paste This Raidable Bases package includes: (In addition to the bases, it includes a well-configured config file that can be uploaded to /serverfiles/oxide/config, but its usage is optional. It also contains 5 different profile configs that can be uploaded to /oxide/data/RaidableBases/Profiles. These are also well-configured and optional to use. The usage of both is entirely up to you.) 30 Easy Bases 30 Medium Bases 30 Hard Bases 10 Expert Bases 10 Nightmare Bases WARNING: TWO DIFFERENT INSTALLATION METHODS (PLEASE READ BOTH AND APPLY ONLY THE ONE THAT FITS YOUR NEEDS) INSTALLATION GUIDE 1 (If you do not have a custom configuration and are not a professional in server configurations, choose this option. However, if you already have your own configuration and profile settings and do not wish to use the optional configs we provide—in other words, if you only need the bases—use the second installation guide instead.) ▶ Step 1: Place the Config File From the extracted ZIP files, locate the config folder and find the RaidableBases.json file. Move it to the following directory: /serverfiles/oxide/config ▶ Step 2: Place the Bases From the extracted ZIP files, locate the copypaste folder and move it to the following directory: /serverfiles/oxide/data ▶ Step 3: Place the Profiles Folder From the extracted ZIP files, locate the profiles folder and move it to the following directory: /serverfiles/oxide/data/RaidableBases Why Are Profiles Important? The profiles folder contains crucial settings that allow you to: Enable/disable the dome Enable/disable NPCs Adjust the number of lootable items These are just a few examples—there are dozens of important settings that directly affect how raid bases function. The config file alone is not enough—these files play a major role in customizing your raid bases. I strongly recommend reviewing each difficulty setting (Easy to Nightmare) inside the profiles folder and adjusting them based on your needs. ▶ Step 4: Restart the plugin via RCON: o.reload RaidableBases INSTALLATION GUIDE 2 (Use this installation method if you do not want to use our configurations and instead prefer to use your own config files and your own /oxide/data/RaidableBases/Profiles configurations.) In this case, you only need to add the bases. To do this, use the following commands in RCON: ▶ Step 1: You can add bases one by one or in bulk. After executing the commands in RCON, the bases will be registered inside the Profiles configuration. Note: If you do not want to deal with these adjustments, it is recommended to use Installation Guide 1 instead. A- Example RCON commands: rb.config add "Easy Bases" fullwipedeasy1 rb.config add "Hard Bases" fullwipedhard1 B- Commands to Integrate Raid Bases in Bulk via RCON: 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 ▶ Step 2: Restart the plugin via RCON: o.reload RaidableBases EXTRA IMPORTANT INFORMATIONS: We do not use a dome, NPCs, or arena walls around raid bases on our servers, and in the ZIP file we provided, these features are also disabled by default. If you want to enable them, you will need to adjust the settings accordingly. For example, to enable the dome, follow the steps below: Navigate to: /oxide/data/RaidableBases/Profiles Open the files inside the Profiles folder with a text editor. Locate the following settings: (This is already set to false because it is required for markers to appear on the map.) "Spawn Silently (No Notification, No Dome, No Map Marker)": false, "Create Dome Around Event Using Spheres (0 = disabled, recommended = 5)": 0, Change the value from 0 to 5 as shown below: "Create Dome Around Event Using Spheres (0 = disabled, recommended = 5)": 5, In our setup: - Timed events and purchasable events are disabled. - After a wipe, easy bases will start spawning 30 minutes later. - Nightmare bases will begin spawning 48 hours (2 days) later. Imagine starting the game with just a torch in hand and immediately encountering a nightmare base on the shore. You’d likely quit the game right away—this setting is crucial for us to avoid such scenarios. Configuration Example: /serverfiles/oxide/config "Maintained Events": { "Always Maintain Max Events": true, "Max Maintained Events": 30, "Enable X Hours After Wipe (0 = immediately)": { "Easy": 0.5, "Medium": 1.0, "Hard": 3.0, "Expert": 24.0, "Nightmare": 48.0 All of our bases from Easy to Nightmare are equipped with turret protection. If you do not want turrets to spawn in your raidable bases on your server, you can use the following method. Go to the file path /data/RaidableBases/Profiles, open the JSON files inside with a text editor, and apply the following: "Kill These Prefabs After Paste": [ "assets/prefabs/npc/autoturret/autoturret_deployed.prefab", "autoturret_deployed" ], If you need not only these bases but also the loot tables for the items that will spawn inside them, check out our one-of-a-kind, exceptional Raidable Base Loot Tables at the link below: https://codefling.com/customizations/raidable-bases-loot-tables-pack (Our loot tables are designed to cater to different server types, including Vanilla (1x) servers as well as 2x, 3x, 5x, 10x, and higher multipliers to match various loot requirements.) If you are satisfied with this package, you can support us by leaving a 5-star review on the site where you purchased it. Your feedback motivates us to continue improving and providing even better configurations for dedicated server owners like you. Please leave a review here: https://codefling.com/bases/raidable-bases-pack-110-bases?tab=reviews Thank you!

This is a custom package designed by us, featuring 210 unique bases and a specialized loot setup for five different difficulty levels, ranging from Easy to Nightmare. Note: The building skins in the package showcase images may differ from the spawned bases or use the default building skin. This MEGA PACK is an upgraded version of the FullWiped-110 Bases + Loot Pack we previously offered. If you've already purchased the FullWiped-110 Bases + Loot Pack, you only need to buy the expansion pack, which includes 100 new bases ranging from Easy to Hard. Get it here: https://codefling.com/bases/raidable-bases-pack-100-bases-expanded-package-from-easy-to-hard Warning: The Raidable Bases plugin requires the Copy Paste plugin to function. You must install both for this bases pack to work. Raidable Bases (Paid): https://codefling.com/plugins/raidable-bases Copy Paste (Free): https://umod.org/plugins/copy-paste This Raidable Bases Pack & Loot Tables package includes: 70 Easy Bases +Base_Loot Tables (Easy "Vanilla" and "Enhanced" tables included) 60 Medium Bases +Base_Loot Tables (Medium "Vanilla" and "Enhanced" tables included) 60 Hard Bases +Base_Loot Tables (Hard "Vanilla" and "Enhanced" tables included) 10 Expert Bases +Base_Loot Tables (Expert "Vanilla" and "Enhanced" tables included) 10 Nightmare Bases +Base_Loot Tables (Nightmare "Vanilla" and "Enhanced" tables included) Beware: Our loot table package includes only the 5-tier loot tables within the Base_loot folder, ranging from easy to nightmare. It does not include the loot tables from the Difficulty_Loot or Weekday_Loot folders. VANILLA AND ENHANCED LOOT TABLES FOR RAIDABLE BASES This package includes 10 different base loot table files, ensuring a well-structured and advanced configuration for every difficulty level, from Easy to Nightmare. - 5 loot files for the Vanilla setup (Easy, Medium, Hard, Expert, Nightmare), offering a balanced loot experience with some junk items, staying close to a 1x rate. - 5 loot files for the Enhanced setup (Easy, Medium, Hard, Expert, Nightmare), designed for modded servers with 2x, 3x, or higher gather rates, featuring cleaner loot tables with minimal junk and more valuable rewards. Installation Path: All loot table files are intended for the /oxide/data/RaidableBases/Base_Loot directory. Setup Requirement: You must choose and install only one loot table setup at a time—either Vanilla or Enhanced. If you want to switch, you can replace the current files with the other set, but both cannot be active simultaneously. For those exclusively seeking the loot table, we offer it as a standalone product: https://codefling.com/customizations/raidable-bases-loot-tables-pack (Note: If you've purchased our Raidable Bases Mega Pack & Loot Tables (210 Bases) package, there is no need to buy this separately.) WARNING: TWO DIFFERENT INSTALLATION METHODS (PLEASE READ BOTH AND APPLY ONLY THE ONE THAT FITS YOUR NEEDS) INSTALLATION GUIDE 1: (If you do not have a custom configuration and are not a professional in server configurations, choose this option. However, if you already have your own configuration and profile settings and do not wish to use the optional configs we provide—in other words, if you only need the bases and loot tables—use the second installation guide instead.) ▶ Step 1: Place the Config File From the extracted ZIP files, locate the config folder and find the RaidableBases.json file. Move it to the following directory: /serverfiles/oxide/config ▶ Step 2: Place the Bases From the extracted ZIP files, locate the copypaste folder and move it to the following directory: /serverfiles/oxide/data ▶ Step 3: Place the Base_Loot Tables From the extracted ZIP files, locate the Base_Loot folder and move it to the following directory: /serverfiles/oxide/data/RaidableBases Important: If there are any existing JSON files inside this folder that are not part of our loot tables, delete them to ensure proper functionality. Choose between Vanilla or Enhanced loot tables based on your preference. If the folder is named "Base_Loot (Enhanced loot)", remove the text in parentheses so that the correct folder name is simply: "Base_Loot" (Otherwise, the loot tables will not work properly.) ▶ Step 4: Place the Profiles Folder From the extracted ZIP files, locate the profiles folder and move it to the following directory: /serverfiles/oxide/data/RaidableBases Why Are Profiles Important? The profiles folder contains crucial settings that allow you to: Enable/disable the dome Enable/disable NPCs Adjust the number of lootable items These are just a few examples—there are dozens of important settings that directly affect how raid bases function. The config file alone is not enough—these files play a major role in customizing your raid bases. I strongly recommend reviewing each difficulty setting (Easy to Nightmare) inside the profiles folder and adjusting them based on your needs. ▶ Step 5: Restart the plugin via RCON: o.reload RaidableBases INSTALLATION GUIDE 2: (Use this installation method if you do not want to use our configurations and instead prefer to use your own config files and your own /oxide/data/RaidableBases/Profiles configurations.) In this case, you only need to add the bases. To do this, use the following commands in RCON: ▶ Step 1: You can add bases one by one or in bulk. After executing the commands in RCON, the bases will be registered inside the Profiles configuration. If you do not want to deal with these adjustments, it is recommended to use Installation Guide 1 instead. A- Example RCON commands: rb.config add "Easy Bases" fullwipedeasy1 rb.config add "Hard Bases" fullwipedhard1 B- Commands to Integrate Raid Bases in Bulk via RCON: 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 fullwipedeasy31 fullwipedeasy32 fullwipedeasy33 fullwipedeasy34 fullwipedeasy35 fullwipedeasy36 fullwipedeasy37 fullwipedeasy38 fullwipedeasy39 fullwipedeasy40 fullwipedeasy41 fullwipedeasy42 fullwipedeasy43 fullwipedeasy44 fullwipedeasy45 fullwipedeasy46 fullwipedeasy47 fullwipedeasy48 fullwipedeasy49 fullwipedeasy50 fullwipedeasy51 fullwipedeasy52 fullwipedeasy53 fullwipedeasy54 fullwipedeasy55 fullwipedeasy56 fullwipedeasy57 fullwipedeasy58 fullwipedeasy59 fullwipedeasy60 fullwipedeasy61 fullwipedeasy62 fullwipedeasy63 fullwipedeasy64 fullwipedeasy65 fullwipedeasy66 fullwipedeasy67 fullwipedeasy68 fullwipedeasy69 fullwipedeasy70 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 fullwipedmed31 fullwipedmed32 fullwipedmed33 fullwipedmed34 fullwipedmed35 fullwipedmed36 fullwipedmed37 fullwipedmed38 fullwipedmed39 fullwipedmed40 fullwipedmed41 fullwipedmed42 fullwipedmed43 fullwipedmed44 fullwipedmed45 fullwipedmed46 fullwipedmed47 fullwipedmed48 fullwipedmed49 fullwipedmed50 fullwipedmed51 fullwipedmed52 fullwipedmed53 fullwipedmed54 fullwipedmed55 fullwipedmed56 fullwipedmed57 fullwipedmed58 fullwipedmed59 fullwipedmed60 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 fullwipedhard31 fullwipedhard32 fullwipedhard33 fullwipedhard34 fullwipedhard35 fullwipedhard36 fullwipedhard37 fullwipedhard38 fullwipedhard39 fullwipedhard40 fullwipedhard41 fullwipedhard42 fullwipedhard43 fullwipedhard44 fullwipedhard45 fullwipedhard46 fullwipedhard47 fullwipedhard48 fullwipedhard49 fullwipedhard50 fullwipedhard51 fullwipedhard52 fullwipedhard53 fullwipedhard54 fullwipedhard55 fullwipedhard56 fullwipedhard57 fullwipedhard58 fullwipedhard59 fullwipedhard60 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 ▶ Step 2: Place the Base_Loot Tables From the extracted ZIP files, locate the Base_Loot folder and move it to the following directory: /serverfiles/oxide/data/RaidableBases Important: If there are any existing JSON files inside this folder that are not part of our loot tables, delete them to ensure proper functionality. Choose between Vanilla or Enhanced loot tables based on your preference. If the folder is named "Base_Loot (Enhanced loot)", remove the text in parentheses so that the correct folder name is simply: "Base_Loot" (Otherwise, the loot tables will not work properly.) ▶ Step 3: Restart the plugin via RCON: o.reload RaidableBases EXTRA IMPORTANT INFORMATIONS: We do not use a dome, NPCs, or arena walls around raid bases on our servers, and in the ZIP file we provided, these features are also disabled by default. If you want to enable them, you will need to adjust the settings accordingly. For example, to enable the dome, follow the steps below: Navigate to: /oxide/data/RaidableBases/Profiles Open the files inside the Profiles folder with a text editor. Locate the following settings: (This is already set to false because it is required for markers to appear on the map.) "Spawn Silently (No Notification, No Dome, No Map Marker)": false, "Create Dome Around Event Using Spheres (0 = disabled, recommended = 5)": 0, Change the value from 0 to 5 as shown below: "Create Dome Around Event Using Spheres (0 = disabled, recommended = 5)": 5, Additionally, the loot amount for bases varies depending on the difficulty level (easy, medium, hard, expert, and nightmare). You can adjust this setting in the same Profiles location according to your needs: "Amount Of Items To Spawn": 210, For example, in medium bases, this value is set to 210, which determines the total number of items that will appear in crates, furnaces, and the cupboard. Our current configuration is specifically adjusted to prevent players from feeling overwhelmed by massive buildings right after a wipe. We have configured Maintained Events accordingly to ensure a balanced experience. In our setup: - Timed events and purchasable events are disabled. - After a wipe, easy bases will start spawning 30 minutes later. - Nightmare bases will begin spawning 48 hours (2 days) later. Imagine starting the game with just a torch in hand and immediately encountering a nightmare base on the shore. You’d likely quit the game right away—this setting is crucial for us to avoid such scenarios. Configuration Example: /serverfiles/oxide/config "Maintained Events": { "Always Maintain Max Events": true, "Max Maintained Events": 30, "Enable X Hours After Wipe (0 = immediately)": { "Easy": 0.5, "Medium": 1.0, "Hard": 3.0, "Expert": 24.0, "Nightmare": 48.0 All of our bases from Easy to Nightmare are equipped with turret protection. If you do not want turrets to spawn in your raidable bases on your server, you can use the following method. Go to the file path /data/RaidableBases/Profiles, open the JSON files inside with a text editor, and apply the following: "Kill These Prefabs After Paste": [ "assets/prefabs/npc/autoturret/autoturret_deployed.prefab", "autoturret_deployed" ], If you are satisfied with this package, you can support us by leaving a 5-star review on the site where you purchased it. Your feedback motivates us to continue improving and providing even better configurations for dedicated server owners like you. Thank you!

Author: MEMUARE Type: BuildBlock / Deployables / repair Version: 2.3.1 Lang files included : (RU/ENG) Description Advanced Softcore Base Destruction System for Rust Vanilla servers SoftBuild is an advanced softcore system for Rust servers that changes how base destruction works — without breaking vanilla mechanics. The plugin is designed to make raids less destructive, bases more recoverable, and gameplay fairer and more controlled, while still rewarding raiders. System Features After a cupboard is destroyed, the people registered in it don't lose their building privileges. Raiders can't install their own cupboard and ruin your house. After a raid, attackers won't be able to steal your deployables; they can only break them. The house owner is given N amount of time to restore broken deployables. Deployables remember their skinid to restore their skin when repaired. The visual appearance of cupboard debris depends on the cupboard's skin. Why SoftBuild? Reduce raid frustration Give players a recovery window Keep raids rewarding, not destructive Maintain the vanilla Rust feeling Configuration You can configure how long broken cupboard and deployables will stay in place. Ability to disable certain deployables to restore them. { "CleanupTimeSeconds": 86400.0, "SoftDeployables": { "Enabled": true, "Deployables": { "assets/prefabs/deployable/bed/bed_deployed.prefab": { "Enabled": true, "CorpsePrefab": "assets/prefabs/deployable/bed/bed_deployed.corpse.prefab" },

Expert Raid Pack – High-Intensity Raidable Bases Greetings, raider. Expert Raid Pack is a collection of high-difficulty raid bases designed for skilled and well-prepared Rust players. These bases deliver serious defensive pressure and require coordination, planning, and solid resource investment to complete successfully. This is advanced-tier content built for experienced raiders. What’s Included • 5 unique Expert-difficulty raid bases • Complex layouts with strong internal and external defenses • Heavy use of turrets, traps, and controlled combat zones • Tight corridors, calculated peek angles, and layered protection • Clean and optimized schematic files (no unnecessary assets or bloat) • Fully compatible with the Raidable Bases plugin Designed For ✔ Experienced players and organized teams ✔ Servers that want challenging endgame-style content ✔ PvE servers seeking high-pressure raid events ✔ PvP servers looking for valuable and contested raid targets Quality & Optimization All files are compact, clean, and optimized. No unnecessary images, duplicated data, or unused assets are included. File sizes reflect only actual base complexity and content. Support & Future Updates If you encounter any issues, need help with installation, or have ideas for future raid bases, feel free to contact me. Feedback is always welcome and helps improve future content. Discord: _real_krw_ Thank you for supporting independent Rust content creation. More packs and updates are planned.

Hard Raid Pack Heavy fire. Tight defenses. No easy wins. Greetings, raider. Hard Raid Pack is a collection of high-difficulty raid bases designed for experienced Rust players who are ready for serious resistance. These bases deliver strong defensive pressure and require planning, coordination, and solid resource investment to complete successfully. This pack is built for players who want demanding but fair raid encounters. What’s Included • 5 completely unique Hard-difficulty raid bases • Structured layouts with calculated defensive positioning • Strong defensive setups: turrets, traps, and controlled combat areas • Reinforced core sections with increased internal pressure • Clean and optimized schematic files (no unnecessary assets or bloat) • Fully compatible with the Raidable Bases plugin Designed For ✔ Experienced players seeking a demanding raid experience ✔ Servers that want challenging and competitive content ✔ PvE servers running high-pressure raid events ✔ PvP servers looking for valuable and contested raid locations Quality & Optimization All files are compact, clean, and optimized. No unnecessary images, duplicated data, or unused assets are included. File sizes reflect only actual base content and structural complexity. Support & Future Updates If you encounter any issues, need help with installation, or have ideas for future raid bases, feel free to contact me. Feedback is always welcome and helps improve future content. Discord: _real_krw_ Thank you for supporting independent Rust content creation. More packs and updates are planned.

Medium Raid Pack – Balanced Challenge Greetings, raider. Medium Raid Pack is a collection of raid bases designed for players seeking a fair and strategic Rust experience. These bases provide moderate difficulty suitable for organized players who want engaging content without being overwhelming. What’s Included • 5 unique Medium-difficulty raid bases • Multiple raid paths in each base (no single correct solution) • Balanced defensive setups: turrets, traps, and tactical chokepoints • Strategic layouts that encourage planning and decision-making • Clean and optimized schematic files (no unnecessary assets or bloat) • Fully compatible with the Raidable Bases plugin Designed For ✔ Players looking for a tactical challenge at moderate difficulty ✔ Servers that want balanced and engaging raid content ✔ PvE servers seeking event-style bases with fair risk ✔ PvP servers looking for competitive but accessible raid targets Quality & Optimization All files are compact, clean, and optimized. No unnecessary images, duplicated data, or unused assets are included. File sizes reflect only actual base content and complexity. Support & Future Updates If you encounter any issues, need help with installation, or have ideas for future raid bases, feel free to contact me. Feedback is always welcome and helps improve future content. Discord: _real_krw_ Thank you for supporting independent Rust content creation. More packs and updates are planned.

ServerPeriods.cs Description : - This plugin offers a complete periodic event system for your Rust server, allowing you to create structured game phases with customizable restrictions. Each period can independently control PvP, raiding, gathering, and building permissions, providing a dynamic gameplay experience. It includes a persistent, real-time user interface displaying the current period name and remaining time, with an automatic "Next Period" indicator, and the execution of custom server commands for each period. Settings : - HUD colors - Custom periods (name/perms/time/commands) F1 Commands : - p.start (to start the periods) - p.stop (to stop the periods) - p.next (to move on to the next period) - p.prev (to move on to the previous period) Permissions : - ownerid <steamID/user> WuyZar's Discord : https://discord.gg/NVwRcQwGwh Chat messages : Game interface :

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 .

Base Insight provides players with the ability to ping loot containers and tool cupboards inside buildings. This allows players to quickly identify valuable loot containers and strategic tool cupboards within a specified radius. Features • Loot Container Pinging – Ping supported storage containers inside a base including large wooden boxes, coffins, barrels, fridges, lockers, vending machines, wall cabinets, drop boxes, and weapon racks. • Tool Cupboard Pinging – Locate Tool Cupboards inside a scanned base. • Allowed Container List – Choose exactly which storage containers can be pinged using the allowed container list in the config. • Loot-Only Pinging – Optionally only ping supported containers that currently contain loot. • Raidable Bases Only Option – Optionally restrict the scanner so it can only be used on **Raidable Bases**. • Customizable Scanner Settings – Adjust scan radius, max distance, ping delay, ping duration, scanner skin, scanner display name, ping types, and more. • Permission-Based Cooldowns – Set a default scan cooldown and override it with permission-based cooldowns. • Chat and Console Distribution – Give the scanner to players through chat command aliases or via console command. • Loot Support – Optionally add the scanner item into supported loot containers with configurable chances and min/max amounts. Permissions • baseinsight.use – Required to use the Base Insight scanner. • baseinsight.give – Required to use the chat command to receive a scanner. Commands Chat Commands • /bis – Gives the Base Insight scanner item to the player. Console Commands • bis [SteamID] – Gives the Base Insight scanner item to the target player. • bi_wipe – Manually wipe the cooldown data file *(automatically wipes on new wipes)*. Configuration Options Scanner Settings • Scanner Display Name – Display name of the Base Insight scanner item. • Scanner Skin ID – Skin ID used for the scanner item. • Enable Storage Containers – Enable or disable storage container pinging. • Enable Tool Cupboard – Enable or disable tool cupboard pinging. • Only Use On RaidableBases – Restrict scanner use to Raidable Bases only. • Only Ping Containers with Loot – Only ping supported containers that currently contain loot. • Destroy Scanner After Use – Destroy the scanner item after one successful use. • Max Distance from Base – Maximum distance the player can be from the base they are scanning. • Scan Radius – Radius around the targeted base used for scanning. • Ping Delay – How long the player must hold before the scan completes. • Ping Duration – How long pings remain visible. • Ping Type – Loot Containers – Ping type used for storage containers. • Ping Type – Tool Cupboard – Ping type used for tool cupboards. • Ping Types – List of available ping types included in the config for reference. Allowed Storage Containers Settings • Allowed Storage Container List – List of storage container prefab names that the scanner is allowed to ping. Permissions & Cooldown Settings • Chat Command Cooldown – Cooldown for receiving a scanner via chat command. • Default Scan Cooldown – Default cooldown between scans. • Scan Cooldowns By Permission – Permission-based scan cooldown overrides. Chat Command Settings • Chat Command Aliases – List of chat commands that give the scanner item. Loot Settings • Add Scanner To Loot Containers – Enable or disable adding the scanner item into loot containers. • Min Scanners Per Container – Minimum number of scanners that can be added. • Max Scanners Per Container – Maximum number of scanners that can be added. • Loot Containers List – Loot container prefab names and the chance for the scanner to be added. Default Configuration { "Scanner Settings": { "Scanner Display Name": "Base Insight Scanner", "Scanner Skin ID": 3242988854, "Enable Storage Containers": true, "Enable Tool Cupboard": true, "Only Use On RaidableBases": false, "Only Ping Containers with Loot": true, "Destroy Scanner After Use": false, "Max Distance from Base": 100, "Scan Radius": 50, "Ping Delay": 5, "Ping Duration": 20, "Ping Type - Loot Containers": 3, "Ping Type - Tool Cupboard": 2, "Ping Types": { "Hostile": 0, "GoTo": 1, "Dollar": 2, "Loot": 3, "Node": 4, "Gun": 5, "Build": 6 } }, "Allowed Storage Containers Settings": { "Allowed Storage Container List": [ "abyss_barrel_horizontal", "abyss_barrel_vertical", "bamboo_barrel", "box.wooden.large", "coffinstorage", "component.box.ammo.large", "component.box.armor.large", "component.box.charcoal.large", "component.box.clothing.large", "component.box.comps.large", "component.box.explosives.large", "component.box.food.large", "component.box.guns.large", "component.box.meds.large", "component.box.metal.large", "component.box.ore.large", "component.box.scrap.large", "component.box.stone.large", "component.box.sulfur.large", "component.box.tools.large", "component.box.wood.large", "dropbox.deployed", "electric.wallcabinet.deployed", "fridge.deployed", "krieg_storage_horizontal", "krieg_storage_vertical", "locker.deployed", "medieval.box.wooden.large", "minifridge.deployed", "pilot_hazmat_woodbox_deployed", "storage_barrel_b", "storage_barrel_c", "twitch_dropbox.deployed", "vendingmachine.deployed", "weaponrack_horizontal.deployed", "weaponrack_single1.deployed", "weaponrack_single2.deployed", "weaponrack_single3.deployed", "weaponrack_stand.deployed", "weaponrack_tall.deployed", "weaponrack_wide.deployed", "wicker_barrel", "woodbox_deployed" ] }, "Permissions & Cooldown Settings": { "Chat Command Cooldown": 3600, "Default Scan Cooldown": 60, "Scan Cooldowns By Permission": { "baseinsight.vip": 30, "baseinsight.elite": 10 } }, "Chat Command Settings": { "Chat Command Aliases": [ "bis", "givebis" ] }, "Loot Settings": { "Add Scanner To Loot Containers": false, "Min Scanners Per Container": 1, "Max Scanners Per Container": 1, "Loot Containers List": { "crate_elite": 0.2, "heli_crate": 0.8, "bradley_crate": 0.8, "codelockedhackablecrate": 0.5, "codelockedhackablecrate_oilrig": 0.5 } }, "Version": { "Major": 2, "Minor": 0, "Patch": 1 } } Language { "Cooldown": "Scan cooldown. Please wait {0} seconds.", "ChatCooldown": "You need to wait {0} seconds to use this command!", "ScanResult": "Found {0} loot containers and {1} Tool Cupboards.", "ScanResultLootOnly": "Found {0} loot containers.", "ScanResultTCOnly": "Found {0} Tool Cupboards.", "NoPerm": "You do not have permission for this command!", "RaidableBasesOnly": "Only Usable On RaidableBases!", "ItemReceived": "You Received A {0}", "NoPermission": "You Don't Have Permission To Use {0}", "TooFar": "Too far away from base! Max distance is {0}m.", "Error": "ERROR: No scannable targets are enabled in the config." }