[MC-174688] Dungeons cannot be located

Note: I'm almost certain this was created and closed already. However, circumstances have changed. MC-171860 was resolved by implementing a /location function for nether fossils, and MC-174499 was permitted to stay open. This can be closed, but I think it's fair to let it stay.

Dungeons cannot be located with the /locate command, nor can they be used in the location advancement trigger.

Linked issues

duplicates 1

MC-107829 /locate command cannot locate dungeons Resolved

Comments 4

PancakeIdentity 2020-03-13T07:28:21Z

Hi, could this be reopened? As detailed in the description, cirumstances around this seem to have changed. I don't think this should be a duplicate (similar to how MC-174499 is technically a duplicate but is being left open)

wobst.michael 2020-03-13T07:34:11Z

As already mentioned in MC-107829, this is a feature request. MC-174499 is only left open because Fossils can now be located in the nether, and not allowing other Fossils to be located might be a inconsistency.

PancakeIdentity 2020-03-13T07:37:40Z

Wouldn't allowing some structures to be located and not others be an inconsistency?

wobst.michael 2020-03-13T07:39:30Z

No. The ticket has clearly be closed as a feature request by a developer. But you can leave a comment in MC-107829 if you want to.