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.
@SupremeSam
I was able to get it to work by restarting my server when it gave that error. also the dev said "Sometimes for meteors to work you need to /powertool meteor. powertool is an Essentials command."
It would be cool if earthquakes generated tsunamis
Hey.
This looks like an amazing plugin but... It won't work. When I am on my server and use /plugins it is in light red. When I use a command such as /meteor it says Unknown Command! Is there any requirements that Storm needs to run? Do I need to get rid of any plugins for it to work? Please let me know ASAP.
@Icynene
Actually,that fixed it. And after a server restart I was able to use the regular command again, maybe it was because this was in a newly generated world
@MrBojangles16
Try, after a meteor, logging out then back in. The update packets may have not been sent.
@therennon
I'll need a bit more information. In what way does it not work? Does it crash on startup? Do weathers not work?
@robotnikthingy
Sometimes for meteors to work you need to /powertool meteor. powertool is an Essentials command.
The command for cracks is not /cracks: its /crack. You can find development builds at our Jenkins. These are not at all supported, and I do not recommend you to use them.
@MrBojangles16
I also noticed that the meteor command does not work for me either and does nothing
and using the /cracks command gives a unknown command error
Is there any place we can download dev builds?
Does not work for me (Spigot 1.6.4) Greetings
Meteor Problem ==Hi...I'm trying to figure out how in the heck I can get the meteors to show a crater...It hurts the mobs and everything above ground, but yet it doesn't leave a crater...Can someone tell me what I have to do to get it to show the crater? Also snow doesn't show up during a blizzard. It just gets really cold and kills mobs/players.
@Farbmond
Thanks for the report.
Unfortunately, from the looks of things it does not appear to be Storm's fault: the error occurs in Bukkit code. The fact that it does occur, however, makes Storm act funky.
The error in question is a simple one to fix: someone is using the function Arrays.asList where they shouldn't be. The list returned by said function does not implement the toArray method.
It looks like you are using NoLag. I'd try removing it and trying Storm without. NoLag may be using its own chunk provider, and that error is caused by a chunk provider.
Failing that, I'm not sure what to do.
@CorruptedHelix
Thank you für your answer!
And finally I have mostly errors, if storm will be active:
@Farbmond
At the moment, you need Shield installed on your server for Storm to hook into protection plugins. Sorry about that.
Are my WorldGuard/Residence/Towny regions safe from meteors and such? A: Yes, they are.
That does not seem to be correct. Or it does not work with 1.6.4. For me, a meteor struck the middle of a protected area (world guard) and blew them a whole village. :-(
What if i only wanted a specific weather event to happen in a specific region? is there a way to accomplish this weather with this plugin or combined with any other plugin?
When is this getting updated? I got same error as with tyg.
@Icynene
I'll try that later tonight -- though I think I've tried it in the past and got the same "error" ("This version is to old") -- have you ever tinkered with MCPC? -- (It's a FTB/Bukkit hybrid)
@tgyk1337
Try out the latest Storm build. It should at least start up; a critical starting point to get it to function properly.
@Icynene
Sounds good! FT student here, so not sure when I'd be able to jump on. For now, here's some logs? :) 12:38:44 [INFO] [Storm] Enabling Storm v0.1.2B 12:38:44 [SEVERE] [Storm] Storm is not compatible with current MC version. Storm execution suspended. 12:38:45 [SEVERE] [Storm] Storm failed to start. 12:38:45 [SEVERE] java.lang.NullPointerException 12:38:45 [SEVERE] at com.github.StormTeam.Storm.Storm.onDisable(Storm.java:121) 12:38:45 [SEVERE] at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:219) 12:38:45 [SEVERE] at com.github.StormTeam.Storm.Storm.configureVersion(Storm.java:142) 12:38:45 [SEVERE] at com.github.StormTeam.Storm.Storm.onEnable(Storm.java:73) 12:38:45 [SEVERE] at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:217) 12:38:45 [SEVERE] at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:396) 12:38:45 [SEVERE] at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:381) 12:38:45 [SEVERE] at org.bukkit.craftbukkit.v1_4_R1.CraftServer.loadPlugin(CraftServer.java:298) 12:38:45 [SEVERE] at org.bukkit.craftbukkit.v1_4_R1.CraftServer.enablePlugins(CraftServer.java:280) 12:38:45 [SEVERE] at net.minecraft.server.MinecraftServer.j(MinecraftServer.java:542) 12:38:45 [SEVERE] at net.minecraft.server.MinecraftServer.e(MinecraftServer.java:508) 12:38:45 [SEVERE] at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:454) 12:38:45 [SEVERE] at ho.c(DedicatedServer.java:203) 12:38:45 [SEVERE] at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:664) 12:38:45 [SEVERE] at fy.run(ThreadMinecraftServer.java:16)
--------- Because I'm running MCPC, this happens. Storm doesn't even create a plugin folder because of this error (assumably).Thoughts?
@tgyk1337
Of course!
For the main part, the latest Storm version should run on 1.4.7. Blizzards, acid rain, thunderstorms and wildfires should work. Volcanoes, meteors and earthquakes, however, all require more intimate access to Minecraft internals to reduce lag.
Updating them from one version to another is generally just a matter of refactoring the package references.
If you wish, you can find me at #storm on the esper.net IRC network.
@CorruptedHelix
I plan on staying at 1.4.7 for a very long time. I'm not a stranger to code as well. Is there any way we'd be able to sit down with the logs and you could show me how widget a goes into slot b? :)
@tgyk1337
I don't test Storm on MCPC, only Craftbukkit and Spigot. You can try yourself by using this build, though.