How does the BigWigs profile function work? When I activate the boss modules, and then pick another profile (default), it disables them. Then when I choose my character, it enables them again. However, as soon as I logout, all the boss mods are disabled on my character's profile. Is there any way to save the active bossmods so I don't have to turn each one on every time I login?

Never used BigWigs before. Installed it today and I get no icon anywhere. /bw icon says icon is disabled. /bw just about anything says that thing is disabled.

Tried newest version off Curse, as well as the r9604 off wowace. Am I just missing something?

Embedded libs of Ace2 are a huge problems. One Ace2 addons can easily break others, and it happens a lot, not only with Bigwigs. If an addon uses version 2.1 of a library and some other uses 2.2, only v2.2 is loaded and there is a chance the addon that is build for the older version will break.

Libraries should keep compatibility from version to version, at least I thought this was the idea behind Ace (not to recode things again and again).

Tekkub, latest BigWigs breaks again some other Ace2 add-ons - it looks as the same problem as in past, different versions of Ace2 libraries. It needs to be finally solved as it is very annoying and ppl will get soon very disappointed by this continous and reappearing problem.

the core lib have some error, so BigWigs can't work for boss at WoW zhCN Client. it's long time.
error in Babble-Boss-2.0 lib. the translate error, for example "\2 32\128". have a simple way to fix the error, replace all "\2 " to "\2" (only for Babble-Boss-2.0 Rev: 6579)...
the new Babble-Boss-2.0 lib i can't fix it.

lots off the plugins for fubar dont work when i have bigwigs loaded.
ive tested it out, when i disable the bigwigs it works

I'm getting the following error when WoW loads:

Error: AceLocale(Bigwigs): No translations registered
File: Interface\AddOns\BigWigs\Version.lua
Line: 81
Count: 1

I also get an error when in an Inst. when one of the "boss-mods" get activated. Unfortunately I did not write the error down, but I do remember it was nothing like the error above. The next time it happens I'll document it.

I have already tried:
deleting BigWigs (including deleting the SavedVariables) and reinstalling
installing an older version of Bigwigs

I'm fully admit that I'm not sure if this is a BigWigs issue or if one of my other addons is causing the problem.

Thanks for any help you can provide,
Doniq

Didn't know...very sorry!! I had never seen that info before...

fred, please stop using WoWTOC, it's a hackjob fix to a "problem" blizzard fixed a year ago. Many devs (myself included) get very pissed when people screw with TOC versions thinking it solves anything. Just tick on "load outdated addons"

brainy, no the game itself has a range limit. CTRA_BossMods suffers from it too. You have two options... get more guildies (MT!) using BigWigs so sync messages can be sent, or tweak up the combat log range (dig in the plugins section of BigWig's settings)

Fred: Stop using WoWToc. It's useless, and it does more harm than good.

I've noticed that it has a range limit on this addon. I have to be in range to get the warnings to come up.

I tried posting on flyspray but i couldnt for some reason.

Weird thing....WoWToc won't update past this mod. If I remove it for a moment it goes through them all.I get a error message...but it's not in English!

Downgrading the AceOO is just going to cause you trouble in the future. Ckknight updated FuBar2 which should stomp out the errors you were getting (The fixed AceOO should be in there as well.)

Hmmm, time to bug Kaelton about updateing the stand-alone Ace2 distro on here. :P

Erm actually I found I had to do it the other way around.

E.g. as a temporary workaround, copy the AceOO-2.0.lua file of your OLDEST Ace2 addon into the relevant directory (usually libs\AceOO-2.0) of your other Ace2 addons. Doing this I've managed to get the following Ace2 addons to "play nice" together:

BigWigs
FuBar
FuBar-VolumeFu
Tinytip
XRaidStatus

Note: I copied the file from FuBar into the other addon directories. as for which is the oldest just open the file and look at its version.