Hi, loved it but is it possible for disaster to not 100% target the player so you can't build house or something, like disaster can happen but in random place and not targetting player ? Ty!

Really great plugin with a developer that communicates quickly and kindly! Really excited to use the plugin moving forward.

Has way too many bugs for production use. Will cause randomly exploding creepers as well. Plugin concept is great but just contains too many bugs.

Very cool plugin. Absolutely worth it. I messed around with it to make the disasters less frequent, in my opinion more server-friendly; also, you can prevent your homes from being obliterated with worldguard and/or griefprevention.

Love it! --------------------------------------------------------------------------------

22:04:05 INFO]: WitherSkeleton55 issued server command: /deadlydisasters:disasters start earthquake 4 redwolf12341
[22:04:05 ERROR]: null
org.bukkit.command.CommandException: Unhandled exception executing command 'deadlydisasters:disasters' in plugin DeadlyDisasters v13.2
at org.bukkit.command.PluginCommand.execute(PluginCommand.java:47) ~[patched_1.17.1.jar:git-Paper-411]
at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:159) ~[patched_1.17.1.jar:git-Paper-411]
at org.bukkit.craftbukkit.v1_17_R1.CraftServer.dispatchCommand(CraftServer.java:869) ~[patched_1.17.1.jar:git-Paper-411]
at net.minecraft.server.network.ServerGamePacketListenerImpl.handleCommand(ServerGamePacketListenerImpl.java:2262) ~[app:?]
at net.minecraft.server.network.ServerGamePacketListenerImpl.handleChat(ServerGamePacketListenerImpl.java:2073) ~[app:?]
at net.minecraft.server.network.ServerGamePacketListenerImpl.handleChat(ServerGamePacketListenerImpl.java:2054) ~[app:?]
at net.minecraft.network.protocol.game.ServerboundChatPacket.handle(ServerboundChatPacket.java:46) ~[app:?]
at net.minecraft.network.protocol.game.ServerboundChatPacket.a(ServerboundChatPacket.java:6) ~[app:?]
at net.minecraft.network.protocol.PacketUtils.lambda$ensureRunningOnSameThread$1(PacketUtils.java:56) ~[app:?]
at net.minecraft.server.TickTask.run(TickTask.java:18) ~[patched_1.17.1.jar:git-Paper-411]
at net.minecraft.util.thread.BlockableEventLoop.doRunTask(BlockableEventLoop.java:149) ~[app:?]
at net.minecraft.util.thread.ReentrantBlockableEventLoop.doRunTask(ReentrantBlockableEventLoop.java:23) ~[app:?]
at net.minecraft.server.MinecraftServer.doRunTask(MinecraftServer.java:1426) ~[patched_1.17.1.jar:git-Paper-411]
at net.minecraft.server.MinecraftServer.executeTask(MinecraftServer.java:192) ~[patched_1.17.1.jar:git-Paper-411]
at net.minecraft.util.thread.BlockableEventLoop.pollTask(BlockableEventLoop.java:122) ~[app:?]
at net.minecraft.server.MinecraftServer.pollTaskInternal(MinecraftServer.java:1404) ~[patched_1.17.1.jar:git-Paper-411]
at net.minecraft.server.MinecraftServer.pollTask(MinecraftServer.java:1397) ~[patched_1.17.1.jar:git-Paper-411]
at net.minecraft.util.thread.BlockableEventLoop.runAllTasks(BlockableEventLoop.java:110) ~[app:?]
at net.minecraft.server.MinecraftServer.tickServer(MinecraftServer.java:1536) ~[patched_1.17.1.jar:git-Paper-411]
at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1282) ~[patched_1.17.1.jar:git-Paper-411]
at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:319) ~[patched_1.17.1.jar:git-Paper-411]
at java.lang.Thread.run(Thread.java:831) ~[?:?]
Caused by: java.lang.NoSuchMethodError: 'void org.bukkit.entity.Player.playSound(org.bukkit.entity.Entity, org.bukkit.Sound, float, float)'
at deadlydisasters.utils.Utils.broadcastEvent(Utils.java:177) ~[DeadlyDisastersPRO-V13.2.jar:?]
at deadlydisasters.events.DestructionDisaster.broadcastMessage(DestructionDisaster.java:47) ~[DeadlyDisastersPRO-V13.2.jar:?]
at deadlydisasters.commands.Disasters.onCommand(Disasters.java:422) ~[DeadlyDisastersPRO-V13.2.jar:?]
at org.bukkit.command.PluginCommand.execute(PluginCommand.java:45) ~[patched_1.17.1.jar:git-Paper-411]
... 21 more

This disaster system is the most perfect. But it seems that the trigger mechanism is a bit simple and rude, I hope These natural disasters can distinguish between regional occurrence and precursor occurrence. In addition, it would be better if blood moon disasters can be added. During this period, the player gains permanent weakness and the attack on a wide range of monsters is more painful.

will be always love this plugin hope you will update this love projekt <3
alway in my heart

A great plugin. Highly customizable, many features but at the same time easy to configure. A lot of details have been added to each of the disasters. Overall a highly recommendable plugin.

It is very good and also there's a lot more new disasters and has support for many other plugins. Great plugin and would recommend to others

This plug-in is very good, but I found problems with solar storms and meteorite disasters in version 1.19.2. It works normally with the command prompt, but it does not work properly

well worth your money. It isn't just the best weather plugin its also an amazing plugin for custom mobs!

There is a bug with mintimer on paperspigot1.18.2,and I adjusted the mintimer to make natural disasters less frequent, but after the adjustment, they became more frequent

After finding out how to regenerate the blocks XD i love the plugin and i definitely think its worth the money for it. I hope the creators dont give up on it cus its fun to play and run a minigame server with it!!

This dev is a great one and it's hard to come by that nowadays. He deserves to be donated to for his diligent work. - fooc

Good and fast support! Dev in discord handles all errors that users provide on their cores and fix them immediately!

THIS PLUGIN IS JUST EPIC.
YOU WON'T REGRET PURCHASING IT.
WE ARE HAVING A LOT OF FUN WITH MY FRIENDS!!!!

This plugin adds lots of fun to the server, and the author gives rapid support in Discord! You won't regret purchasing it