You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Walking through a dimensional door caused this error. Not sure if another mod has affected Dimensional Doors in any way since it's a very small mod list, but the log output only references Dimensional Doors.
Mod Version
5.4.1
What versions of Minecraft does this issue happen on?
No response
Log
[18:31:13] [Server thread/INFO]: Generating pocket from template dimdoors:dungeon/ruins_target_practise at location BlockPos{x=-288, y=0, z=240}
[18:31:13] [Server thread/ERROR]: Teleporting failed with the following exception:
java.lang.ArrayIndexOutOfBoundsException: Index 0 out of bounds for length 0
at org.dimdev.dimdoors.util.schematic.RelativeBlockSample.<init>(RelativeBlockSample.java:80)~[dimdoors-5.4.1-1.20.1-forge.jar%23307!/:?]
at org.dimdev.dimdoors.util.schematic.Schematic.getBlockSample(Schematic.java:155) ~[dimdoors-5.4.1-1.20.1-forge.jar%23307!/:?]
at org.dimdev.dimdoors.util.schematic.SchematicPlacer.getAbsoluteRifts(SchematicPlacer.java:45) ~[dimdoors-5.4.1-1.20.1-forge.jar%23307!/:?]
at org.dimdev.dimdoors.pockets.PocketTemplate.getAbsoluteRifts(PocketTemplate.java:74) ~[dimdoors-5.4.1-1.20.1-forge.jar%23307!/:?]
at org.dimdev.dimdoors.pockets.generator.SchematicGenerator.prepareAndPlacePocket(SchematicGenerator.java:149) ~[dimdoors-5.4.1-1.20.1-forge.jar%23307!/:?]
at org.dimdev.dimdoors.pockets.virtual.reference.PocketGeneratorReference.prepareAndPlacePocket(PocketGeneratorReference.java:157) ~[dimdoors-5.4.1-1.20.1-forge.jar%23307!/:?]
at org.dimdev.dimdoors.pockets.PocketGenerator.generatePocketV2(PocketGenerator.java:59) ~[dimdoors-5.4.1-1.20.1-forge.jar%23307!/:?]
at org.dimdev.dimdoors.pockets.PocketGenerator.generateFromPocketGroupV2(PocketGenerator.java:49) ~[dimdoors-5.4.1-1.20.1-forge.jar%23307!/:?]
at org.dimdev.dimdoors.pockets.PocketGenerator.generateDungeonPocketV2(PocketGenerator.java:63) ~[dimdoors-5.4.1-1.20.1-forge.jar%23307!/:?]
at org.dimdev.dimdoors.rift.targets.RandomTarget.generatePocket(RandomTarget.java:192) ~[dimdoors-5.4.1-1.20.1-forge.jar%23307!/:?]
at org.dimdev.dimdoors.rift.targets.RandomTarget.receiveOther(RandomTarget.java:173) ~[dimdoors-5.4.1-1.20.1-forge.jar%23307!/:?]
at org.dimdev.dimdoors.api.rift.target.Target.as(Target.java:16) ~[dimdoors-5.4.1-1.20.1-forge.jar%23307!/:?]
at org.dimdev.dimdoors.block.entity.RiftBlockEntity.teleport(RiftBlockEntity.java:210) ~[dimdoors-5.4.1-1.20.1-forge.jar%23307!/:?]
at org.dimdev.dimdoors.block.entity.EntranceRiftBlockEntity.innerTeleport(EntranceRiftBlockEntity.java:89) ~[dimdoors-5.4.1-1.20.1-forge.jar%23307!/:?]
at org.dimdev.dimdoors.block.entity.EntranceRiftBlockEntity.teleport(EntranceRiftBlockEntity.java:85) ~[dimdoors-5.4.1-1.20.1-forge.jar%23307!/:?]
at org.dimdev.dimdoors.block.DimensionalPortalBlock.m_7892_(DimensionalPortalBlock.java:54) ~[dimdoors-5.4.1-1.20.1-forge.jar%23307!/:?]
at net.minecraft.world.level.block.state.BlockBehaviour$BlockStateBase.m_60682_(BlockBehaviour.java:766) ~[client-1.20.1-20230612.114412-srg.jar%23394!/:?]
at net.minecraft.world.entity.Entity.m_20101_(Entity.java:998) ~[client-1.20.1-20230612.114412-srg.jar%23394!/:?]
at net.minecraft.world.entity.Entity.m_146872_(Entity.java:773) ~[client-1.20.1-20230612.114412-srg.jar%23394!/:?]
at net.minecraft.world.entity.Entity.m_6478_(Entity.java:718) ~[client-1.20.1-20230612.114412-srg.jar%23394!/:?]
at net.minecraft.server.network.ServerGamePacketListenerImpl.m_7185_(ServerGamePacketListenerImpl.java:909) ~[client-1.20.1-20230612.114412-srg.jar%23394!/:?]
at net.minecraft.network.protocol.game.ServerboundMovePlayerPacket.m_5797_(ServerboundMovePlayerPacket.java:114) ~[client-1.20.1-20230612.114412-srg.jar%23394!/:?]
at net.minecraft.network.protocol.game.ServerboundMovePlayerPacket$Pos.m_5797_(ServerboundMovePlayerPacket.java:42) ~[client-1.20.1-20230612.114412-srg.jar%23394!/:?]
at net.minecraft.network.protocol.PacketUtils.m_263899_(PacketUtils.java:22) ~[client-1.20.1-20230612.114412-srg.jar%23394!/:?]
at net.minecraft.server.TickTask.run(TickTask.java:18) ~[client-1.20.1-20230612.114412-srg.jar%23394!/:?]
at net.minecraft.util.thread.BlockableEventLoop.m_6367_(BlockableEventLoop.java:156) ~[client-1.20.1-20230612.114412-srg.jar%23394!/:?]
at net.minecraft.util.thread.ReentrantBlockableEventLoop.m_6367_(ReentrantBlockableEventLoop.java:23) ~[client-1.20.1-20230612.114412-srg.jar%23394!/:?]
at net.minecraft.server.MinecraftServer.m_6367_(MinecraftServer.java:770) ~[client-1.20.1-20230612.114412-srg.jar%23394!/:?]
at net.minecraft.server.MinecraftServer.m_6367_(MinecraftServer.java:161) ~[client-1.20.1-20230612.114412-srg.jar%23394!/:?]
at net.minecraft.util.thread.BlockableEventLoop.m_7245_(BlockableEventLoop.java:130) ~[client-1.20.1-20230612.114412-srg.jar%23394!/:?]
at net.minecraft.server.MinecraftServer.m_129961_(MinecraftServer.java:753) ~[client-1.20.1-20230612.114412-srg.jar%23394!/:?]
at net.minecraft.server.MinecraftServer.m_7245_(MinecraftServer.java:747) ~[client-1.20.1-20230612.114412-srg.jar%23394!/:?]
at net.minecraft.util.thread.BlockableEventLoop.m_18701_(BlockableEventLoop.java:139) ~[client-1.20.1-20230612.114412-srg.jar%23394!/:?]
at net.minecraft.server.MinecraftServer.m_130012_(MinecraftServer.java:733) ~[client-1.20.1-20230612.114412-srg.jar%23394!/:?]
at net.minecraft.server.MinecraftServer.m_130011_(MinecraftServer.java:665) ~[client-1.20.1-20230612.114412-srg.jar%23394!/:?]
at net.minecraft.server.MinecraftServer.m_206580_(MinecraftServer.java:251) ~[client-1.20.1-20230612.114412-srg.jar%23394!/:?]
at java.lang.Thread.run(Thread.java:840) ~[?:?]
The text was updated successfully, but these errors were encountered:
What happened?
Walking through a dimensional door caused this error. Not sure if another mod has affected Dimensional Doors in any way since it's a very small mod list, but the log output only references Dimensional Doors.
Mod Version
5.4.1
What versions of Minecraft does this issue happen on?
No response
Log
The text was updated successfully, but these errors were encountered: