Search the Community

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

AgileZones will create and remove ZoneManager zones around Player Bases as well as moving points of interest like CargoShip, Supply Drops, Bradley, Tugboats, and Heli-Crash sites. Great care has been taken to ensure the plugin does not impact server performance and that Zones are consistent even after server-crashes. It's your choice to use TruePVE (default) or NextGenPVE to tailor what happens inside and outside of the zones. Add the ZoneManagerAutoZones plugin to generate ZoneManager zones around monuments and you've got a server-enforced hybrid PVP/PVE world. Add the ZoneDomes plugin for optional visible domes. Demo You should be able to find a demo server by searching modded servers for "AgileZones". Be sure to "Show Empty" servers. Default Configuration { "Enable TruePVE": true, "Enable NextGenPVE": false, "Enable ZoneDomes": true, "Enable ZoneDomes For TCs": false, "Enable ZoneDomes For SupplyDrops": true, "Enable ZoneDomes For Cargo": true, "Enable ZoneDomes For HeliCrash": true, "Enable ZoneDomes For BradleyAPC": true, "Enable ZoneDomes For Tugboats": false, "Visible Domes for Moving Zones Darkness (Default 1)": 1, "Delay creating a zone after placing a TC in seconds": 600.0, "Delay removing a zone after a TC is destroyed": 900.0, "TC Zone Radius in meters - set zero to disable": 50, "TC RuleSet": "exclude", "TC Zone Flags": null, "CargoShip Zone Radius in meters - set zero to disable": 125, "Cargo RuleSet": "exclude", "Cargo Zone Flags": null, "SupplyDrop Zone Radius in meters - set zero to disable": 50, "SupplyDrop RuleSet": "exclude", "Supply Drop Zone Flags": null, "Apc Zone Radius in meters - set zero to disable": 50, "Apc RuleSet": "exclude", "Apc Zone Flags": null, "HeliCrash Zone Radius in meters - set zero to disable": 50, "Heli RuleSet": "exclude", "Heli Zone Flags": null, "Tugboats Zone Radius in meters - set zero to disable": 50, "Tugboats RuleSet": "exclude", "Tugboats Zone Flags": null, "Entering Zone Message": "WARNING: You are now entering a PVP Zone", "Leaving Zone Message": "Leaving a PVP Zone" } I recommend changing ZoneDomes Darkness to 1 (down from 5 by default) as well. Installation: Just Drop the .cs file into the oxide/plugins directory/folder. AgileZones can be installed on existing servers as easily as a fresh wipe, at any time. Existing Bases, SupplyDrops, CargoShips, Bradley, even Heli Crashsites will be handled and have zones created, no restart required. A config file will be generated in oxide/config where you can modify the default configuration. There is a caveat regarding config: Zones for bases (that have already been built) will not be reinitialized to account for your config changes. New TCs placed after the change will reflect your change. This means that if you drop the plugin onto a server for the first time, it will be loaded, create the default configuration .json file, and build zones for all of the existing bases using those default settings. If you wanted a different zone radius, or to enable the ZoneDome visualization (which is disabled by default so that player bases are less visible), you would need to have the configuration file in-place first. For now, if you plan to install AgileZones onto an existing wipe and you don't want to use the default configuration, Copy the above config, and make an 'AgileZones.json' file in oxide/config, make sure it's there before you install the plugin itself. Alternatively you can delete the zone_data.json, zonedomes_data.json, and restart the server, or reload the zone-related plugins, and everything will be rebuilt using your new parameters. Future: This started as a 2 hour proof of concept for player-added PVP zones around TCs and ended up featuring-creeping it's way into weeks of work. There are still some things I'd like to add, but I wanted to get it out there, I hope this is a huge improvement for hybrid PVP servers. TODO: For now, you must modify the oxide/config/AgileZones.json file and reload the plugin. RCON Command: oxide.reload AgileZones ZoneManager doesn't handle overlapping zones very well; you'll receive a notification for each zone you leave which might be confusing when you are still inside a PVP zone. I'd like to improve on this and some other issues with ZoneManager. I didn't realize the ZoneManager license allowed for branching; I wouldn't have jumped through some of the hoops had I known.

