MC-195692Structure 'End City' and configured structure in vanilla end 'End City' use inconsistent identifiers
The (not - configured) structure has id "minecraft:endcity" and the struture in the end lists as "minecraft:end_city".
It is now imprtant as worldgen is now publicly accessible via datapacks, not an internal concept
Since all identifiers use snake case consistently, suggesting encoding structure name as 'end_city', the same way you have fixed all instance of 'village_snovy'
Attached screenshots of vanilla world gen json for end_city structure
There are another related issues that point to different identifiers related with end cities:
MC-187911
Linked Issues
![[Mojang] Gnembon](../../../data/avatars/users/93709.png){kind=small}
Created Issue:
Structure 'End City' and configured structure in vanilla end 'End City' use inconsistent identifiers
The (not - configured) structure has id "minecraft:endcity" and the struture in the end lists as "minecraft:end_city".
It is now imprtant as worldgen is now publicly accessible via datapacks, not an internal concept
Since all identifiers use snake case consistently, suggesting encoding structure name as 'end_city', the same way you have fixed all instance of 'village_snovy'
Attached screenshots of vanilla world gen json for end_city structure
Environment
Windows
Attachments1
The (not - configured) structure has id "minecraft:endcity" and the struture in the end lists as "minecraft:end_city".
It is now imprtant as worldgen is now publicly accessible via datapacks, not an internal concept
Since all identifiers use snake case consistently, suggesting encoding structure name as 'end_city', the same way you have fixed all instance of 'village_snovy'
Attached screenshots of vanilla world gen json for end_city structure
There are another related issues that point to different identifiers related with end cities:
https://bugs.mojang.com/browse/MC-187911
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
The (not - configured) structure has id "minecraft:endcity" and the struture in the end lists as "minecraft:end_city".
It is now imprtant as worldgen is now publicly accessible via datapacks, not an internal concept
Since all identifiers use snake case consistently, suggesting encoding structure name as 'end_city', the same way you have fixed all instance of 'village_snovy'
Attached screenshots of vanilla world gen json for end_city structure
There are another related issues that point to different identifiers related with end cities:
https://bugs.mojang.com/browse/MC-187911The (not - configured) structure has id "minecraft:endcity" and the struture in the end lists as "minecraft:end_city".
It is now imprtant as worldgen is now publicly accessible via datapacks, not an internal concept
Since all identifiers use snake case consistently, suggesting encoding structure name as 'end_city', the same way you have fixed all instance of 'village_snovy'
Attached screenshots of vanilla world gen json for end_city structure
There are another related issues that point to different identifiers related with end cities:
MC-187911
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
Can confirm in 21w17a.
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
![[Mod] markderickson](../../../data/avatars/users/18946.svg){kind=small}
Windows
![[Mod] SPGoding](../../../data/avatars/users/44622.png){kind=small}
relates to
Can confirm in 21w17a.
See MC-195692 for more details.
Isn't this just a duplicate of
MC-187911?Can confirm in 21w44a.