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 force the decay of building blocks with Twigs grade, even if there is wood in the Tool Cupboard; The ability to toggle the gather resource restriction in someone else's Building Privileges; No one, except the owner or their friends, will be able to open their loot containers (chests, storages, bodies, etc.); Administrators can bypass loot restrictions; The ability to schedule the killing of players if they disconnect within someone else's Building Privilege; Disabling backpack and active item drop upon death, even if backpack is full; The ability to disable 'Give' messages; The ability to modify the items given at spawn on the beach; The ability to create an unlimited number of custom permissions; The ability to allow players to bypass the queue; The ability to set limits on sleeping bags, shelters and auto turrets for each permission; The ability to set a multiplier for the prices of monuments and events for each permission; The ability to customize the price and amount of vehicles for each of your custom permissions; The ability to assign vehicles to each player; The ability to customize the assigned price and available amount of vehicles for each of your custom permissions; An assigned vehicle can't be damaged, looted or pushed by other players, but it can be pushed if it is within someone else's Building Privilege; The ability to loot monuments through a queue system; The ability to configure monuments, setting their looting price and time, and adjusting status bars for each monument; The ability to acquire the privilege to loot events (helicopters, bradleys, and raidable bases) through a purchase; The ability to customize the price of each event types and loot attempts (lives); NPCs only aggress against players who are looting monuments, events or raidable bases; Only players who are looting monuments, events or raidable bases can inflict damage to NPCs; RaidableBases are protected from griefing(no damage, no loot and etc). Only the owner can interact with the raid; Neutral RaidableBases can be purchased; Prices for purchasing neutral raids are configurable for each difficulty level; Configurable raid limits (currently available) along with discount multipliers for purchases, for each permission. File location: *SERVER*\oxide\data\RealPVE\PermissionConfig.json Default: https://pastebin.com/5VtWZZVr All permissions are created and configured in the config file under the "List of permissions" section. You can create as many permissions as needed and customize them flexibly. It is recommended to use the prefix "realpve" in the permission's name, for example: "realpve.vip". NOTE: The first permission will serve as the default permission for those who do not have any permissions. { "List of permissions. NOTE: The first permission will be used by default for those who do not have any permissions.": [ { "Permission Name": "realpve.default", "Bypass Queue": false, "Limit of beds": 15, "Limit of shelters": 1, "Limit of auto turrets": 12, "Seconds that will be skipped when opening HackableLockedCrate. Range from 0 to 900": 0.0, "Monuments price multiplier": 1.0, "Events price multiplier": 1.0, "Limit of RaidableBases(at the time)": 1, "RaidableBases price multiplier": 1.0, "Vehicles settings": { "Horse": { "Limit": 1, "Price": 10.0 }, "Bike": { "Limit": 1, "Price": 5.0 }, "MotorBike": { "Limit": 1, "Price": 20.0 }, "Car": { "Limit": 1, "Price": 25.0 }, ... } }, { "Permission Name": "realpve.vip", "Bypass Queue": true, "Limit of beds": 20, "Limit of shelters": 2, "Limit of auto turrets": 15, "Seconds that will be skipped when opening HackableLockedCrate. Range from 0 to 900": 450.0, "Monuments price multiplier": 0.9, "Events price multiplier": 0.9, "Limit of RaidableBases(at the time)": 2, "RaidableBases price multiplier": 0.9, "Vehicles settings": { "Horse": { "Limit": 5, "Price": 9.0 }, "Bike": { "Limit": 5, "Price": 4.5 }, "MotorBike": { "Limit": 5, "Price": 18.0 }, "Car": { "Limit": 5, "Price": 22.5 }, ... } } ], "Version": { "Major": 0, "Minor": 1, "Patch": 1 } } An example of a monument/event/rb multipliers using default permissions. For example, if you set the price for the Harbor at $1000, a player with the default permission(1.0) will pay $1000 * 1 = $1000. Meanwhile, a player with a VIP permission(0.9) will pay $1000 * 0.9 = $900. However, if a player possesses a misbehaving permission with a value of 1.1, they will need to pay $1000 * 1.1 = $1100. { "Chat admin command": "adminpve", "Chat command": "realpve", "Is it worth forcibly implementing PvE for a server?": true, "Is it worth enabling GameTips for messages?": true, "Is it worth preventing the sending of 'Give' messages?": true, "Is it worth preventing resource gathering in someone else's building privilege area?": false, "Is it worth preventing the pickup of plants spawned by the server in someone else's building privilege zone?": false, "Is it worth preventing players from handcuffing others?": true, "Is it worth preventing a backpack from dropping upon player death?": true, "Is it worth preventing damage to the laptop of the Hackable Crate?": true, "Is it worth removing the penalties for recyclers in safe zones?": true, "Which currency symbol and format will be utilized?": "${0}", "Vehicles - Time(in seconds) to display the marker when searching for a vehicle. A value of 0 disables the marker": 15.0, "Anti-Sleeper - Time in seconds after which a player will be killed if they disconnect while inside someone else's Building Privilege. Set to 0 to disable": 1200.0, "PatrolHelicopterAI - Monument Crash. If set to true, the helicopter will attempt to crash into the monument": false, "PatrolHelicopterAI - Use Danger Zones. If set to false, the helicopter will function as it did before the April update": false, "PatrolHelicopterAI - Flee Damage Percentage. A value of 1 or above will make the helicopter behave as it did before the April update": 1.0, "Is Npc Random Raids enabled?": true, "PvP - Is friendly fire enabled by default when creating a team?": false, "PvP - Is it worth adding map markers for PvP zones?": true, "PvP - Name of the map maker": "PvP Zone!", "PvP - Settings for the status bar": { "Order": 9, "Height": 26, "Main_Color(Hex or RGBA)": "1 1 1 1", "Main_Transparency": 0.15, "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 1 1 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", "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": 12 } } ENG: https://pastebin.com/ZMUL6pYL RUS: https://pastebin.com/Mx8cbMts Main commands(/realpve ) : vehicle: find - helps to find a player's vehicle; unlink - unlinks the vehicle without the need to approach it; clear - unlinks all vehicles. team: ff - Enable/Disable damage to teammates. Only the group leader can use this command. Admin commands(/adminpve). Permission "realpve.admin" required: loot - Toggle unrestricted looting. If a userID is added at the end, the command will apply to that player, otherwise, it will apply to the person who entered it. monument: pvp - Toggle the PvP flag for a monument. If a monumentID is added at the end, the command will apply to that monument, otherwise, it will apply to the monument the player is currently in. Example: /realpve team ff /realpve vehicle find *netID* /adminpve loot /adminpve loot *userID* /adminpve monument pvp /adminpve monument pvp *monumentID* This plugin provides the ability to claim vehicles, thereby preventing theft and griefing from other players. In permissions, you can set the price and quantity restrictions for each type of vehicle, ensuring flexible customization according to your preferences. An assigned vehicle can't be damaged, looted or pushed by other players, but it can be pushed if it is within someone else's Building Privilege. File location: *SERVER*\oxide\data\RealPVE\MonumentConfig.json Default: https://pastebin.com/XY1d9YaM This plugin introduces queue system and loot purchases for monuments. You can customize the price and time for looting for each monument. Within monuments, only the "Looter" and his friends have the ability to loot, pick up items or damage entities. Additionally, NPCs and animals within monuments do not aggress against other players and do not receive damage from them. If a player dies within the monument, they will have a grace period to return. This allows players to safely loot monuments without fear of griefing. Example of monument configuration: "ferry_terminal_1": { "Type(This parameter is just a hint. Changes won’t have any effect)": "RadTown", "Time in seconds(1-15) given to respond for purchasing monument looting": 5.0, "ShowSuffix": true, "Broadcast": true, "PvP - Is PvP enabled at this monument? If so, players will be able to kill each other, and loot will be publicly accessible": false, "PvP - Sets the delay in seconds that a player remains in PvP mode after leaving a PvP monument. 0 disables the delay": 10, "PvP - Is it worth adding map markers for monuments if they are PvP zones?": true, "LootingTime": 900, "Price": 15.0, "Is it worth using a progress bar for bars with a counter?": true, "BarSettings": { "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", "Progress_Reverse": true, "Progress_Color": "#FFBF99", "Progress_Transparency": 0.8, "Progress_OffsetMin": "", "Progress_OffsetMax": "" } } Type - This field serves only as an indicator for you. The changes won't have any impact; ShowSuffix - Suffix display. Some monuments (for example Warehouses) have suffixes in the name, like "Warehouse #12"; Broadcast - Enabling or disabling broadcasts when a monument is occupied or vacated; LootingTime - Time allocated for looting the monument; Price - The price for which you can start looting the monument. 0 means looting is free; BarSettings - Settings for the Advanced Status Bar. You can also choose the types of monuments by specifying them under the "List of tracked types of monuments" section. A list of all available types can be viewed on the MonumentsWatcher's page in the "Developer API" section. "List of tracked types of monuments": [ "RadTown", "RadTownWater", "RadTownSmall", "TunnelStation", "Custom" ] Events, similar to monuments, offer the opportunity to claim events. All events are configured in the config file under the "Settings for the events" section. You can customize the price of looting and looting attempts(deaths, including friends). Just like in monuments, only the "Looter" and his friends have the ability to loot and damage entities. Additionally, in events, NPCs do not aggress against other players. If a player(including friends) exceeds the death limit, the event became free, thereby providing other players with the opportunity to claim the event. Example of event configuration: { "Settings for the PatrolHelicopter events": { "IsEnabled": true, "Time in seconds (1-15) given to respond for purchasing this event. Note: This is shown to everyone who deals damage, and the first person to buy it will claim it": 5.0, "Is it worth removing fire from crates?": true, "The price to capture the event. 0 means the event is free": 50.0, "The number of deaths after which the event becomes public": 5 }, "Settings for the BradleyAPC events": { "IsEnabled": true, "Time in seconds (1-15) given to respond for purchasing this event. Note: This is shown to everyone who deals damage, and the first person to buy it will claim it": 5.0, "Is it worth removing fire from crates?": true, "The price to capture the event. 0 means the event is free": 50.0, "The number of deaths after which the event becomes public": 5 }, "Version": { "Major": 0, "Minor": 1, "Patch": 0 } } Price - The price to claim the event. 0 means looting is free; DeathLimit - Limit of deaths after which the event becomes free. File location: *SERVER*\oxide\data\RealPVE\NewbieConfig.json Default: https://pastebin.com/QHZCqpji An example of an item list given for the main inventory: "List of items for the main inventory": [ { "ShortName": "note", "Slot": 0, "Amount": 1, "SkinID": 0, "Text": "MsgNoteText" } ] P.S. In the Text field, you need to specify the language key. Or, you can just write any text, but there won't be a translation of the text. File location: *SERVER*\oxide\data\RealPVE\RaidableBasesConfig.json Default: https://pastebin.com/rpDng7Fd Integration with the RaidableBases plugin does not restrict its functionality in any way. On the contrary, it adds an anti-grief system that protects bases from malicious players. In raid bases, NPCs and other entities can only receive damage from the raid owner or their friends; Turrets and traps do not aggress against outsiders; You can customize the price of claiming to each difficulty and set individual discounts for each permission. You can still purchase raid bases using the /buyraid command. Raid bases without owners(buyable, maintained, manual and scheduled) can be bought for a price set in the configuration file or assigned to the first player who enters its radius, if the final price(price * discount) less or equals to 0. Additionally, as a bonus, upon buying this plugin, you receive 5 free bases for 3 difficulty levels, along with configured loot for them.

