Bukkit

Installed the update and found it to still not be functioning properly. The weather would start and stop a second later and you couldn't see the rain or the snow.

Also can you add a duration function to set how long the duration of each catastrophe will be?

Thanks a lot, I did /meteor and destroyed my spawn...

I got the latest version and that but it wont load help!

Read it all, Icyene and I also replied to your pm.

I understand if it may not be possible for you to implement/change things to my likings and definitely can't say otherwise as I really don't know where to even begin making a plugin... but I'll still gladly suggest ways that would make things more awesome.

Feel free to add my skype and message me whenever, I usually always leave it online on 'busy' and will always reply if I'm there :p

meteor not working
it generates no errors
nothing generated in console nor any error logs
all it does is hang my server and crashes it

while i type in the command /<weather feature> <world> and it said <The Weather Feature> are not enabled in specified world or are conflicting with another weather. Whats wrong? BTW,i have essentials

Where can I find player data to remove slowness effect?

is there a way to cancel the slowness effect on players? I had some defaults watch an earthquake about a week ago and they have been stuck with slowness ever since. I just updated to your most recent build, and had them experience an earthquake again, but they still have the effect. Help? :[

@Icynene

God yes. PLEASE add this command. I've been trying to figure out a way to bypass this immunity for a while now.

Also, I have to say I've been having some pretty massive problems with your plugin in regards to a few of its features, mostly being the natural disaster events. The blizzard/electrical storm/acid rain events are actually pretty solid, although I still have a few suggestions for improving them. I have much to say, but I'll start with the problems that I have/things that I don't like and my suggestions to improve them and work my way towards a few other things:

1) Why is there no way for even an operator of a server to stop a volcano? A permission to use a command to remove the volcano from the area should be implemented. I was using worldedit to select the region and repeatedly type the command to regenerate it to its original state because of how it was literally ruining the entire area. It shouldn't endlessly grow; there should be a range of possible y-coordinate values, and x-coordinate values according to the height. Furthermore, we should be able to customize said range to our liking. The only way to delete a volcano is to delete the entry from the volcanoes.bin file, which would be satisfactory if there was a command to do it ingame as well. Typing /volcano doesn't turn it off, obviously.

2) to add on to #1, you should probably change the way volcanoes work. It would be a lot more sensible and they would look more like volcanoes if perhaps they began to form instead of just erupt in a random location. What I mean is this, for example:

-msg: "A volcano has begun forming at x y z" (possibly include an estimated and vague amount of time until eruption, such as "and will erupt in under 10 minutes!")

-a mound of stone/obsidian/whatever begins to form in what would appear to be a volcano, and gradually increase until the volcanic eruption happens

-would it be possible to add smoke to the feature? I'm unsure of how this would be done, but clouds and fog were clearly possible in minecraft, so if you'd be capable of finding a way to cause smoke to produce from the top of the volcano or simulate the appearance of it, that would truly be phenomenal.

-instead of it exploding all of the blocks around it, explode the top of the volcano and have the lava flow the way it currently does.

-as stated already, there should always be a way to stop the volcano; make it a command. The volcano should eventually cease to flow at a certain point of time elapsed, or on command by either an op or one with the permission to do so.

3) meteors aren't working properly, unless they're supposed to only occur with the command /meteor only once in every 50-100 entries. Whenever the meteor DID apparently land, all it would do was create an obscenely large crater with nothing in it. No meteor was found any attempt of mine at all, and I checked to make sure that I didn't set anything up improperly:

"# Will solid meteor spawn? Meteor Spawn: true"

With that being said, I can't really evaluate anything about meteors aside from the fact that they're not working properly. I tested them in my world, and world_nether (not world_end) for my server. I suppose a suggestion that I could make for when this event is working properly is that there should be a default range of the size of the meteor, as well as the ability to customize it just as we're able to customize the damage radius and contents of the supposed solid meteor that should appear :(

4) I have a suggestion for the blizzard event; if there is a way that you'd be able to have snow pile up on the blocks more so than the default and current little slab of snow, it would not only make much more sense but it would be very awesome addition to it. When the blizzard event would end, it would melt accordingly. Obviously a limit to the amount of snow settling would be more sensible, and if at all possible set the amount of snow to pile up to 'thin out' as it approaches the end of the biome.

