Get an Epic Experience with Premium

BigWigs Bossmods

Boss Encounters Login to Add Favorites
  • 60 Likes
  • World of Warcraft
  • 77,423 Monthly Downloads
  • Supports: 5.4.7
  • 13,935,269 Total Downloads
  • Updated 03/31/2014
  • Created 03/25/2008
  • 7,458 Favorites
  • Project Site
  • Comments
  • Release Type: Release
  • License: All Rights Reserved
  • Newest File: r11753-release
or
Support development! **
Donate

About BigWigs Bossmods

Introduction

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

Feedback

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 curse.com are rarely, if ever, read or replied to by any of the Big Wigs authors.

Open

Note that the Big Wigs project - like 99% of all add-ons hosted on wowace.com - 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 dump.no 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.


Features

Plug-ins

  • 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.

Extras

  • 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.


Credits

Thanks to all the wonderful people in #wowace on irc.freenode.net 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.
------------------------------------------------------------------------

Comments

First Previous Page 38 of 101 Next Last
  • #1136
    Hi there, I have add BigWigs today to my UI and I got now BG icon with name at my screen as seen here http://img31.imageshack.us/img31/8136/wowscrnshot121209171353.jpg - I can move it around but I dont see any option how to hide it. Any ideas/help?
  • #1142
    If you had thought it through, you would have gone to the UI's website (since this is a UI compilation called LUI 2.0) and would've realized that numerous people have already have this question answered in the comments section...

    But since you didn't I can tell you it's StatBlock Core or just type /sbc ingame. Then just disable Bigwigs in there. No biggies..
  • #1140
    This has nothing to do with BigWigs, you have a separate addon creating a new display out of the bigwigs plugin. Most likely the same addon showing your stats.
  • #1134
    In Heroic ToGC The Timer for Anub's burrowers should not stop running in PII, since in Heroic the adds keep spawning every 45secs.
  • #1133
    Since the patch the BigWigs minimap button is empty. The circular boarder is there but it's completely transparent (I can see through it).
  • #1131
    Unfortunately 3.3 came before we could finish some new BigWigs features, so they were stripped from this release, it's mainly module updates.
  • #1126
    I have a problem with Fubar and BW working together. It always used to work just perfectly fine, but now it's giving me problems for some time. When I disable Fubar everything works fine. When I enable it, I get the following error:

    Message: Interface\AddOns\BigWigs_Plugins\Colors.lua:5: attempt to index global 'BigWigs' (a nil value)
    Time: 11/26/09 15:22:10
    Count: 1

    [C]: ?
    Interface\AddOns\BigWigs_Plugins\Colors.lua:5: in main chunk
    [C]: ?
    [C]: in function `pcall'
    Interface\AddOns\FuBar\FuBar.lua:829: in function
    Interface\AddOns\FuBar\FuBar.lua:959: in function `LoadPlugin'
    Interface\AddOns\FuBar\FuBar.lua:1094: in function `object_method'
    ...Ons\FuBar\libs\LibRockTimer-1.0\LibRockTimer-1.0.lua:289: in function
    Locals: (*temporary) = nil
    (*temporary) = nil
    (*temporary) = nil
    (*temporary) = nil
    (*temporary) = nil
    (*temporary) = nil
    (*temporary) = nil
    (*temporary) = nil
    (*temporary) = nil
    (*temporary) = nil
    (*temporary) = nil
    (*temporary) = nil
    (*temporary) = nil
    (*temporary) = "attempt to index global 'BigWigs' (a nil value)"

    I already tried to remove all the bigwigs and fubar files and reinstall them but that didn't help. I also tried to disable the bigwigs part from fubar but it still won't enable and show me boss warnings.
  • #1127
    Oh I forgot to add:
    When I open the bigwigs options and click the big red CONFIGURE bar, I get the following error (and nothing in the config screen works)
    Message: Usage: GetModule(name, silent): 'name' - Cannot find module 'Bars'.
    Time: 11/26/09 15:27:45
    Count: 1

    (tail call): ?
    [C]: in function `error'
    Interface\AddOns\Ace3\AceAddon-3.0\AceAddon-3.0.lua:224: in function
    (tail call): ?
    Interface\AddOns\BigWigs_Options\Options.lua:54: in function
    (tail call): ?
    [C]: ?

    (tail call): ?
    ...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:799: in function
    (tail call): ?
    [C]: ?

    (tail call): ?
    ...ace\AddOns\EveryQuest\libs\AceGUI-3.0\AceGUI-3.0.lua:326: in function `Fire'
    ...uest\libs\AceGUI-3.0\widgets\AceGUIWidget-Button.lua:27: in function

    Locals: (*temporary) = "Usage: GetModule(name, silent): 'name' - Cannot find module 'Bars'."
  • #1409
    I'm also having this problem, I'm running the latest BW version too (7542 at the time of posting this)
  • #1410
    update: I had Quartz2, replacing it with Quartz3 seemed to fix it. Also deleted some random outdated savedvariables.
  • #1150
    Same problem here. ;-(
  • #1122
    I installed this addon using the Curse client and it works perfectly, however I can't seem to find the custom bars option in the config. Can you tell me where to find it please?

    /bwcb command doesn't work :S
  • #1121
    maybe you should try the alpha version on
    http://www.wowace.com/addons/big-wigs/
    which currently is r6807 and includes several fixes
  • #1113
    Ditto on BW not starting on its own - encountered this in Ony and TotC/TotGC so far. Able to get it going by click my minimap button to reset encounter, but it leaves me missing out on the first warning on say, Anub's burrowing, which can be fatal to miss as a tank.
  • #1104
    I recently upraged to windows 7 and for some reason my wow addons got broken.

    I installed the addons back and now eveything seems to be fine expect the problem with bigwigs not showing my spell bars.

    I'm using Parrot as my combat text addon. I've tryed everything from bigwig's customize tab but nothing seems to get them back.

    thank you for help in advance
  • 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 »

ESO Prize Pack Giveaway!