Problems encountered during version upgrade

Questions
12

Good question! Instances can sometimes be little rebels when you try to sync them back to an older version. Here’s the game plan:

  1. Backup your instance’s folder first. Even though it’s gotten fancy with 2.6.2.0, back that up because, well, we can’t trust tech!

  2. Fresh install with 2.6.1.6 if you haven’t done this already (see steps above).

  3. Repair the instance to match the current AMP version. In AMP’s web interface, go to the ADS panel (Instance Manager), and find the rebellious instance. Then, use the “Repair” button—this forces AMP to re-evaluate the version and try syncing things back to the same.

Instances should sync back to the correct version if running the older AMP build, but if it still acts up, poke me, and we’ll poke it back! :blush:

:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback