Back up Interface/AddOns for code and WTF for saved data. Replace one addon at a time with the game closed, keep one active copy, and verify controls and persistence in the current client.
Back up code and saved data separately
Addon source lives under Interface/AddOns. Persistent game settings and addon saved variables live under the client’s WTF directory. Copying only the addon folder does not necessarily preserve your notes or settings.
Close the game before making a backup. Keep the backup outside the active client directories and label it with the date and addon version. Saved variables may contain personal notes or character details; keep that backup private.
Read the release you are about to install
Confirm the addon name, published version, client notes, and dependencies. A community page hosts the creator’s published copy; changes still being edited in their private workspace are not automatically in that download.
Compare the documented behavior with the version you use. If the update changes commands or saved-data structure, keep the earlier source and data backup together so you can restore the matching pair.
Replace one addon while the game is closed
Extract the new ZIP into a temporary folder. Inspect the matching TOC and Lua files, move the old addon folder into your backup location, and copy the replacement into Interface/AddOns. Keeping stale files in the active folder can hide packaging mistakes.
Use one active folder for the addon. Renaming the old folder and leaving it beside the new one can load both manifests. The optional browser installer can back up owned packages, but protected game directories may require a manual ZIP install.
Verify the behavior you rely on
Restart the client and confirm that the intended addon version is enabled. Open its main interface, exercise a documented control, move it if supported, and reload to check persistence. Test combat-related displays both outside and inside combat when appropriate.
- Confirm your saved notes or settings remain present.
- Check command names and controls against the new description.
- Check the first Lua error before making additional changes.
- Repeat the original task that motivated the update.
- Keep the backup until the addon has survived a normal play session.
Roll back source and data carefully
If the update breaks the behavior you need, close the game and restore the previous addon folder. Restore its matching saved-data backup only when needed; doing so discards notes or settings created after that backup.
Send the creator or builder the exact version and failure steps. If you publish addons yourself, publish a corrected release only after reviewing and testing it. Unpublishing stops future downloads from your public page, while copies already downloaded remain with their recipients.