No, the trigger really needs the name of the boss and not just "%s" like in all other triggers (see my other Post). Seems like Blizzard made a mistake there.
Kel'Thuzad phase2_trigger3 and Sapphiron airphase_trigger and deepbreath_trigger were fixed in r4927, so everything should work now.
Cremor is correct. Always copy Transcriptor word for word even if it has 20 spaces between words that is what you need to copy. Obviously Blizzard mucked something up with chat.
1) Version r4928 shows up in game as version 4922.
You used the core version check. The shown version for the core version check only shows the latest revision in which the file Core.lua was changed. But almost all changes only change module files, not the core file.
You have to use the zone version check to get the version number of modules (e.g. do a zone version check for "Naxxramas").
You have to use the zone version check to get the version number of modules (e.g. do a zone version check for "Naxxramas").
Ah ok, thanks for clarifying that.
So here's a thought. As a feature request, I guess, it would be nice if there was an "overall version check" that checked for updates everywhere, to everyone in the raid, no matter what zone they're in -- and did a comparison against the latest known version.
If all raiding members are supposed to be updating BigWigs every week, for example, then there should be a check to see if they're all on the latest version of the entire addon. It doesn't matter at that point whether the raid we're going to on one particular night had changed data or not; the check is to see if they're on the latest version.
The current version checks are useful as far as they go, but from a raid management standpoint it would be most helpful to have a check that compares to the latest version number seen in the raid, no matter what. (And it should check everyone regardless of what zone they're in -- the time you want to be checking people's versions and bugging them to get the upgrade is when the raid is forming, not when everybody's already in the zone.)
They way it currently works, versions would fluctuate whether a person had the instance loaded. For example, someone in Naxx might have the "global version" XXXX whilst someone who hasn't entered yet (only core detected) would have a lower XXYY, because Naxx wasn't loaded yet.
They way it currently works, versions would fluctuate whether a person had the instance loaded. For example, someone in Naxx might have the "global version" XXXX whilst someone who hasn't entered yet (only core detected) would have a lower XXYY, because Naxx wasn't loaded yet.
The core can conceivably perform GetAddOnMetaData("Bigwigs_Naxxramas", "Version") though, to retrieve the version in the ## Version field, or any other ## X-Blah field, and check their versions without actually loading them. You would then just need to maintain a list of Bigwigs LoD modules in the core, or simply iterate over all addons looking for the word "Bigwigs_".
GatherMate does this on GatherMate_Data (LoD addon) to determine if it should auto-import on a newer revision of _Data (if the auto-import option is turned on).
That would require switching from svn:keywords to Curses keyword replacement, and would cause all svn checkouts to not be able to report the correct version.
The core can conceivably perform GetAddOnMetaData("Bigwigs_Naxxramas", "Version") though, to retrieve the version in the ## Version field, or any other ## X-Blah field, and check their versions without actually loading them. You would then just need to maintain a list of Bigwigs LoD modules in the core, or simply iterate over all addons looking for the word "Bigwigs_".
GatherMate does this on GatherMate_Data (LoD addon) to determine if it should auto-import on a newer revision of _Data (if the auto-import option is turned on).
Firstly, touching the TOC every time a change is made for the version field is not a solution, so that's out the window.
Curse's X-whatever, that's a nice idea, but what if I made changes to Naxx, then someone committed a change to an old module like Sunwell (like the other day). Anyone doing a global version would think they are out-of-date because of 1 person with Sunwell still installed (and auto updated). It would mean having a list of all Core modules, then I'm not sure how far this line I want to go for a simple version check.
What about just a check for "core and WotLK" modules? That's what 99% of people care about on a daily basis right now, for a boss mod. As a raid leader, if I know that people are up to date in those, I'm happy, and the raid runs more smoothly. Optional modules don't need to be looked at in a generic version check; if someone is running an older raid like Sunwell, they can do the check just for that zone's module.
While we're on the topic... is it possible to change the display of all version checks to list the people who do not have the module(s) being checked? It's a bit of a pain to see that 23 people have the addon, and then sit there for 2 minutes trying to read the (non-alphabetical) list of names to figure out just who is missing it. If the list displayed all the names in the raid, and showed who didn't have the addon/module at all, that would be great; I believe oRA2 has this sort of display.
Thanks for any changes that can be done to help out in this area. It's somewhat tedious, but from a day to day raiding perspective these version checks are the part of the addon that raid leaders interact with the most; anything that can improve that experience would be a big help.
Not to derail the thread, but what's the big deal with version checks? There's not really anything in the current WotLK content that even requires a boss mod, let alone requires everyone to have the same version of a boss mod. Also, a version check isn't even necessarily a guarantee that someone has the latest version or even a version; it's extremely simple to send a fake version response (there are even addons released to do this), and in fact I have done exactly that to every guild I've ever been in that's required an addon I didn't want to use.
There's not really anything in the current WotLK content that even requires a boss mod, let alone requires everyone to have the same version of a boss mod.
That's a flawed argument though, because future content and raid instances makes it relevant.
That's a flawed argument though, because future content and raid instances makes it relevant.
The situations that "require" any kind of syncing to enhance functionality are extremely few and far between, and are still not required to successfully complete the encounter. For example, for the Kalecgos encounter in Sunwell Plateau it may be useful to have your boss mod sync with other raid members to keep track of the health for both the dragon Kalecgos and the human Kalecgos, but it's also quite possible to do that without boss mod syncing or any addon at all, by having people call it out over voice chat or type it in raid chat. Not only does current content not include anything like this, but it is pretty much guaranteed that Blizzard will never add content that cannot be done reasonably simply without a syncing boss mod. Boss mods are a convenience, not a necessity.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumKel'Thuzad phase2_trigger3 and Sapphiron airphase_trigger and deepbreath_trigger were fixed in r4927, so everything should work now.
-
View User Profile
-
View Posts
-
Send Message
Forum Moderator1) Version r4928 shows up in game as version 4922.
2) The main BigWigs info page has an outdated link to this thread, which does not work.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumYou used the core version check. The shown version for the core version check only shows the latest revision in which the file Core.lua was changed. But almost all changes only change module files, not the core file.
You have to use the zone version check to get the version number of modules (e.g. do a zone version check for "Naxxramas").
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorFixed.
I need translators to localize the main pages in their language.
http://www.wowace.com/projects/big-wigs/pages/
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumSo I think I'll stick to triggers and boss spells ;)
But another Thread came in my mind. Seems like leXin is pretty good in translating text, so you maybe ask him.
Ah ok, thanks for clarifying that.
So here's a thought. As a feature request, I guess, it would be nice if there was an "overall version check" that checked for updates everywhere, to everyone in the raid, no matter what zone they're in -- and did a comparison against the latest known version.
If all raiding members are supposed to be updating BigWigs every week, for example, then there should be a check to see if they're all on the latest version of the entire addon. It doesn't matter at that point whether the raid we're going to on one particular night had changed data or not; the check is to see if they're on the latest version.
The current version checks are useful as far as they go, but from a raid management standpoint it would be most helpful to have a check that compares to the latest version number seen in the raid, no matter what. (And it should check everyone regardless of what zone they're in -- the time you want to be checking people's versions and bugging them to get the upgrade is when the raid is forming, not when everybody's already in the zone.)
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorThey way it currently works, versions would fluctuate whether a person had the instance loaded. For example, someone in Naxx might have the "global version" XXXX whilst someone who hasn't entered yet (only core detected) would have a lower XXYY, because Naxx wasn't loaded yet.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe core can conceivably perform GetAddOnMetaData("Bigwigs_Naxxramas", "Version") though, to retrieve the version in the ## Version field, or any other ## X-Blah field, and check their versions without actually loading them. You would then just need to maintain a list of Bigwigs LoD modules in the core, or simply iterate over all addons looking for the word "Bigwigs_".
GatherMate does this on GatherMate_Data (LoD addon) to determine if it should auto-import on a newer revision of _Data (if the auto-import option is turned on).
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorFirstly, touching the TOC every time a change is made for the version field is not a solution, so that's out the window.
Curse's X-whatever, that's a nice idea, but what if I made changes to Naxx, then someone committed a change to an old module like Sunwell (like the other day). Anyone doing a global version would think they are out-of-date because of 1 person with Sunwell still installed (and auto updated). It would mean having a list of all Core modules, then I'm not sure how far this line I want to go for a simple version check.
-
View User Profile
-
View Posts
-
Send Message
Project AuthorI just woke up, so maybe I'm misunderstanding, but...this wouldn't work?
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorI think that works yes, but that brings us to the same problem as #2. It would essentially be the same thing as the X-curse metadata.
-
View User Profile
-
View Posts
-
Send Message
Project AuthorWhat about just a check for "core and WotLK" modules? That's what 99% of people care about on a daily basis right now, for a boss mod. As a raid leader, if I know that people are up to date in those, I'm happy, and the raid runs more smoothly. Optional modules don't need to be looked at in a generic version check; if someone is running an older raid like Sunwell, they can do the check just for that zone's module.
While we're on the topic... is it possible to change the display of all version checks to list the people who do not have the module(s) being checked? It's a bit of a pain to see that 23 people have the addon, and then sit there for 2 minutes trying to read the (non-alphabetical) list of names to figure out just who is missing it. If the list displayed all the names in the raid, and showed who didn't have the addon/module at all, that would be great; I believe oRA2 has this sort of display.
Thanks for any changes that can be done to help out in this area. It's somewhat tedious, but from a day to day raiding perspective these version checks are the part of the addon that raid leaders interact with the most; anything that can improve that experience would be a big help.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThat's a flawed argument though, because future content and raid instances makes it relevant.
The situations that "require" any kind of syncing to enhance functionality are extremely few and far between, and are still not required to successfully complete the encounter. For example, for the Kalecgos encounter in Sunwell Plateau it may be useful to have your boss mod sync with other raid members to keep track of the health for both the dragon Kalecgos and the human Kalecgos, but it's also quite possible to do that without boss mod syncing or any addon at all, by having people call it out over voice chat or type it in raid chat. Not only does current content not include anything like this, but it is pretty much guaranteed that Blizzard will never add content that cannot be done reasonably simply without a syncing boss mod. Boss mods are a convenience, not a necessity.