5) A new idea for a weather event; windstorm. The visibility would change, the option to toggle on flying blocks, speed loss, the option to toggle player/entity damaging, and perhaps a way to have mobs/the player occasionally get 'knocked back' (just as how the enchantment on a sword for it can knock the opponent backwards several squares). Also, instead of creating a separate event for the desert biome, there should be the option of sand blocks forming (to simulate a sandstorm) which could potentially cover up entities, etc. This would be an amazing event, imo. I guess this also could be organised along with the blizzard event into one category, and the three sub-categories of the storms would be per-biome.

6) A general suggestion that applies to just about everything is to always have the option of toggling something off, and perhaps make the configuration files per world a bit more user-friendly/practical to configure and more customizable in the ways that I mentioned above + more if you can think of any (one off the top of my head is being able to choose which types of biomes the events can occur in). The plugin itself was a great idea, but there's simply so much that could be done to make it even more fun :)

Hope you like my suggestions, I only seek to help you improve it for not only my own use, but for anyone else that tries this out as well.

@Icynene

Look forward to it. Thank you.

Seeing a few odd balls things in the server.log related to Storm.

2013-02-04 03:16:26 [SEVERE] Storm encountered an error: java.lang.IndexOutOfBoundsException: Index: 39, Size: 39 at java.util.ArrayList.rangeCheck(ArrayList.java:604) at java.util.ArrayList.get(ArrayList.java:382) at com.github.StormTeam.Storm.Volcano.Tasks.LifeTask.run(LifeTask.java:19) at org.bukkit.craftbukkit.v1_4_R1.scheduler.CraftTask.run(CraftTask.java:53) at org.bukkit.craftbukkit.v1_4_R1.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:344) at net.minecraft.server.v1_4_R1.MinecraftServer.r(MinecraftServer.java:521) at net.minecraft.server.v1_4_R1.DedicatedServer.r(DedicatedServer.java:224) at net.minecraft.server.v1_4_R1.MinecraftServer.q(MinecraftServer.java:485) at net.minecraft.server.v1_4_R1.MinecraftServer.run(MinecraftServer.java:420) at net.minecraft.server.v1_4_R1.ThreadServerApplication.run(SourceFile:849)

Message from Log File System Details Details: Minecraft Version: 1.4.7 Operating System: Linux (amd64) version 2.6.32-279.19.1.el6.x86_64 Java Version: 1.7.0_11, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 4309908032 bytes (4110 MB) / 6390546432 bytes (6094 MB) up to 6390546432 bytes (6094 MB) JVM Flags: 2 total; -Xms6G -Xmx6G AABB Pool Size: 267 (14952 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used Suspicious classes: $Proxy3, $Proxy5[com.avaje.ebean.EbeanServer], [com.avaje.ebean.config.ServerConfig], [com.avaje.ebean.config.dbplatform.DatabasePlatform, SQLitePlatform], [com.google.common.base.Predicate, Function, Joiner,$ IntCache: cache: 0, tcache: 0, allocated: 1, tallocated: 63 CraftBukkit Information: Running: CraftBukkit version git-Spigot-478 (MC: 1.4.7) (Implementing API version 1.4.7-R1.1-SNAPSHOT) true Plugins: { MultiWorld v4.5.0 multiworld.MultiWorldPlugin [ferrybig], CityWorld v2.03 me.daddychurchill.CityWorld.CityWorld [DaddyChurchill], Sonic Screwdriver v0.4 com.xern.jogy34.sonicscrewdriver.general.SonicScrewdriverMain [Jogy34$ Warnings: DEFAULT Threads: { TIMED_WAITING Timer-0: [java.lang.Object.wait(Native Method), java.util.TimerThread.mainLoop(Timer.java:552), java.util.TimerThread.run(Timer.java:505)], TIMED_WAITING com.mchange.v2.async.ThreadPoolAsynchronousRunner$Pool$ Recent tasks from 684615-684645{Prism:me.botsko.prism.actionlibs.ActionRecorder@684647,Prism:me.botsko.prism.actionlibs.ActionRecorder@684650,Prism:me.botsko.prism.actionlibs.ActionRecorder@684653,Prism:me.botsko.prism.actionlibs.Act$

@Icynene Answers it but unfortunately doesn't fix the problem. =/ Is there anyway we can turn it off as ... OPs can just do /god and be immune, it seems redundant to give them immunity automatically.