Authors CurseForge

Omen itself is working fine for me. I have been updating it a few times a week since 2.4 hit. Here is how I have been updating it:

I exit WoW, delete the Omen folder, log back into WoW - all the way to in-game. I then exit WoW, download Omen and extract it, and go back in-game. Say I do this for 5 subsequent versions, it still shows the old version!

Why? What am I doing wrong?

You're not downloading the new version?

You're using disembedded libs and you're not updating Threat-2.0?

If Omen gets an update it doesnt mean Threat-2.0 got an update. And the revision of Threat-2.0 is shown, as that is the "threat gathering and sharing part" that makes Omen getting data to display. Its much more important to have a update Threat-2.0(its either included in Omen our disembedded) than having a updated Omen.

That means EVEN if Omen gets an update it does NOT mean the revision number goes up. Would be really stupid anyway when dozens of hundreds of people update to a new revision just because some korean localisations goes inside(ok Koreans might want to update then :P )

Quote from saikonate »

You're not downloading the new version?

I am. The version number displayed in-game isn't updated. However, when I go into the patch notes (notepad file) in the Omen folder, the latest version (the one I downloaded) is shown. This is not an issue of Omen not downloading properly.

Quote from Seerah »

Is Omen still present when you log back into the game between reinstalls?

I've tried both ways.

Quote from Seerah »

ie, are you using Vista with WoW installed to Program Files and/or do you have more than one copy of WoW installed?

I am using Windows XP SP 2, and it's a pretty fresh install. I have one copy of WoW installed.

Quote from Snago »

You're using disembedded libs and you're not updating Threat-2.0?

I'm not sure what this means, but thanks. I'm downloading it from files.wowace.com, and extracting as is normally done.

Quote from Matrix110 »

If Omen gets an update it doesnt mean Threat-2.0 got an update. And the revision of Threat-2.0 is shown, as that is the "threat gathering and sharing part" that makes Omen getting data to display. Its much more important to have a update Threat-2.0(its either included in Omen our disembedded) than having a updated Omen.

That means EVEN if Omen gets an update it does NOT mean the revision number goes up. Would be really stupid anyway when dozens of hundreds of people update to a new revision just because some korean localisations goes inside(ok Koreans might want to update then :P )

Although I don't know what disembedded means in this case (I'm not that techy or into mods), this is the answer I was looking for. Thanks.

Addons here on wowace often use different libaries.
The concept of a Libary is basically "Put Stuff that some Addons need in 1 Addon that can get used by other Addons to realise some more complex task(s) without having to write it yourself".
This concept has quite some advantages, for example normally Libaries are more efficent coded than when everyone has to implement this task in their own way. Another one is when 20 Addons use this Libary then its only 1 time there and not 20 times when everyone has to write it themself.

Problem is everyone needs those Libaries to run the mod:

To do that you can either have these Libaries embedded, so they are inside the "libs" or "Libs" folder in each AddOn. This is best for the people with a few AddOns and easiest for distribution, as the mod runs out of the box.

Some people though use lets say 100 AddOns, if these 100 Addons all need Libary X. You would have this Libary X in 100 versions(some older some new etc. etc.) which adds more files to your Interface folder and delays Loadingtime a bit as the Libaries first have to "find out" which Libary is the most recent one so only it gets used. (The Loading speed often isnt noticeably shorter).
So some people, especially developers have these Libaries as their own AddOns inside the Interface/AddOns folder. So the libary is DISEMBEDDED.

If you are not using a external Updater you should NOT bother with this at all. Many External Updaters already take care of disembedding and do it automatically if configured like that.

Besides, there is no need to exit WoW to update an addon you already use.
Delete the old folder, put new content in, and type /reloadui

Most of the time updating an addon does not require restarting WoW.exe. However, if any new files are added that weren't present before, you will need to restart WoW in order for it to see the new files. Deleting an old file and adding a new file with the same name doesn't count as adding a new file.