[MCPE-187398] Outdated block ID content errors for blocks.json do not trigger for all outdated IDs

In 1.21.30, the format_version of blocks.json is now used to find outdated block IDs used in the file. These outdated IDs appear as content errors in the Creator Content Log.

However, some outdated block IDs still function without causing a content error.

For example, "terracotta" is counted as an outdated ID instead of "stained_hardened_clay". It should not be possible to have "outdated block ID" and "not in registry" errors for the same ID, but "terracotta" does: Fixed in 1.21.50

~~False Positives~~

~~These block IDs throw errors when they shouldn't.~~ Fixed in 1.21.50

~~Block ID~~	~~Notes~~
~~terracotta~~	~~This ID has never been used for a block on Bedrock Edition. It was included in the list instead of "stained_hardened_clay".~~

Omissions

Many outdated block IDs are missing from content error reporting. These block IDs should throw errors, but don't.

Block ID	New Block IDs	Changed in...	Notes
concretePowder	black_concrete_powder blue_concrete_powder brown_concrete_powder cyan_concrete_powder gray_concrete_powder green_concrete_powder light_blue_concrete_powder light_gray_concrete_powder lime_concrete_powder magenta_concrete_powder orange_concrete_powder pink_concrete_powder purple_concrete_powder red_concrete_powder yellow_concrete_powder white_concrete_powder	1.20.30	The "concretePowder" ID was changed to "concrete_powder" in 1.18.30, but blocks.json still accepts concretePowder.
grass	grass_block	1.21.0	"grass_block" is never used in a vanilla blocks.json, but it is fully functional. Since this is the ID used in commands, it should also be the preferred ID in blocks.json.
invisibleBedrock	invisible_bedrock	1.18.30
movingBlock	moving_block	1.18.30
pistonArmCollision	piston_arm_collision	1.18.30
seaLantern	sea_lantern	1.18.30
stickyPistonArmCollision	sticky_piston_arm_collision	1.18.30
tripWire	trip_wire	1.18.30
yellow_flower	dandelion	1.21.20

To Reproduce

Go to the Settings -> Creator menu
Turn on the "Enable Content Log GUI" option.
Download and apply the attached sample pack:

[media]

Look at blocks.json from the sample pack:
1. [media]
Enter a world.
Go to the Settings -> Creator -> Content Log History menu.
Notice no errors have occurred despite using old block IDs in blocks.json.
Exit the menu.
Place any color of concrete powder.
Notice all concrete powder blocks are using the "bamboo_sapling" sound.
Place a dandelion.
Notice the dandelion uses stone sounds.
These outdated block IDs should have caused content errors, but they did not.

Expected Result

All outdated block IDs throw errors when used in blocks.json with a format_version of 1.21.30 or later.

Observed Result

Some outdated block IDs still do not throw errors when used in blocks.json.

Attachments

outdated_block_id_tester.mcpack

Comments 4

migrated 2024-10-12T15:35:00Z

[media][media]

KR_ 2024-12-05T14:47:08Z

Can confirm.

v-kyrylo.kunytskyi 2025-02-05T13:09:55Z

Thank you for your feedback!
_{However, the issue is being temporarily resolved as}_{Awaiting Response}_.
Please, let us know whether the bug still occurs on the latest versions. In case it does, please, update the Affects Version/s field.
_{Once the requested information has been delivered, the report will be reopened automatically.}

Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

AgentMindStorm2 2025-02-05T14:41:05Z

Replying to v-kkunytskyi:

This is still an issue in the latest versions. You can easily reproduce this by downloading the attached resource pack, applying it in the main menu, enabling Content Log GUI, and loading into a world.

There should be content log errors due to outdated block IDs used in blocks.json, but no errors appear.