-
Notifications
You must be signed in to change notification settings - Fork 65
Description
What happened?
[org.dimdev.dimdoors.block.entity.RiftBlockEntity/]: Teleporting failed with the following exception:
java.lang.NullPointerException: Cannot invoke "org.dimdev.dimdoors.block.entity.RiftBlockEntity.getProperties()" because "toBe" is null
at org.dimdev.dimdoors.rift.targets.RandomTarget.linkRifts(RandomTarget.java:200) ~[dimdoors-5.4.4-1.20.1-forge.jar%23374!/:?]
at org.dimdev.dimdoors.rift.targets.RandomTarget.receiveOther(RandomTarget.java:177) ~[dimdoors-5.4.4-1.20.1-forge.jar%23374!/:?]
at org.dimdev.dimdoors.api.rift.target.Target.as(Target.java:16) ~[dimdoors-5.4.4-1.20.1-forge.jar%23374!/:?]
at org.dimdev.dimdoors.block.entity.RiftBlockEntity.teleport(RiftBlockEntity.java:210) ~[dimdoors-5.4.4-1.20.1-forge.jar%23374!/:?]
at org.dimdev.dimdoors.block.entity.EntranceRiftBlockEntity.innerTeleport(EntranceRiftBlockEntity.java:89) ~[dimdoors-5.4.4-1.20.1-forge.jar%23374!/:?]
at org.dimdev.dimdoors.block.entity.EntranceRiftBlockEntity.teleport(EntranceRiftBlockEntity.java:85) ~[dimdoors-5.4.4-1.20.1-forge.jar%23374!/:?]
at org.dimdev.dimdoors.block.door.DimensionalDoorBlock.onCollision(DimensionalDoorBlock.java:129) ~[dimdoors-5.4.4-1.20.1-forge.jar%23374!/:?]
at org.dimdev.dimdoors.block.door.DimensionalDoorBlock.onAfterMovePlayerCollision(DimensionalDoorBlock.java:74) ~[dimdoors-5.4.4-1.20.1-forge.jar%23374!/:?]
at net.minecraft.server.network.ServerGamePacketListenerImpl.handler$dof000$dimdoors$checkBlockCollision(ServerGamePacketListenerImpl.java:3823) ~[client-1.20.1-20230612.114412-srg.jar%23473!/:?]
at net.minecraft.server.network.ServerGamePacketListenerImpl.m_7185_(ServerGamePacketListenerImpl.java:947) ~[client-1.20.1-20230612.114412-srg.jar%23473!/:?]
at net.minecraft.network.protocol.game.ServerboundMovePlayerPacket.m_5797_(ServerboundMovePlayerPacket.java:114) ~[client-1.20.1-20230612.114412-srg.jar%23473!/:?]
at net.minecraft.network.protocol.game.ServerboundMovePlayerPacket$PosRot.m_5797_(ServerboundMovePlayerPacket.java:16) ~[client-1.20.1-20230612.114412-srg.jar%23473!/:?]
at net.minecraft.network.protocol.PacketUtils.m_263899_(PacketUtils.java:22) ~[client-1.20.1-20230612.114412-srg.jar%23473!/:?]
at net.minecraft.server.TickTask.run(TickTask.java:18) ~[client-1.20.1-20230612.114412-srg.jar%23473!/:?]
at net.minecraft.util.thread.BlockableEventLoop.m_6367_(BlockableEventLoop.java:156) ~[client-1.20.1-20230612.114412-srg.jar%23473!/:?]
at net.minecraft.util.thread.ReentrantBlockableEventLoop.m_6367_(ReentrantBlockableEventLoop.java:23) ~[client-1.20.1-20230612.114412-srg.jar%23473!/:?]
at net.minecraft.server.MinecraftServer.m_6367_(MinecraftServer.java:770) ~[client-1.20.1-20230612.114412-srg.jar%23473!/:?]
at net.minecraft.server.MinecraftServer.m_6367_(MinecraftServer.java:161) ~[client-1.20.1-20230612.114412-srg.jar%23473!/:?]
at net.minecraft.util.thread.BlockableEventLoop.m_7245_(BlockableEventLoop.java:130) ~[client-1.20.1-20230612.114412-srg.jar%23473!/:?]
at net.minecraft.server.MinecraftServer.m_129961_(MinecraftServer.java:5851) ~[client-1.20.1-20230612.114412-srg.jar%23473!/:?]
at net.minecraft.server.MinecraftServer.m_7245_(MinecraftServer.java:747) ~[client-1.20.1-20230612.114412-srg.jar%23473!/:?]
at net.minecraft.util.thread.BlockableEventLoop.m_18699_(BlockableEventLoop.java:115) ~[client-1.20.1-20230612.114412-srg.jar%23473!/:?]
at net.minecraft.server.MinecraftServer.m_130012_(MinecraftServer.java:732) ~[client-1.20.1-20230612.114412-srg.jar%23473!/:?]
at net.minecraft.server.MinecraftServer.m_130011_(MinecraftServer.java:665) ~[client-1.20.1-20230612.114412-srg.jar%23473!/:?]
at net.minecraft.server.MinecraftServer.m_206580_(MinecraftServer.java:251) ~[client-1.20.1-20230612.114412-srg.jar%23473!/:?]
at java.lang.Thread.run(Thread.java:842) ~[?:?]
[10Juni2025 22:33:52.664] [Render thread/INFO] [net.minecraft.client.gui.components.ChatComponent/]: [System] [CHAT] Something went wrong while trying to teleport you, please report this bug.
Mod Version
5.4.4
What versions of Minecraft does this issue happen on?
No response
Log
1.20.1