TCLevels is a plugin that will make your server more fun and have more things to do! FEATURES ★ • Reduce the decay damage by tick; • Upgrade the authorizations limit; • Upgrade the building grade limit; • Upgrade the storage capacity of the cupboard; • Upgrade the stack size limit of the cupboard; • Unlock some deployable items; • Set a default building grade for the server; • Modify the default decay; • Keep the cupboard attributes when remove; Make your server fun ^u^ PERMISSIONS The plugin has a unique permission, which allows the player to use the cupboard upgrade: tclevels.use F.A.Q 1. How many items can be blocked? and which? You can block unlimited items and all items must be deployable or they will not be blocked. 2. Which area will be checked when i place my cupboard? The entire privilege area will be checked. But you can also disable checks in the configuration file. 3. Could it cause conflict with any plugin? Yes, but i am providing an API for the plugin so that other developers can integrate with it, so if there is a conflict, just go to the developer's plugin support and ask them to integrate it. Also if it is possible for me to integrate it from my plugin, i will do so without any problem. API </> // Gets the current cupboard allowed building grade limit // If the cupboard isn't provided, it will return the default building grade limit of the config; private BuildingGrade.Enum GetBuildingGradeLimit(BuildingPrivlidge? cupboard); // Gets the current cupboard decay multiplier // If the cupboard isn't provided, it will return the default decay multiplier of the config; private float GetDecayMultiplier(BuildingPrivlidge? cupboard); // Gets the current cupboard authorization limit // If the cupboard isn't provided, it will return the default auth limit of the config; private int GetAuthLimit(BuildingPrivlidge? cupboard); // Gets the current cupboard storage capacity // If the cupboard isn't provided it will throw an exception; private int GetCapacity(BuildingPrivlidge cupboard); // Gets a list of the cupboard blocked items // If the cupboard isn't provided it will return all locked items listed in the config; private List<string> GetLockedItems(BuildingPrivlidge? cupboard); CONFIGURATION TCLevels.json

Open UI - /tssettings (use permission - tcauth.use) FEATURES: The maximum number of players that can authorize in a cupboard Only authorized players can open crates (on/off) Only authorized players can look inside and open Furnaces (on/off) Authorized players are automatically not attacked by turrets and SAM site (on/off) Authorized players no longer need codes and keys to open doors (on/off) Automatically if players are registered on the TC (remove building parts) (on/off) Automatically registered your teammates on the TC PERMISSIONS: "tcauth.use" - you can use UI (only for config setup) "tcauth.bypass" - you can use all the functionality "tcauth.ignore" - you ignore all the functionality "tcauth.auth.use" - you are automatically authorizing in your teammates TC (AutoTurrets + SAM optional) "tcauth.lock.use" - you can open what's under lock and key "tcauth.chest.use" - you can open chests "tcauth.turret.use" - you are automatically authorized in the turrets and SAM "tcauth.furnace.use" - you can open the ovens "tcauth.removebp.use" - you can destroy parts of the building at any time P.s - (My Discord - tofurahie#4144)

TC Item Block prevents players from storing certain items inside the Tool Cupboard.

