Xenia87's Wishlist

Water Bases rust plugin enables players with permissions to construct and expand structures on and underwater without the need for pillars, incorporating vanilla-like mechanics, special features like underwater nettings, and customizable settings for different player tiers.
Questions? Support? Join the discord: https://discord.nikhub.dev

In short
This Rust plugin enables players with the right permissions to construct structures on the water's surface and even extend them below water in a way that feels natural and in keeping with the game's original style. There's no need for tall, unstable pillars reaching down to the seabed; simply place your foundation on the water and use a building plan or hammer to expand it.

These aquatic constructions adhere to the same principles of stability, upkeep, and decay as traditional bases on your server but also introduce unique elements like underwater nettings for gathering random items (with fully customizable loot tables) and innovative building techniques.
The plugin accommodates various configuration profiles based on permissions, offering an excellent method to reward VIP players across different levels. It grants you control over who is allowed to build on the water, the size of their constructions, their proximity to the shore, and the highest tier of building blocks they can use, among other aspects.

Additionally, the plugin is designed to alert players if their construction interferes with the Cargo Ship's route. With the Submarine update on the horizon, it's time to prepare your server for aquatic adventures with Water Bases!

Watch the video below to see what water bases are all about.

"What about Cargo Ship, will it destroy structures in the way?"
By default, players will get a warning if they try to to build a water foundation in the path of the cargo ship, but their water foundation will stay. You can change this setting from "Warn" to "Prevent", and the player won't be able to build it in first place. Changing it to "None" will skip this check. Every ocean path node creates a "bubble" with a configurable radius. See Admin chat commands section below to visualise those bubbles and guide your players to areas where they will be able to build without issues.

Quick start (for players and admins)
Upload the WaterBases.cs file to your oxide/plugins folder and you should be good to go, it's all plug-and-play. No need to restart your server! Before you can build on water, you need some Water Foundations. Water foundations are re-skinned Inner Tube items (Shortname: innertube / Item ID: -697981032 ; mind the minus sign, it matters!) with a skin ID 2484982352 (https://steamcommunity.com/sharedfiles/filedetails/?id=2484982352) or 2485021365 (https://steamcommunity.com/sharedfiles/filedetails/?id=2485021365). That info is just in case you'd like to include those in your own Kits/Server Rewards shops/loot tables/custom crafting plugins. How to obtain those within the plugin?

Crafting water base foundations (with Building Planner)
By default, all players will be able to craft, deploy, expand and reinforce water foundations. More on the limits and how to change them (how far/close to the shore, min and max depth of the water, how many water foundations allowed per building etc) in the section Advanced Config. When a player equips a Building Plan, a small GUI will show in the bottom right (positions/colours etc can be changed in the config too). There, players will be able to craft deployable water foundations - both square and triangle. Those crafted items will also be consumed when players expand their already deployed foundations or reinforce them. The default permission profile requires a player to be close to a Level 2 Workbench - this requirement can be edited in the config to change the level needed, or you can turn off the need for a workbench altogether, per permission profile. If you don't want your players to be able to craft foundations - so they have to find them/buy them/earn them instead - you can disable it per-profile. In that case, they won't see the GUI.

Giving with chat commands (admins only)
Type /give_square [amount] or /give_triangle [amount] to give yourself some foundations of that type. If you don't specify an amount, you will only receive 1.
Deploying a "starter" foundation on water
Go out to the lake/ocean, select the water foundation as your active item and using the doughnut-shaped guide, deploy it on the water surface. After trying to deploy/expand upon an existing water foundation, a couple of checks will be performed according to global config and individual permission profile for that player:
Does the player have permission to deploy the first foundation/expand existing one? Is the player building blocked? How far is the player trying to build from shore (based on the map topology)? Too close/too far? How deep is the water where the player is trying to build? Is it too deep/too shallow? Is the player trying to build too close to the path of cargo/Oil Rig? Is the player allowed to have this many water foundations in the building? If all the checks have been successful, a new twig floor, with a stability 100% (like normal foundations) will be built. It will have some indestructible floatation barrels attached to it, partially covering the water foundation's soft side (the bottom). Then, a water foundation can be expanded, upgraded, protected with a Tool Cupboard (like any other buildings, really), or reinforced.

Expanding
Once you've deployed your first "starter" water foundation, all the subsequent foundations will be placed using vanilla building mechanics - just take a building plan and build some floors neighbouring your water foundation on the sides! If you have enough water foundation items of the required kind in your inventory, those newly placed floors will also turn into water foundations. And they can call be demolished/upgraded, just like normal twig structures, as soon as you place a Tool Cupboard. Expanding a single-sided water foundation requires 1 proper water foundation item, expanding a double sided water foundation (reinforced one) requires two.

Reinforcing
Reinforcing a water foundation means making it double sided - so it fully covers the soft side AND gives you the ability to build from the surface down, to the seabed/lakebed! To reinforce, make sure a built water foundation is fully repaired, and them hit it with a hammer. If you have a required water foundation item in your inventory, it will be consumed and the foundation will be reinforced: you will see another floor with floatation barrels attached upside down. If you try to expand a reinforced foundation (by attaching a floor at the bottom, reinforced side) and there's no water foundation above it (normal orientation), it will try to create one, provided you have enough items in your inventory. Reinforcements (upside down water foundations) are always associated with the water foundation they're attached to and cannot exist on their own - if you destroy the water foundation, its reinforcement will be destroyed too. However, destroying the reinforcement will not destroy is water foundation.

