Bug Closed · Could not replicate

Unable to play dungeons

#4118 opened by Unknown 3 years ago

Unknownreported this bug

When testing out the first dungeon that I made, I used the command /md play {dungeon} and I would load into the dungeon for a split second, I would see it, then I would return to the place of origin and the following error was sent to my console.

[19:04:52 WARN]: [MythicDungeons] Task #428679 for MythicDungeons v1.1.2-SNAPSHOT generated an exception java.lang.NullPointerException: Cannot invoke "java.util.List.iterator()" because "entities" is null at net.playavalon.mythicdungeons.dungeons.Instance.lambda$dispose$4(Instance.java:438) ~[MythicDungeons-1.1.2-SNAPSHOT.jar:?] at net.playavalon.mythicdungeons.utility.ProcessTimer.run(ProcessTimer.java:9) ~[MythicDungeons-1.1.2-SNAPSHOT.jar:?] at net.playavalon.mythicdungeons.dungeons.Instance.dispose(Instance.java:430) ~[MythicDungeons-1.1.2-SNAPSHOT.jar:?] at org.bukkit.craftbukkit.v1_19_R3.scheduler.CraftTask.run(CraftTask.java:101) ~[purpur-1.19.4.jar:git-Purpur-1985] at org.bukkit.craftbukkit.v1_19_R3.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:483) ~[purpur-1.19.4.jar:git-Purpur-1985] at net.minecraft.server.MinecraftServer.tickChildren(MinecraftServer.java:1510) ~[purpur-1.19.4.jar:git-Purpur-1985] at net.minecraft.server.dedicated.DedicatedServer.tickChildren(DedicatedServer.java:488) ~[purpur-1.19.4.jar:git-Purpur-1985] at net.minecraft.server.MinecraftServer.tickServer(MinecraftServer.java:1424) ~[purpur-1.19.4.jar:git-Purpur-1985] at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1195) ~[purpur-1.19.4.jar:git-Purpur-1985] at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:325) ~[purpur-1.19.4.jar:git-Purpur-1985] at java.lang.Thread.run(Thread.java:833) ~[?:?]

Other times, the same thing occurs in-game, but instead in the console, I get this message.

[21:19:30 INFO]: CafDad issued server command: /md play GoblinKing [21:19:31 INFO]: Preparing start region for dimension minecraft:goblinking_0 [21:19:31 INFO]: Time elapsed: 9 ms [21:19:31 INFO]: [WorldGuard] (GoblinKing_0) TNT ignition is PERMITTED. [21:19:31 INFO]: [WorldGuard] (GoblinKing_0) Lighters are PERMITTED. [21:19:31 INFO]: [WorldGuard] (GoblinKing_0) Lava fire is PERMITTED. [21:19:31 INFO]: [WorldGuard] (GoblinKing_0) Fire spread is UNRESTRICTED. [21:19:31 INFO]: [WorldGuard] Loaded configuration for world 'GoblinKing_0' [21:19:31 INFO]: [dynmap] World 'GoblinKing_0' disabled [21:19:31 INFO]: [MythicDungeons] -= Loading map GoblinKing_0 processed in 71ms. =- [21:19:31 INFO]: [MythicDungeons] -= Loading Dungeon GoblinKing processed in 214ms. =- [21:19:31 INFO]: [MythicDungeons] PLAYER FOUND [21:19:31 INFO]: [MythicDungeons] Cleaning up instance 'GoblinKing_0'... [21:19:31 WARN]: [Multiverse-Core] Hmm Multiverse does not know about this world but it's loaded in memory. [21:19:31 WARN]: [Multiverse-Core] To let Multiverse know about it, use: [21:19:31 WARN]: [Multiverse-Core] /mv import GoblinKing_0 NORMAL [21:19:31 INFO]: [ChunkHolderManager] Waiting 60s for chunk system to halt for world 'GoblinKing_0' [21:19:31 INFO]: [ChunkHolderManager] Halted chunk system for world 'GoblinKing_0' [21:19:31 INFO]: [MythicDungeons] -= Unloading world GoblinKing_0 processed in 22ms. =- [21:19:31 INFO]: [MythicDungeons] -= Cleaning up GoblinKing_0 processed in 25ms. =-

Here is my full console log for the first error, and then as you can see when I run the command again a second time, the second error code that I have shown above appears. Console Logs

Also, here is a youtube video explaining what I, or the player, sees in the game Youtube Video

Unknowncommented

Hey there. So a few things here.

  1. The error you're seeing is actually unrelated to being booted out of the dungeon.
  2. The second one (containing Multiverse's message) is harmless and should be ignored.

As for the actual issue itself... I'm at a total loss. There's no reason you should be immediately removed from the dungeon world unless you have some other plugin or configuration that would do so.

One possibility is that you have a "leave" or "finish" function that is being activated shortly after entering. Otherwise, it's got to be some other plugin sending you back to the main world.

Unknowncommented

Since there hasn't been any further information or a response to this issue in a month, I'm going to go ahead and close it. Please open it again if you have further details about the issue or if anyone else is able to replicate it.

Sign in to join the discussion.