[Bug]: Unable to TP to pocket dimension 1.20.1

[mutantalpaca]

What happened?

when trying to enter my own pocket dimension it just gave me the message "something went wrong trying to teleport you please report this bug" I do have other mods (about 200) installed and can list them if needed but I cannot figure out which mod would be conflicting with it as its its very inconsistent with which mods its crashing with, sometimes when i uninstall my other mods it simply wont tp me and gives me this msg and I can keep playing, sometimes it works and other times it crashes my game when going through a door I placed.

Mod Version

5.4.4

What versions of Minecraft does this issue happen on?

No response

Log

[01:26:29] [Server thread/ERROR]:Teleporting failed with the following exception:
java.lang.NullPointerException: Cannot invoke "org.dimdev.dimdoors.api.rift.target.EntityTarget.receiveEntity(net.minecraft.world.entity.Entity, net.minecraft.world.phys.Vec3, net.minecraft.core.Rotations, net.minecraft.world.phys.Vec3, org.dimdev.dimdoors.api.util.Location)" because "blockEntity" is null
	at org.dimdev.dimdoors.rift.targets.PrivatePocketTarget.processEntity(PrivatePocketTarget.java:85) ~[dimdoors-5.4.4-1.20.1-forge.jar%23379!/:?]
	at org.dimdev.dimdoors.rift.targets.PrivatePocketTarget.receiveEntity(PrivatePocketTarget.java:63) ~[dimdoors-5.4.4-1.20.1-forge.jar%23379!/:?]
	at org.dimdev.dimdoors.block.entity.RiftBlockEntity.teleport(RiftBlockEntity.java:222) ~[dimdoors-5.4.4-1.20.1-forge.jar%23379!/:?]
	at org.dimdev.dimdoors.block.entity.EntranceRiftBlockEntity.innerTeleport(EntranceRiftBlockEntity.java:89) ~[dimdoors-5.4.4-1.20.1-forge.jar%23379!/:?]
	at org.dimdev.dimdoors.block.entity.EntranceRiftBlockEntity.teleport(EntranceRiftBlockEntity.java:85) ~[dimdoors-5.4.4-1.20.1-forge.jar%23379!/:?]
	at org.dimdev.dimdoors.block.door.DimensionalDoorBlock.onCollision(DimensionalDoorBlock.java:129) ~[dimdoors-5.4.4-1.20.1-forge.jar%23379!/:?]
	at org.dimdev.dimdoors.block.door.DimensionalDoorBlock.onAfterMovePlayerCollision(DimensionalDoorBlock.java:74) ~[dimdoors-5.4.4-1.20.1-forge.jar%23379!/:?]
	at net.minecraft.server.network.ServerGamePacketListenerImpl.handler$dhj000$checkBlockCollision(ServerGamePacketListenerImpl.java:6329) ~[client-1.20.1-20230612.114412-srg.jar%23506!/:?]
	at net.minecraft.server.network.ServerGamePacketListenerImpl.m_7185_(ServerGamePacketListenerImpl.java:947) ~[client-1.20.1-20230612.114412-srg.jar%23506!/:?]
	at net.minecraft.network.protocol.game.ServerboundMovePlayerPacket.m_5797_(ServerboundMovePlayerPacket.java:114) ~[client-1.20.1-20230612.114412-srg.jar%23506!/:?]
	at net.minecraft.network.protocol.game.ServerboundMovePlayerPacket$Pos.m_5797_(ServerboundMovePlayerPacket.java:42) ~[client-1.20.1-20230612.114412-srg.jar%23506!/:?]
	at net.minecraft.network.protocol.PacketUtils.m_263899_(PacketUtils.java:22) ~[client-1.20.1-20230612.114412-srg.jar%23506!/:?]
	at net.minecraft.server.TickTask.run(TickTask.java:18) ~[client-1.20.1-20230612.114412-srg.jar%23506!/:?]
	at net.minecraft.util.thread.BlockableEventLoop.m_6367_(BlockableEventLoop.java:156) ~[client-1.20.1-20230612.114412-srg.jar%23506!/:?]
	at net.minecraft.util.thread.ReentrantBlockableEventLoop.m_6367_(ReentrantBlockableEventLoop.java:23) ~[client-1.20.1-20230612.114412-srg.jar%23506!/:?]
	at net.minecraft.server.MinecraftServer.m_6367_(MinecraftServer.java:770) ~[client-1.20.1-20230612.114412-srg.jar%23506!/:?]
	at net.minecraft.server.MinecraftServer.m_6367_(MinecraftServer.java:161) ~[client-1.20.1-20230612.114412-srg.jar%23506!/:?]
	at net.minecraft.util.thread.BlockableEventLoop.m_7245_(BlockableEventLoop.java:130) ~[client-1.20.1-20230612.114412-srg.jar%23506!/:?]
	at net.minecraft.server.MinecraftServer.m_129961_(MinecraftServer.java:753) ~[client-1.20.1-20230612.114412-srg.jar%23506!/:?]
	at net.minecraft.server.MinecraftServer.m_7245_(MinecraftServer.java:747) ~[client-1.20.1-20230612.114412-srg.jar%23506!/:?]
	at net.minecraft.util.thread.BlockableEventLoop.m_18701_(BlockableEventLoop.java:139) ~[client-1.20.1-20230612.114412-srg.jar%23506!/:?]
	at net.minecraft.server.MinecraftServer.mixinextras$bridge$m_18701_$261(MinecraftServer.java) ~[client-1.20.1-20230612.114412-srg.jar%23506!/:?]
	at net.minecraft.server.MinecraftServer.wrapOperation$zhp000$managedBlock(MinecraftServer.java:1856) ~[client-1.20.1-20230612.114412-srg.jar%23506!/:?]
	at net.minecraft.server.MinecraftServer.m_130012_(MinecraftServer.java:733) ~[client-1.20.1-20230612.114412-srg.jar%23506!/:?]
	at net.minecraft.server.MinecraftServer.m_130011_(MinecraftServer.java:665) ~[client-1.20.1-20230612.114412-srg.jar%23506!/:?]
	at net.minecraft.server.MinecraftServer.m_206580_(MinecraftServer.java:251) ~[client-1.20.1-20230612.114412-srg.jar%23506!/:?]
	at java.lang.Thread.run(Unknown Source) ~[?:?]

