Test an Oraxen pack update with a clean client download

Applies to: Oraxen; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

A cached client pack can hide a successful update or make a broken update seem healthy. Compare a clean download with an existing client while keeping server definitions unchanged.

Check the installed content

Oraxen combines server-side item definitions with client resource-pack assets. Check the installed release before copying a recipe or component example, because Minecraft item formats have changed between releases. Work on a staging copy for changes that affect existing player items.

Work through the change

1. Record the installed Oraxen version and the pack build being tested. Save the source assets and generated output together so the comparison uses a reproducible build.
2. Change one disposable staging texture with an unmistakable difference and generate the pack through the supported workflow. Inspect build errors before sharing its download address.
3. Join with a test client that has not cached this pack version and accept the pack. Compare the disposable item with a client that previously used the earlier build.
4. Check the server-provided download settings and any external hosting cache if the clients disagree. Confirm that the downloaded file is the new output rather than changing item IDs to force a visual difference.

Verify the result

Both clients should receive the intended build and show the changed test asset. The server-side item identity and unrelated textures should remain unchanged throughout the comparison.

If the result differs

If a clean client also shows the old asset, inspect the generated file and hosting path. If only the existing client differs, investigate cache identity and the release-supported pack delivery settings.

Keep a recovery path

Restore the earlier assets and pack output together if the new build is invalid. Keep the test change out of valuable items and avoid asking every player to clear unrelated client data during diagnosis.

References and related help

Check the maintainer reference: Oraxen documentation, Oraxen documentation.

Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.