You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What are you trying to do, and what do you expect to happen?
In Minecraft, all non-empty strings are valid bone names. I expect Blockbench to support this behavior.
What happens instead?
Bone names are transformed, disrupting block, animation, render controller, and culling definitions. The simplest (and most harmful) example involves .s. Periods are stripped from bone names, leaving links to such names in other definitions invalid.
A more radical example could be: banister.geo.json. When this geometry definition is opened and saved in Blockbench, the bone name `!@#$%~^&*()_+-={}[]|;:'",<.>/?∆🦋 is transformed to __. However, `!@#$%~^&*()_+-={}[]|;:'",<.>/?∆🦋 is a valid bone name in the engine.
Model format in which the issue occurs
Bedrock Block, Bedrock Entity
Blockbench variant
Program
Blockbench version
4.12.0 Beta 1
Operating System
macOS Sequoia 15.2
Installed Blockbench plugins
N/A
The text was updated successfully, but these errors were encountered:
Any reason why you need to have support for all special characters in bone names? They are fine when just used in a model, but will break the asset as soon as you need to reference those bones in animations, render controllers etc. Blockbench sanitizes bone names to prevent issues like that.
I can add supports for periods though. It looks like those are supported everywhere for bone names.
What are you trying to do, and what do you expect to happen?
In Minecraft, all non-empty strings are valid bone names. I expect Blockbench to support this behavior.
What happens instead?
Bone names are transformed, disrupting block, animation, render controller, and culling definitions. The simplest (and most harmful) example involves
.
s. Periods are stripped from bone names, leaving links to such names in other definitions invalid.A more radical example could be: banister.geo.json. When this geometry definition is opened and saved in Blockbench, the bone name
`!@#$%~^&*()_+-={}[]|;:'",<.>/?∆🦋
is transformed to__
. However,`!@#$%~^&*()_+-={}[]|;:'",<.>/?∆🦋
is a valid bone name in the engine.Model format in which the issue occurs
Bedrock Block, Bedrock Entity
Blockbench variant
Program
Blockbench version
4.12.0 Beta 1
Operating System
macOS Sequoia 15.2
Installed Blockbench plugins
N/A
The text was updated successfully, but these errors were encountered: