Skip to main content
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

​
Isolate the add-on safely

1

Preserve the error

Copy the first relevant console message and the add-on name. Do not rely only on the final process-exit line.
2

Restore a clean test point

Stop the server and create a backup. When available, restore the backup made before the add-on was installed.
3

Verify the complete pack set

Confirm the behavior pack, resource pack, dependency versions, and server version match the author’s requirements.
4

Enable only required experiments

Turn on Beta APIs or another experiment only when the add-on documentation requires it. Restart after changing world experiments.
5

Install and test one change

Install one add-on or dependency set, restart, then test its main feature before adding another pack.
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.

​
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 for the normal installation workflow.