Basing it on how much work I have to do (work-work, not hobby-work like WUU :( ), I'm guessing we'll let 1.6 live past christmas, with some minor updates to fix the worst problems. I'm looking at the WoWAce code right now, as I've found some bugs, so I might do the ext/noext as different sites split in 1.6 already :)
I've noticed for a while now that mods have not been updating as often. While this may be related to the authors, I'm thinking there's something else going on here. I'm not sure if it's even WUU but since I use WUU to update, I posted here. Hope it's appropriate.
The one thing that really grabbed my attention is how Omen's Threat Meter seems to be updating at WoWAce but the version remains the same. (55025) Virtually all other users I play with have far more updated versions. I remember checking files.wowace.com and noticing that Omen was updated 4 days ago but showing 55025, and today it shows "updated less than a minute ago" or something and still sitting at 55025. WUU reads Omen as 55025 and never updates it. I get the feeling this is true for other mods as well. What could be causing this? Should I post this elsewhere?
I've noticed for a while now that mods have not been updating as often. While this may be related to the authors, I'm thinking there's something else going on here. I'm not sure if it's even WUU but since I use WUU to update, I posted here. Hope it's appropriate.
The one thing that really grabbed my attention is how Omen's Threat Meter seems to be updating at WoWAce but the version remains the same. (55025) Virtually all other users I play with have far more updated versions. I remember checking files.wowace.com and noticing that Omen was updated 4 days ago but showing 55025, and today it shows "updated less than a minute ago" or something and still sitting at 55025. WUU reads Omen as 55025 and never updates it. I get the feeling this is true for other mods as well. What could be causing this? Should I post this elsewhere?
I'm not sure what externals are, but all I know is that I see people running around with Omen 554xx and I think today I saw 55647 or something like that. Is this different than 55025 or is it 55025 with external updates? Also, how do I get WUU to update Omen when these externals get updated?
Externals are libraries of code that may be used by many different mods. These can be embedded in each mod package, which means Wow loads them multiple times, which increases load times, among other things. Or they can be "dis-embedded", so that only one copy of each library is loaded (because only one exists in your addons folder, at least as far as WoW is concerned). You do the latter by selecting the "no externals" option in WUU preferences. You'll end up with a lot more folders in the root of your addons folder, but don't let that bother you. With the no externals option set, WUU will update the libraries automatically as needed.
I'm not sure what externals are, but all I know is that I see people running around with Omen 554xx and I think today I saw 55647 or something like that. Is this different than 55025 or is it 55025 with external updates? Also, how do I get WUU to update Omen when these externals get updated?
Omen is updated when externals are updated (didn't you just update?). Also, the version you see reported is not Omen, but one of the externals named Threat-1.0.
So by selecting the no externals option in WUU, all those embedded libraries will be loaded automatically, but as seperate addons, with their own folders? That way only one copy of each will exist, and any mod that needs these libraries will be able to use the same lone copy if needed?
So by selecting the no externals option in WUU, all those embedded libraries will be loaded automatically, but as seperate addons, with their own folders? That way only one copy of each will exist, and any mod that needs these libraries will be able to use the same lone copy if needed?
As of now, I don't think so. It seems to me you have to download those manually. (Or use WAU to switch to non-embed.)
I did actually try this. It didn't behave any differently. I tried renaming my AddOn folder and forcing an update on everything, and the results were slightly different. Although no external libraries were embedded into the mod folders for mods that use them, none of these externals were downloaded at all. Almost all of my mods failed to load in the game due to them missing. WUU apparently needs to have you download/install each external library seperately.
I guess the no-ext option is for those who maintain these libraries on their own.
So here are two questions. One, if each mod has it's own external libraries, meaning some of these libraries will have multiple copies, each embedded in various mod folders, are they all loaded as seperate mods or does WoW ignore any more copies of a library once it has been loaded?
And two, what about Omen? Why is WUU not updating it's externals if the no-ext option is turned off? It reads 55025 instead of 55025.xx as I assume it should. Omen has not updated in two weeks or so and I am falling behind on its updates. Is this happening to everyone?
The thing is, with the no-ext option off, WUU should update the extension libraries I would think. It has not been doing that lately. I decided to force an update for Omen and it seems to have done the trick. I am no longer receiving newer version available messages from everyone I play with.
I also noticed a couple weeks ago it stopped updating Omen, Omen itself has not been updated since Nov 16th but the latest version with libs is Omen-r55025.34.zip but WUU is pulling back the older Omen-r55025.zip. The version columns say 55025, I think it uses to say 55025.XX. How does WUU determine the latest version, I think something must have changed with that code.
The thing is, with the no-ext option off, WUU should update the extension libraries I would think. It has not been doing that lately. I decided to force an update for Omen and it seems to have done the trick. I am no longer receiving newer version available messages from everyone I play with.
I am having the exact same problem, and noticed it the same way you did. This is happening to a lot of mods.
WUU 1.6.483 (released on 21-11-07) shows 27/71 mods out of date.
WUU 1.6.488 (released on 02-12-07) shows 3/71 mods out of date.
Seems to be a bug in the new version.
Guess I will be using WUU 1.6.483 until this is fixed, hope there weren't too many bug fixes since then. :)
I just noticed I was wrong about Omen, now I'm even further behind... Yes, it seems to me as well that WUU is pulling 55025 Omen without updating extensions. I am forcing all mods to update but I may be setting myself further behind on revisions due to this issue. I'm glad other people are finally noticing this. I'll try 1.6.483 and see how it works out for me. Thanks for the heads up!
Update: 1.6.483 did the trick! Extension updates are working again! Tons of updates to say the least. =P
* After One-Button now worksreliable for me, i would like to have the chance to start WUU with a commandline of one-button-update and then quit itself again, preferably running minimized.
* Is there a chance to be able to hide the Libraries or "secondary"-Addons, the same way as Outdated and ignored ones can be hidden ? (even if this means, i would have to mark them by hand )
maybe its a first step to be able to Show/Hide any "site" not only [outdated], [related], ... since you are going to implement the ext/onext stuff anyways.
* Are you thinking about an option to show which addon is ENABLED for what Accoutn/Char ?
* Another Idea is to parse reverse dependencies and make an advice, if one Addon is NOT used by another, so it can be deleted (if it has been marked as Lib or Secondary) - and to see if this addon is used by any other addon ?
I can imagine, you have lots to do, but since its soon Christmas, I felt like placing a wish ;-)
Yeah, I actually was finally coming in to post on this issue. I think the last time I saw an Externals update of any kind was about a month ago, same time as 488 was released.
For whatever reason, 488 isn't checking externals and updating them at ALL. It's caused some seriously odd things to occur too.
Going to fall back to 483 until Lejordet gets less busy and can take a look at it.
Basing it on how much work I have to do (work-work, not hobby-work like WUU :( ), I'm guessing we'll let 1.6 live past christmas, with some minor updates to fix the worst problems. I'm looking at the WoWAce code right now, as I've found some bugs, so I might do the ext/noext as different sites split in 1.6 already :)
The one thing that really grabbed my attention is how Omen's Threat Meter seems to be updating at WoWAce but the version remains the same. (55025) Virtually all other users I play with have far more updated versions. I remember checking files.wowace.com and noticing that Omen was updated 4 days ago but showing 55025, and today it shows "updated less than a minute ago" or something and still sitting at 55025. WUU reads Omen as 55025 and never updates it. I get the feeling this is true for other mods as well. What could be causing this? Should I post this elsewhere?
This is due to externals getting updated.
http://files.wowace.com/Omen/no-ext/ Omen-r55025.zip 2007-Nov-16
http://files.wowace.com/Omen Omen-r55025.29.zip 2007-Dec-17
No Omen update since 55025 on Nov 16th, just externals.
Externals are libraries of code that may be used by many different mods. These can be embedded in each mod package, which means Wow loads them multiple times, which increases load times, among other things. Or they can be "dis-embedded", so that only one copy of each library is loaded (because only one exists in your addons folder, at least as far as WoW is concerned). You do the latter by selecting the "no externals" option in WUU preferences. You'll end up with a lot more folders in the root of your addons folder, but don't let that bother you. With the no externals option set, WUU will update the libraries automatically as needed.
Omen is updated when externals are updated (didn't you just update?). Also, the version you see reported is not Omen, but one of the externals named Threat-1.0.
As of now, I don't think so. It seems to me you have to download those manually. (Or use WAU to switch to non-embed.)
I guess the no-ext option is for those who maintain these libraries on their own.
So here are two questions. One, if each mod has it's own external libraries, meaning some of these libraries will have multiple copies, each embedded in various mod folders, are they all loaded as seperate mods or does WoW ignore any more copies of a library once it has been loaded?
And two, what about Omen? Why is WUU not updating it's externals if the no-ext option is turned off? It reads 55025 instead of 55025.xx as I assume it should. Omen has not updated in two weeks or so and I am falling behind on its updates. Is this happening to everyone?
Yes, Omen has not been updated. Threat-1.0 has. And with no-ext you have to install that one to make Omen work (probably with some other libs too)
I am having the exact same problem, and noticed it the same way you did. This is happening to a lot of mods.
WUU 1.6.483 (released on 21-11-07) shows 27/71 mods out of date.
WUU 1.6.488 (released on 02-12-07) shows 3/71 mods out of date.
Seems to be a bug in the new version.
Guess I will be using WUU 1.6.483 until this is fixed, hope there weren't too many bug fixes since then. :)
Update: 1.6.483 did the trick! Extension updates are working again! Tons of updates to say the least. =P
are you accepting wishes still ?
* After One-Button now worksreliable for me, i would like to have the chance to start WUU with a commandline of one-button-update and then quit itself again, preferably running minimized.
* Is there a chance to be able to hide the Libraries or "secondary"-Addons, the same way as Outdated and ignored ones can be hidden ? (even if this means, i would have to mark them by hand )
maybe its a first step to be able to Show/Hide any "site" not only [outdated], [related], ... since you are going to implement the ext/onext stuff anyways.
* Are you thinking about an option to show which addon is ENABLED for what Accoutn/Char ?
* Another Idea is to parse reverse dependencies and make an advice, if one Addon is NOT used by another, so it can be deleted (if it has been marked as Lib or Secondary) - and to see if this addon is used by any other addon ?
I can imagine, you have lots to do, but since its soon Christmas, I felt like placing a wish ;-)
Ciao,
Barracuda
Yeah, I actually was finally coming in to post on this issue. I think the last time I saw an Externals update of any kind was about a month ago, same time as 488 was released.
For whatever reason, 488 isn't checking externals and updating them at ALL. It's caused some seriously odd things to occur too.
Going to fall back to 483 until Lejordet gets less busy and can take a look at it.
E.g.:
ItemBonusLib ItemBonusLib
Instead:
ItemBonusLib Lib:ItemBonusLib
?