Generally, block type IDs seem to be accurate to their respective blocks' names; however, weathering_copper_trap_door is one case where this is not true. The block type registry is exposed in the blocks' data generator report, meaning this behavior is observable with the vanilla Minecraft server JAR.
Steps to reproduce
Run the data generator
Search for
weathering_copper_trap_doorin the output, observing that it existsSearch for
trapdoorin the output, observing that it also exists
Expected result
The block type ID shown would be weathering_copper_trapdoor.
Actual result
The block type ID shown is weathering_copper_trap_door.
The output can also be viewed here: https://github.com/misode/mcmeta/blob/98d7bad8ba0a906d1a8fcc78f1cdc5a415ecca5d/block_definitions/data.json#L1110
Comments 3
Confirmed in 1.21.11.
Steps to reproduce:
Run the vanilla data generator using the official server JAR:
java "-DbundlerMainClass=net.minecraft.data.Main" -jar server.jar --reportsOpen the generated
reports/registries.jsonfile.Search for the
minecraft:block_typeregistry.
Observe that the copper trapdoor variant is incorrectly serialized as
"minecraft:weathering_copper_trap_door", while standard trapdoors are correctly serialized as"minecraft:trapdoor".
jq.a($$0, "trapdoor", eiw.a);
jq.a($$0, "weathering_copper_door", ejw.g);
jq.a($$0, "weathering_copper_trap_door", ekc.g); 
Thank you for your report!
After consideration, the issue is being closed as Invalid.
This report does not describe a bug.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Hi!
Could you please confirm that this issue is present in-game?
This ticket will automatically reopen when you reply. Thanks!
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki