Often when I use /locate ruinedportal command it gives me coordinates but then when I look there is nothing there even if I dig down to bedrock.
Appears to also be affecting Bastions
Linked issues
is duplicated by 14
Attachments
Comments 8
@unknown please use the project linked below, as you are playing a different version of Minecraft
@Celesian Thanks. Embarrassing. Will do. I found the MC Java edition issue: MC-179029. You or someone may want to link these issues as possibly related.
Could someone affected please provide a seed used and the location you ran the command? (Not the location the command gave you, where you ran it, so someone else can reproduce).
Edit: It would also help to know if your world was created prior to the BETA's and updated or if it was a brand new world created in the BETA.
@IonicEcko, 1273368191 is the seed I use, and if you write /locate ruinedportal, you get 696, ?, 24 or something. This turns to be underwater, and if you look all the way to bedrock, you still can't see the portal. I tried digging a bit in all directions, but still can't find it. Hope this gets resolved soon
According to https://www.minecraft.net/en-us/article/minecraft-snapshot-20w16a, they sometimes spawn underground or in oceans.
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response
Is this still an issue in the latest version? If so, please add a comment or update the affected version field.
To make your bug report as effective as possible, please try and include the following steps to reproduce the problem:
Steps to Reproduce:
1.
2.
3.Observed Results:
(Briefly describe what happens)Expected Results:
(Briefly describe what should happen)
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
For any account or purchasing related issues, please contact Minecraft Customer Support directly, as we cannot assist with those here at the bug tracker.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
I have experienced this phenomenon also. I suspect that the problem behavior is caused by the user searching for the portal in the Overworld but the /locate command is giving Nether coordinates. I suspect this becomes a problem in this release because Ruined_Portals can generate in either the Overworld or the Nether and the /locate command offers no parameter for specifying the present dimension or a different one.
I will investigate further and offer an additional comment once this is confirmed.Investigation continues below.I used a portal to go to the Nether and /tp to the coordinates given and there was no portal, ruined or otherwise, at those coordinates at any altitude. I returned to the Overworld and tried the original search, but inverting the sign on each of the coordinates, and teleporting and searching at all altitudes for the new coordinates. No Ruined Portal was found.
The original /locate Ruined_Portal command was issued from coordinates 146. 86. /-383. The returned coordinates were "/---576. /~. /-1104 1019 blocks away." I can attach or make game world files available if requested.
Note: The game world was originally generated by a 1.14 pre-release shapshot and contained previously loaded and modified chunks before being updated to snapshot 20w16a.