Get an Epic Experience with Premium

BigWigs Bossmods

Boss Encounters Login to Add Favorites
  • World of Warcraft
  • 86,361 Monthly Downloads
  • Supports: 5.4.8
  • 14,212,819 Total Downloads
  • Updated 07/20/2014
  • Created 03/25/2008
  • 7,462 Favorites
  • Project Site
  • Comments
  • Release Type: Release
  • License: All Rights Reserved
  • Newest File: r11776-release
Support development! **

About BigWigs Bossmods


Big Wigs is a boss encounter add-on. It consists of many individual encounter scripts, or boss modules; mini add-ons that are designed to trigger alert messages, timer bars, sounds, and so forth, for one specific raid encounter. These encounter scripts are activated when you target or mouse over a raid boss, or if any other Big Wigs user in your raid does. In most cases only one module will be running at any given time.

If you're looking for boss encounter scripts for 5-man dungeons, these are not in Big Wigs proper, but live in their own add-on: Little Wigs.

Help us out


Please remember that we are always interested in hearing directly from you. About anything you want to share or ask. You may file tickets from our project page about anything, and you may also contact us on IRC; see the bottom here for details.

The comments on are rarely, if ever, read or replied to by any of the Big Wigs authors.


Note that the Big Wigs project - like 99% of all add-ons hosted on - is open for free access to anyone who cares to join. The source code is open and free, and we welcome you to participate in the future development of Big Wigs.

Transcripts and combat logs

If you want to help us out with a new boss encounter that was recently introduced to the game, you can get our Transcriptor add-on that helps you record raw, relevant data for each encounter. Your help is appreciated, and also needed! Compressed output from Transcriptor may be uploaded alongside a ticket, or dumped on sites such as and linked from a ticket. Or you can even e-mail it to one of the authors.

But if you don't care for Transcriptor, a simple /combatlog will also help. Don't forget to tell us what raid size, difficulty, and encounter the log is for.



  • Messages: Can be moved, coloured, locked, outputted to all kinds of different text areas.
  • Bars: Can be moved, skinned to different textures (SharedMedia compatible), resized & also have an 'emphasis' feature to flash and move to a different anchor when they are about to expire.
  • Raid icons: Target painting (put an icon over a player that has been singled out by the boss).
  • Boss Block: Suppress Blizzard boss emotes.
  • Sound: Plays various sounds on different events (SharedMedia compatible).
  • LibDataBroker/Minimap: Button for easy access to the configuration menu, resetting running modules, and seeing what modules are active.


  • Proximity: For displaying players within a certain range on certain boss encounters.
  • Test: Test and preview your bars and warnings configuration, and move them around.
  • CustomBar: For 'pizza timers', create your own custom bars.
  • Flash: Flash the screen blue when something important happens that directly affects you, such as a debuff.
  • Clickable bars: Lets you define left/middle/right click actions for your timer bars.
  • Super Emphasise: Any encounter ability you want to be extra vigilant of, you can enable Super Emphasise to get a voiced countdown and more.

Ancient project history

Tekkub, the original BigWigs1 for Ace1 author - back in the MC days, was inspired to write BW1 after his very first raid. He was horrified by the massive amount of spam his raid leader was creating with his boss mod. Getting messages all over the place for things he didn't care about (Hunters can't dispel a curse or interrupt a heal - well, they couldn't back then). He also found that the "60 seconds until painful doom" timer messages were such a waste. Why not use a simple timer bar to show this?

Our goals

Big Wigs aims to be as efficient as possible (creating a lower memory per second footprint and using a lower amount of CPU than any other boss mod). When modules are written, every aspect of the encounter is inspected. Is add-on synchronisation required? Is target scanning required? What events are really needed? We also aim to have the latest encounter scripts released ASAP; not long after the first few attempts of a brand new boss, we usually have a working encounter script for it.


Thanks to all the wonderful people in #wowace on for help with transcripts, translations, libraries, etc. Visit the About screen in the Big Wigs interface options for a complete list of all authors who helped directly with source changes.

If you want to contact us on IRC, remember that all the main Big Wigs authors live in Europe, and the nature of IRC means you might not get a response for as long as 10 - yes, TEN - hours. Just stick around and eventually, I guarantee we will answer. If you have the patience of a goldfish, however, you might as well just stay away.

r11776 | funkydude | 2014-07-21 02:34:27 +0000 (Mon, 21 Jul 2014) | 1 line
Changed paths:
   A /tags/r11776-release (from /trunk:11775)

Tagging as r11776-release
r11775 | funkydude | 2014-07-21 02:32:24 +0000 (Mon, 21 Jul 2014) | 1 line
Changed paths:
   M /trunk/Loader.lua

