Non-player entities teleport incorrectly with End portal #2707
Comments
|
@JamesRagnarok I can shed a bit of light on your issues. As far as non player entities entering the end at 0,0 you need to set your spawn location (MVSpawnLocation) for your end worlds to the air block above the center of the obsidian platforms, thus making it like vanilla. I'm having the same issue where non player entities (items, mobs, armor stands) that go into the exit end portal in the main end world always arrive in the main world near 0, 0. What I expect to happen is for those entities to arrive at the main world spawn location (-8325, 11132) that is set in the Multiverse worlds.yml file just as players do. I'm suspect that Multiverse-NetherPortals (4.2.1) has something to do with this issue since if I remove it, everything works as expected. We use MVNP for a resource world with it's own nether. I've tested this with Multiverse-Core 4.2.2, 4.3.0 as well, also tried linking the 2 worlds to and from the end and that did not fix the issue. Any help would be greatly appreciated. Startup log: https://paste.lucko.me/2wmkCoCCw7 |
|
Recently I ran into this issue as well. I tried to transport a shulker from the end to the overworld, but every time it suffocated in the bedrock at y=0. Interesting enough it did not spawn the shulker at x=0 and z=0, but instead at the original world spawn location (and at y=0). I managed to solve this by loading spawn with a second player account. This way the area was loaded and upon transporting a shulker or item, it got placed at the actual spawn location as it was set with /mvsetspawn. I hope this will be fixed properly at some point, but at least this is a workaround. |
|
@Flexcrash Are you using Multiverse-NetherPortals? |
|
I am indeed. Version 4.2.1 to be precise |
|
So is this issue somehow related to spawn chunks loading? I thought |
|
We have our world spawn in memory. I've even set our world spawn at 0,0 and non player entities still arrive at a random location around it, so no difference. I've also tested using other players. I can have only Multiverse-Core and Multiverse-NetherPortals loaded and the problem exists. If I remove MVNP, everything works fine except for our mining world nether portals, so we're kind of stuck using it. |
That is a very good point I forgot to mention. We indeed have our spawn chunks turned off. Now I think about it, it was slightly different even. Indeed as has been said here, the items never end up as where I set /mvsetspawn. The items will always go to the original world spawn location. Its been some time ago since we brought shulkers over from the end :p |
|
Thought that this might be useful or at least interesting. I tossed a wool block in each of the 8 corners of the exit and portal. Then placed an armor stand against each of the 4 faces of the pillar. This is where they came out centered around the yellow block at 0,0. Which is outside of our world border but increased for this testing. I marked the wool items with torches. |
benwoo1110
added
Bug: Unconfirmed
|
This problem can still be reproduced nowadays. Debug information by When I try to push a living entity or throw an item entity into an end portal, it always disappears. |
Information
Server version: git-Paper-266 (MC: 1.17.1) (Git: 0d19cd7)
Full output of
/mv version -p: https://j.mp/3u0kFaJServer log: https://gist.github.com/JamesRagnarok/8a786bfadc4ef73e674c26a53d846d17
Help request
Problem
With Multiverse activate, non-player entities such as items and mobs can't land on obsidian platform in the End while going through the End portal. Instead, they seems spawn at 0, 63, 0, right on the Exit portal, and immediately teleport back into overworld. Moreover, when items and mobs leave the End through Exit portal, they do not show up at the world spawn of the overworld (I had my overworld spawn moved to 800 blocks away), but somewhere near 0, 63, 0. These are not vanilla behaviors and somehow do not affect players.
What I have tried
Disable Multiverse would fix this problem. I had the respawnWorld property set before (otherwise players cannot leave the End), but removing respawnWorld didn't help.
Screenshots
The text was updated successfully, but these errors were encountered: