Mapping api v2 predicate property fishing_rod_cast or crossbow charged Not compatible with Java players

[llsssssdsfa3t24wfeerwds]

Describe the bug

Mapping api v2 predicate property fishing_rod_cast or crossbow charged Not compatible with Java players
For example, if I use a fishing rod with a Java player, the condition "property": "fishing_rod_cast",

"type": "condition" will not work, and the model will remain as is. However, if I use it as a Bedrock player and use a fishing rod, the cast condition will work.

To Reproduce

Mapping api v2 predicate property fishing_rod_cast or crossbow charged Not compatible with Java players
For example, if I use a fishing rod with a Java player, the condition "property": "fishing_rod_cast",

"type": "condition" will not work, and the model will remain as is. However, if I use it as a Bedrock player and use a fishing rod, the cast condition will work.

Expected behaviour

Mapping api v2 predicate property fishing_rod_cast or crossbow charged Not compatible with Java players
For example, if I use a fishing rod with a Java player, the condition "property": "fishing_rod_cast",

"type": "condition" will not work, and the model will remain as is. However, if I use it as a Bedrock player and use a fishing rod, the cast condition will work.

Screenshots / Videos

2026-04-02.21-18-42.-.Trim.mp4

Server Version and Plugins

No response

Geyser Dump

No response

Geyser Version

Build #1109 · 30‏/3‏/2026

Minecraft: Bedrock Edition Device/Version

No response

Additional Context

No response

[onebeastchris]

Hello! There seems to be a translation or understanding issue here - Geyser mappings have no effect on Java players by design. Can you rephrase it to better show what the issue is?
If you are talking about the missing fishing hook "line", that is not something we can resolve on Geyser's end unfortunately