Vanilla Tweaks reference
Changes some blocks' breaking particles to properly reflect their textures.

Bedrock feasibility
|
|
| Verdict |
blocked (medium confidence) |
| Checked |
2026-07-25 by agent |
Bedrock exposes no per-block break-particle control point: the destroy particle always samples the block's own face texture and blocks.json has no particle field.
How it would work on Bedrock. Java does this by changing the particle texture slot inside each block's model JSON. Bedrock has no equivalent. The only per-vanilla-block visual control point is resource_pack/blocks.json, and across all 1213 entries in the vanilla file the complete key set is textures, carried_textures, sound, isotropic and ambient_occlusion_exponent - there is no particle or particle-texture key. The destroy particle itself, minecraft:block_destruct in resource_pack/particles/block_destruct.json, renders from atlas.terrain at UVs the engine supplies via variable.emitter_texture_coordinate, so overriding the particle cannot pick a different texture per block. The only remaining lever - changing a block's blocks.json texture entry - also changes how the block itself renders, which is not what the pack does. Vanilla block models, where Java keeps the particle slot, are hardcoded on Bedrock.
Caveats. Global changes to break particles (count, size, motion, tint) are still possible by overriding minecraft:block_destruct. Only per-block texture selection is unavailable. Some of the blocks the Java pack corrects may already sample a sensible face on Bedrock - worth spot-checking before closing the issue.
Sources
Maintained by tools/vt-diff. Edits inside this block are overwritten on the next run.
Vanilla Tweaks reference
ProperBreakParticles)fixes_and_consistency26.2Bedrock feasibility
Bedrock exposes no per-block break-particle control point: the destroy particle always samples the block's own face texture and
blocks.jsonhas no particle field.How it would work on Bedrock. Java does this by changing the
particletexture slot inside each block's model JSON. Bedrock has no equivalent. The only per-vanilla-block visual control point isresource_pack/blocks.json, and across all 1213 entries in the vanilla file the complete key set istextures,carried_textures,sound,isotropicandambient_occlusion_exponent- there is no particle or particle-texture key. The destroy particle itself,minecraft:block_destructinresource_pack/particles/block_destruct.json, renders fromatlas.terrainat UVs the engine supplies viavariable.emitter_texture_coordinate, so overriding the particle cannot pick a different texture per block. The only remaining lever - changing a block'sblocks.jsontexture entry - also changes how the block itself renders, which is not what the pack does. Vanilla block models, where Java keeps the particle slot, are hardcoded on Bedrock.Caveats. Global changes to break particles (count, size, motion, tint) are still possible by overriding
minecraft:block_destruct. Only per-block texture selection is unavailable. Some of the blocks the Java pack corrects may already sample a sensible face on Bedrock - worth spot-checking before closing the issue.Sources
Maintained by
tools/vt-diff. Edits inside this block are overwritten on the next run.