-
Bug
-
Resolution: Unresolved
-
None
-
1.21.60.21 Preview, 1.21.50.22 Preview, 1.21.40.25 Preview, 1.21.31 Hotfix, 1.21.50, 1.21.70.20 Preview, 1.21.51 Hotfix
-
Community Consensus
-
Multiple
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
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: outdated_block_id_tester.mcpack
- Look at blocks.json from the sample pack:
- 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.
