Storm
Ever bored with the vanilla weather? Storm is a plugin that adds a whole new range of weather mechanics to Bukkit servers.
Features
- Acid Rain: Green rain, which damages players and animals, as well as deteriorates blocks. Turn a 'grey day' into a 'radioactive-green' day!
- Blizzards: Makes snow a real threat! Players and entities caught outside during a blizzard will experience snow acting as slow sand, limited visibility, and cold damage, so long as they are not inside or near a heating block.
- Thunder Storms: If supercharged creepers were not already a threat, how will your players react to hordes of zombie pigmen? Thunder storms are massive discharges of lightning over a short period of time, in which players will be hard-pressed to survive.
- Meteors: Fireballs trailed by explosions, burrowing in the ground, and flattening all entities in their path. Players who survive, however, can delight themselves with the ores the meteor leaves behind.
- Wildfires: We can all safely say vanilla fires are boring. To spice up the game, we've added wildfires; a naturally occurring event in which entire forests will be devoured by fire with pre-1.6B physics.
- Earthquakes: With massive rifts opening up, screens shaking, and blocks flying about, Storm earthquakes will be an experience for your players to remember. Seems to be bugging in Version2.3
- Volcanoes: Large mounds of lava spurting out of the ground, explosions and flying lava bombs. Fun, fun, fun. Seems to be bugging in Version2.3
Getting started with Storm
If you are a visual learner, this video by WoopaGaming is for you! Some information is outdated, but the gist remains the same.
You can gain some more in-depth information from this "Curse Minecraft Spotlight" on Storm, as it presents most of the features of Storm in a nice format. Thanks to Xenius01 of Curse for this one!
Storm has a command for all its weather types:
Command | Usage | Permission | Description |
---|---|---|---|
/acidrain | /<command> [world] | storm.acidrain.command | Starts acid rain in specified world. |
/blizzard | /<command> [world] | storm.blizzard.command | Starts a blizzard in specified world. |
/thunderstorm | /<command> [world] | storm.thunderstorm.command | Starts a thunder storm in specified world. |
/wildfire | /<command> [world] | storm.wildfire.command | Starts a wildfire where player is looking at. |
/meteor | /<command> [world] | storm.meteor.command | Spawns a meteor and targets the block the player is looking at. |
/volcano | /<command> [world] | storm.volcano.command | Spawns a volcano at the targeted block. |
/earthquake | /<command> [world] | storm.earthquake.command | Spawns a earthquake at the targeted block. |
/cracks | /<command> [world] | storm.earthquake.command | Spawns a crevice at the targeted block. |
And immunity permissions from their associated weathers:
Immunity | Permission | Description |
---|---|---|
Acid Rain Damage | storm.acidrain.immune | Prevents damage from acid rain. |
Blizzard Damage | storm.blizzard.immune | Prevents damage from blizzards. |
Lightning Attraction | storm.lightning.immune | Prevents extra damage from lightning & lightning attraction. |
Meteor Damage | storm.meteor.immune | Prevents damage from meteor shockwaves. |
If Storm doesn't load, first, make sure that you are running a compatible build of Storm. For example, 0.1.2 will run only on Bukkit 1.4.6, while 0.1.2 R1 will only run on 1.4.7. You can see the supported versions in the Files menu. If that doesn't work or Storm throws exceptions, leave a ticket.
When asking for support...
...please answer the following questions: they help us get back to you quicker and consequently address any issues faster.
- What Storm version are you running? Be specific.
- What server implementation are you running (usually CraftBukkit)?
- What Minecraft version are you running?
- What is the issue you are experiencing?
- Provide a traceback, if the issue is a crash and a log is available.
Any chance this works for mcpc 1.4.7? I'd really appreciate it. Would make my server "oh so much more fun" lol
@matthileo
Resource packs over servers aren't implemented in Bukkit yet. It wouldn't help.
Can I have it so, say, a blizzard will stay on until I disable it? Rather than it stopping by itself after a set amount of time?
Any chance you can send me the texture files so i can host them myself. The ones linked in the config file don't work.
When I type a command. It returns "Unknown command". Craftbukkit 1.6.2.
How do i stop the volcanoe from growing?
any easy way is to go into the "volcano" file and delete the existing volcanoes. It seems that by default volcanoes grow up to 90 blocks above the source
@GrimSpec
Unless it was added in 2.0.0, the answer is no, although it's definitely a feature to consider.
Hello,
I have this problem with Minecraft 1.6.2
Mod edit: http://hastebin.com/raw/yubasoketi
Hey all, Great plugin, liking everything so far. Questions I do have, is there a way to change what blocks a volcano converts to after the lava hardens? Is there a wiki page somewhere which list configuration file help?
Thanks in advance and keep up the good work
I'm seriously sorry for pretty much dropping off the earth. I'm back now, and I'll try to check in, but with school starting and my infrequency with Minecraft nowadays, I might not be responding to support messages.
Storm 2.0.0 is here!
Though it took time, its finally here, and better than ever!
Key changes include:
Under the hood, Storm is radically different, with almost everything refactored and cleaned. Native MC code has been contained to just a few files, allowing for faster updates.
The Github repository has also been updated with the newest code. Note that its been moved from StormTeam/Storm to the StormProject/Storm, so you'll have to change your Git to point to the new location.
Storm is now licensed under the GPLv3.
Important note: Storm will no longer obey region protection plugins unless the Shield plugin is installed.
The latter might change in the future, but for now it is the simplest solution.
Enjoy!
@infiniteoverlord
Floods, though cool and all, would greatly increase update times. Floods would require the same (non-Bukkit) mechanism to prevent lag. The same goes for any sinkhole larger than a few blocks in diameter. Tornadoes aren't really possible because there is no way to show a tornado. Yes, I could use explosions and smoke, but those are only visible when you are a few blocks away. You wouldn't be able to survive a tornado once its upon you!
@Drakortha
Yes, that should do it.
@djnazaroth
Thanks! I just have a few more things to improve!
@GamePlayEpicHD
You cannot stop an earthquake via a command like you can acid rain and such. This is because you can have multiple earthquakes at the same time. One of the planned (though not guaranteed) features for Storm 2.0 is a `stopall` command, which will stop all weather instances. For now, a server restart should do it.
How to stop earthquake , pls ans me :(
Thanks! Eagerly looking forward to the release!
If I set, say, acid rain chance to "0", will that weather never occur naturally? I'd like this plugin for our server but I'd like these weather events to only happen when I want it to using commands.
I'm wondering if you can use 1.6.2 build if that's the one you use as I would like to see the full plugin and would like to see sinkholes or per say extreme weather such as tornadoes or hurricanes if tornadoes is possible assuming not with bukkit and even more extreme tsunami or floods or even alien invasion but alien is not weather though sinkholes are caused after weather same with floods
@pacodeng
@djnazaroth
When I released v1.3.1, I was assuming that Bukkit 1.6.2 dev build would shortly be promoted to recommended status. And so I thought that I'd save time by targeting 1.6.2 builds instead. Unfortunately this was not the case, and there still hasn't been a 1.6 RB. Storm can only function on a specific MC version, due to the need to use native Minecraft code.
However, since Storm 1.2, I've been working to remove the need for Minecraft hooking. I've been mostly successful: acid rain, blizzards, thunderstorms and wildfires have been decoupled from native code. The more catalytic events: meteors and volcanoes still need said code to function without immense lag.
Therefore, I should be able to use the version checker only for the latter events, allowing the rest to function even if running on an unsupported MC version. I shall be pushing out this build shortly.
@pangys
It is v1.3.1, I just forgot to rename it to reflect this. So though it may say it is v1.3.0, it is in fact v1.3.1.
@bobthehuntedbobcat
You'd do it just as you would making a normal texture pack, excluding the textures that you are not modifying (these will be set to the default texture pack textures).
@SpudcraftMC
Odd, I believe I had ironed out that bug ages ago. If you remove the colour codes and edit some other field, can you still reproduce the error?
@bluemedley
It is semi-compatible, in the sense that Storm will load and function alongside RealWeather, but RealWeather cannot control Storm weathers. So when RealWeather spawns a rainstorm, Storm might come in and turn it into acid rain.
@KingFaris10
I'll be committing the latest source code once I release the next version, such that it is less painful to read and understand.
Do you plan on supporting the current recommended build iteration of Craftbukkit, i.e. 1.5.2-RB 1.0? I'm curious as to why you've skipped over anyways considering it has been out for months? Or is there a way to easily remove your version checker and use Storm v1.3.0 for CB 1.5.1-R0.2 instead? Thanks!
The latest version isn't v1.3.1,it is 1.3.0b.Please update as soon as possible!It often makes Spigot crash.