bump DBM faker
r11774 | funkydude | 2014-07-10 21:08:52 +0000 (Thu, 10 Jul 2014) | 1 line
Changed paths:
   M /trunk/SiegeOfOrgrimmar/GarroshHellscream.lua

GarroshHellscream: Power Icon Star is 10s on heroic, not 15 (normal mode).
r11773 | funkydude | 2014-07-10 19:27:04 +0000 (Thu, 10 Jul 2014) | 1 line
Changed paths:
   M /trunk/BigWigs.toc
   M /trunk/Loader.lua
   M /trunk/SiegeOfOrgrimmar/Immerseus.lua

Immerseus: Revert previous change to win on reform, false wins reported.


First Previous Page 36 of 102 Next Last
  • #1211
    Feature removed next version (soon) since you get a monster whisper anyway. Hopefully the warnings should work properly.
  • #1206
    Message: Interface\AddOns\BigWigs_Citadel\Valithria.lua:58: Usage: UnitIsUnit("unit", "otherUnit")
    Time: 02/17/10 22:15:32
    Count: 4
    Stack: (tail call): ?
    [C]: in function `UnitIsUnit'
    Interface\AddOns\BigWigs_Citadel\Valithria.lua:58: in function `?'
    Interface\AddOns\BigWigs_Core\BossPrototype.lua:102: in function `?'
    ...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:147: in function

    [C]: ?
    [string "safecall Dispatcher[12]"]:13: in function `?'
    ...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: in function `Fire'
    Interface\AddOns\Ace3\AceEvent-3.0\AceEvent-3.0.lua:120: in function

    Locals: Sometimes debuglocals() returns nothing, it's one of those times... (FYI: This last sentence (only) is a HotFix from Decursive to prevent a C stack overflow in the new Blizzard error handler and thus giving you the opportunity to send this debug report to the author of the problematic add-on so he/she can fix it)
  • #1212
    Unfortunately points to a line that is currently invalid, hopefully wont error next version.
  • #1202
    I came up with some worthy changes:
    -"Messages" bar having a grow upward/downward option rather than being only upward.
    -Bars in transition from Regular to Emphasized should have an option to slide across the screen instead of just popping. It's more visually effective and I know I'm not alone on that.
    -Enable bars to be re-sized vertically and not just horizontally. Maybe that's only me, and it's not too big a deal but it seems like it should be an option.
  • #1197
    any chance to add a
    -- shaking screen to shadow flame on Blood Queen
    -- better Alert to when u have like 5 sec left until you get the "tooth" and have to bite some1
    -- better alert for the ooze and the Bottles on Professor.
  • #1191
    No one emphasize works.
    Blood council and blood queen only less then the half from the time bars works.
  • #1192
    I'm sorry but I have no idea what you're reporting here. Bars "not working" is usually caused by a rare Blizzard bug where you loose sync with the server. This causes your combat log to be blank, and anything that relies on it to malfunction.

    Relogging fixes this issue.
  • #1193
    Ok, the bug with the combat log I will look at the next time.

    But what I mean with emphasize... as example I take Anub at 25er hero mode: The ability "shadow strike", there I have "emphasize" activated, but there is coming nothing special.
    Short said: Emphasize does not work.
  • #1194
    Ahhh yes, this is not yet finished.
  • #1182
    any chance to add the option to flash/shake your screen when a malleable goo is throw towards you.
  • #1183
    Should sort of work in r7030
  • #1181
    Has either DBM for BW made a notification for who Rotface targets with Plague Spray?
  • #1184
    It warns when he does it, showing target is useless information since it doesn't change what you do. i.e. get out the way of the spray.
  • #1178
    I noticed in the changelog for version r6997 a line that says "Citadel/Festergut: If you can't see a spore above your head, you can't see a raid icon. Revert."

    I'm not sure if that means what I think it means, but if it means you no longer are marking people with spores over their heads, I'd recommend putting marks back -in-. Why? Well, some of us run XPerl, or other raid addons that show marks next to player names in the raid interface. If we see marks go out on, say, nothing but melee, we know to call out "(NAME) take that spore to ranged".
  • #1185
    It takes less effort reading the warning which tells you who has the spore rather that searching Unit Frames.
  • To post a comment, please login or register a new account.
Login to Curse

Don't have an account? Create One.

Get an epic experience with Curse Premium
  • Faster addon downloads
  • Premium-Only Beta Giveaways
  • Ad-Free Curse experience
  • Premium Curse Client
  • and many More Features
  • Learn More »

SteelSeries Warlords Prize Pack Giveaway