[SOLVED] Correct API version for Update 1.6.x, but client still lists addons as out of date

shiva7663 · March 2015

I have noticed that newly updated addons for 1.6 are still shown as out of date even though their .txt files show a reference to the correct API version. Anyone know what's happening here? Was there some crucial change in how the client software detects addon API compliance?

The only exception I've seen so far is that Wykkyd's Gaming Suite addons are listed as current.

shiva7663 · March 2015

Further data to follow.

Garkin · March 2015

Can you write me which addons are listed as outdated?

Can you check if they really have the following line in addon manifest (.txt)?

## APIVersion: 100011

Make sure that there is no space between API and Version.

shiva7663 · March 2015

Okay, that's interesting. A recent example, "Lost Treasures", shows "100010" in its text file on my system, even after uninstalling and reinstalling it via Minion. However, a manual download of the .zip shows the correct "100011" in its .txt file.

So, it appears that I'm dealing with a Minion issue, where it reports a completed update, but doesn't actually load in the new files.

I'll follow up with ESOUI.com support.

shiva7663 · March 2015

Issue resolved. Minion was set to look for addons at the standard default location, but the ESO Client was looking for addons on a different hard drive, a non-standard location. I don't know how the ESO Client determines where to look; it doesn't seem to be in the Windows 7 system registry.

Anyway, I'm back to normal.