A lot of blocks that used to be grouped together with the same block IDs have been split into their own unique IDs recently, and resource packs have been properly updated to accomodate that change.
However, the planks and stone variants did not receive the same treatment. Despite being split, their blocks.json
definitions are still grouped together.
Block | Current Definition | Ideal Split |
---|---|---|
Oak Planks |
|
|
Stone |
|
|
This is inconsistent and unintuitive for creators.
Attachments
Comments 6

For an example of how this harms creators — a creator may want to change granite, diorite, and andesite to use different sound sets like tuff and calcite. However, because all these blocks use the "stone" entry in blocks.json, the creator cannot do this. This affects all block properties like "isotropic" and "brightness_gamma" too.
As stated in another comment, stone IDs have been separated in blocks.json in the vanilla_1.21.10 resources. Unfortunately, they are affected by MCPE-186255, which means they do not work separately.
The planks split IDs have not appeared in the vanilla resources yet, but they are functional. Here is an example where I used the "oak_planks" ID in blocks.json to make Oak Planks randomly rotate, without affecting Spruce Planks. (Halloween Mash-up is also applied):
[media]Once the split planks IDs are included in the vanilla resources, this report can be considered "fixed" and the remaining issues with blocks.json should move to MCPE-186255.