Multiverse-Core: [1.15.2] Unable to exit end dimension
Environment
Tested Server Software:
PaperDragon 1.15.2 (Base: Paper @ f11d64728fd4351a74edd672ec336f3f07921abb)
Paper 1.15.2 - Build 67 (8a0b371c6803027f15a3bfc66e2285955e9b8dc1)
Plugins:
- Multiverse-Core @ 4.1.1-SNAPSHOT-b777
Summary
When attempting to exit the end dimension through the central end portal, you get teleported on top of where the dragon egg spawns. Nether portals work in both directions, as well as entering the end.
Debug: https://j.mp/2TMqmce
Related:
About this issue
- Original URL
- State: open
- Created 4 years ago
- Comments: 16 (2 by maintainers)
I found a much simpler workaround - the
respawnWorldproperty can be set for the end world, so if your overworld is calledWORLD, use this command:It seems like this should be the default for consistency with vanilla Minecraft.
@dumptruckman The vanilla behavior of this action is to return the player to the world spawn point, if their bed is broken or obstructed. With multiverse, it teleports the player to the top of the bedrock pillar at the end gateway, and gives the error that their bed was broken or obstructed.
Please fix this issue by restoring the vanilla behavior if the player’s bed is broken or obstructed. This is still present in 1.18.1.
I believe there was a change in either 1.15.1 or 1.15.2 that meant that exit portals no longer trigger the PlayerPortalEvent, but instead the PlayerRespawnEvent. That’s my theory as to why this issue popped up. I’ll do some testing to make sure, I’ll post my findings here.
We’ve had this problem for a while - it seems to be when you don’t have a bed set. My guess is it tries to respawn you at “spawn”, in the current dimension, which then in our case just drops you through the portal over and over again (and an admin has to teleport you out). If your bed has been properly set and not destroyed before you enter the end, everything seems to work fine.