Skip to content

Bone parent resolution is case-sensitive, inconsistent with MCBE #3652

Description

@wcg21444

What are you trying to do, and what do you expect to happen?

Import a standard Bedrock Entity model (piglin.geo.json) where bone "parent" field casing differs from the target bone "name": leftItem is expected to be parented under leftarm, matching MCBE engine behavior which treats bone names case-insensitively.

{
    "name": "leftarm",
    "parent": "body",
    "pivot": [5, 22, 0],
    "cubes": [
        {"origin": [4, 12, -2], "size": [4, 12, 4], "uv": [32, 48]},
        {"origin": [4, 12, -2], "size": [4, 12, 4], "uv": [48, 48], "inflate": 0.25}
    ]
},
{
    "name": "leftItem",
    "parent": "leftArm",
    "pivot": [ 6.0, 15.0, 1.0 ]
}

What happens instead?

BlockBench attaches leftItem to root instead of leftarm due to case-sensitive name matching, breaking the intended parent-child hierarchy. The resulting bone tree does not match what MCBE produces at runtime, and the user receives no warning or indication that the hierarchy was modified.
The following image shows the incorrect result in BlockBench — leftItem appears as a direct child of root rather than under leftarm:
Image

Model format in which the issue occurs

Bedrock Model

Blockbench variant

Program

Blockbench version

5.1.4

Operating System

Windows 11

Installed Blockbench plugins

No response

Are there any console errors?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugAn issue, where the program does not do what it is supposed to

    Projects

    Status
    Unreleased

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions