Search the Community

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 - /wsetup (permission for use - weather. Use) FEATURES: Customize the weather the way you want it Setup your config with UI Weather presets (defaults included) Smooth transition between presets Set day or night chat command [setday | setnight] Commands: /wsetup - open setup UI /setday - set day /setnight - set night Q&A: Q: How can i now which one is active? A: In the UI you can see all presets and when you open it you can see the current active preset (its name will be green) (if the preset is just selected, it will be white) Q: What happens when the current preset is over? A: New one will randomly start. Config: { "Auto reload [If you change the config and save the file the plugin will reload itself]": true, "Day length [minutes]": 30, "Night length [minutes]": 30, "Use time control": true, "Presets": [ { "Name": "Drunk", "Duration [seconds]": 50, "Chance [0 - 100%": 1, "Wind": -1.0, "Rain": -1.0, "Thunder": -1.0, "Rainbow": -1.0, "Ocean": -1.0, "Atmosphere rayleigh": 3.0, "Atmosphere mie": 3.0, "Atmosphere contrast": 2.0, "Atmosphere directionality": 2.0, "Atmosphere fogginess": 3.0, "Atmosphere brightness": -1.0, "Clouds size": -1.0, "Clouds opacity": 0.0, "Clouds coverage": -1.0, "Clouds sharpness": -1.0, "Clouds coloring": -1.0, "Clouds attenuation": -1.0, "Clouds saturation": -1.0, "Clouds scattering": -1.0, "Clouds brightness": -1.0 }, { "Name": "Clear", "Duration [seconds]": 14400, "Chance [0 - 100%": 20, "Wind": 0.0, "Rain": 0.0, "Thunder": 0.0, "Rainbow": 0.0, "Ocean": 3.0, "Atmosphere rayleigh": 1.0, "Atmosphere mie": 1.0, "Atmosphere contrast": 1.2, "Atmosphere directionality": 0.9, "Atmosphere fogginess": 0.0, "Atmosphere brightness": 1.0, "Clouds size": 2.0, "Clouds opacity": 1.0, "Clouds coverage": 0.0, "Clouds sharpness": 0.0, "Clouds coloring": 1.0, "Clouds attenuation": 0.15, "Clouds saturation": 1.0, "Clouds scattering": 1.0, "Clouds brightness": 1.0 }, { "Name": "Dust", "Duration [seconds]": 14400, "Chance [0 - 100%": 20, "Wind": 0.0, "Rain": 0.0, "Thunder": 0.0, "Rainbow": 0.0, "Ocean": 3.5, "Atmosphere rayleigh": 2.0, "Atmosphere mie": 4.0, "Atmosphere contrast": 1.25, "Atmosphere directionality": 0.75, "Atmosphere fogginess": 0.3, "Atmosphere brightness": 0.9, "Clouds size": 2.0, "Clouds opacity": 0.25, "Clouds coverage": 0.0, "Clouds sharpness": 0.0, "Clouds coloring": 1.0, "Clouds attenuation": 0.25, "Clouds saturation": 1.0, "Clouds scattering": 1.0, "Clouds brightness": 1.0 }, { "Name": "Fog", "Duration [seconds]": 14400, "Chance [0 - 100%": 20, "Wind": 0.0, "Rain": 0.0, "Thunder": 0.0, "Rainbow": 0.0, "Ocean": 4.5, "Atmosphere rayleigh": 1.0, "Atmosphere mie": 1.0, "Atmosphere contrast": 1.0, "Atmosphere directionality": 0.2, "Atmosphere fogginess": 0.9, "Atmosphere brightness": 0.5, "Clouds size": 2.0, "Clouds opacity": 0.0, "Clouds coverage": 0.0, "Clouds sharpness": 0.1, "Clouds coloring": 0.15, "Clouds attenuation": 0.15, "Clouds saturation": 0.8, "Clouds scattering": 100.0, "Clouds brightness": 0.8 }, { "Name": "Overcast", "Duration [seconds]": 14400, "Chance [0 - 100%": 20, "Wind": 0.0, "Rain": 0.0, "Thunder": 0.0, "Rainbow": 0.0, "Ocean": 3.5, "Atmosphere rayleigh": 0.2, "Atmosphere mie": 5.0, "Atmosphere contrast": 1.5, "Atmosphere directionality": 0.75, "Atmosphere fogginess": 0.8, "Atmosphere brightness": 0.9, "Clouds size": 2.0, "Clouds opacity": 1.0, "Clouds coverage": 1.0, "Clouds sharpness": 0.05, "Clouds coloring": 0.15, "Clouds attenuation": 0.15, "Clouds saturation": 0.8, "Clouds scattering": 20.0, "Clouds brightness": 1.0 }, { "Name": "RainMild", "Duration [seconds]": 14400, "Chance [0 - 100%": 20, "Wind": 1.0, "Rain": 0.2, "Thunder": 0.0, "Rainbow": 0.0, "Ocean": 4.7, "Atmosphere rayleigh": 1.0, "Atmosphere mie": 1.0, "Atmosphere contrast": 1.3, "Atmosphere directionality": 0.9, "Atmosphere fogginess": 0.2, "Atmosphere brightness": 1.0, "Clouds size": 1.0, "Clouds opacity": 1.0, "Clouds coverage": 0.4, "Clouds sharpness": 0.0, "Clouds coloring": 0.8, "Clouds attenuation": 0.05, "Clouds saturation": 0.8, "Clouds scattering": 0.4, "Clouds brightness": 1.0 }, { "Name": "RainHeavy", "Duration [seconds]": 14400, "Chance [0 - 100%": 20, "Wind": 1.0, "Rain": 1.0, "Thunder": 0.0, "Rainbow": 0.0, "Ocean": 7.4, "Atmosphere rayleigh": 0.2, "Atmosphere mie": 5.0, "Atmosphere contrast": 1.5, "Atmosphere directionality": 0.75, "Atmosphere fogginess": 0.7, "Atmosphere brightness": 0.8, "Clouds size": 2.0, "Clouds opacity": 1.0, "Clouds coverage": 0.9, "Clouds sharpness": 0.25, "Clouds coloring": 0.15, "Clouds attenuation": 0.15, "Clouds saturation": 0.8, "Clouds scattering": 5.0, "Clouds brightness": 1.0 }, { "Name": "Storm", "Duration [seconds]": 14400, "Chance [0 - 100%": 20, "Wind": 1.0, "Rain": 1.0, "Thunder": 1.0, "Rainbow": 0.0, "Ocean": 8.0, "Atmosphere rayleigh": 1.0, "Atmosphere mie": 3.0, "Atmosphere contrast": 1.3, "Atmosphere directionality": 0.75, "Atmosphere fogginess": 0.95, "Atmosphere brightness": 0.8, "Clouds size": 2.0, "Clouds opacity": 1.0, "Clouds coverage": 1.0, "Clouds sharpness": 0.4, "Clouds coloring": 0.15, "Clouds attenuation": 0.15, "Clouds saturation": 0.8, "Clouds scattering": 5.0, "Clouds brightness": 1.0 } ] }