Are you tired of filling up multiple "public" containers only to see that person X has walked by and completely looted them? "STORAGE LOCK" is our solution. With a simple chat command you can now lock certain public containers. The command will automatically fill the containers with 1 or more predefined items. Already implemented containers: - Hitchtrough - Cursed Cauldron - Lantern - Tuna light - Skull fire pit - Hobo barrel - Bonfire - Chinese lantern - Fireplace - Fireplace - Tool cabinet Locked fireboxes do not turn off anymore, as far as the charcoal slot is full. (Attention: these containers do not produce charcoal at all). Just be sure to set the predefined amount of resources high enough so you don't get any nasty surprises. -------------------------------- Sind Sie es leid, immer wieder mehrere "öffentliche" Container aufzufüllen, nur um zu sehen, dass Person X vorbeigegangen ist und sie komplett geplündert hat? "STORAGE LOCK" ist unsere Lösung. Mit einem einfachen Chatbefehl könnt ihr nun bestimmte öffentliche Container sperren. Durch den Befehl werden die Container automatisch mit 1 oder mehreren vordefinierten Gegenständen gefüllt. Bereits implementierte Containers: - Hitchtrough - Verfluchter Kessel - Laterne - Tunalicht - Totenkopf-Feuergrube - Hobo-Fass - Lagerfeuer - Chinesische Laterne - Feuerstelle - Feuerstelle - Werkzeugschrank Verschlossene Brennbehälter schalten sich nicht meh aus, insofern der Holzkohleslot voll ist. (Achtung: Diese Container produzieren gar keine Holzkohle) Achten Sie nur darauf, die vordefinierte Menge an Ressourcen hoch genug einzustellen, damit Sie keine bösen Überraschungen erleben. { "Main config": { "Debug": false, "Use Permissions": true, "Use Permission": "storagelock.use", "Auto Lock Permission": "storagelock.autolock", "Chaticon": 76561199180049293, "Chat Prefix": "[<color=#00ffff>StorageLock</color>] ", "Chat Command": "lock", "Items set invulnerable?": true }, "Container Settings": { "hitchtrough.deployed": { "Items": [ { "Input Item": "pumpkin", "Input Amount": 10000 } ], "Remove charcoal": false, "Autolock when player has permission": true }, "cursedcauldron.deployed": { "Items": [ { "Input Item": "wood", "Input Amount": 100000 } ], "Remove charcoal": true, "Autolock when player has permission": true }, "lantern.deployed": { "Items": [ { "Input Item": "lowgradefuel", "Input Amount": 100000 } ], "Remove charcoal": false, "Autolock when player has permission": true }, "tunalight.deployed": { "Items": [ { "Input Item": "lowgradefuel", "Input Amount": 100000 } ], "Remove charcoal": false, "Autolock when player has permission": true }, "skull_fire_pit": { "Items": [ { "Input Item": "wood", "Input Amount": 100000 } ], "Remove charcoal": true, "Autolock when player has permission": true }, "hobobarrel.deployed": { "Items": [ { "Input Item": "wood", "Input Amount": 100000 } ], "Remove charcoal": true, "Autolock when player has permission": true }, "campfire": { "Items": [ { "Input Item": "wood", "Input Amount": 100000 } ], "Remove charcoal": true, "Autolock when player has permission": true }, "campfire_static": { "Items": [ { "Input Item": "wood", "Input Amount": 100000 } ], "Remove charcoal": true, "Autolock when player has permission": true }, "chineselantern.deployed": { "Items": [ { "Input Item": "lowgradefuel", "Input Amount": 100000 } ], "Remove charcoal": false, "Autolock when player has permission": true }, "furnace": { "Items": [ { "Input Item": "wood", "Input Amount": 100000 } ], "Remove charcoal": true, "Autolock when player has permission": true }, "fireplace.deployed": { "Items": [ { "Input Item": "wood", "Input Amount": 100000 } ], "Remove charcoal": true, "Autolock when player has permission": true }, "cupboard.tool.deployed": { "Items": [ { "Input Item": "wood", "Input Amount": 1000000 }, { "Input Item": "stones", "Input Amount": 1000000 }, { "Input Item": "metal.fragments", "Input Amount": 1000000 }, { "Input Item": "metal.refined", "Input Amount": 1000000 } ], "Remove charcoal": false, "Autolock when player has permission": true } } }

Allows players with the required permission to automatically loot items from a distance from destroyable containers with the option for them to enable/disable it for themselves whenever they see fit. Permission: "autoloot.use" - Required to use the plugin Command: /aloot - Enables or disables the plugin for the individual player as they see fit. Configuration: Lets you set the maximum distance the plugin will be allowed to work. Set the command for players to use. Enable optional containers. Add/remove optional containers using the short prefab name. Default Config: { "Distance to allow Auto Loot to be used (meters): ": 15.0, "Auto Loot command for players: ": "aloot", "Enable Optional Containers": true, "Optional Containers": [ "box.wooden.large", "woodbox_deployed", "cupboard.tool.deployed", "coffinstorage", "vendingmachine.deployed", "dropbox.deployed", "fridge.deployed", "tunalight.deployed", "furnace.prefab", "furnace.large.prefab", "bbq.deployed", "mixingtable.deployed", "composter", "fireplace.deployed", "researchtable_deployed", "hitchtrough.deployed", "locker.deployed" ] }