[caydenrm]

I've done some digging on this because I had a similar issue, also 5.4.4 on MC 1.20.1

I crashed the game (hey don't use a black hole spell in a personal pocket, the blocks that aren't meant to be destroyed get unhappy)

-and we decided to just erase the regions/poi files because very little had been done up to that point.

Started having the "Something went wrong..." error

What I wanted to find and could not is where on earth the RiftRegistry records the nbt player-specific data for where their personal pocket is intended to be. Something in the issue is that using the quartz door in either the overworld or the pocket dimension points it toward your last door exited in the opposite dimension and when a door is deleted it freaks out because the reference door no longer exists OR if you've been troubleshooting, sometimes there are multiple registered last doors you used and it doesn't know which one to send you to.

That said, I did find at least a fix which was the following:

1. Go into creative mode

2. Get rid of all quartz doors in the overworld you've used. This includes the item and the placed block. (optionally close all those rifts immediately, yike)

3. Place a new quartz door down where desired.

4. Use /dimteleport or /execute command to teleport into the pocket dimension, find using a map mod or some other method where your pocket was if you haven't deleted it OR use /fill to make a platform you're willing to use as your pocket dimension OR (what I did) use a Structure block/equivalent to in a new world save the structure that normally generates (the big white cube) and then load it into your broken world's pocket dim.

5. If your 4. method involved copying a door, delete that door, close its rift.

6. Place a new quartz door, open it, use it.

7. If 6 fails or crashes your game, start from 2 again, using NEW doors only, but this time try to use the overworld new quartz door first. It will likely send you to where your old door used to be.

8. Exit the pocket dimension through a NEW quartz door where you want your pocket to be linked at.

9. Whether after 6 or 8, your door and any new doors after SHOULD link to the new exit you've created and the new exit should take you back to your last entered overworld quartz door.

I never did find the RiftRegistry save data but at least this functionally resolves the problem, albeit not through the save data side - I haven't played long enough post-fix to know if there are trickle down problems due to that but worst case, don't put stuff you super want in the pocket dimension and keep repeating this method if it goes sideways.

AND DON'T USE A BLACK HOLE SPELL FROM IRON'S. that would be silly.