> ## Documentation Index
> Fetch the complete documentation index at: https://docs.purpify.host/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot Bedrock add-on errors

> Fix incompatible behavior packs, resource packs, dependencies, experiments, and script errors on a Purpify Bedrock server.

Confirm the add-on supports the server version, then check its behavior pack, resource pack, dependencies, and required experiments as one complete installation.

## Match the symptom

| Symptom                              | Likely cause                                                | What to check                                                                |
| ------------------------------------ | ----------------------------------------------------------- | ---------------------------------------------------------------------------- |
| Pack does not appear                 | Invalid archive or incorrect folder structure               | Confirm `manifest.json` is inside the actual pack folder.                    |
| Missing dependency                   | Required behavior or resource pack is absent                | Install every dependency and matching version named by the author.           |
| Purple-and-black or missing textures | Resource pack is missing, inactive, or incompatible         | Reinstall and activate the matching resource pack.                           |
| Script or API error                  | Required experiment is disabled or the API changed          | Check the author's version requirements and [Beta APIs](/bedrock/beta-apis). |
| Duplicate UUID or version conflict   | Two installed pack manifests conflict                       | Keep only the intended compatible release after backing up.                  |
| Server fails after installation      | Invalid pack, dependency failure, script crash, or conflict | Restore the pre-installation backup and add packs one at a time.             |

## Isolate the add-on safely

<Steps>
  <Step title="Preserve the error">
    Copy the first relevant console message and the add-on name. Do not rely only on the final process-exit line.
  </Step>

  <Step title="Restore a clean test point">
    Stop the server and create a backup. When available, restore the backup made before the add-on was installed.
  </Step>

  <Step title="Verify the complete pack set">
    Confirm the behavior pack, resource pack, dependency versions, and server version match the author's requirements.
  </Step>

  <Step title="Enable only required experiments">
    Turn on Beta APIs or another experiment only when the add-on documentation requires it. Restart after changing world experiments.
  </Step>

  <Step title="Install and test one change">
    Install one add-on or dependency set, restart, then test its main feature before adding another pack.
  </Step>
</Steps>

<Warning>
  Removing an add-on does not necessarily remove its custom world data safely. Restore a backup or follow the author's uninstall procedure when the pack adds blocks, entities, items, or scripted data.
</Warning>

## Information to collect

When the problem continues, record:

* Bedrock server version
* Add-on name and version
* Behavior and resource pack versions
* Enabled experiments
* First relevant console error
* Whether the problem also occurs on a fresh test world

See [Install behavior and resource packs](/server/install-addons) for the normal installation workflow.