id mappings custom model data : definition threshold

[sdawd2q3e]

Describe the bug

There seems to be an issue with item mappings when using range_dispatch with custom_model_data thresholds.

For example, I have the following mapping:

{
"bedrock_identifier": "fairyset_bow",
"bedrock_options": {
"display_handheld": true,
"icon": "fairyset_bow"
},
"display_name": "Fairy Bow",
"model": "minecraft:bow",
"predicate": {
"property": "custom_model_data",
"threshold": 1001,
"type": "range_dispatch"
},
"type": "definition"
}

The item is not registered or detected correctly by the server when using this mapping.

I believe the issue may occur when the Java resource pack contains both range_dispatch threshold values (floats) and item model definitions in the same model file. It looks like the item model definition may be taking priority over the threshold-based mapping.

In my opinion, both item model definitions and threshold-based definitions should work correctly, since they are both valid and properly defined in the model.

The strange part is that the item works correctly when using the legacy custom_model_data mapping instead.

To Reproduce

Create an item using a Java resource pack model that contains both item model definitions and range_dispatch thresholds.
Add a mapping using a range_dispatch predicate with a custom_model_data threshold (for example 1001).
Start the server and load the resource pack.
Give yourself the item.
Notice that the item is not detected or mapped correctly.

Expected behaviour

The item should be detected and mapped correctly when using a range_dispatch predicate with a custom_model_data threshold, just as it works with legacy custom_model_data mappings.

Additional information

As a workaround, I had to use the legacy format below, which works correctly:

{
"bedrock_identifier": "fairyset_bow",
"bedrock_options": {
"display_handheld": true,
"icon": "fairyset_bow"
},
"custom_model_data": 1001,
"display_name": "Fairy Bow",
"type": "legacy"
}

Screenshots / Videos

Server Version and Plugins

No response

Geyser Dump

No response

Geyser Version

Build #6435 · 1‏/6‏/2026:

Minecraft: Bedrock Edition Device/Version

No response

Additional Context

No response

[onebeastchris]

The two mappings you shared are different:

• The definition type expects the item_model to match first, and then they would also match additional predicates, such as custom model data
• The legacy type only works if you don't have an item_model set, and would then compare custom model data

The screenshot you shared shows that the plugin uses the item model minecraft:fairyset/bow - it's not recommended to put things into the minecraft namespace, but still possible to do so

Closing since this works as expected