Test translated items before publishing a Java resource pack
ViaVersion translates network protocol data; it is not a resource-pack converter. A custom item that looks correct on the native server client can display a fallback model or different behaviour on another supported version. Check the cosmetic feature itself rather than treating a successful login as complete compatibility.
Record the starting point
Prepare a small private test area containing the exact items, menus and interactions used by your pack. Record the pack release and its intended client versions. Keep the existing pack URL and hash so the previous presentation can be restored without changing inventories.
Work through the change
- Use the native server client to confirm that the resource pack downloads and that the test item works before involving translation. A broken download is independent of ViaVersion.
- Repeat with the oldest and newest clients in your published support range. Accept the pack where supported and compare inventory icons, held models, placement and menu clicks.
- Record a fallback as a presentation limitation rather than replacing the real item with a different identifier on the live server. Ask the pack or custom-item maintainer about its supported client formats.
- Decide whether to publish the limitation, adjust the pack through its documented process, or narrow the permitted client range. Retest after the chosen change.
Check the result
Players should know which versions receive the full presentation and which receive a fallback. Verify that clicking or moving the item does not duplicate it or lose it during the trial. Keep screenshots labelled with client versions so two different renderers are not mistaken for changing server data.
If the result differs
If every client sees the wrong model, inspect the resource-pack URL, hash and pack configuration first. If only translated clients differ, collect the client version, item plugin build and ViaVersion build. Avoid submitting a full paid resource pack in a public issue.
Restore the previous pack reference if the updated asset breaks the native client. Keep the test items isolated and remove only those created for the trial. Do not roll back an entire player inventory because a model rendered incorrectly.