Get an Epic Experience with Premium

BigWigs Bossmods

Boss Encounters Login to Add Favorites
  • World of Warcraft
  • 83,503 Monthly Downloads
  • Supports: 5.4.7
  • 13,952,099 Total Downloads
  • Updated 03/31/2014
  • Created 03/25/2008
  • 7,459 Favorites
  • Project Site
  • Comments
  • Release Type: Release
  • License: All Rights Reserved
  • Newest File: r11753-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.

r11753 | funkydude | 2014-03-31 14:28:32 +0000 (Mon, 31 Mar 2014) | 1 line
Changed paths:
   A /tags/r11753-release (from /trunk:11752)

Tagging as r11753-release
r11752 | funkydude | 2014-03-31 14:27:08 +0000 (Mon, 31 Mar 2014) | 1 line
Changed paths:
   M /trunk/BigWigs.toc

bump version
r11751 | funkydude | 2014-03-31 14:24:22 +0000 (Mon, 31 Mar 2014) | 1 line
Changed paths:
   M /trunk/Loader.lua

bump DBM faker
r11750 | nebula169 | 2014-03-16 23:50:44 +0000 (Sun, 16 Mar 2014) | 1 line
Changed paths:
   M /trunk/SiegeOfOrgrimmar/GeneralNazgrim.lua

GeneralNazgrim: fix Arcane Shock option
r11749 | funkydude | 2014-03-10 14:24:27 +0000 (Mon, 10 Mar 2014) | 1 line
Changed paths:
   M /trunk/SiegeOfOrgrimmar/SpoilsOfPandaria.lua

SpoilsOfPandaria: Don't directly use the spark name which can sometimes come up as "Unknown".
r11748 | funkydude | 2014-02-27 22:59:47 +0000 (Thu, 27 Feb 2014) | 1 line
Changed paths:
   M /trunk/SiegeOfOrgrimmar/Galakras.lua

Galakras: Warmup timer, patch by Asteague. Requires localization.


First Previous Page 24 of 101 Next Last
  • #1568

    I've had nothing but big wigs on some alt's and they still show up. Not sure how a add on can add blizzard sounds when you think all you need is the game.


    Ok i found the add on i guess that add's it but I still don't get it It's overachiever a add on that doesn't even use sounds, teh sounds im talkign about are the ones like the night elf bell or horde bell that ton's of people use and i don't think they all have overachiever.

    Last edited by furydeath on 10/11/2011 1:28:17 PM
  • #1557
    is there a way to Disable the Notifications in MSBT for BigWigs when a Timer Ends etc? Can be quite annoying.

  • #1558
    Yes, choose a different output.
  • #1556
    Hello can you dont do this with BigWigs as DBM like ''/dbm broadcast timer 5 PULLING''?
  • #1559
    If you're promoted and want a raid-wide timer:
    /bwcb 5 PULLING

    If you want a personal timer only you can see:
    /bwlcb 5 PULLING
  • #1555
    Kinda random, but has anyone mentioned after the intermission on Rag that the message says "Rag is back, parry on!" instead of "party on!"?
  • #1560
    I think this is an inside joke, purely intentional :)
  • #1564
    I bet he's a range dps or healer.
  • #1553
    hi, when being in demon form with my warlock in the shannox fight and becomming a target for crystal trap, i dont get any further warnigs during the fight for those traps. When doing the fight again after a whipe, i have to reload the ui to make it work again. could it be that the demon language causes the problem and can i do anything against it (except to go whithout demon form). it´s a german client.
  • #1550
    About your refusing a /say msg for immo traps: There IS a need for informing others where a new immo trap spawns. We have two rogues with the task to disarm all immolation traps and they use DBM's say message to locate them. But no Big Wigs user generates such a message and so we could (for the first time ever) be forced by our raid lead to switch to DBM, what I actually don't want.
  • #1554
    This actually happened to me tonight during Shannox Hc tried to force me to use dbm which i didn't want and i got put out of the raid. Reasoning "Don't you want to help others with a /s message to make them aware of the traps?" I see those things, why can't others see them even though they aren't cast on me i see them. This prolly will cost me my raid spot. Guild:
  • #1551
    That doesn't make sense. If your rogues are in range of someone to even see the "say" bubble, they're going to see the trap. BigWigs warns if the immo trap is on you, so you can move away from it. If your rogues don't see it, someone didn't move away from it and is still standing on top of it.

    The reason a /say isn't used for the immo trap is because of the frequency they spawn.
  • #1549
    hello and thanks for this great add on !
    i would like to know if it is possible to use custom sound ? Bigwigs menu only allows me to change sound for Alarm, alert, info, long or victory but i want to change sound for custom event (one sound for tantrum, one other sound for molten seed, etc...) such as you did with ragnaros lavawave.
  • #1552
    Not possible currently, but you can use an addon like "SharedMedia" to add your own sounds to BigWigs.
  • #1547
    I've been having an error everytime i log in and everytime I get in combat. My bar timers aren't working at all. Anytime I try to test them, I get the lua error again. This is the error:

    Date: 2011-08-02 19:55:52
    ID: 2
    Error occured in: Global
    Count: 1
    Message: ..\AddOns\BigWigs_Plugins\Bars.lua line 1150:
    attempt to index upvalue 'currentBarStyler' (a nil value)
    (tail call): ?
    BigWigs_Plugins\Bars.lua:1150: ?()
    [string "safecall Dispatcher[6]"]:4:
    [string "safecall Dispatcher[6]"]:4
    [C]: ?
    [string "safecall Dispatcher[6]"]:13: ?()
    ...ade\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: SendMessage()
    BigWigs_Core\Core.lua:171: Test()
    (tail call): ?
    [C]: ?
    [string "safecall Dispatcher[4]"]:9:
    [string "safecall Dispatcher[4]"]:5
    (tail call): ?
    ...e\AddOns\ButtonFacade\Libs\AceGUI-3.0\AceGUI-3.0.lua:314: Fire()
    Swatter, v3.2.3 ()
    Align, v
    Bartender4, v4.4.13
    BasicMinimap, v1.80
    BigWigs, v3.750
    BigWigsBaradin, v
    BigWigsCore, v
    BigWigsOptions, v
    BigWigsPlugins, v
    ButtonFacade, v4.0.344
    ButtonFacadeCaith, v4.0.64
    ForteCooldown, v
    ForteCore, v1.975.5
    kgPanels, v1.6
    LeatrixTooltip, v4.23
    MikScrollingBattleText, v5.6.108
    NeedToKnow, v3.1.8
    Omen, v3.1.0
    OmniCC, v3.1.4
    OmniCCConfig, v
    Postal, v3.4.4
    Prat30, v3.4.24
    Prat30HighCPUUsageModules, v
    Prat30Libraries, v
    Quartz, v3.0.6
    QueueAlert, v1.0
    Recount, v
    ReforgeSaver, v1.11
    SatrinaBuffFrame, v3.2
    ShadowedUnitFrames, vv3.3.5
    SLDataText, v4.0.6
    SnowfallKeyPress, v
    BlizRuntimeLib_enUS v4.2.0.40200

    Any way to fix this?
  • 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 »

Leaguepedia PAX Skin Giveaway