Prevent Add Friends Bag, Bed, Cupboard Permissions: preventaddfriends.bypass Image Made by @Azmo thanks

Ultimate Beds, allows you to change the number of sleeping bags and beds you can place compared to the basic limit imposed by rust. You can also decide the time within which a sleeping bag/bed becomes available for spawning and adjust the time for successful spawns, all through various permissions, including VIP permissions. It also allows you to define the distance between the various beds, preventing them from going into cooldown between them. Oxide/Carbon compatibility Permissions ultimatebeds.default — Assign the limits configured in the group: default. ultimatebeds.vip1 — Assign the limits configured in the group: vip1. ultimatebeds.vip2 — Assign the limits configured in the group: vip2. ultimatebeds.vip3 — Assign the limits configured in the group: vip3. Default Configuration The configurationcan be found in the file: /oxide/config/UltimateBeds.json { "RolePermission": { "default": { "Player Max Sleeping Bag/Bed limit": 15, "Sleeping bag unlock time after placed": 300, "Bed unlock time after placed": 120, "Sleeping bag respawn cooldown": 300, "Bed respawn cooldown": 120, "Sleeping Bag Range: Radius within which to check other Sleeping Bags placed. Default: 50 (lower = more Sleeping Bags close to each other)": 50, "Bed Range: Radius within which to check other Beds placed. Default: 50 (lower = more Beds close to each other)": 50 }, "vip1": { "Player Max Sleeping Bag/Bed limit": 20, "Sleeping bag unlock time after placed": 200, "Bed unlock time after placed": 100, "Sleeping bag respawn cooldown": 180, "Bed respawn cooldown": 80, "Sleeping Bag Range: Radius within which to check other Sleeping Bags placed. Default: 50 (lower = more Sleeping Bags close to each other)": 50, "Bed Range: Radius within which to check other Beds placed. Default: 50 (lower = more Beds close to each other)": 50 }, "vip2": { "Player Max Sleeping Bag/Bed limit": 40, "Sleeping bag unlock time after placed": 100, "Bed unlock time after placed": 50, "Sleeping bag respawn cooldown": 80, "Bed respawn cooldown": 40, "Sleeping Bag Range: Radius within which to check other Sleeping Bags placed. Default: 50 (lower = more Sleeping Bags close to each other)": 50, "Bed Range: Radius within which to check other Beds placed. Default: 50 (lower = more Beds close to each other)": 50 }, "vip3": { "Player Max Sleeping Bag/Bed limit": 60, "Sleeping bag unlock time after placed": 60, "Bed unlock time after placed": 30, "Sleeping bag respawn cooldown": 40, "Bed respawn cooldown": 20, "Sleeping Bag Range: Radius within which to check other Sleeping Bags placed. Default: 50 (lower = more Sleeping Bags close to each other)": 50, "Bed Range: Radius within which to check other Beds placed. Default: 50 (lower = more Beds close to each other)": 50 } } } Basically 4 groups are created, and you can change the settings for each of these groups default vip1 vip2 vip3 FIELDS PlayerMaxSleepingBagBed — Defines the maximum number of sleeping bags/beds a player can place. SleepingBagUnlockTime — Defines after how many seconds the sleeping bag is ready for use when placed for the first time. BedUnlockTime — Defines after how many seconds the bed is ready for use when positioned for the first time. SleepingBagRespawnCooldown — Defines after how many seconds the sleeping bag can be used to spawn after the sleeping bag has already been used. BedRespawnCooldown — Defines after how many seconds the bed can be used for spawning after the bed has already been used. Sleeping Bag Range: Radius within which to check other Sleeping Bags placed. Default: 50 (lower = more Sleeping Bags close to each other) : 50, Bed Range: Radius within which to check other Beds placed. Default: 50 (lower = more Beds close to each other) : 50

