Suppose I have a 1.21.11 resource pack with 3 custom assets files: blockstates/brown_mushroom_block.json, models/block/red.json, textures/block/red.png
blockstates/brown_mushroom_block.json:
{
"multipart":[
{"when":{"down":false,"east":false,"north":false,"south":false,"up":false,"west":false},"apply":{"model":"block/gold_block"}},
{"when":{"down":false,"east":false,"north":false,"south":false,"up":false,"west":true},"apply":{"model":"block/red"}}
]
}models/block/red.json:
{
"parent": "block/cube_all",
"ambientocclusion": false,
"textures": {
"particle": "block/red",
"all": "block/red"
}
}I do not change models/block/gold_block in any way, it is only used to help demonstrate another texture
Here's how it looks in the game when I break the according blocks (I use fill command with destroy parameter in the screenshots):
as you can see, both blocks have the same particle breaking texture, even though we specified "particle": "block/red" in the models/block/red.json model.
Now let's change the order of entries in the multipart json for blockstates/brown_mushroom_block.json:
{
"multipart":[
{"when":{"down":false,"east":false,"north":false,"south":false,"up":false,"west":true},"apply":{"model":"block/red"}},
{"when":{"down":false,"east":false,"north":false,"south":false,"up":false,"west":false},"apply":{"model":"block/gold_block"}}
]
}And now we have the opposite effect, we only see the red texture particles, but not gold_block:
Is this intended behavior? Is there any chance to make it so each block model have their own particle breaking texture?
Expected result: each entry of multipart applying the particle texture to the respective model.
Actual result: only the first entry of multipart json is responsible for applying the particle texture.
Environment
openjdk 21.0.10 2026-01-20
Attachments
Comments 6
We do not have enough resources to reproduce this issue.
Please attach a minimal setup resource pack that can be used to reproduce this issue.
This issue is being temporarily resolved as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.
Quick Links:
π Bug Tracker Guidelines β π¬ Community Support β π§ Mojang Support (Technical Issues) β π§ Microsoft Support (Account Issues)
π Project Summary β βοΈ Feedback and Suggestions β π Game Wiki
Here are two resource packs to recreate the issue
They are identical apart from the multipart section in the assets/minecraft/blockstates/brown_mushroom_block.json
To recreate place mushroom blocks with commands:
(red texture): /setblock ~ ~ ~ minecraft:brown_mushroom_block[down=false,east=false,north=false,south=false,up=false,west=false]
(blue texture): /setblock ~ ~ ~ minecraft:brown_mushroom_block[down=false,east=false,north=false,south=false,up=false,west=true]
If you use the v1 resource pack both blocks have red particles, if you use the v2 resource pack both blocks have blue particles. There is no way to make it so they each have their own particle texture, because that is determined by the order of the multipart in the blockstate, only the first entry is used for particles (the texture, the model and the rest are fine and act as expected, the problem is only with the particles - when you break the block or particles from sprinting on the block)
I donβt know how to edit the original post, please add the resource packs there if needed
One way to fix the particle problem is by switching from multipart to variants and by specifying the particle textures in each model.
replace
{
"multipart":[
{"when":{"down":false,"east":false,"north":false,"south":false,"up":false,"west":false},"apply":{"model":"block/red"}},
{"when":{"down":false,"east":false,"north":false,"south":false,"up":false,"west":true},"apply":{"model":"block/blue"}}
]
}with
{
"variants": {
"west=true": { "model": "block/blue" },
"west=false": { "model": "block/red" }
}
}Blocks:
{
"parent": "block/cube_all",
"textures": {
"all": "block/red",
"particle": "block/red"
}
}{
"parent": "block/cube_all",
"textures": {
"all": "block/blue",
"particle": "block/blue"
}
}Thank you, katerina!
Since there is a way to make particles work with variants tag instead of multipart tag the issue can be closed
Thank you for your report!
After consideration, the issue is being closed as Invalid.
You have posted a feature request or a suggestion. This site is for bug reports only.
For suggestions, please visit The official Minecraft feedback site or visit the Minecraft Feedback Discord server.
Quick Links:
π Bug Tracker Guidelines β π¬ Community Support β π§ Mojang Support (Technical Issues) β π§ Microsoft Support (Account Issues)
π Project Summary β βοΈ Feedback and Suggestions β π Game Wiki
I didn't understand the essence of the reported error at all. π€