Shulkers teleport with original dimension coordinates after passing through portals
The bug
If a shulker is unable to find a valid attachment location in its first tick after traveling through a portal (tested with Nether portals and End portals), it will keep its attached block data from the previous dimension and appear at the previous dimension coordinates (explanation obtained from MC-139265 and verified with /data commands). Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). When it arrives at the Nether side, it fails to find a valid block to attach to in its first tick, so it is re-positioned to align with its attached block data from the overworld, causing it to be in the Nether at (240, 65, 238), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether/overworld. When using this method, this is what I found when teleporting a shulker to the Overworld from the Nether:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2). See https://www.youtube.com/watch?v=P25DK1cm74M&t=822s for evidence it was an issue (though slightly different and primarily with end portals) in 1.12.
How to reproduce
(Step 2 not necessary, but recommended)
- Build a Nether portal in a release after 1.14 for the bug in its current state
(or in 1.13.2 for the proper behavior). - To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
- Use a piston to push a shulker through the portal or spawn a shulker in the portal. You may need to repeat this step several times.
Linked Issues
testing discovered1
is duplicated by5
MC-171954Shulkers won't change dimensionsDuplicateMC-176399Shulker teleports to its nether coordinates when travelling to the OverworldDuplicateMC-194121Shulkers don't use nether portals correctlyDuplicateMC-202267Shulkers and portals don't work well togetherDuplicateMC-203891Shulkers going through a nether portal without a valid teleportation spot would ignore dimension scaling, and would remain in the coordinates of their previous dimension.Duplicate
Created Issue:
Shulker's Often Disappear when Going through Nether Portals
The Bug:
When pushing a shulker through a Nether portal, once the shulker is teleported by the portal to the Nether or overworld, it often vanishes. This behavior is slightly different between spawn chunks and more distant locations. In the spawn chunks, the shulkers can often be detected or teleported with commands after going through the portal even if unable to be found by inspection, and sometimes they behave as expected.
As far as I've seen, the bug is more consistent outside spawn chunks, but usually happens to some degree in both regions.
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2).
How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug (or in 1.13.2 for the proper behavior).
2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal.
Environment
Intel i7 8th Gen CPU
NVIDIA Quadro P500 GPU
(Lenovo ThinkPad P52 Laptop)
Java 1.8.0_51 (the Java version bundled with the launcher).
Attachments2
The Bug:
When pushing a shulker through a Nether portal, once the shulker is teleported by the portal to the Nether or overworld, it often vanishes. This behavior is slightly different between spawn chunks and more distant locations. In the spawn chunks, the shulkers can often be detected or teleported with commands after going through the portal even if unable to be found by inspection, and sometimes they behave as expected.
As far as I've seen, the bug is more consistent outside spawn chunks, but usually happens to some degree in both regions.
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2).
How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug (or in 1.13.2 for the proper behavior).
2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal.
Shulker's Often DisappearwhenGoing through Nether PortalsShulker's Often Disappear After Going through Nether Portals
Shulker'sOften DisappearAfter Going through Nether PortalsShulkers Randomly Teleport to Near the World Spawn Coordinates After Going through Nether Portals
ShulkersRandomly Teleport to Near the World Spawn Coordinates After Goingthrough Nether PortalsShulkers Do Not Teleport through Nether Portals as the Should
Shulkers Do Not Teleport through Nether Portals as they Should
The Bug:
When pushing a shulker through a Nether portal, once the shulker is teleported by the portal to the Nether or overworld, it often vanishes. This behavior is slightly different between spawn chunks and more distant locations. In the spawn chunks, the shulkers can often be detected or teleported with commands after going through the portal even if unable to be found by inspection, and sometimes they behave as expected.
As far as I've seen, the bug is more consistent outside spawn chunks, but usually happens to some degree in both regions.
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2).
How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug (or in 1.13.2 for the proper behavior).
2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal.
The Bug:
When pushing a shulker through a Nether portal, it will randomly either appear where it should (next to the corresponding Nether portal) or somewhere near the worldspawn coordinates. When teleporting from the overworld to the Nether, the shulkers will often appear at the overworld coordinates of the world spawn. The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers.
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2).
An Example:
1) I spawned a shulker in a nether portal at (758, 67, 204):
How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug (or in 1.13.2 for the proper behavior).
2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal.
image-2020-01-02-17-58-05-454.png
The Bug:
When pushing a shulker through a Nether portal, it will randomly either appear where it should (next to the corresponding Nether portal) or
somewherenear theworldspawn coordinates. When teleporting from the overworld to the Nether, the shulkers will often appear at the overworld coordinates of the world spawn. The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers.Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2).
An Example:
1) I spawned a shulker in a nether portal at (758, 67, 204):
How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug (or in 1.13.2 for the proper behavior).
2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal.
The Bug:
When pushing a shulker through a Nether portal, it will randomly either appear where it should (next to the corresponding Nether portal) or near the original dimension coordinates in the new dimension. The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers.
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2).
How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug (or in 1.13.2 for the proper behavior).
2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal.
ShulkersDo NotTeleportthrough Nether Portals as they ShouldShulkers Teleport with Original Dimension Coordinates after Passing through Portals
The Bug:
When pushing a shulker through a Nether portal, it will randomly either appear where it should (next to the corresponding Nether portal) or near the original dimension coordinates in the new dimension. The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers
.Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2).
How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug (or in 1.13.2 for the proper behavior).
2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal.
The Bug:
If a shulker uses its ability to teleport as it is being sent through a portal (tested with Nether portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, but in the Nether, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2).
How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug (or in 1.13.2 for the proper behavior).
2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal.
The Bug:
If a shulker uses its ability to teleport as it is being sent through a portal (tested with Nether portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, but in the Nether, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether, and, if it teleports, to its new, distant location.
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2).
How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug (or in 1.13.2 for the proper behavior).
2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal.
The Bug:
If a shulker uses its ability to teleport as it is being sent through a portal (tested with Nether portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, but in the Nether, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether, and, if it teleports, to its new, distant location.
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2).
How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug (or in 1.13.2 for the proper behavior).
2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal.
The Bug:
If a shulker uses its ability to teleport as it is being sent through a portal (tested with Nether portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, but in the Nether, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether, and, if it teleports, to its new, distant location. When using this method, this is what I found:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2).
How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug (or in 1.13.2 for the proper behavior).
2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal.
The Bug:
If a shulker uses its ability to teleport as it is being sent through a portal (tested with Nether portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated,
but in the Nether,causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether, and, if it teleports, to its new, distant location. When using this method, this is what I found:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2).
How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug (or in 1.13.2 for the proper behavior).
2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal.
The Bug:
If a shulker uses its ability to teleport as it is being sent through a portal (tested with Nether portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether/overworld, and, if it teleports, to its new, distant location. When using this method, this is what I found:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2).
How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug (or in 1.13.2 for the proper behavior).
2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal.
The Bug:
If a shulker uses its ability to teleport as it is being sent through a portal (tested with Nether portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether/overworld, and, if it teleports, to its new, distant location. When using this method, this is what I found and my interpretation of the data:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2).
How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug (or in 1.13.2 for the proper behavior).
2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal.
The Bug:
If a shulker uses its ability to teleport as it is being sent through a portal (tested with Nether portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether/overworld, and, if it teleports, to its new, distant location. When using this method, this is what I found
and my interpretation of the data:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2).
How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug (or in 1.13.2 for the proper behavior).
2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal.
The Bug:
If a shulker uses its ability to teleport as it is being sent through a portal (tested with Nether portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether/overworld, and, if it teleports, to its new, distant location. When using this method, this is what I found:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2).
How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug (or in 1.13.2 for the proper behavior).
2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal. You may need to repeat this step several times.
The Bug:
If a shulker uses its ability to teleport as it is being sent through a portal (tested with Nether portals and End portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether/overworld, and, if it teleports, to its new, distant location. When using this method, this is what I found:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2).
How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug (or in 1.13.2 for the proper behavior).
2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal. You may need to repeat this step several times.
The Bug:
If a shulker uses its ability to teleport as it is being sent through a portal (tested with Nether portals and End portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether/overworld, and, if it teleports, to its new, distant location. When using this method, this is what I found:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2).
How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug (or in 1.13.2 for the proper behavior).
2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal. You may need to repeat this step several times.
The Bug:
If a shulker uses its ability to teleport as it is being sent through a portal (tested with Nether portals and End portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether/overworld, and, if it teleports, to its new, distant location. When using this method, this is what I found:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2). See https://www.youtube.com/watch?v=P25DK1cm74M&t=822s for evidence it was an issue in 1.12.How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug (or in 1.13.2 for the proper behavior).
2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal. You may need to repeat this step several times.
The Bug:
If a shulker uses its ability to teleport as it is being sent through a portal (tested with Nether portals and End portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether/overworld, and, if it teleports, to its new, distant location. When using this method, this is what I found:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2). See https://www.youtube.com/watch?v=P25DK1cm74M&t=822s for evidence it was an issue in 1.12.How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug (or in 1.13.2 for the proper behavior).
2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal. You may need to repeat this step several times.
The Bug:
If a shulker uses its ability to teleport as it is being sent through a portal (tested with Nether portals and End portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether/overworld, and, if it teleports, to its new, distant location. When using this method, this is what I found:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2). See https://www.youtube.com/watch?v=P25DK1cm74M&t=822s for evidence it was an issue in 1.12.How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug
(or in 1.13.2 for the proper behavior).2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal. You may need to repeat this step several times.
The Bug:
If a shulker uses its ability to teleport as it is being sent through a portal (tested with Nether portals and End portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether/overworld, and, if it teleports, to its new, distant location. When using this method, this is what I found:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2). See https://www.youtube.com/watch?v=P25DK1cm74M&t=822s for evidence it was an issue (though slightly different and primarily with end portals) in 1.12.How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug
(or in 1.13.2 for the proper behavior).2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal. You may need to repeat this step several times.
The Bug:
If a shulker uses its ability to teleport as it is being sent through a portal (tested with Nether portals and End portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether/overworld, and, if it teleports, to its new, distant location. When using this method, this is what I found:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2). See https://www.youtube.com/watch?v=P25DK1cm74M&t=822s for evidence it was an issue (though slightly different and primarily with end portals) in 1.12.How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug in its current state
(or in 1.13.2 for the proper behavior).2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal. You may need to repeat this step several times.
The Bug:
If a shulker uses its ability to teleport as it is being sent through a portal (tested with Nether portals and End portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether/overworld, and, if it teleports, to its new, distant location. When using this method, this is what I found when teleporting a shulker to the Overworld:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2). See https://www.youtube.com/watch?v=P25DK1cm74M&t=822s for evidence it was an issue (though slightly different and primarily with end portals) in 1.12.How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug in its current state
(or in 1.13.2 for the proper behavior).2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal. You may need to repeat this step several times.
The Bug:
If a shulker uses its ability to teleport as it is being sent through a portal (tested with Nether portals and End portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether/overworld, and, if it teleports, to its new, distant location. When using this method, this is what I found when teleporting a shulker to the Overworld from the Nether:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2). See https://www.youtube.com/watch?v=P25DK1cm74M&t=822s for evidence it was an issue (though slightly different and primarily with end portals) in 1.12.How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug in its current state
(or in 1.13.2 for the proper behavior).2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal. You may need to repeat this step several times.
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
relates to
is duplicated by
Intel i7 8th Gen CPU
NVIDIA Quadro P500 GPU
(Lenovo ThinkPad P52 Laptop)
Java 1.8.0_51 (the Java version bundled with the launcher).
The Bug:
If a shulker uses its ability to teleport as it is being sent through a portal (tested with Nether portals and End portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether/overworld, and, if it teleports, to its new, distant location. When using this method, this is what I found when teleporting a shulker to the Overworld from the Nether:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2). See https://www.youtube.com/watch?v=P25DK1cm74M&t=822s for evidence it was an issue (though slightly different and primarily with end portals) in 1.12.How to Replicate:
(Step 2 not necessary, but recommended)
1) Build a Nether portal in a release after 1.14 for the bug in its current state
(or in 1.13.2 for the proper behavior).2) To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
3) Use a piston to push a shulker through the portal or spawn a shulker in the portal. You may need to repeat this step several times.
The bug
If a shulker uses its ability to teleport as it is being sent through a portal (tested with Nether portals and End portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether/overworld, and, if it teleports, to its new, distant location. When using this method, this is what I found when teleporting a shulker to the Overworld from the Nether:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2). See https://www.youtube.com/watch?v=P25DK1cm74M&t=822s for evidence it was an issue (though slightly different and primarily with end portals) in 1.12.How to reproduce
(Step 2 not necessary, but recommended)
- Build a Nether portal in a release after 1.14 for the bug in its current state
(or in 1.13.2 for the proper behavior).- To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
- Use a piston to push a shulker through the portal or spawn a shulker in the portal. You may need to repeat this step several times.
ShulkersTeleport withOriginalDimensionCoordinates afterPassing throughPortalsShulkers teleport with original dimension coordinates after passing through portals
is duplicated by
The bug
If a shulker
uses its ability to teleport as it is being sent througha portal (tested with Nether portals and End portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether/overworld, and, if it teleports, to its new, distant location. When using this method, this is what I found when teleporting a shulker to the Overworld from the Nether:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2). See https://www.youtube.com/watch?v=P25DK1cm74M&t=822s for evidence it was an issue (though slightly different and primarily with end portals) in 1.12.How to reproduce
(Step 2 not necessary, but recommended)
- Build a Nether portal in a release after 1.14 for the bug in its current state
(or in 1.13.2 for the proper behavior).- To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
- Use a piston to push a shulker through the portal or spawn a shulker in the portal. You may need to repeat this step several times.
The bug
If a shulker is unable to find a valid attachmenta portal (tested with Nether portals and End portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). As it enters the portal, it starts to teleport to another block, calculating its new coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether/overworld, and, if it teleports, to its new, distant location. When using this method, this is what I found when teleporting a shulker to the Overworld from the Nether:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2). See https://www.youtube.com/watch?v=P25DK1cm74M&t=822s for evidence it was an issue (though slightly different and primarily with end portals) in 1.12.How to reproduce
(Step 2 not necessary, but recommended)
- Build a Nether portal in a release after 1.14 for the bug in its current state
(or in 1.13.2 for the proper behavior).- To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
- Use a piston to push a shulker through the portal or spawn a shulker in the portal. You may need to repeat this step several times.
The bug
If a shulker is unable to find a valid attachmenta portal (tested with Nether portals and End portals), it will calculate it's teleportation position with coordinates from the starting dimension. Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.
For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30).
As it enters the portal, it starts to teleport to another block, calculatingitsnew coordinates. While it is teleporting, it is sent to the Nether. It then finishes teleporting to the coordinates it just calculated, causing it to be in the Nether at (235, 60, 241), over 300 blocks away from the portal it should appear near.The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether/overworld
, and, if it teleports, to its new, distant location. When using this method, this is what I found when teleporting a shulker to the Overworld from the Nether:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2). See https://www.youtube.com/watch?v=P25DK1cm74M&t=822s for evidence it was an issue (though slightly different and primarily with end portals) in 1.12.How to reproduce
(Step 2 not necessary, but recommended)
- Build a Nether portal in a release after 1.14 for the bug in its current state
(or in 1.13.2 for the proper behavior).- To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
- Use a piston to push a shulker through the portal or spawn a shulker in the portal. You may need to repeat this step several times.
The bug
If a shulker is unable to find a valid attachment location in its first tick after traveling through a portal (tested with Nether portals and End portals), it will keep its attached block data from the previous dimension and appear at the previous dimension coordinates (explanation obtained from
MC-139265). Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). When it arrives at the Nether side, it fails to find a valid block to attach to in its first tick, so it is re-positioned to align with its attached block data from the overworld, causing it to be in the Nether at (240, 65, 238), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether/overworld. When using this method, this is what I found when teleporting a shulker to the Overworld from the Nether:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2). See https://www.youtube.com/watch?v=P25DK1cm74M&t=822s for evidence it was an issue (though slightly different and primarily with end portals) in 1.12.How to reproduce
(Step 2 not necessary, but recommended)
- Build a Nether portal in a release after 1.14 for the bug in its current state
(or in 1.13.2 for the proper behavior).- To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
- Use a piston to push a shulker through the portal or spawn a shulker in the portal. You may need to repeat this step several times.
The bug
If a shulker is unable to find a valid attachment location in its first tick after traveling through a portal (tested with Nether portals and End portals), it will keep its attached block data from the previous dimension and appear at the previous dimension coordinates (explanation obtained from
MC-139265and verified with /data commands). Thus, shulkers sent through portals will often appear over a hundred blocks away from the portal in the new dimension.For example, a shulker is sent through a nether portal from the overworld at (240, 65, 238) to a portal in the nether at (30, 70, 30). When it arrives at the Nether side, it fails to find a valid block to attach to in its first tick, so it is re-positioned to align with its attached block data from the overworld, causing it to be in the Nether at (240, 65, 238), over 300 blocks away from the portal it should appear near.
The command "/execute at @e[type=minecraft:shulker] run tp <your player name> ~ ~ ~" is useful for locating wrongly positioned shulkers if they are still in loaded chunks. Setting up a repeat command block with that command in a chunk that will stay loaded and spawning a shulker in a Nether portal will allow you to follow the path of the shulker as it moves into the Nether/overworld. When using this method, this is what I found when teleporting a shulker to the Overworld from the Nether:
Shulker transport to the Nether and back appears to work as it should before 1.14 (tested in 1.13.2). See https://www.youtube.com/watch?v=P25DK1cm74M&t=822s for evidence it was an issue (though slightly different and primarily with end portals) in 1.12.How to reproduce
(Step 2 not necessary, but recommended)
- Build a Nether portal in a release after 1.14 for the bug in its current state
(or in 1.13.2 for the proper behavior).- To prevent the shulker from teleporting to a nearby open block once it goes through the portal, build the receiving portal at least 17 blocks from any solid block face and cover all the solid faces within 17 blocks with buttons.
- Use a piston to push a shulker through the portal or spawn a shulker in the portal. You may need to repeat this step several times.
After some thought, I believe this could be related to MC-149563.
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
is duplicated by
![[Helper] gaspoweredpick](../../../data/avatars/users/80904.png){kind=small}
![[Bot] Piston](../../../data/avatars/users/31202.png){kind=small}
testing discovered
Thank you for your report!
However, we are already tracking this issue, and this report is a Duplicate of MC-168900, which is a report that has not been resolved yet.
If you want, you can upvote the parent ticket, and enable watching to receive any updates about it - if you believe you have any information that may be important for this issue, please leave a comment on the parent. Please also use the search function in the future to prevent duplicate reports.
Quick Links:
📓 Issue Guidelines – 🛠 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
💬 Mojira Subreddit – 💬 Mojira Discord
![[Mod] Anthony Cicinelli](../../../data/avatars/users/10122.svg){kind=small}
Does MC-168900 describe your issue?
Close to MC-168900 bug. And like the bug I'm talking about, it seems like he's gone from time to time without being sent to Overworld.
Thank you for your report!
However, we are already tracking this issue, and this report is a Duplicate of MC-168900, which is a report that has not been resolved yet.
If you want, you can upvote the parent ticket, and enable watching to receive any updates about it - if you believe you have any information that may be important for this issue, please leave a comment on the parent. Please also use the search function in the future to prevent duplicate reports.
Quick Links:
📓 Issue Guidelines – 🛠 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
💬 Mojira Subreddit – 💬 Mojira Discord
Chava is right, this ticket is duplicating MC-168900. Hopefully a mod comes soon.
It possible that the shulker is in the nether, but in the wrong location. MC-168900 was recently fixed as part of 1.17+
Rather than near the portal it would be in the nether using overworld coordinates.
Can confirm
Still an issue in 20w08a
This is almost certainly a duplicate/combination of
MC-139265andMC-176399I'm in 1.15.2 - this is still an issue. I was going crazy trying to find out why my shulkers weren't coming to the overworld - I saw this post another one about the same problem, I checked the coordinates of the end portal in the overworld, and it was there. Thank you so much because I really don't think I would have found the shulker.
Can confirm for 1.16.4 and 20w45a.
If this get's patched then the real question is, what should a shulker do if it is unable to find an attatchment point as it passes through the portal? Should it:
A. Do nothing.
B. Appear in the portal in the other dimension then do nothing.
C. Appear at the same coordinates it entered the portal in the alternate dimension.
I should note, that options A and B both retract from what a player can accomplish when transporting shulkers whilst option C which is currently in the game adds an additional feature. It is still possible to get the 1/8 conversion by providing valid locations on the other side of the portal.
One major caveat to your final note about it still being possible to get the 1/8 conversion: even if you provide a reasonable number of valid locations on the other side, there is a moderate chance the shulker will not be able to find a spot before it gives up and appears at it's original dimension coordinates.
I believe there are several ways this could be patched in a consistent and useful way that is significantly less confusing to the average player.
All of the ways would start with the shulker arriving in the portal frame in the other dimension and looking for a valid attachment point, similarly to the current behavior. Afterwards, if it doesn't find an attachment point, one of the following could happen:
All of these methods retain at least some consistency in portal-entity interactions while accounting for some of the unique shulker behaviors. They also all either significantly reduce or completely eliminate the chance that players who aren't highly familiar with the technical community will encounter the current poorly documented behavior that can cause them to waste hours of time without a clue as to what's going on.
There are a few issues with your response, in option 2 you mentioned that block updates should intiate the search, however block updates only send updates to blocks immediately ajacent to them. Which means unless the shulker is right next to the block update there is no way to implement this than to have the shulker deliberately search for block updates within the 17x17x17 cube every gametick.
A deterministic search would mean that instead of searching 5 spaces every gametick, the shulker would eventually have to search 4913 spaces which would tank performance. The current behaviour of searching 5 random positions every gametick if the shulker is in an invalid position is quite well optimized.
Also I have observed the random behaviour when going through portals, the most optimized layout you can have has a 50% chance for the shulker to find a space each attempt. Repeating attempts 5 times in a row and the probability of a shulker not finding a space drops to about 1.2%. So out of 1000 shulkers you could expect to get 12 of them appearing at the same coordinates instead of going through the portal.
In hindsight it might be easier to manage shulkers if this behaviour was patched as portal linking would make them all appear in the same space, so for the shulker farm you wouldn't need a massive collection platform in the nether. But this mechanic is also very useful for populating mobswitches as you don't need a portal in the middle of your mobswitch that you can't get near to remove.
Yeah, I was concerned about the deterministic method's performance, but I thought there might be ways to mitigate it. Perhaps if it was able to be spread over multiple ticks, that could reduce the impact, but then of course, that would require extra data fields to save the search's progress. Alternatively, as most inexperienced players sending a shulker through a portal would expect it to appear near the front or back, a deterministic search over a small region in front and back could be used if the normal placing method doesn't work after going through a portal.
Likewise, I can see the issue with block updates. I wasn't positive how the entity AI's keep track of blocks around them, so I was just throwing out ideas.
I can also see the benefits of the current behavior, the main issue I see is that inexperienced players trying to get into technical minecraft will likely not have an optimized layout for shulker attachment, so a notably larger percent of the shulkers could be lost. Of course, once renewable shulkers are in a major release, that loss will not be as frustrating as it would be in the current release.
I propose the mechanics should work exactly as they are now, except if going from overworld to nether and the teleport checks fail, the X and Z coordinates are divided by 8, instead of staying the same as the overworld. Likewise, if going from nether to overworld, the coordinates would multiply by 8. Thus, the shulkers would be guaranteed to stay close to the portal, like every other entity.
Please note that the comment section on the bug tracker is not for discussing bugs, but it is for adding missing information to the ticket. If you wish to discuss this, feel free to create a thread on /r/Mojira or initiate a discussion on our Discord server.
After reflecting on this issue I found that it would really stink to have to travel thousands of blocks in the nether to get to the nether side of one of the new shulker farms. Therefore I think this should be fixed even though it was quite useful for transporting them large distances, this is a very niche application and carries more negatives than positives.