Deploy floating sleeping bags with customizable settings like distance from land, movement, and wave effects, giving you total control over placement. Breaks on collision with boats or cargo ships, and can be picked up with a hammer. Reskin restrictions and cooldown settings keep things balanced, while multilingual support ensures accessibility. Be careful—if the sleeping bag rolls over, you won’t be able to respawn on it! Key Features There is a lang ru/en/uk/es. Ability to disallow sleeping bag reskinning. Ability to customize the maximum distance from land. Ability to disable drifting towards the island. Ability to disable movement. [ Sleeping bag will always stay in the same place. ] Ability to disable the effect of waves. Ability to set CoolDown to default. [ CoolDown settings by permissions. ]. The sleeping bag breaks down in a collision boat/cargo ship. A water sleeping bag is subject to the limit of regular sleeping bags. The water sleeping bag can be picked up with a hammer. A water sleeping bag can be broken in any number of ways. If the sleeping bag rolls over, you cannot respawn on it. Permissions xwatersleepingbag.use - allow a sleeping bag to be placed. xwatersleepingbag.admin - allow a player(administrator) to use the command to give sleeping bags. Commands give_wsb steamID amount - to give a water sleeping bag to a player. API bool IsCustomWI(WaterInflatable mountable) - check if the board is part of the water sleeping bag. bool IsWSB(SleepingBag bag) - check if the sleeping bag is a - water sleeping bag. Config { "General settings": { "Item: Water sleeping bag - SkinID": ?, "Item: Custom name": "Water sleeping bag", "Default sleeping bag - SkinID": ?, "Allow sleeping bag reskin": false, "Distance to the edge of the map. The sleeping bag cannot be placed far from the land. [ The default value is 0, which is the edge of the map. Set any value to increase or decrease the distance to land. (100.0 or -100.0) ]": 0.0, "Enable drift towards island": false, "Enable movement": false, "Enable wave effect": true, "Default CD": 300.0, "List of permits and CD for water sleeping bag": { "xwatersleepingbag.cd90": 90.0, "xwatersleepingbag.cd150": 150.0, "xwatersleepingbag.cd210": 210.0 } } }

The plugin displays the time until the bed cooldown ends in the status bar. Depends on AdvancedStatus plugin. The ability to set a limit on the number of displayed bars; The ability to skip sleeping bags with the same unlockTime; The ability to set the bar's deletion time for each type, earlier than the cooldown time expires; The ability to choose between bar types(TimeCounter and TimeProgressCounter); The ability to specify the order of the bar; The ability to change the height of the bar; The abillity to customize the color and transparency of the background; The ability to set a material for the background; The ability to switch between CuiRawImageComponent and CuiImageComponent for the image; The ability to get images from the local folder(*SERVER*\oxide\data\AdvancedStatus\Images); The abillity to set own image and customize the color and transparency of the image; The abillity to set sprite instead of the image; The ability to customize the color, size and font of the text; The ability to customize the bar for each type of bed. { "Is it worth using a progress bar in the status bar?": true, "Is it worth skipping sleeping bags with the same UnlockTime?": true, "Limit on the simultaneously displayed bars. 0 disables the limit.": 5, "Limit name length. 0 disables the limit.": 20, "List of status bar settings for each type": { "BedStatus_SleepingBag": { "Order": 21, "Height": 26, "Main_Color": "#FFFFFF", "Main_Transparency": 0.15, "Main_Material": "", "Image_Url": "https://i.imgur.com/9kTXWBz.png", "Image_Local(Leave empty to use Image_Url)": "BedStatus_SleepingBag", "Image_Sprite(Leave empty to use Image_Local or Image_Url)": "", "Image_IsRawImage": true, "Image_Color": "#FFB200", "Progress_Color": "#F79E61", "Image_Transparency": 1.0, "Text_Size": 12, "Text_Color": "#F79E61", "Text_Font": "RobotoCondensed-Bold.ttf", "Text_Offset_Horizontal": 0, "SubText_Size": 12, "SubText_Color": "#F79E61", "SubText_Font": "RobotoCondensed-Bold.ttf", "DestroyTime - Time in seconds after which the bar will be destroyed. Leave 0 to destroy the bar when the time expires.": 0, "Progress_Transparency": 0.7, "Progress_OffsetMin": "0 0", "Progress_OffsetMax": "0 0" }, "BedStatus_Bed": { "Order": 22, "Height": 26, "Main_Color": "#FFFFFF", "Main_Transparency": 0.15, "Main_Material": "", "Image_Url": "https://i.imgur.com/LXyo8X4.png", "Image_Local(Leave empty to use Image_Url)": "BedStatus_Bed", "Image_Sprite(Leave empty to use Image_Local or Image_Url)": "", "Image_IsRawImage": true, "Image_Color": "#FFB200", "Progress_Color": "#F79E61", "Image_Transparency": 1.0, "Text_Size": 12, "Text_Color": "#F79E61", "Text_Font": "RobotoCondensed-Bold.ttf", "Text_Offset_Horizontal": 2, "SubText_Size": 12, "SubText_Color": "#F79E61", "SubText_Font": "RobotoCondensed-Bold.ttf", "DestroyTime - Time in seconds after which the bar will be destroyed. Leave 0 to destroy the bar when the time expires.": 0, "Progress_Transparency": 0.7, "Progress_OffsetMin": "25 0", "Progress_OffsetMax": "0 0" }, "BedStatus_BeachTowel": { "Order": 23, "Height": 26, "Main_Color": "#FFFFFF", "Main_Transparency": 0.15, "Main_Material": "", "Image_Url": "https://i.imgur.com/hYp0VXa.png", "Image_Local(Leave empty to use Image_Url)": "BedStatus_BeachTowel", "Image_Sprite(Leave empty to use Image_Local or Image_Url)": "", "Image_IsRawImage": true, "Image_Color": "#FFB200", "Progress_Color": "#F79E61", "Image_Transparency": 1.0, "Text_Size": 12, "Text_Color": "#E2DBD6", "Text_Font": "RobotoCondensed-Bold.ttf", "Text_Offset_Horizontal": 2, "SubText_Size": 12, "SubText_Color": "#E2DBD6", "SubText_Font": "RobotoCondensed-Bold.ttf", "DestroyTime - Time in seconds after which the bar will be destroyed. Leave 0 to destroy the bar when the time expires.": 0, "Progress_Transparency": 0.7, "Progress_OffsetMin": "25 2.5", "Progress_OffsetMax": "-3.5 -3.5" }, "BedStatus_Camper": { "Order": 24, "Height": 26, "Main_Color": "#FFFFFF", "Main_Transparency": 0.15, "Main_Material": "", "Image_Url": "https://i.imgur.com/PCGeaee.png", "Image_Local(Leave empty to use Image_Url)": "BedStatus_Camper", "Image_Sprite(Leave empty to use Image_Local or Image_Url)": "", "Image_IsRawImage": true, "Image_Color": "#FFB200", "Progress_Color": "#F79E61", "Image_Transparency": 1.0, "Text_Size": 12, "Text_Color": "#E2DBD6", "Text_Font": "RobotoCondensed-Bold.ttf", "Text_Offset_Horizontal": 0, "SubText_Size": 12, "SubText_Color": "#E2DBD6", "SubText_Font": "RobotoCondensed-Bold.ttf", "DestroyTime - Time in seconds after which the bar will be destroyed. Leave 0 to destroy the bar when the time expires.": 0, "Progress_Transparency": 0.7, "Progress_OffsetMin": "0 0", "Progress_OffsetMax": "0 0" } }, "Version": { "Major": 0, "Minor": 1, "Patch": 0 } }

