Search the Community

Displays the name of the zone the player is in. You can customize text, text color, background color, etc. This plugin takes information about zones from zonemanager, all information is saved in a config file, after which you can customize information about these zones, which will be displayed Commands: /rzinfo - update zone information Config file: { "Settings outside the zone": { "Id": "0", "Name": "Outside", "AnchorMin": "0.649 0.041", "AnchorMax": "0.695 0.081", "Color_Background": "0.1 0.1 0.8 0.8", "Color_Text": "1 1 1 1", "TextSize": "16", "TextPlaceHolder": "Outside" }, "Default settings for the new zone": { "Id": "0", "Name": "Default", "AnchorMin": "0.649 0.041", "AnchorMax": "0.695 0.081", "Color_Background": "0.1 0.8 0.1 0.8", "Color_Text": "1 1 1 1", "TextSize": "16", "TextPlaceHolder": "Default" }, "Zones list": [] }

Introduction Automatically manages PVP zones for player bases, legacy shelters and tugboats. Features Manages its own Zone Manager zones and maps them as True PVE exclusion zones (Re)creates zones on plugin load and cleans them up on unload Provides tool cupboard based zones: Configurable creation & deletion delays Automatic resizing to always encompass the base as building blocks are added/destroyed, with configurable delay Configurable minimum total base and per-building-block buffer sizes Provides legacy shelter based zones: Configurable zone size Provides tugboat based zones: Configurable zone size Zone moves with the tugboat Optional support for visible zone spheres: Configurable sphere darkness Option to globally network tugboats to prevent spheres from disappearing Optional support for language file based zone creation/deletion and entry/exit notifications Configurable PVP expiration delay on player exit from zones Compatibility Hard dependency on Zone Manager for creating zones. Should work with various PVE plugins - tested with TruePVE and SimplePVE. Configuration Default configuration: { "Zone creation delay in seconds (excludes tugboat)": 60.0, "Zone creation delay notifications (owner only, excludes tugboat)": true, "Zone deletion delay in seconds": 300.0, "Zone deletion delay notifications (all players in zone)": true, "Zone creation/deletion notification prefix": "[PBPZ] ", "Zone exit PvP delay in seconds (0 for none)": 5.0, "Zone sphere darkness (0 to disable, maximum 10)": 0, "Zone entry/exit ZoneManager messages": true, "Zone TruePVE mappings ruleset name": "exclude", "Building settings": { "Building update check delay in seconds": 5.0, "Building zone overall minimum radius": 16.0, "Building zone per-block minimum radius": 16.0 }, "Shelter settings": { "Shelter zone radius": 8.0 }, "Tugboat settings": { "Tugboat force global rendering on/off when spheres enabled (null=skip)": null, "Tugboat force enable buoyancy when forcing global rendering": false, "Tugboat zone radius": 32.0 } } NOTE: The tugboat rendering options should be left at defaults. The options are provided for the case that you are running other plugins that force global networking/rendering for tugboats, which can cause spheres to disappear when a tugboat comes back into client render range.This plugin will automatically attempt to synchronize tugboat sphere networking with each tugboat's networking type when (re)creating the spheres. Developer API Supported API calls: string OnPlayerBasePvpDelayQuery(ulong playerID) Provides the ability to query whether a player has an active PVP delay Returns the triggering zone ID if the referenced player has an active PVP delay Returns an empty string If no PVP delay is active Hooks: void OnPlayerBasePvpDelayStart(ulong playerID, string zoneID) Called when PVP exit delay is applied to a player as a result of their exiting a base zone playerID is the ID of the triggering player zoneID is the Zone Manager zone ID whose exit triggered the delay void OnPlayerBasePvpDelayStop(ulong playerID, string zoneID) Called when PVP exit delay expires from a player playerID is the ID of the triggering player zoneID is the Zone Manager zone ID whose exit triggered the delay Zone Manager / PVE Plugin Integration Zone Manager zones are maintained for all bases, and are mapped to the configured True PVE ruleset (`exclude` by default). This will cause True PVE to treat them as vanilla areas by default, allowing for PVP to take place. Zone names are broken into categories in case you want other plugins to recognize them separately: `PlayerBasePVP:building` for building block bases `PlayerBasePVP:shelter` for legacy wood shelters `PlayerBasePVP:tugboat` for tugboats Developer note: Zone IDs are `PlayerBasePVP:` followed by a unique identifier. Background Player Base PVP Zones is meant for hybrid PVP servers that want to allow online raiding. It is meant to complement Dynamic PVP which only provides zones for monuments and events. Zone Manager is a hard requirement in order to implement moving zones for tugboats, as it doesn't officially support this feature. A PVE mod is required to make this useful. I only tested with True PVE for various reasons. Credits Thanks to the following folks for making this plugin possible: bmgjet (help with / code for tugboat sphere issues) CatMeat & Arainrr (moving Zone Manager zones code examples in Dynamic PVP) Karuza (help with unique entity identifiers & tugboat sphere issues) Kulltero (help with TC/building relationship) WhiteThunder (help with tugboat sphere issues) AFKBank and Mooselips whose bases I took screenshots of on my server during testing

I bring to you a new plugin that will add Pogo Sticks to your server! These Pogo Sticks will allow players to jump, somersault, and parkour in ways never seen before in the game. With default configuration, Pogo Sticks don't do as well on sand and snow, for obvious reasons right? But don't worry you can configure any of the pogo presets, such as the speed and height of jump for example. The Pogo Stick is an ordinary worn item with a skinID that can be given to the player by console command, or any of the other unique ways you might want to give them out in your servers. There are two activation modes for Pogo Sticks. With default configuration, the player has to put the item in a belt container. In this mode, the Pogo Stick is only used when it is selected as an active item. In the second mode, the Pogo Stick is activated when it is added to a clothing/armor container. In order to use the second mode, replace the shortnames of all Pogo Sticks with a clothing item. As an example "burlap.gloves.new" to replace a less noticable part of your wardrobe. In this second mode, players will be able to shoot and use items while on the Pogo Stick! The creativity is in your hands, have fun with it! Chat commands (only for administrators) /givepogo <pogoPresetName> - give the pogo stick to yourself Console commands (RCON only) givepogo <userID> <pogoPresetName> <amount> – give the pogo stick to player. Config plugin_en – example of plugin configuration in English plugin_ru – example of plugin configuration in Russian Dependencies (optional, not required) GUI Announcements Notify ZoneManager My Discord: Adem#9554 Join the Mad Mappers Discord here! Check out more of my work here!

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 and correct even after a server-crash. TruePVE (default) and NextGenPVE integration allows you to configure detailed rules for each zone type, e.g., Cargo Ship versus Supply Drops, with Rulesets and ZoneFlags. 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. Add the Zone PVx Info plugin to get whether the player is inside a PVP zone on the HUD. Set Entering and Leaving Zone messages to empty quotes ("") to disable them. 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", "Zone Tag (Adds this string to zone names)": "_PVP" } 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. Use the admin only chat command "/ReloadTCs" to apply config changes to already created zones. Don't forget that config changes are not automatically loaded. You can "Oxide.Reload AgileZones" to load new config without restarting the server, and then use the /ReloadTCs chat command to apply those changes to existing zones. 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. You can improve on this by setting Entering and Leaving zone messages to empty quotes (""), and installing the Zone PVx Info plugin which will put a UI element on the HUD instead.

