Authors CurseForge

Thanks, Ammo!

Quote from Farmbuyer

congress bars?

Thanks folks, I'm here all week. Tip your servers.

Every 2 months. At least, the Blizzard Servers...

Quote from Ammo

It should have a frontend, showing the name of the resser next to the cursor when someone is ressing someone you're trying to res. If that makes sense.

-Ammo

Uh, sorry, but that was one of the more confusing sentences I've read in a while. Please elaborate?

Quote from mojosdojo

There is no frontend. Use something like HealInc or SmartRes. If I remember correctly, there's even a module for Grid.

Sorry, I chuckled, as I maintain SmartRes, and work on SmartRes2 here and there when I have time.

Alright, that answered the question, but brings up another: if there is no front end for a res monitor in oRA3, why does it use LRC-1.0? I know HealInc and SmartRes2 use the lib natively, so should I guess that oRA3 eventually will have said front end?

Pardon my noobness, but a question: since oRA3 is using LibResComm-1.0 then presumably there is a res monitor, but I can't find it anywhere in game. Someone please point the way?

Quote from cohu

[2009/10/21 22:09:02-4572-x1]: BigWigs_Coliseum-r6624\ValkyrTwins.lua:136: attempt to perform arithmetic on upvalue 'currentShieldStrength' (a nil value)
BigWigs_Core-r6624\BossPrototype.lua:91: in function `?'
CallbackHandler-1.0-5:146: in function <...non\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher[16]":4: in function <[string "safecall Dispatcher[16]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[16]":13: in function `?'
CallbackHandler-1.0-5:91: in function `Fire'
AceEvent-3.0-3 (Bagnon):119: in function <...ace\AddOns\Bagnon\libs\AceEvent-3.0\AceEvent-3.0.lua:118>

Got this error on heroic Twins with r6624 today a few times.

You want this.

I just wanted to say that you have my vote of confidence. I've been using BW in some form or another since vanilla, and having briefly switched to DBM back then to compare, I came back to the good stuff.

I might have quibbled and quarreled with the devs on occasion, but honestly, I love this addon, and think the authors have done an amazing job!

For that, you have my thanks. Lots and lots of thanks!

There is a section near the end (hint!) of the book World of Warcraft Programming by James Whitehead II, Bryan McLemore, and Matthew Orlando that deals with creating raid frames.

As Bubble said, that is an advanced topic. But if you want to create them, I would start with the book.

Quote from funkydude

Exactly why is this a BW problem? Every addon should use several commands for this exact reason. /tt should also be used in tiptac.

You suggest /bwtip, yet I don't see a suggestion for /tttip. I'm not trying to be an ass, but why should we have to shove an addon acronym onto our slash handler?

Already one step ahead of you. I posted a ticket to the TipTac page. I am not saying that it is a BW problem, only that there is a conflict, and I offered a suggestion. In TT's case, I suggested they add /tiptac.

I agree the fault really lies with the TT code only having one slash command, and the one picked was not an intelligent choice. However, it was used months, if not years, before BW3's use of that command.

Quote from Skylinee

The /tip command interfers with TipTac, as it uses the same command :/

I already made that observation on this thread, and posted a Ticket about it, but I'm glad I'm not the only one who noticed this annoyance.

My suggestion was to rename the BigWigs /tip command to /bwtip if you were curious.

I noticed you had to do a full SV delete when upgrading to BW3. Sucks, but it least configging is fast.

I just noticed the /tip command conflicts with TinyTip. I can't configure TT unless I disable BW3 entirely. Might I suggest /bwtip instead?

I know wowprogramming.com sometimes gets dated, but the lads update it fairly often; on the other hand, hasn't wowwiki been outdated for ages?

Alright, thanks for the shortcut, Jerry, and to Tekkub for the obvious. There is only one issue left, and that when I do the /mbd default command, it prints out the message correctly, but doesn't change the settings back to default. The strange thing is that I didn't play with that bit of code.
http://pastey.net/125497
is the newest pastey. I wonder why that command isn't working?

**edit** nvm, I figured it out. It was that redundant line 121 ... I just commented out the whole line, and voila!

Let me guess: line 16 should read

MBD_CHAT_OUTPUT = string.format("Using %s chat type.", addon.settings.chat)

?