Feel like your players have it too easy? Want to make your server more challenging for even the most unemployed zergs? Freak Radiation automatically creates radiation storms in your world; and they crawl around the world, sparing nobody the danger of being irradiated. By default they're visible as an orb moving through the world, but if you really want that Dark Souls experience you can make them fully invisible turning radiation storms into a scary, silent killer. You have total control with a vast array of configuration options; the number of storms, how big they are, their speed, damage, lifespan and respawn duration. You're able to manually add exclusion zones which redirect storms when they get too close for comfort. Performance is important with a plugin like this, so we've allowed you to configure performance to your servers capabilities. What are you waiting for? It's time to make radiation truly terrifying. Preview <I/O> Getting Started <I/O> Permission User is required to be admin in order to configure exclusion zones User is required to be admin in order to teleport to radiation zones Installation Place .cs in Plugins Folder Configure config Once Installed, zones should start spawning according to the config Commands /freakradiation exclude uniquename/id radius - Create new exclusion zone, which prevents and redirects radiation storms. /teleport countNumb - Teleports admins to radiation zone centers, if given a valid number. if 5 storms exist, the teleport range is 0-4. /teleport 1 Config Explained { "General settings": { "Is enabled": true, // if false, plugin will do nothing "Minutes until start": 5 //Delay before storms start. Must exceed an average of 1 minute on my server. If Obj err on serverinit, increase }, "Radiation settings": { "Minimum zones at any time": 0, //min amount of storms per spawn, if zero, it is possible that on respawn, no radiation storm will apear "Maximum zones at any time": 5, //max possible amount of storms per spawn "Minimum zone duration (Minutes)": 10, //min duration of storms natural lifespan "Maximum zone duration (Minutes)": 45, //max duration of storms natural lifespan "Minimum respawn duration (Minutes)": 10, //min duration it can take for storms to respawn after lifespan end "Maximum respawn duration (Minutes)": 45, //max duration it can take for storms to respawn after lifespan end "Minimum zone size": 20.0, //min zone radius, cannot spawn smaller than this | NOTE: if the same as max, will only spawn that size "Maximum zone size": 70.0, //max zone radius, cannot spawn larger than this | NOTE: if the same as min, will only spawn that size "Minimum radiation strength": 0.3, //min possible radiation strength, default minimum | NOTE: if the same as max, will only spawn that strength "Maximum radiation strength": 10.0, //max possible radiation strength, default max | NOTE: if the same as min, will only spawn that strength "Minimum radiation speed": 0.15, //min possible speed zone can move. If zero, can be still. | NOTE: if the same as max, will only spawn that speed "Maximum radiation speed": 0.5//max possible speed zone can move. | NOTE: if the same as min, will only spawn that speed }, "Chat settings": { "Messages enabled": true, //if false, plugin will not announce storms or storm subsided "Chat tag enabled ": true, //if false, Freak Radiation prefix will not show in chat announcements "Chat tag color": "4A95CC", //default tag colour of Freak Radiation Prefix "Chat message color": "C57039" //default message colour of Freak Radiation Messages }, "Performance settings": { "Show radiation domes (may impact performance)": true, //if false, radiation will be invisible "Show exclusion domes (may impact performance)": true, //if false, exclusion zones will be invisible "Storms redirect storms (may impact performance)": false, //if true, storms will redirect other storms "Exclusion dome layers": 10, //more layers, more performance hit, darker domes "Radiation dome layers": 10, //more layers, more performance hit, darker domes "Max possible spawn points": 1000, //Max amount of possible spawn points collected. Leave above atleast 100 "Max spawn point creation attempts (10000 attempts results in around 1000 valid points)": 10000 // Max possible creation attempts }, "Version": { "Major": 1, //Version, if diff from plugin version, will generate default "Minor": 0, "Patch": 0 } } Exclusion Data Explained "airfield": { // name "Position": { // position "x": -1142.34265, "y": 26.7350559, "z": -1.583567 }, "Radius": 150.0 //radius }, //if changed reload plugin <I/O> Contacting Us <I/O> You can contact us at Our discord: discord.gg/TTb3f3XEhq