The command /place structure minecraft:ancient_city places the city, but within blocks such that the city cannot be accessed. No air, access or carving is done to make the structure appear as expected, or usable.
This bug was reported back in 2022, and was closed as “Works as intended” Which was a negligent oversight. This is clearly not “Expected behavior” and is evidently a bug to anyone who attempt to replicate the steps. Please see the attachments to view the “Working as intended” command.
The players expectation and the actual output are incongruous.
Old bug report: https://bugs.mojang.com/browse/MC/issues/MC-251339
Replication
Any server attempt
/place structure minecraft:ancient_city
Go underground in spectator mode
View city that is not accessible or usable due to the lack of carving air or caverns expected of an ancient city.
Environment
Minecraft:Overworld
Java Edition
Versions 1.19-Current
Linked issues
Attachments
Comments 13
MC-251413: The command /place generates some constructions. For example, I wanted to create my own village, but I saw that the paths were very littered. The ancient city is generated without space. (Resolved)
- [media]
- [media]
MC-252453: Ancient Cities Generate Buried When Using The /place Feature. (Resolved)
- [media]
MC-252896: Ancient Cities do not generate correctly using the "place" command (Resolved)
- [media]
- [media]
MC-256435: place structure feature needs a small adjustment (Resolved)
- [media]
MC-263279: /place command doesn't work with custom-generated biomes/terrain (Resolved)
- [media]
MC-267848: Place Ancient City structure bug (Resolved)
Each of these are closed without consideration as they are considered duplicates.
Please for the community, listen to them. We don’t want a useless command, we want something that actually works.
Creating duplicate reports intentionally is not the right approach—sorry. This isn’t an effective way to raise concerns, and submitting the issue again simply because you disagree with the outcome won’t change the result. If you believe the parent ticket was incorrectly marked as "WAI," the proper way to proceed is to leave a well-reasoned comment on that ticket, explaining why you think the resolution was incorrect. You can also request a Mojang review there. They will then make a second (and final) decision. Closing this as a duplicate.
I am not a support agent, so I am unable to provide customer service. If you're just here to complain, this isn't the right place for you. Consider this a warning.
And again, we are bug tracker staff, not support. Support can be contacted via https://aka.ms/Minecraft-Support. I look forward to your comment on the parent ticket, after which I will request a Mojang review.
Alright, I appreciate your help. I made a comment on the original bug. It appears people have made the same points that I make, but I tried to summarize them.
A Mojang review is requested — thanks! You can now 'watch' the report and check regularly to see if Mojang reopens this ticket.
Please do not close this as a duplicate. The original ticket was closed as “Working as intended” but clearly, as evident by tens of bug reports, and the command’s nature of not being useful, it is indeed something that should be fixed. No other structures work in such a way as this one.