A lightweight plugin that disables various teaming methods to restrict players to solo gameplay. Now featuring an automated warning system with kick/ban abilities! Permissions soloenforcement.enforce Configuration { "Discord webhook URL": "https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks", "Discord message color": 9109504, "Log turret violations to Discord": false, "Log respawn violations to Discord": true, "Log revive violations to Discord": false, "Log cupboard auth violations to Discord": false, "Log team violations to Discord": false, "Log crafting violations to Discord": true, "Log automatic kicks/bans from warning system to Discord": false, "Show violation messages in chat (does not need automatic warning turned on)": true, "Use automatic warning system": false, "Maximum warnings": 3, "Show warning count (popup)": false, "Warning popup time (seconds)": 5, "Ban after maximum warnings reached (will kick otherwise)": false, "Warn for turret violations": false, "Warn for respawn violations": false, "Warn for revive violations": false, "Warn for cupboard violations (recommended NOT to use)": false, "Warn for team violations": false, "Warn for crafting violations": false, "Restrict tool cupboards": true, "Require destruction of tool cupboards": true, "Ignore tool cupboard restrictions on decaying bases": true, "Restrict turrets": true, "Restrict sleeping bags & beds": true, "Restrict team creation": true, "Restrict codelock & keylock crafting": true } Localization { "DiscordTitle": "Solo Enforcement", "ChatCupboard": "Another player is already authorized on this tool cupboard.", "DiscordCupboard": "{player1} ({player1_id}) attempted to authorize themselves on an already authorized tool cupboard.", "ChatTurretAuth": "Another player is already authorized on this turret.", "DiscordTurret": "{player1} ({player1_id}) attempted to assign {player2} ({player2_id}) to their turret.", "ChatTurretAssign": "You are not allowed to assign players to your turret.", "DiscordRespawnAssign": "{player1} ({player1_id}) attempted to assign their sleeping bag/bed to {player2} ({player2_id}).", "ChatRespawnAssign": "You are not allowed to assign players to your sleeping bags/beds.", "DiscordPublicBed": "{player1} ({player1_id}) attempted to set their bed to public.", "ChatPublicBed": "You are not allowed to set your bed to public.", "DiscordTeam": "{player1} ({player1_id}) attempted to create a team.", "ChatTeam": "Teams have been disabled.", "DiscordCraft": "{player1} ({player1_id}) attempted to craft a codelock/key.", "ChatCraft": "You are not allowed to craft that item.", "DiscordRevive": "{player1} ({player1_id}) revived {player2} ({player2_id}).", "BanMessage": "Too many teaming violations detected (auto ban).", "KickMessage": "Too many teaming violations detected (auto kick).", "WarningPopup": "Warning {0}/{1}" }

