Bug Closed · Could not replicate

Console Spam error

#3812 opened by Unknown 3 years ago

Unknownreported this bug

After updating to the latest version of mythicdungeons, when a player completes a dungeon I get the following error and it spams constantly on the console.

[15:39:01 WARN]: [MythicDungeons] Task #633419 for MythicDungeons v1.1.1 generated an exception java.lang.IllegalArgumentException: World unloaded at com.google.common.base.Preconditions.checkArgument(Preconditions.java:145) ~[guava-31.0.1-jre.jar:?] at org.bukkit.Location.getWorld(Location.java:112) ~[purpur-api-1.19.2-R0.1-SNAPSHOT.jar:?] at net.playavalon.mythicdungeons.utility.Util.getPlayersWithin(Util.java:962) ~[MythicDungeons-1.1.1.jar:?] at net.playavalon.mythicdungeons.dungeons.triggers.TriggerDistance$1.run(TriggerDistance.java:75) ~[MythicDungeons-1.1.1.jar:?] at org.bukkit.craftbukkit.v1_19_R1.scheduler.CraftTask.run(CraftTask.java:101) ~[purpur-1.19.2.jar:git-Purpur-1825] at org.bukkit.craftbukkit.v1_19_R1.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:483) ~[purpur-1.19.2.jar:git-Purpur-1825] at net.minecraft.server.MinecraftServer.tickChildren(MinecraftServer.java:1500) ~[purpur-1.19.2.jar:git-Purpur-1825] at net.minecraft.server.dedicated.DedicatedServer.tickChildren(DedicatedServer.java:486) ~[purpur-1.19.2.jar:git-Purpur-1825] at net.minecraft.server.MinecraftServer.tickServer(MinecraftServer.java:1424) ~[purpur-1.19.2.jar:git-Purpur-1825] at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1194) ~[purpur-1.19.2.jar:git-Purpur-1825] at net.minecraft.server.MinecraftServer.lambda$spin$1(MinecraftServer.java:310) ~[purpur-1.19.2.jar:git-Purpur-1825] at java.lang.Thread.run(Thread.java:833) ~[?:?]

Version: Paper 1.19.2 MythicDungeons-1.1.1 MythicMobs-5.2.1

Unknowncommented

Hello. From what I'm seeing in the code, this should only happen under incredibly specific circumstances caused by other issues... however, I have implemented a bandaid fix in the latest dev build that should hopefully eliminate the console spam and possibly allow you to identify any other error messages that might occur before this one appears.

Let me know if the new version reveals any new information about what went wrong.

Sign in to join the discussion.