Upgrading Water base structures
Building blocks inside your water bases have certain tier limits associated with them - it's to help balance things out. By default, non-VIP and non-admin players will be able to upgrade water foundations to sheet metal tier, floor frames and wall frames to stone tier, and everything else (including walls, floors and reinforcement foundations) to wood tier. You can easily decide which permission profile has which max tier (per type of building block) in the config.

Water Base exclusive features
Because water foundations are treated as floors with the stability of a foundation, you can place roofs at "ground level", which is not possible with normal foundations! Similarly, you can leave a "hole" where a water foundation would be and place a floor frame with a hatch instead - now you can enter your base from the bottom, underwater! Reinforcing a water foundation means you'll be able to build down from the surface to the bottom of the water to create extra layers of protection, or... Nettings deployed in wall frames underwater will collect random junk items with editable loot tables, including fish and diving equipment! This feature is heavily configurable and can even be disabled. But also Sharks! Read just below.
NEW IN 1.0.5: Beware the Netting Sharks!
If enabled, Sharks will randomly spawn around Nettings underwater. Especially ones that have accumulated a lot of items, but only if there's at least 1 player within the distance of 100 meters from the Netting. As soon as the first item is caught in an empty Netting, a random silent timer will be set. Every additional item spawning reduces the timer left by a certain percentage (default by 8%). When it hits 0, AND local/global Netting Shark population limits haven't yet been reached (all in the config), a Shark will spawn somewhere near that Netting. The sharks have a configurable aggro distance and multipliers for speed and health. They will linger around the position of the netting that attracted them and try to pursue anyone in sight. Harvesting a Netting Shark corpse with a proper tool will yield some free items from its entrails - by default 5 times more than you'd normally get from a netting full of items from the default loot tables. Of course the default Shark loot tables in the config are, just like the Netting loot tables, completely configurable - check the config section below.

All in all, it's like any other base... just on water, without annoying seafloor supports.
The stability of the water foundation is always 100% and goes down the higher you built. The stability of a reinforcement foundation also starts at 100% and goes down the deeper towards the seafloor you build. All the decaying things (walls, floors, doors etc) will require appropriate upkeep materials in the Tool Cupboard. Structures can be repaired, demolished, upgraded and removed using plugins. Bases can be raided, taken over or left to decay.

Water Bases Permissions (Oxide.Grant user YourName [permission name starting with waterbases.])
By default, the plugin generates 3 permission profiles in the config - one for admins, one for normal players with no specific permissions (default) and one for VIP. More on permission profiles and config values they can handle can be found in the section Advanced Config. Unless you have added more permission profiles, only these two below are going to be used by your config:
waterbases.admin
Holders of the admin permission will also be able to run the /wb_cfg, /give_square and /give_triangle commands. Also, by default, they will be associated with the permission profile that has no limits on placing water foundations.
waterbases.vip1
Holders of this permission will follow settings and limits associated with with that permission profile.   The permissions below are also registered, but not used by default. To use them, just create some permission profiles with those permissions as the key.
waterbases.vip2 waterbases.vip3 waterbases.vip4 waterbases.vip5
Admin chat commands (must have ownerid/moderatorid/waterbases.admin permission)
/give_square [optional arg: amount of items to receive] Will give the player a given amount of square-shaped water foundations. If no amount is provided, only 1 will be received. /give_triangle [optional arg: amount of items to receive] Will give the player a given amount of triangle-shaped water foundations. If no amount is provided, only 1 will be received. /draw_cargo This will draw a "bubble" (only for you, not every player) around every path node, and the bubble's radius will be taken from your config. If a player tries building inside one of these bubbles, they might get a warning or get prevent from doing so (because cargo ship destroys all structures in its way). Useful to visualise where your players can and cannot build, based on the cargo ship path. /shore_distance This will show you the current distance from the shore, to help you decide how close to/far from the shore to allow players to build. The unit used by Rust to measure shore distance is not in meters, it's something roughly equivalent to 1/10th of a map grid length. Mind you though, it's based off of the map's topology, so it should be fine on procgens, but if you have a custom map without topology layers reflecting the actual shoreline, you might want to disable relying on shore distance in your config. Admin console / chat command
This command will work both from the chat (in that case, prefix it with a forward slash / ) and the console, (F1 or server/RCON console). Running this command as a player will require the waterbases.admin permission for players that are not moderatorid/ownerid enabled.
wb.give [square/triangle] [partial player name or full steam ID] If a player executes it in the chat or console in-game and they don't specify a recipient, it will be given to the player executing this command. Executing from the server console requires specifying the player.
Configuration (oxide/config/WaterBases.json and /wb_cfg chat command)
Vast majority of the settings can be configured with the /wb_cfg chat command. Typing it in the chat with no parameters should dump a rundown of config fields and their values. In order to run any of the config commands, you will need to have ownerid or moderatorid (or the waterbases.admin permission).
/wb_cfg RelyOnShoreDistance [logical values (true or false)] /wb_cfg GlobalOceanLevelCheckBeforePlacing [logical values (true or false)] /wb_cfg GlobalOceanLevelBaseline [fractions (like 1.2345) between -1000.00 and 1000.00] /wb_cfg CargoShipPathHandling ["Warn", "Prevent" or "None"] /wb_cfg MinDistanceFromCargoShipNode [fractions (like 1.2345) between 0.00 and 10000.00] /wb_cfg UnderwaterNetsCollectJunk [logical values (true or false)] /wb_cfg UnderwaterNetsRandomTimerMin [fractions (like 1.2345) between 0.00 and 10000.00] /wb_cfg UnderwaterNetsRandomTimerMax [fractions (like 1.2345) between 0.00 and 10000.00] /wb_cfg UnderwaterNetsItemLimit [integers (like 12345) between 0 and 100] /wb_cfg UnderwaterNetsSpawnSharks [logical values (true or false)] /wb_cfg UnderwaterNetsSharkRandomTimerMin [fractions (like 1.2345) between 1.00 and 100000.0] /wb_cfg UnderwaterNetsSharkRandomTimerMax [fractions (like 1.2345) between 1.00 and 100000.0] /wb_cfg UnderwaterNetsSharkTimerShortenByPercent [fractions (like 1.2345) between 1.00 and 100000.0] /wb_cfg UnderwaterNetsSharkSpawningMinDistance [fractions (like 1.2345) between 2.00 and 100000.0] /wb_cfg UnderwaterNetsSharkSpawningMaxDistance [fractions (like 1.2345) between 2.00 and 100000.0] /wb_cfg UnderwaterNetsSharkPopulationLimitLocal [integers (like 12345) between 0 and 1000] /wb_cfg UnderwaterNetsSharkPopulationLimitGlobal [integers (like 12345) between 0 and 1000] /wb_cfg UnderwaterNetsSharkSleepDespawnTimer [fractions (like 1.2345) between 2.00 and 100000.0] /wb_cfg UnderwaterNetsSharkHealthMultiplier [fractions (like 1.2345) between 0.001 and 100.0] /wb_cfg UnderwaterNetsSharkSpeedMultiplier [fractions (like 1.2345) between 0.001 and 100.0] /wb_cfg UnderwaterNetsSharkAggroRange [fractions (like 1.2345) between 0.001 and 100.0] /wb_cfg SharkHarvestingLootEnabled [logical values (true or false)] /wb_cfg GuiNEW1AnchorMinX [fractions (like 1.2345) between 0.00 and 1.00] /wb_cfg GuiNEW2AnchorMinY [fractions (like 1.2345) between 0.00 and 1.00] /wb_cfg GuiNEW3AnchorMaxX [fractions (like 1.2345) between 0.00 and 1.00] /wb_cfg GuiNEW4AnchorMaxY [fractions (like 1.2345) between 0.00 and 1.00] /wb_cfg GuiNEW5OffsetMinX [fractions (like 1.2345) between 0.00 and 1.00] /wb_cfg GuiNEW6OffsetMinY [fractions (like 1.2345) between 0.00 and 1.00] /wb_cfg GuiNEW7OffsetMaxX [fractions (like 1.2345) between 0.00 and 1.00] /wb_cfg GuiNEW8OffsetMaxY [fractions (like 1.2345) between 0.00 and 1.00] /wb_cfg GuiTextSize [integers (like 12345) between 0 and 100] /wb_cfg GuiButtonColor [hexadecimal numbers WITHOUT preceding # (like 3db4b3)] /wb_cfg GuiTextColor [hexadecimal numbers WITHOUT preceding # (like 3db4b3)] /wb_cfg GuiButtonAlpha [fractions (like 1.2345) between 0.00 and 1.00] /wb_cfg GuiTextAlpha [fractions (like 1.2345) between 0.00 and 1.00] /wb_cfg EnableBarrelEntities [logical values (true or false)]
Advanced config (only editable through oxide/config/WaterBases.json) Water foundation crafting cost
Here you can adjust how much it costs to craft water foundations. Make it more expensive, less expensive, or add/remove required materials. The cost will stay the same for all permission profiles. A full list of short names for items can be found at https://www.corrosionhour.com/rust-item-list/
"CraftingCostSquare": [ { "Shortname": "wood", "Amount": 100 }, { "Shortname": "metal.fragments", "Amount": 200 } ], "CraftingCostTriangle": [ { "Shortname": "wood", "Amount": 50 }, { "Shortname": "metal.fragments", "Amount": 100 } ], Shortname should belong to one of the available items in-game. The amount should be a whole number larger than 0 and smaller than the limit of a signed 32-bit integer (2 147 483 647).

Permission profiles
Using profiles you can quickly create/edit different permissions for different players, for example, if you have more than 1 VIP tier on your server - just add some new profiles. Different players can have different limits and permissions associated with building water bases. To check which permission profile the player should fall under, the plugin goes through all permission profiles and checks whether the player has that permission granted. The permissions are checked in order, meaning that if the player doesn't have the first permission, it will try the next permission on the list, etc (similar to how Auto Kits checks which kit to give to a player based on their permissions in order). If the player doesn't have any permissions from the list granted, they will fall back to the "default" profile. That's the only one that you shouldn't remove! If you remove it, a new one with default values will be created. So if you don't want your default, non-VIP players to build water bases, don't remove the default profile, just take away privileges in that profile (like deploying/expanding/reinforcing). You don't have to use the built-in VIP permissions - any permission from any plugin will do just fine! By default, three permission profiles are generated in the config: default, waterbases.admin and waterbases.vip1. The default permission profile will apply to any player who doesn't have any permissions listed in the profile list - let's have a look at it:
"PermissionProfiles": { "default": { "PermissionRequired": "default", "MaxBuildingGradeGeneric": "Wood", "MaxBuildingGradeFrames": "Stone", "MaxBuildingGradeWaterFoundations": "Metal", "WaterDepthMin": 2.0, "WaterDepthMax": 100.0, "MaxWaterFoundationsPerBuilding": 25, "MinDistanceFromOilrig": 200.0, "MinDistanceFromShore": 2.0, "MaxDistanceFromShore": 20.0, "CanDeployWaterFoundations": true, "CanReinforceWaterFoundations": true, "CanExpandWaterFoundations": true, "CanExpandReinforcedFoundations": true, "CanCraftWaterFoundations": true, "RequireMaterialsForCrafting": true, "WorkbenchLevelRequired": 2.0, "CanDeployUnderwaterNets": true, }  
PermissionRequired should contain an already existing permission registered by any plugin in the form of pluginname.permissionname MaxBuildingGradeGeneric, MaxBuildingGradeFrames andMaxBuildingGradeWaterFoundations define the highest allowed grade for a particular part of a water base. Generic means anything that's not a water foundation or a door/floor frame (that includes normal floors, walls, half walls, and inverse foundations). For those 3 settings, the accepted options are "Twigs", "Wood", "Stone", "Metal" or "TopTier". Set all of them to "TopTier" if you don't want any tier limits on water bases. WaterDepthMin and WaterDepthMax define the allowed range for water depth when placing water foundations - to make sure that certain players are not building in water that is too shallow/too deep. The unit meters. MaxWaterFoundationsPerBuilding is what it sounds like it will prevent a player under this permission profile from adding more water foundations to a water base, limiting their size. Set to a large value like 100000 for virtually no limits. MinDistanceFromOilrig will define the minimum distance from the closest oilrig (in meters) that has to be respected before placing a water foundation down. Decrease to let players build closer, increase to make them build farther away. MinDistanceFromShore and MaxDistanceFromShore both rely on your map topology. If you're sure that you're quite close to the shore, but the /shore_distance command shows you ridiculous values, it means your map does not have the topology map painted properly (contact the map dev and let them know!). In that case, you should set the RelyOnShoreDistance option in the config to false and instead rely on water depth (if shore distance is enabled, it will rely on both). The unit here is not a meter, but roughly 1/10th of a map grid (around 15 meters). CanDeployWaterFoundations if set to true, will allow players using this profile to deploy newly started foundations (using the doughnut guide, provided they have a properly shaped water foundation item to be consumed). CanReinforceWaterFoundations if set to true, will allow players using this profile to reinforce water foundations by hitting them with a hammer (provided they have a properly shaped water foundation item to be consumed). CanExpandWaterFoundations if set to true, will allow players using this profile to build more water foundations upon already existing ones by placing neighboring floors with their building plan (provided they have a properly shaped water foundation item to be consumed). CanExpandReinforcedFoundations if set to true, will allow players using this profile to attach a floor to the side of a reinforcement foundation - and as long as they have 2 water foundation items in their inventory, they will expand that reinforced foundation along with its water foundation. CanCraftWaterFoundations if set to true, will allow players using this profile to craft water foundations using a GUI in the bottom-right (showing while a Building Plan is equipped). Profiles with this setting set to false won't display those GUIs and players will have to find other ways of obtaining water foundations (loot, kits, server rewards etc). RequireMaterialsForCrafting if set to true, players using this profile will need to have required crafting materials in their inventory when trying to craft a Water Foundation. If set to false, the player will be able to craft an infinite amount of water foundations for free, so use them with caution. WorkbenchLevelRequired Set to 0.0 (no workbench nearby required), 1.0 (Level 1 required), 2.0 (Level 2 required) or 3.0 (Level 3 required) for crafting Water Foundations. CanDeployUnderwaterNets if set to true, players will be able to deploy nettings in underwater wall frames. Those settings will slowly accumulate underwater junk items if the feature is enabled on your server - look below for the loot table configuration.
Underwater junk & Netting Shark loot tables
If you have not disabled underwater nets collecting junk, this is where you can adjust the kind and rarity of certain items. You can even remove entries and add your own, including a custom skin and item name! A "loot table" is perhaps not the right term, as the list contains individual chances of a "caught" item being of a particular kind. There can be only 1 item caught at a time, and the table defines random weights for every possible entry. The larger the weight (compared to the sum of all weights), the bigger chance of encountering a particular item. So if you have 10 entries and each of them have a weight of 1, each item will have an equal 10% chance of being one of the random entries in the list (as the weights sum up to 10). Thus you can have some items really common, and some of them really rare. Here are 2 sample entries from the list:
{ "Shortname": "innertube", "CustomName": null, "SkinID": 2484982352, "RandomChanceWeight": 1.0, "MinRandomAmount": 1, "MaxRandomAmount": 1 }, { "Shortname": "innertube", "CustomName": null, "SkinID": 2485021365, "RandomChanceWeight": 1.0, "MinRandomAmount": 1, "MaxRandomAmount": 1 },  
Shortname is the most important bit - make sure it's correct! You can find a link to a full list of those names above. CustomName lets you give items caught in the netting different names. You can leave that null to leave a default item name. In this example, the two items are water foundations - the proper name for those items will be applied automatically by the plugin anyway. Whatever you type there, make sure to encompass it in quotes, like "CustomName": "My Custom Item Name" if it's not null! SkinID is pretty self-explanatory - it's the long number in the URL of a Steam Workshop item. By default, it's 0 (no skin). RandomChanceWeight lets you decide the item's rarity when spawning - relative to the rarity of other items. Increase or decrease this number (it can be fractional) to make the item more or less rare. MinRandomAmount and MaxRandomAmount are what they sound like - they should both be larger than 0 (whole numbers) and when that particular item is caught, the stack will contain an amount between these two numbers.
Translation support (oxide/lang/en/WaterBases.json)
Almost every string the players see, including names for the water foundation items and messages displaying in the chat and the GUI, can be edited. Just load the plugin and let it generate the file - after you edit it, reload the plugin.

The world has changed. The island in the ocean has become a haven for evil spirits, the surviving inhabitants call them the Walking Dead. Once the blooming and fragrant city of Atlanta was the center of this island, now it is a dead city with its inhabitants. There are very few people left who are opposed by the walking dead, but every day there are more and more of them, the dead people turn into zombies and there is no stopping it. I present to your attention my new map with incredible detail of monuments and their features, the plug-ins included will give even more atmosphere of the lost world of the zombie apocalypse. On the map you will find a large number of roads, railways, tunnels and rivers. You will also love the many unique places to build bases for your players. I tried very hard to create this map, I hope you like it, Thank you. Good luck surviving in Atlanta!
Attention: The Train Home plugin shown in the video does not come with the map, it is sold separately
Features:
Prefab Count: ~71к prefabs Size: 4500 A lot of interesting locations to explore Marketplaces, Helicopter Salesman  and recycler have been added to fishing villages Railway A large number of places for the construction of foundations in the form of unusual rocks, caves, landscape, underwater  and icebergs Custom ways to overcome distances on boats and tugboat Custom plugin Event Prison Alert (by  KpuctaJL) Custom plugin Map Skinner  (by  Adem) Custom plugin  Npc Moving Control  (by  Adem) Realistic zombies on the map The atmosphere of the zombie apocalypse This map is constantly supported and updated for the current version of the game with all updates!
How can I view the map?
You can do this in our Discord server by submitting a request for an invitation to our servers. There you will be given the rights of an "administrator” and without any difficulties you will be able to fly around the map and fully familiarize yourself with it.

Custom Monuments:
Atlanta City Alexandria Woodbury Prison Police Department Harrison Hospital Railway Depot Herschel Farm Hilltop Strange Swamp Lonely Wandered Nomads Camp Gang of Survivors Convoy Desert Gas Station Ore Mine Farmers Camp Laundry Motel Old Cave Monument Train Home Custom point Zipline  interesting places to build a base marked X Monument Facepunch:
Launch Site Ferry Terminal Missile Silo   Junkyard Harbor 1 and 2 Arctic Research Base Satellite Dish Airfield Bandit Camp Outpost Giant Excavator Pit Water Treatment Military Tunnel The Dome Ranch Fishing Village 1,2,3 (Modified version) Lighthouse Underwater Lab Railway HQM, Sulfur, Stone Quarry Roadside Monument RadTown Water Well

Welcome to SYNECDOCHE!
Synecdoche (noun) Sin-eck-doh-key: A figure of speech in which a part is made to represent the whole.
Crafted over the course of years, this map offers something extraordinarily rare in this community. Custom monuments are amazing and fun to explore! I've seen so much hard work go into them and people have made some really cool stuff. However, custom monuments are only a small part of the level design in Rust. Wouldn't it be nice if we could get as much unique design detail out of the rest of the map? Wouldn't it be nice if your server felt like a real place, instead of a procedural blob map?


A Map Focused on Detail, no matter where you are:
But who would be insane enough to do such a thing? And how would it be possible? A 4k Rust map is 16 square kilometers. To make this feel like a real place, and give each space the attention to detail it needs demands thousands of hours working with consistent standards. This is why almost all of the maps aside from a handful on these sites will choose to use some form of procedural generation, and what makes synecdoche so uncommon. Every square meter was hand crafted with care, to make a place that feels alive and fantastical. it's what makes the map feel so beautiful.

Still Not Convinced?
Well, here's some of the feedback we've gotten from the community!

Where Reality Meets Fantasy
Each and every spot on the map was precisely manicured to feel unique and significant. Every rock has its purpose, and every nook and cranny was deliberately sculpted to inspire exploration. There are no locations on the map that were forgotten or left behind. Each location plays its part to represent the world as a whole.
Information and Specifics:
This map includes only vanilla monuments and can be run under the community tab. It does not require any 3rd party dependencies, not even the RustEdit Oxide DLL. However, you will need to place the included Harmony mod in you harmony folder to prevent Cargoship from leaving the map while it docks at the northern harbor.
Size: 4096 x 4096
Entity Count: ~68,000
Prefab Count: ~16,000
Can Edit: True
Required Plugins:
Block CargoShip Egress (Included with Map Download) Monuments
Junkyard Trainyard Outpost Bandit Camp Fishing Village (X3) Missile Silo Arctic Research Base Military Base (X2) Airfield Water Treatment Plant Sewer Branch (X2) Satellite Dish The Dome Harbor (X3) Military Tunnel Launch Site Power Plant Mining outpost (X7) Oxum's Gas Station Supermarket (X3) Lighthouse (X5) Abandoned Cabins Oil Rigs (large and small) Caves Underground train system Aboveground train system Underwater Labs (X2) Featured Videos:
 
 
 
 

Nuclear war, what could be worse than that. War is a harbinger of death. I present to your attention a map in the post-nuclear world. Nuclear bombs were dropped long ago on this once beautiful island, radiation destroyed most of the living world, craters formed and a handful of people were able to take refuge in shelters. You are one of the lucky ones who have been in the shelter for a long time, you were born in the shelter and do not know what is happening on the surface.
In the craters formed after the missile strike, they served as excellent places for the construction of cities and factories, the remaining technologies allowed the surviving population to develop. On this map you will find many custom monuments in an unusual style, and the music plugin from  KpucTaJl  will add to you the atmosphere of the old world. Monorails run along the entire outskirts of the island, which fit very well into the atmosphere.
Remember, the wasteland does not spare anyone, good luck! I express my gratitude to  STAR  for providing the  DELTA  monument.
Description 2
Size: 4000к
Prefab Count: ~60к
Operation of the "SoundRustEdit" plugin
In some moments there is a radio that plays and the music changes, there are 12 different songs from the Fallout game in the plugin
How can I view the map?
You can do this in our Discord server by submitting a request for an invitation to our servers. There you will be given the rights of an "administrator” and without any difficulties you will be able to fly around the map and fully familiarize yourself with it.
Discord Server:  https://discord.gg/UpUXuxs4Vx
Custom monuments:
Sunctuary Vault 103 Concord City Camp in Pit Vault 118 General Atomics Robotics Opencast Mine Large Dam Rad Farm Radar Vault Tec Barge Village Junk Town Olivia Station Open Air Cinema Diner Starline Restaurant Mobile Station Red Rocket (2 options) Monorails and railway tracks Many islands, for those who like to live far from the mainland Places to build (some can only be accessed by air transport) Monuments from Facepunch:
Launch Site Nuclear Missile Silo Outpost Ferry Terminal Junkyard Water Treatment Plant Train Yard Airfield Military Tunnel Power Plant Giants Excavator OilRig (2) Harbor Bandit Camp Sewer Branch Lighthouse Fishing Village Ranch The Dome Satellite Dish Roadsite Monument Underground Tunnels Arctic Research Base Underwater Lab Ziggurat Required Dependencies:https://github.com/k1lly0u/Oxide.Ext.RustEdit

This map is constantly supported and updated for the current version of the game with all updates!

Auto Turret Interference & Settings
Auto Turret Interference allows you or your CLAN/TEAM to change the limit of turrets allowed for different players, based on your configurations and assigned roles. You can also make sure that the server or event turrets do not have interference, for example Raidable Base.
In addition, it offers commands to see the statistics on the auto turrets, the possibility of turning the turrets ON and OFF via command, automatic switching ON and OFF of the auto turrets and much more.

It also allows you to modify some automatic turret configurations, for example:
Customize rotation angle, Viewing angle and target scanning, Infinite Ammo: In the next release Health, Range, Bullet Speed, Aim Cone, Damage Scale
Oxide/Carbon compatibility
 
Basically, 4 groups are configured: Default, VIP1, VIP2, VIP3, in this way you can decide the limit of turrets in a given radius based on the group assigned to the user or the group they belong to
Permissions:
autoturretinterference.admin -- Allows you to execute some commands reserved for administrators autoturretinterference.show.allowed -- Allows you to use the /ati show command, to display text above the auto turrets with the status they are in.  
---------------------------------------- autoturretinterference.default -- Assign configurations: Default autoturretinterference.vip1 -- Assign configurations: VIP1 autoturretinterference.vip2 -- Assign configurations: VIP2 autoturretinterference.vip3 -- Assign configurations: VIP3  
These are the groups that are created by default, but you can add and/or edit groups as you wish.
For example, if you change the group vip1 to vip_elite, the permission autoturretinterference.vip_elite will be created
If you create a new group, for example vipvanilla, the permission autoturretinterference.vipvanilla will be created.
 
COMMANDS
Commands can be typed in chat (by putting the / character in front of the command), or from console.
/ati status or /ati st -- This command allows the player to see his auto turret statistics and limits /ati status <steamID> or  /ati st <steamID> -- This command allows the administrator to see another players auto turret and limit statistics. To use this command you must have permission: autoturretinterference.admin
  /ati start or  /ati stop -- This command allows the player to turn on or off the single auto turret you are looking at. To use this command, you must enable the AllowCommandsToStartAndStop = true property in your configuration or have permission: autoturretinterference.admin NB: If you have autoturretinterference.admin permission, you can turn on or off the auto turret you are watching of any player.
  /ati startall or  /ati stopall -- This command allows the player to turn all of your auto turrets ON or OFF. To use this command, you must enable the AllowCommandsToStartAndStop = true property in your configuration or have permission: autoturretinterference.admin NB: If the player is part of a clan/team, all turrets of all members of the clan/team will be turned ON or OFF. /ati startall <steamID> or  /ati stopall <steamID> -- This command allows you to turn ON or OFF all turrets of a player based on its SteamID. To use this command you must have permission: autoturretinterference.admin NB: If the player is part of a clan/team, all turrets of all members of the clan/team will be turned ON or OFF.
  /ati show or /ati sh -- Command to display text above the auto turret with the status they are in.
Useful for finding turrets that are having problems.
To use this command you must have permission: autoturretinterference.show.allowed
You can pass one of these parameters: /ati show 0: Show all player auto turrets in all states. /ati show 1: Show text on all player active auto turrets /ati show 2: Show text on all player turned off auto turrets /ati show 3: Display text on all player auto turrets not connected to power /ati show 4: Display text on all player auto turrets with interference /ati show 5: Display text on all player auto turrets with information on the name of the weapon and the ammunition present in the auto turrets /ati show 6: Display text on all player auto turrets without a weapon /ati show 7: Display text on all player auto turrets without ammunition
  /ati show <numbr> <steamID> or /ati sh <numbr> <steamID> -- Command to display text above the auto turret with the state it is in based on the players SteamID.
To use this command you must have permission: autoturretinterference.admin Commands can be added or modified in the configuration file: /oxide/config/AutoTurretInterference.json

Command output example (/ati status or /ati st) :




Command output example (/ati show or /ati sh) :
 


CLAN/TEAM
If you are part of a clan/team and there are 1 more members who have the VIP/ROLE, then all members of the clan/team will benefit.
Example: a clan/team member has the VIP/ROLE to be able to place 40 turrets, in this case all clan/team members will be able to place 40 turrets, but this does not mean that the total number of turrets you can place are added, the limit in in this case there are still 40 turrets, but they can be positioned by all members of the clan/team, rather than just the player who has the VIP/ROLE (in this case we assumed that the VIP/ROLE limited to 40 turrets).
You can enable this setting from the configuration file: "Share Group With Clan/Team members. Default FALSE": false": true


Configuration
The settings and options can be configured in the AutoTurretInterference under the config directory. The use of an editor and validator is recommended to avoid formatting issues and syntax errors.  
{ "Remove interference for server auto turrets: default true (Useful for Raidable Bases or events)": true, "Share Group With Clan/Team members. Default FALSE": false, "PlayerShowTurretCountInfoMessage (Show the player, when he places a turret, a message with the number of turrets that are placed in the radius he is in. Default true.)": true, "AllowCommandsToStartAndStop (If set to TRUE, enables commands to allow the player or clan/team to turn their all auto turrets ON or OFF. Default FALSE)": false, "EnableAutomaticsStartAndStop (If set to TRUE, the player's turrets will be turned OFF when they go offline and ON when they come back online. For the clan/team, the entire clan must be offline to turn OFF the turrets automatically, but if at least one member of the clan comes back online, all the auto turrets will turn ON. Default FALSE)": false, "EnableMessageInfo (If set to TRUE, it shows a message info to the player, when he takes hold of an auto turret, of the commands that the plugin makes available to him)": true, "Auto Turret Draw Time (seconds). Default 60s": 60, "Auto Turret Draw Font Size (px). Default 16 pixel": 16, "Enable SentryTurrets plugin integration. If set to true, avoid conflicts with turret interference, interference will be handled by the AutoTurretInterference plugin. Default true": true, "Chat Command": [ "ati", "autoturretinterference" ], "RolePermission": { "vip1": { "Priority. (lower = higher priority)": 1, "Force the maximum number of Auto Turrets for player or entire clan/team (-1 no limit). Default -1": -1, "Player Auto Turrets without interference limit": 40, "Radius within which the system checks for other turrets (lower = more turrets)": 40, "Rotate Auto Turrets 180° degrees instead 90°. Default false": false, "Rotate Auto Turrets 270° degrees instead 90°. Default false": false, "Rotate Auto Turrets 360° degrees instead 90°. Default false": false, "Auto Turret Viewing angle and target scanning. Default 180° Degrees": 180, "Enable Auto Turrets custom settings": false, "Health (Default 1000)": 1000.0, "Range (Default 30)": 30.0, "Bullet Speed (Default 200)": 200.0, "Aim Cone (Default 4)": 4.0, "Damage Scale (Default 1.0)": 1.0 }, "vip2": { "Priority. (lower = higher priority)": 2, "Force the maximum number of Auto Turrets for player or entire clan/team (-1 no limit). Default -1": -1, "Player Auto Turrets without interference limit": 30, "Radius within which the system checks for other turrets (lower = more turrets)": 40, "Rotate Auto Turrets 180° degrees instead 90°. Default false": false, "Rotate Auto Turrets 270° degrees instead 90°. Default false": false, "Rotate Auto Turrets 360° degrees instead 90°. Default false": false, "Auto Turret Viewing angle and target scanning. Default 180° Degrees": 180, "Enable Auto Turrets custom settings": false, "Health (Default 1000)": 1000.0, "Range (Default 30)": 30.0, "Bullet Speed (Default 200)": 200.0, "Aim Cone (Default 4)": 4.0, "Damage Scale (Default 1.0)": 1.0 }, "vip3": { "Priority. (lower = higher priority)": 3, "Force the maximum number of Auto Turrets for player or entire clan/team (-1 no limit). Default -1": -1, "Player Auto Turrets without interference limit": 20, "Radius within which the system checks for other turrets (lower = more turrets)": 40, "Rotate Auto Turrets 180° degrees instead 90°. Default false": false, "Rotate Auto Turrets 270° degrees instead 90°. Default false": false, "Rotate Auto Turrets 360° degrees instead 90°. Default false": false, "Auto Turret Viewing angle and target scanning. Default 180° Degrees": 180, "Enable Auto Turrets custom settings": false, "Health (Default 1000)": 1000.0, "Range (Default 30)": 30.0, "Bullet Speed (Default 200)": 200.0, "Aim Cone (Default 4)": 4.0, "Damage Scale (Default 1.0)": 1.0 }, "default": { "Priority. (lower = higher priority)": 100, "Force the maximum number of Auto Turrets for player or entire clan/team (-1 no limit). Default -1": -1, "Player Auto Turrets without interference limit": 12, "Radius within which the system checks for other turrets (lower = more turrets)": 40, "Rotate Auto Turrets 180° degrees instead 90°. Default false": false, "Rotate Auto Turrets 270° degrees instead 90°. Default false": false, "Rotate Auto Turrets 360° degrees instead 90°. Default false": false, "Auto Turret Viewing angle and target scanning. Default 180° Degrees": 180, "Enable Auto Turrets custom settings": false, "Health (Default 1000)": 1000.0, "Range (Default 30)": 30.0, "Bullet Speed (Default 200)": 200.0, "Aim Cone (Default 4)": 4.0, "Damage Scale (Default 1.0)": 1.0 } }, "VersionNumber": { "Major": 1, "Minor": 3, "Patch": 1 } }  
Remove interference for server auto turrets: default true (Useful for Raidable Bases or events): Whether or not to enable interference for server auto turrets. By default it is true, in this way the server's automatic turrets will not have interference, useful for events for example: Raidable Base. Share Group With Clan/Team members: If set to TRUE, the group assigned to a player is shared with all members of the clan/team. The group with the lowest priority is shared, then all members of the clan/team will benefit. Default FALSE PlayerShowTurretCountInfoMessage: Show the player, when he places a turret, a message with the number of turrets that are placed in the radius he is in. Default: TRUE. AllowCommandsToStartAndStop: If set to TRUE, enables commands to allow the player or clan/team to turn their all auto turrets ON or OFF. Default FALSE. EnableAutomaticsStartAndStop: If set to TRUE, the player's turrets will be turned OFF when they go offline and ON when they come back online. For the clan/team, the entire clan must be offline to turn OFF the turrets automatically, but if at least one member of the clan comes back online, all the auto turrets will turn ON. Default FALSE. EnableMessageInfo: If set to TRUE, it shows a message info to the player, when he takes hold of an auto turret, of the commands that the plugin makes available to him. Default: TRUE. Auto Turret Draw Time (seconds). Default 60s: Duration of display of text above the auto turret. Default 60 seconds. Auto Turret Draw Font Size (px). Default 16 pixel: Size of text above auto turret. Default 16 pixel Enable SentryTurrets plugin integration. If set to true, avoid conflicts with turret interference, interference will be handled by the AutoTurretInterference plugin: Enables integration with the SentryTurrets plugin to avoid conflicts with auto turrets interference management. If set to true, auto turrets interference will be handled by the AutoTurretInterference plugin. Default true
Chat Command: Here you can add, edit or delete Commands can be typed in chat (by putting the / character in front of the command), or from console.  
Priority. (lower = higher priority) -- Each group has its own property, the lower this number is, the more important the group is.
This is useful in the case where a player has more roles assigned. In this case, the group with the lowest priority will be assigned, the most important group.
Negative numbers are also allowed. Player Auto Turrets without interference limit: How many automatic turrets can a player place within the radius within which the system controls the other turrets, without them interfering. For example, basic rust allows 12 turrets in a radius of 40 meters, you can set for example 30 turrets instead of 12. Radius within which the system checks for other turrets (lower = more turrets) Force the maximum number of Auto Turrets for player or entire clan/team (-1 no limit).
Maximum total number of auto turrets that can be active for player or entire clan/team.
When Auto Turrets are placed, only a certain number in a certain radius, configured in the configuration file, can be active at a given time.
However, this does not prevent you from being able to place unlimited Auto Turrets.
For example, you have set a limit of 20 Auto Turrets in a 40 meter radius, this means that in a 40 meter radius there can be a maximum of 20 Auto Turrets. But if you place another 20 Auto Turrets more than 40 meters away from the first ones, then you can place another 20 active Auto Turrets, and so on.
With this option you can establish the maximum number of Auto Turrets that can be active regardless of the radius, in order to avoid unlimited Auto Turrets.
It is always recommended to use this configuration together with the others.
For example you can decide that the forced maximum Auto Turrets limit is 5 times the number of active Auto Turrets in a given radius, it's up to you to decide. Default -1.
  Auto Turrets rotation angle: Allows you to change the rotation angle of the turret. Targets will be acquired as usual, if they are in front of the turret which however can move to a larger angle. Rotate Auto Turrets 180° degrees instead 90°: If set to TRUE, the auto turrets will rotate 180° instead of the default 90° (degrees). Default False Rotate Auto Turrets 270° degrees instead 90°: If set to TRUE, the auto turrets will rotate 270° instead of the default 90° (degrees). Default False Rotate Auto Turrets 360° degrees instead 90°: If set to TRUE, the auto turrets will rotate 360° instead of the default 90° (degrees). Default False
  Auto Turret Viewing angle and target scanning: This is a very powerful setting, it allows the auto turrets to see and acquire targets instantly based on the set angle, regardless of whether the target is in front of the auto turrets or not.
For example if set to 200°, the auto turrets will acquire targets instantly within 200°.
Or if set to 360°, the auto turrets will acquire targets instantly in all directions. You can choose the angle you prefer by entering a number between 1° and 360° (degrees). Default 180° Degrees.
  Enable Auto Turrets custom settings: If set to TRUE, it allows you to change some Auto turret settings. Default FALSE Health (Default 1000): Auto Turrets maximum health.
Range (Default 30): Distance from which the weapon can see.
Bullet Speed (Default 200): Speed of bullets fired.
Aim Cone (Default 4): The weapon's aiming cone.
Damage Scale (Default 1.0): allows you to increase the damage of Auto turrets. A higher value indicates greater damage.

PlayerShowTurretCountInfoMessage EXAMPLE:



EnableMessageInfo EXAMPLE:


Localization
The plugin, therefore the automatic messages and statistics, are translated into the following languages:
English Italian Spanish French German Dutch Turkish Russian Ukrainian Translation files are located in the /oxide/lang folder, here is an example of a /oxide/lang/en/AutoTurretInterference.json translation file.

You can add translations for other languages by adding them to the folder: /oxide/lang