forBaseMapping

Stable short name keyed by the (model, base-item) pair, with no predicate component. Equivalent to forBaseMapping with an empty signature. Retained so unconditional callers stay terse and so historical identifiers (no predicate) are produced byte-for-byte as before.

---

Stable short name keyed by the (model, base-item, predicate-signature) triple.

Use this for the attachable file path and the Geyser bedrock_identifier, both of which are per-mapping not per-model. Two mappings that share a Java model but target different Bedrock base items will get different short names here, so each attachable lives at its own file path and gets its own identifier in the Geyser mappings.

Why the predicate signature is part of the key

A single Java model under a single base item can produce several Geyser definitions that differ only by predicate — the canonical case is a crossbow whose charge_type=arrow and charge_type=rocket branches resolve to the same custom model. Geyser keys every custom item definition by its bedrock_identifier and rejects duplicates ("conflicts with another custom item definition with the same bedrock identifier"), silently dropping all but the first. Folding the predicate signature into the hash gives each predicate variant a distinct identifier (and a distinct attachable file), so Geyser registers them all.

Pass null or an empty string for unconditional mappings; the hash input is then identical to the legacy (model, base) form, so existing Bedrock client caches for predicate-free items stay valid across upgrades.