READ BELOW FOR REQUIRED FIX FOR ABANDONEDBASES PLUGIN (CARBON ONLY)! READ BELOW FOR REQUIRED FIX FOR DYNAMICPVP PLUGIN (OXIDE & CARBON) YOU NEED TO HAVE RAIDABLEBASES 2.8.9 OR NEWER TO USE COUNTING DOWN PVPDELAY FOR RAIDABLE BASES (OXIDE & CARBON) Features: Tested on Carbon and Oxide Uses SimpleStatus to make a sleek customizable UI to show PVxStatus (PVE, PVP, PVPCooldown) Each UI Component can be individually toggled off or on Color settings allow for both: html color codes or rust colors (eg. #3AC916 OR 0.23 0.79 0.09 1 ) (NOTE: You will need to use the Rust color codes, if you would like to use transparency) Includes PVPDelay display and checking that integrates with: DynamicPVP, AbandonedBases, RaidableBases PVPDelay display should work with any plugin that utilizes DynamicPVP (eg. https://codefling.com/plugins/convoy) As long as the ZoneManger zone's name includes "pvp", the pvp tag will show up Option in config to enable Automatic FullPVP, if there are no PVE plugins detected (TruePVE, RealPVE, NextGenPVE, SImplePVE) Integrates with TruePVE pvp schedule (I will work on integrating schedules for other PVE plugins also) Specify additional PVE zones by including "pve" in the zone's name Command to mark the whole server as PVP, regardless of zones (such as PURGE on PVE servers (this setting saves and persists on server restart, you will need to re-issue the command, or edit the settings file to revert back) Customizable information for all 3 PVxStatus UI (Title, Text, Icon, and colors) Ability to use Rust icons, on the UI (eg. assets/icons/weapon.png) Ability to use Rust item images on the UI (eg. itemid:1055319033) NOTE: the itemID MUST have itemid: at the beginning Custom image from URL, and item images instead of only being able to use Icons (NOTE: URL MUST contain http:// OR https:// otherwise it will be seen as invalid) Integrates with DynamicPVP, AbandonedBases, RaidableBases for PVPDelay time remaining to allow for a live update of PVPDelay status with a draining UI bar (NOTE: "Separate UI Icon" AND "PVPDelay Countdown" need to be set to true to take advantage of this new UI Setting Commands: From the RCON, Console, or chat as an admin, you can type: pvpall (/pvpall for chat) to toggle the server to PVP displayed everywhere Planned Features: Languages to provide multi-language support proper integration with other PVE plugins Known Issues: PVP zone will still display, even if you are in a "Safe Zone", with FullPVP enabled Disappearing UI sometimes when leaving DynamicPVP zone. Make sure the change line specified below when using countdown PVPDelay, sometimes UI disappears and console spams "[AddUI] Unable to update object 'ss.PVxZoneStatus': can't be found" - Working on locating the underlying issue, to fix: set "PVPDelay Countdown": false, in the config and reload plugin (This should be fixed in version 1.1.0, but will leave it here for now and monitor) Recommended: Set the Default color as needed: eg. if you have PVE hidden, and PVP shown, set the default color to PVP (this is caused by an issue where the UI will flash to the default color scheme when showing the UI) Recommend setting RaidableBases DelayUI to disabled in your RaidableBases config file Tips: Using "Separate UI Icon": true in the config file will give you a slightly different design Using "PVPDelay Countdown": true in the config will give you a counting down timer/bar for your PVP delay RaidableBases config: Delay UI": { "Enabled": false, REQUIRED MODIFICATIONS!! Carbon: AbandonedBases If you are running AbandonedBases version <= 2.1.4, you need modify on Line 2667: (Line number would change depending on version, this line number is as of the most recent version of 2.1.4) if (!TryGetDelayValue(player.userID, out var ds)) to the following: if (TryGetDelayValue(player.userID, out var ds)) { ds.Timer?.Destroy(); PvpDelay.Remove(player.userID); } if (!TryGetDelayValue(player.userID, out ds)) This is to fix a bug with the timers in Carbon with Abandoned bases, as a player can clear their PVP Delay by running in and out of the base (CARBON ONLY) OXIDE & CARBON: DynamicPVP THIS IS ONLY IF YOU WOULD LIKE TO USE: "PVPDelay Countdown": true If you are running DynamicPVP version 4.2.17, you need modify on Line 1627 : (Line number would change depending on version, this line number is as of the most recent version of 4.2.17) Interface.CallHook("OnPlayerAddedToPVPDelay", player.userID, zoneId, baseEvent.PvpDelayTime); Change to: Interface.CallHook("OnPlayerAddedToPVPDelay", player.userID.Get(), zoneId, baseEvent.PvpDelayTime); Default Config { "Mark whole server as PVP Zone": false, "Default Colors (PVE, PVP, or PVPDelay)": "PVE", "FullPVP if no PVE Plugins Found": false, "Enable Schedule (TruePVE)": false, "Scheduled PVP mapping": "pvp", "Separate UI Icon": false, "PVPDelay Countdown": false, "Pvx UI Settings": { "PVE": { "Show on UI": true, "Title": "PVE Zone!", "Title Color": "#FFFFFF", "Text": "SAFE", "Text Color": "#FFFFFF", "Icon": "assets/icons/weapon.png", "Icon Color": "#FFFFFF", "Background Color": "#738D45" }, "PVP": { "Show on UI": true, "Title": "PVP Zone!", "Title Color": "#FFFFFF", "Text": "UNSAFE", "Text Color": "#FFFFFF", "Icon": "assets/icons/weapon.png", "Icon Color": "#FFFFFF", "Background Color": "#C44D43" }, "PVPDelay": { "Show on UI": true, "Title": "PVP Cooldown!", "Title Color": "#FFFFFF", "Text": "UNSAFE", "Text Color": "#FFFFFF", "Icon": "assets/icons/weapon.png", "Icon Color": "#FFFFFF", "Background Color": "#B35F1E" } } } Shoutout to @ELF for deciding to YOLO and live test

The plugin displays the status when the player is in the PvP zone. Features: Comprehensive setup of all aspects Option to tailor text for different languages to reach players from various countries Lang files for all languages are auto-generated, so you only need to write your text. Default Config: { "Icon Url": "default", "Colors": { "Color": "0.65 0 0 1", "Icon Color": "1 1 1 1", "Text Color": "1 1 1 1", "Subtext Color": "1 1 1 1" } } Default Lang: { "Text": "You're in the PVP zone", "Subtext": "" }

- Mars Attacks Arena Mars Attacks Arena is a booby-trapped battlefield where players must fight to the death. Beautifully decorated in a sci-fi style, Mars Attacks Arena will leave your players with their mouths agape. - Includes: Two zones: Floor 1 and 2, with Traps, Barricades, Parkour, Radiation Zone, NPCS and Loots.

Nova Weather is a drop-in replacement for Rust’s native server-side weather system. It is very customizable with unique features such as timelined profiles with events, and exceptional features that make it stand out such as support for zone-specific weather systems. Please note: This mod has no required dependencies, and can work out of the box without Oxide. Only if you need zone support will you need Oxide and the ZoneManager plugin. Let’s list some of Nova Weather’s best features. Below you’ll find a description for every major feature found in the mod. First off, we have Profile Timelines. This allows you to carefully construct your weather system by introducing elements staggered instead of all at once. For example; you could make a heavy rain storm by first making some clouds, then 30 seconds later darkening them, and when they’re done, slowly start rain that increases over 5 minutes until it’s at full strength. You can play with about 20 weather properties ranging from cloud coverage to fogginess to windspeed, and even override temperatures. For the first time, you can now have several separate weather systems active in your world using Nova Weather’s support for the ZoneManager plugin. You could make it rain on one island, and make it tropical on another. You could create zones for bosses where the sky darkens with thunderclouds the closer you get, or you could make your admin crib always sunny while the rest of the world is experiencing heavy rain. The possibilities are endless. Want to give your VIPs a sunny start to their day? Want to slap tryhards with a permanent storm over their heads? This can now be accomplished by using permissions. Nova Weather supports permission-based overrides to give you maximum flexibility. Although this is a Harmony mod, Nova Weather will hook into Oxide's permission system to allow you to manage permissions like you're used to. If Oxide is not installed, it'll fire up its' own permissions instead, modelled after Oxide so you're able to work with commands you're used to. Please note: If you're using Nova Weather's native permissions, instead of "o.<command> <arguments>" you should use "nw.perm.<command> <arguments>". Not only are you able to use the Profile Timelines feature to create beautiful and realistic weather patterns, you can also make things happen based on whatever weather you have running. Using the timeline, you can create a property element or you can create a command element. If you create a command element and place it on the 30 second mark in your timeline, the command will execute when 30 seconds have elapsed in that profile. Want to spawn a boss when the thunder starts in a thunderstorm? Want to start an event when the rain stops? Want to give everyone some currency when you’ve had fog on for 10 minutes?! You can do that with scheduled commands! All weather systems work on a few simple concepts, and the most important of those are Profiles. Profiles determine what should be shown in the world. You’ll have a profile for Clear, Rain, Fog, etc. These profiles live in your configuration folder as separate files, and are completely interchangeable. Created a kickass weather profile but hate the hassle of having to mix and match your config files? Just drop ‘em your profile files. They can just drag-and-drop them into their profiles folder, and they’re immediately usable. Share away! With advanced features comes some advanced configuration. We’ve tried to make it as simple as possible though, and in the Configuration chapter below we explain what everything does. There’s all sorts of settings to make your weather look amazing, or to optimize the weather system’s performance for lower end machines. You can choose whether or not to use ZoneManager support, you can tweak the amount of times a second the system updates, etc. With a ton of RCON Commands included (20+!) you can even do most of it without ever looking at a JSON file. The mod installs with a very comprehensive default configuration, created to mimic the native weather system with a bit of a makeover on install so you can just install and forget about it. The default profiles have timelines, and tweaked load chances to bring back some good looking weather types. Nova Weather offers you a ton of commands to make your life as an admin easier, and to give you full control over your server’s weather. Don’t like a particular profile right now? Skip it! Wanna show off your profile but the fun only starts at the 1-minute mark? Skip to that moment in the timeline! All commands are to be executed from the RCON or Server Console, not from in-game! All commands must start with either ‘novaweather.’ Or ‘nw.’. The list below uses the former for clarity, but you can use ‘nw.’ As a substitute to shorten your commands. Arguments indicated with “<argument>” are mandatory for use with the command, while “(argument)” indicates an optional argument. Please note: To be able to use any of the zone-related commands you need to have Oxide installed and have loaded the ZoneManager plugin. Below you’ll find a list of all commands available with a short description. Basic commands novaweather.reload Reloads the mod and will reload all profiles from disk, as well as check for the existence of ZoneManager zones. If you’ve purchased or downloaded profiles into your Profiles folder, reload the mod to have it take effect. novaweather.report (climate) Reports the current weather conditions for all climates if the optional climate argument is not set. If it is, will limit the report to just that climate. novaweather.tickrate (number) If no number is set, will return the current tick rate. If a number is passed, will set the tick rate to that number. The tick rate determines how often the weather system calculates and updates, with a lower number meaning more often. It’s basically saying “Update every <number>th frame”, with 1 being the lowest possible number and 50 being the highest. The lower the number, the smoother the transitions. Climate-related commands novaweather.globalclimate (climate) If the climate argument is set, will set the global weather system’s climate to that climate. If the climate argument is not set, will return the name of the climate currently assigned to global weather. Novaweather.load <climate> <profile> (transition) Used to forcefully load a given profile to the climate immediately. If a numeric transition argument is passed, it will override the profile’s set transition time. “nw.load default default_clear 10” will load the default_clear profile and override the transition to 10 seconds to speed up the appearance of the profile. novaweather.loadnext <climate> <profile> Will forcefully set the next profile for a climate. When the current weather profile reaches its’ end, the next profile is automatically loaded. novaweather.next <climate> (transition) Forcefully ends the currently active profile’s timeline and loads in the next profile in the queue. If a numeric transition argument is passed, it will override the profile’s set transition time. novaweather.pause <climate> Pauses the timeline for the provided climate. Pausing a climate will effectively freeze the current weather in its’ current state indefinitely until unpaused. novaweather.unpause <climate> The ‘counter charm’ to the pause command. Unpauses the provided climate’s timeline (if it is paused). novaweather.skipto <climate> <seconds> Skip the current profile’s timeline to the provided seconds mark. If you enter a seconds mark greater than the timeline’s duration, it will skip it to the last frame effectively ending the profile’s timeline. novaweather.listclimates Presents you with a neat list of all running climates and their status and a list of all assigned profiles. Zone-related commands novaweather.disablezones Disables the ZoneManager support altogether. Will deactivate all non-global climates to save processing power. novaweather.enablezones Basically the ‘counter charm’ to disablezones. Re-enables all disabled zones and boots up all non-global climates if any exist. novaweather.disablezone <zone> Disables a single zone’s overrides. That’s about it. novaweather.enablezone <zone> The brother-command of the above mentioned one. Enables the zone again. novaweather.showzone <zone> More of a debug function, shows the wireframe for the given zone as if you’re editing it with ZoneManager. Good for determining a zone’s transition buffer zone. novaweather.zoneclimate <zone> (climate) This is a big one. This will do a few things based on the provided arguments; - If the climate argument is set and the zone is already registered with Nova Weather, it’ll change that zone’s climate and load it up immediately. - If the climate is set and the zone is not already registered, it will register it and set the zone’s climate and load it up. - If the climate argument is not set but the zone is registered, will return that zone’s set climate. novaweather.removezone <zone> Contrary to what you may think, this does not remove the actual ZoneManager zone. It just removes it from Nova Weather’s configuration and thus removes any zone overrides. This is permanent, if you’re just wanting to temporarily disable it use the ‘disablezones’ command listed above. novaweather.listzones Lists all zones that are configured within Nova Weather with their status and climate. Profile-related commands novaweather.getprofile <climate> Returns the name of the currently active profile for the given climate. novaweather.assignprofile <climate> <profile> (chance) Adds a profile to a climate’s profile list to be included in rotation. If the chance argument is set, will override the default value of “100”. Note that “chance” doesn’t literally mean a chance %, it’s a weight to make a weighted random, just named “chance” to make sure people understand its’ intended use. novaweather.unassignprofile <climate> <profile> The antithesis of the above-mentioned command. Will remove the profile from the climate’s profile rotation permanently. novaweather.setprofilechance <climate> <profile> <chance> Sets the chance (weight) for the given profile in the context of the given climate’s list of profiles. novaweather.listprofiles Lists all profiles loaded into Nova Weather’s memory. If you just created a profile file and don’t see it listed in this list, reload the plugin using the reload command in this list and try again. Nova Weather’s configuration is pretty in-depth but we’re going to try to make it as painless as possible. There’re two distinct types of configuration file for this mod, and those are the singular Configuration.json file and the individual Profile files. We’ll go over both in this section. All of Nova Weather's configuration files can be found in: ROOT / HarmonyMods_Data / NovaWeather (/ Profiles) Before diving into these options, a few key concepts need to be clear for you to fully understand all the ways you can customize your server’s weather. Profiles Profiles are separate files with properties. They contain all actual weather data such as rain level, cloud coverage, etc. It does not do anything in and of itself, it's just basically a timeline that shows the climate what weather to present. Climates Second, there’s Climates. Climates are each individual and isolated weather systems, and are assigned one or more profiles to cycle through. They read the profile data and make all calculations for transitions, timelines, etc. They’re the brain of the operation. Zones Lastly there’s Zones. A zone is a ZoneManager zone that's registered with Nova Weather, and contains information like the zone ID and the climate that should be presented to the clients present within that zone. In and of itself this doesn't to anything, it just tells us to override the global weather climate with another climate. Climates all cycle continuously in the background. Applying a climate to a zone doesn't change the climate at all, it just sort of subscribes to it. The climate is always telling the mod "Hey man, rain should be 1. wind should be 0". It doesn't care if anything's listening. The zone can then sort of connect to that, and hear what the climate is saying, and then show that to the player. This makes it so you can have 10 zones that share 1 climate, saving a ton of processing power. Configuration files: Configuration.json All right, let’s dive into our first bit of configuration. We’ll first take a look at Configuration.json. Note that this config is subject to change, and the image below may not be a fully accurate depiction of the current state of the config file structure. Modification enabled (true/false) A Boolean to turn the mod on or off without having to unload it. Will enable the native weather system if set to false. Enable debug logs (true/false) Will print quite verbose logs, meant to provide the developer more insight into potential problems. If you’re contacting support, make sure you include logs with this set to true. Global Options -> Pause weather if server empty (true/false) Pauses all climates’ timelines to halt processing, since nobody’s there to enjoy it anyway. I can’t think of a real reason to set this to false unless its for testing purposes, but you have the option to. Global Options -> Global weather climate Determines what climate will be applied to the global weather. Speaks for itself. ZoneManager options -> Use ZoneManager zones (true/false) If set to true, this will apply (a) climate(s) to the zone(s) in the zone climates list. If set to false, this will completely disable all zone functionality and will limit the mod to only global weather. ZoneManager options -> ZoneManager zone climates This is where you register and modify zone information. A zone can be disabled individually, have a climate set, and have a modified transition buffer. More on that below. ZoneManager options -> ZoneManager zone climates -> Enabled (true/false) Enables or disables this particular zone from having a climate override. ZoneManager options -> ZoneManager zone climates -> Climate The climate that should be shown to the clients within that zone. ZoneManager options -> ZoneManager zone climates -> Zone transition buffer percentage (1-100) The percentage of the zone’s radius which should be used as a transition buffer. When you enter a zone, you don’t want to instantly have another weather type pop into existence. This is where the zone transition buffer saves the day; the weather types are gradually transitioned between until you’re well and proper into the zone. If you put this at 50%, you’ll see the transition happen for half of the zone. After halfway into the zone, you’ll see no trace of the “outside” climate and will just see the zone climate. ZoneManager options -> ZoneManager zone climates -> Zone transition buffer max. Size (meters) With this you can put an absolute limit on the transition buffer size. This works best if you don’t exactly know the dimensions of the zone(s) you’ll be placing. This makes it so that the transition buffer will not go past the given number of meters past the zone’s border. So, if you set the buffer percentage to 50%, but set the max. meters to 10, the buffer will either go to 50% if it’s shorter than 10m, or it will cap at 10m. Please note: due to there not being a reliable method to calculate the distance travelled within a cuboid shaped zone, there is no transitional buffer for those. The mod will still function, though the weather will not smoothly transition from and to a cuboid shaped zone. See the graphic below for a visual representation of a buffer zone within a radial zone, with “%” meaning the buffer zone percentage. Climate definitions This will contain the definitions for the climates to be used. Climate definitions are very straightforwards, we only need an enabled status and a list of assigned profiles. Climate definitions -> Enabled This enables or disables a climate. A disabled climate will not do any calculations, or propagate any data to players. If you have a special event planned where you’d want to use a specific climate, but don’t want to accidentally use it elsewhere, you can disable it. Climate definitions -> Profiles This is the list of assigned profiles. That’s it. Climate definitions -> Profiles -> Profile The name of the profile to assign to this climate. Note that the name must match exactly, case sensitively. Climate definitions -> Profiles -> Chance This is the chance (weight) for this profile. A climate will cycle through all profiles based on their weight; if one profile has a weigh of 1 and one has a weight of 10, the latter will be 10x more likely to be picked as the next profile to be loaded. The weight is not capped at 100, it is just named “chance” to make sure everyone understands its’ function. From version 1.1.0: Update 1.1.0 introduces permission based overrides. This adds a section to your config: "Permissions options": { "Use Oxide permissions if possible (true/false)": true, "Permission climate overrides (set 'disabled' to disable)": { "novaweather.vip": "default_clear", "novaweather.disabled": "disabled" } } While pretty basic and self explanatory, it adds the following fields: Use Oxide permissions if possible (true/false) This tells the mod to use Oxide permissions if Oxide is installed. If Oxide is not installed, this option is ignored and native permissions are used. If this is set to false, native permissions are always used regardless of Oxide's status. Permission climate overrides (set 'disabled' to disable) These are the actual overrides. Works in a key-value pair, with the key being the permission and the value being the Climate that it should use. Note that the give permission must be fully specified with the 'novaweather.' prefix if its a novaweather-specific permission. Because of this, you can insert another mod's permission in here as well if you like. If the Climate is set to 'disabled', the user will not see changing weather as the mod will skip that user while calculating weather changes. This will allow other mods to influence weather for that user. Configuration files: Profiles/*.json With that out of the way, let’s dive into the profile configuration. { "Transition time (seconds)": 300, "Parent profile": "default_overcast", "Duration": { "Type": "range", "Min. seconds": 900, "Max. seconds": 1800 }, "Base properties": [ { "Property": "wind", "Value": 0.8 }, { "Property": "rain", "Value": 1 } ], "Steps": { "0": [ { "Type": "Property", "Property": "cloud_coverage", "Value": 0.8, "Fade (seconds)": 60 } ], "60": [ { "Type": "Property", "Property": "cloud_attenuation", "Value": 0.7, "Fade (seconds)": 30 } ] } } Transition time (seconds) Determines the duration of the transition between the last profile and this one. When a climate is cycling through the profile’s timeline and the timeline ends, the next profile will be loaded and the transition to it will start from the last frame of the last profile. If you set this to 0, the new profile just pops into existence. Set this to 10 and over 10 seconds the old profile vanishes and the new one appears. Parent profile There’re about 20 weather settings to mess around with, so if you had to enter them all every time it’d be annoying as ****. Thats why we’ve implemented profile inheritance. If you leave this empty you need to enter all 20 properties yourself, but if you already have a profile with properties you like and wish to modify a bit, you can enter that there. Say for example you have a “storm” profile with a regular old storm. But then, in addition to that regular storm, you also want a profile that storms but that also thunders and has a deep red sky. But you don’t want to have to copy-paste the “storm” profile. Instead what you can do is set the parent profile to “storm”, and then just set the thunder property to 1 and the atmosphere rayleigh to whatever you want. The profile will then use the properties of “storm” as a base, and use its’ own base properties to override those. This way you can make infinite variations of similar weather types. Duration Speaks for itself; the profile’s actual duration. There’re two types, “static” and “range”. If the type is set to “range”, it will randomly pick a number between the min and the max values. If the type is set to “static”, it will always pick the min. seconds value as its’ duration. Base properties These are the profile’s properties that are always set and will be transitioned to when the profile loads. You can find all possible properties in the “detailed convars” section of the following URL: https://wiki.facepunch.com/rust/Weather#detailedconvars In the profile’s properties you don’t include the “weather.” prefix for those properties, so “weather.rain” just becomes “rain”. The only property not included in that list that is usable with Nova Weather is the “temperature” property. This property is used to override the locally calculated temperature (think of temperature drops at night and such) and will always be the temperature you enter. This property can also be animated with steps. Steps This is how you animate a weather profile. Using steps, you can populate the profile’s timeline however you see fit. Remember that fun timeline graphic at the top of the page? That roughly translates to: "Steps": { "5": [ { "Type": "Property", "Property": "cloud_coverage", "Value": 0.8, "Fade (seconds)": 120 } ], "30": [ { "Type": "Property", "Property": "rain", "Value": 1.0, "Fade (seconds)": 120 } ], "130": [ { "Type": "Property", "Property": "thunder", "Value": 1.0, "Fade (seconds)": 150 } ] } Steps are put at static positions in the timeline by setting it to a specific second. Want rain to come in at the 30 seconds mark? You add a step at “30”. A step is animated as well; you can have the rain come in at 30 seconds and have it take 60 seconds to go from just a drop to a full on downpour. It’s all in the fade time. Within a step there’s four properties: - Type – this is either “Property” (case sensitive!) or “Command”. - Property – this is the actual weather property name like “wind” or “rain” and such - Value – the value of that property, usually between 0 and 1 - Fade (seconds) – the amount of time it should transition from base value to the new value Nova Weather will release with a few very basic weather profiles that showcase the function of the mod with base properties and timeline steps. You can play with this to your heart’s content. But, for those of you who are not super keen on spending hours configuring the perfect weather, we’re way ahead of you. Our team is working on a set of beautiful weather profiles that’ll be released on this marketplace in the near future. This takes significant amounts of time, so it may not yet be released at the time you’re reading this. But if they are, they will be released either for free or for a small fee. Check the related products for more information. Important to note is that any profile packs that you purchase from us are licensed, and therefore cannot be shared with others who have not bought the pack. Profiles are separate files that are found in the /Profiles folder of the Nova Weather folder. These profiles are in .json format and can be shared basically anywhere. All you have to do to import them is to place the .json file you received into your /Profiles folder with the other profile files, and reload the mod using the appropriate command. The smoothness of the transitions is determined by your Tickrate setting. If you set this to 10, then the mod will calculate new values every 10th frame. To make transitions smoother, you lower the Tickrate setting by either modifying the Configuration.json or use the appropriate command. Note that if you lower this number, the load on your server will slightly increase due to it having to calculate more often. As this is a Harmony mod, you install this by dropping the .dll file into the HarmonyMods folder in the root directory of your Rust server.

Open UI - /zm FEATURES: Create and setup zone with GUI Can damage other player in Zone Can Damage other player structures Can damage NPC Can damage Helicopter P.s - (My Discord - tofurahie#4144) Config: { "Show Notification": true, "Show None zone type": true, "Notification message when enter in zone(%ZONENAME% - Zone name, %ZONETYPE% - Zone type)": "You have entered the zone %ZONENAME%\nZone type: %ZONETYPE%", "Notification message when leave from zone": "You have left the Zone, now you are in the open world", "Zones": [ { "ZoneID(Uniq)": 1633968236, "Zone Name": "ZONE NAME", "Zone Type": "ZONE TYPE", "Zone Type Color(HEX FORMAT)": "white", "Zone Position": { "x": 189.8238, "y": 4.038739, "z": 606.1398 }, "Zone Radius": 10.0, "Visible sphere?": false, "Can damage other players in Zone": false, "Can damage other player structures": false, "Can damage NPC": false, "Can damage Helicopter": false } ] }

Create epic player vs. player battles with this original arena. Arena Dome is fully compatible with Zone Manager and Event Manager. Arena Dome contains NPCs, loot, walls for players to cover their backs, and several towers for players to shoot from above.

Prevents the use of certain commands in certain regions in Config. Required : https://umod.org/plugins/zone-manager Permission : blockcommands.bypass Config : { "Console Command Settings": [ { "Command": "backpack.open", "Zone List": [ "72827873", "21026923" ] }, { "Command": "test1", "Zone List": [ "72827873", "21026923" ] }, { "Command": "test2", "Zone List": [ "72827873", "21026923" ] } ], "Chat Command Settings": [ { "Command": "backpack", "Zone List": [ "72827873", "21026923" ] }, { "Command": "test1", "Zone List": [ "72827873", "21026923" ] }, { "Command": "test2", "Zone List": [ "72827873", "21026923" ] } ] } Lang : { "NoPerm": "<color=#00ffff>This command is not available in your area!</color>" } Placeholders : {command} - player use command {displayname} - player displayname {playerId} - player id