Allows complete individual settings of Beds | Towels | Bags & Campers using Permissions or Global setters with radius & limits! Improves server/client performance by auto-managing players bag limits & radius! You can assign a bed to a friend on your friends list in game & when they join it will give them the invite to join your team to get the bed/bag/towel/etc! Notes: Better Vanish ( the paid version ) has known bugs with chat commands not working while in vanish. To resolve the problem leave vanish mode. Player Chat Commands /bag <Shows just the limits & how many of what you have placed.> /bag bags | towels | beds | campers <Selects & shows how many of the specific bag you have placed down.> /bag towels clear | rename | limits /bag towels clear <Clears all of the selected bag type from the player that ran the command> /bag towels rename dingus <Renames all of the selected bag type to the new name> Configuration { "# of players that can place a spawn point in a zone radius": 16, "Player Respawn Zone Radius Check": 35, "Sets Global Defaults": { "True Only Owner can set name | False Allows team members": false, "Sets Total Max Limit within a radius": 12, "Sets Limit radius": 35, "Sleeping Bags": { "DefaultTextName": "Unnamed Bag", "SecondsBetweenReuses": 300.0, "UnlockTime": 30.0 }, "Towel Bags": { "DefaultTextName": "Unnamed Towel", "SecondsBetweenReuses": 300.0, "UnlockTime": 30.0 }, "Beds": { "DefaultTextName": "Bed", "SecondsBetweenReuses": 120.0, "UnlockTime": 30.0 }, "Camper Bags": { "DefaultTextName": "Unnamed Camper Seat", "SecondsBetweenReuses": 120.0, "UnlockTime": 30.0 } }, "Player Permissions": { "vip1": { "True Only Owner can set name | False Allows team members": false, "Sets Total Max Limit within a radius": 12, "Sets Limit radius": 35, "Sleeping Bags": { "DefaultTextName": "Unnamed Bag", "SecondsBetweenReuses": 150.0, "UnlockTime": 20.0 }, "Towel Bags": { "DefaultTextName": "Unnamed Towel", "SecondsBetweenReuses": 150.0, "UnlockTime": 20.0 }, "Beds": { "DefaultTextName": "Bed", "SecondsBetweenReuses": 60.0, "UnlockTime": 20.0 }, "Camper Bags": { "DefaultTextName": "Unnamed Camper Seat", "SecondsBetweenReuses": 150.0, "UnlockTime": 20.0 } }, "vip2": { "True Only Owner can set name | False Allows team members": false, "Sets Total Max Limit within a radius": 12, "Sets Limit radius": 35, "Sleeping Bags": { "DefaultTextName": "Unnamed Bag", "SecondsBetweenReuses": 75.0, "UnlockTime": 15.0 }, "Towel Bags": { "DefaultTextName": "Unnamed Towel", "SecondsBetweenReuses": 75.0, "UnlockTime": 15.0 }, "Beds": { "DefaultTextName": "Bed", "SecondsBetweenReuses": 30.0, "UnlockTime": 15.0 }, "Camper Bags": { "DefaultTextName": "Unnamed Camper Seat", "SecondsBetweenReuses": 75.0, "UnlockTime": 15.0 } } } }

What is it? This is a simple plugin, that lets you monitor all bed and bag renames. Usage People are changing bag names to racist or inappropriate names? With this plugin you can take care of these people by checking who did it! Just install & punish! Discord WebHook Just create a webhook for your channel, paste it into the config, reload the plugin and it's done! Localization {0} - X Y Z Position {1} - Player name {2} - Player ID {3} - Old Bed/Bag name {4} - New Bed/Bag name { "SleepingBagRename": "{0} {1}({2}) renamed sleeping bag from {3} to {4}", "BedRename": "{0} {1} ({2}) renamed bed from {3} to {4}" } Config { "Discord webhook url": "Your discord webhook URL", "log to discord?": true } Where's the log folder? Since the 1st log it should automatically create a folder and you can find logs here: oxide/logs/BedNameLogs/bednamelogs_renames-xxxx-xx-xx.txt

No more sleeping bag cooldowns ! Great for those crazy, heavy modded servers. You can control to which users the cooldown will be removed by granting the permission OxidationNoBagCooldown.Allow. If you'd like to remove the cooldown to all your players just grant the permission to the default group on the console like so: oxide.grant group default OxidationNoBagCooldown.Allow