Any chance of a LibBabble-CreatureFamily? LibBabble-CreatureType-3.0 is a good base. All the possible return values are of interest to me, as documented on wowwiki:
1.7.0 is out, should come with hefty bug fixes and improved functionality. Next on the list is to improve out-of-combat performance with many players, and get some right-click menus to force party members into specific (saved) roles :)
I hate to necro, but this thread is exactly on topic.
Has a common library been made since Sept '09? A number of functions I use give localized results, which I need to compare. The return values from UnitCreatureType is one example ("Beast", "Demon", "Humanoid", etc). Checking if GetUnitName() returns a placeholder "Unknown" is another example.
I'd rather just "borrow" someone's tested localizations, vs asking my translators to iterate on exactly how blizzard interprets some of these obscure words. Any specific or generic responses are welcome!
Looking to replace ZOMG, trying out Cork but it's a little too limited for me. Came across this and read the Curse faq but still have a few questions....
- Plan on using this on my resto Druid. Will it cast thorns on myself when solo, but only on tanks when in groups?
- Can you set it to warn a set amount of time before the buffs actually expire (30 seconds for example)
- What kind of warnings can this give? Can sounds be played, or can the icon be set to blink/flash, etc?
-Thorns is a tank-only (for now). It will not be suggested for you while solo. I might add this to the feature request list.
-It can be set to refresh before the buff actually expires; default is 2 minutes remaining for druid buffs, I think. I use 5 minutes on my paladin.
-The only warning is a lit up button, with the texture of the next suggested spell to cast. Some users put the button in an obvious place, but configured to "hide" when everyone's buffs are active. Others stick it in a corner, or next to their action bars. I suggest trying it out; bandwidth is cheap these days ;)
I updated the FAQ, in light of blizzard's announced change to the inspection UI. This change won't affect the stability of Buff Broker, but it might impact response time, and the span to parse the entire party.
I'll likely be adding additional information in the tooltip for scan operations/progress. It's possible the inspection priority will change too.
Caching the role of each player/spec would be a cool optimization, but it wouldn't alleviate PUG runs. There would also have to be API changes to allow independent inquiries regarding a target's primary/secondary spec selection.
I plan to start a thread on the technical ramifications tonight. Hopefully, we can flush out how the current API works (and doesn't) for the uses we've found for it. Best case scenario, this gets back to the UI team well before Cataclysm changes are finalized :)
When the pet buffing was originally implemented few years ago, pets weren't assigned to any particular class. That's why they were stacked in the pet category.
Some time ago Blizzard made an unannounced stealth change and assigned default classes to pets. I'm still not sure how exactly they are chosen.
UnitClass reports consistently, but not very helpfully:
"Rogue" if the unit has not-mana: Ghoul, probably hunter pets (unconfirmed)
"Paladin" if the unit has mana and melees: Voidwalker, Succubus, Felhunter, Felguard
"Mage" if the unit has mana and casts: imp, water elemental
You probably already knew that, since it's obvious & even shows up in Unit Frames and stuff. It's useless data though, which is why I did some testing in 3.3.5 to find specific greater-paladin groupings.
I haven't had a chance to test water elementals or ghouls first-hand. They're sketchy to begin with, though, since their API GUID classifies them as NPCs/Guardians instead of player-controlled pets. I imagine the grouping and/or the GUID classifications could change for Cataclysm.
The only thing I have noticed that seems problematic is that on my shaman in groups with no Blessing of Wisdom, BuffBroker insists I should use Mana Spring Totem. Mathematically, this is probably a sound recommendation, but practically, mana is such a joke these days that there's almost no situation where I'd use Mana Spring instead of Healing Stream.
I forget when, but the ability to toggle specific totem elements is available now. In your case, turning off water totem suggestions might be worthwhile?
Starting a new development cycle, to get german localization in. Still considering what features to add; leaning towards weapon buffs & per-spec persistent buffs.
Conversation sake...totems are a bit mathier than "do I need mana to heal". This is more apparent with air totems, where it weighs who can benefit, and how MUCH they'll benefit, from (i.e.) Windfury vs wrath of air. A heroic group with 2 rogues, a warrior, you, and a warlock will probably get windfury...a bear, a moonkin, a mage, a rogue, and you will probably get wrath of air...a ret paladin, DK tank, enhancement shaman, dps warrior, and resto sham will probably get wrath of air (and the enh sham would probably drop windfury anyway).
Now that i think about it, I don't think 3% moonkin haste OR "empty totem slot" are handled... but that's how it SHOULD happen :3
The only thing I have noticed that seems problematic is that on my shaman in groups with no Blessing of Wisdom, BuffBroker insists I should use Mana Spring Totem. Mathematically, this is probably a sound recommendation, but practically, mana is such a joke these days that there's almost no situation where I'd use Mana Spring instead of Healing Stream.
Sounds like someone isn't using enough chain lightning :rolleyes:
I can't really tell what's going on without looking at the code itself. You can PM it to me or something if you wish. I'm going to guess that it's something to do with your group calls, but we'll see.
It might come to that; I'll check out BlizzFacade first though, thanks
As far as your second post goes, the BF GUI only saves the last known "global" change so that it can be displayed in the "global" options pane. If changes are made at the add-on or group level, they are not reflected in the global pane. Additionally, if the callback is not set up to catch add-on/group-specific settings, they will not be displayed correctly in the GUI. Basically, in your callback function, you have to check the "Group" argument. If it's nil, that's the add-on level skin settings.
The odd thing here is that my groups show up in the LBF:ListGroups("MyAddon") call. I'm getting a callback notification twice on start-up; once with a nil group (i.e. my addon data) and again with my group name (i.e. the group level). The skinID/etc pushed with this notification is the global setting, in both cases. This occurs well after I've done config load in OnInitialize, so any data I try to save/load is rofflestomped :confused:
0
http://www.wowwiki.com/API_UnitCreatureFamily
Seems like setting this up as a shared library is the sensible thing to do :)
0
http://www.youtube.com/watch?v=oliM-toWgHU
0
0
Has a common library been made since Sept '09? A number of functions I use give localized results, which I need to compare. The return values from UnitCreatureType is one example ("Beast", "Demon", "Humanoid", etc). Checking if GetUnitName() returns a placeholder "Unknown" is another example.
I'd rather just "borrow" someone's tested localizations, vs asking my translators to iterate on exactly how blizzard interprets some of these obscure words. Any specific or generic responses are welcome!
0
-Thorns is a tank-only (for now). It will not be suggested for you while solo. I might add this to the feature request list.
-It can be set to refresh before the buff actually expires; default is 2 minutes remaining for druid buffs, I think. I use 5 minutes on my paladin.
-The only warning is a lit up button, with the texture of the next suggested spell to cast. Some users put the button in an obvious place, but configured to "hide" when everyone's buffs are active. Others stick it in a corner, or next to their action bars. I suggest trying it out; bandwidth is cheap these days ;)
0
I'll likely be adding additional information in the tooltip for scan operations/progress. It's possible the inspection priority will change too.
Caching the role of each player/spec would be a cool optimization, but it wouldn't alleviate PUG runs. There would also have to be API changes to allow independent inquiries regarding a target's primary/secondary spec selection.
I plan to start a thread on the technical ramifications tonight. Hopefully, we can flush out how the current API works (and doesn't) for the uses we've found for it. Best case scenario, this gets back to the UI team well before Cataclysm changes are finalized :)
0
UnitClass reports consistently, but not very helpfully:
You probably already knew that, since it's obvious & even shows up in Unit Frames and stuff. It's useless data though, which is why I did some testing in 3.3.5 to find specific greater-paladin groupings.
I haven't had a chance to test water elementals or ghouls first-hand. They're sketchy to begin with, though, since their API GUID classifies them as NPCs/Guardians instead of player-controlled pets. I imagine the grouping and/or the GUID classifications could change for Cataclysm.
Hope this is helpful, even if it is a month late.
0
I forget when, but the ability to toggle specific totem elements is available now. In your case, turning off water totem suggestions might be worthwhile?
0
0
Now that i think about it, I don't think 3% moonkin haste OR "empty totem slot" are handled... but that's how it SHOULD happen :3
0
I saw it last night, with 2 paladins & 2 shamans (elemental + resto). I got some solid debug data to try to address the problem, luckily :)
Sounds like someone isn't using enough chain lightning :rolleyes:
0
0
Looks like I was loading groups into LibButtonFacade too early. Delaying any calls until OnEnable fixed the issue.
Thanks for the example, Storm!
0
I'll try that out this morning, thanks.
It might come to that; I'll check out BlizzFacade first though, thanks
The odd thing here is that my groups show up in the LBF:ListGroups("MyAddon") call. I'm getting a callback notification twice on start-up; once with a nil group (i.e. my addon data) and again with my group name (i.e. the group level). The skinID/etc pushed with this notification is the global setting, in both cases. This occurs well after I've done config load in OnInitialize, so any data I try to save/load is rofflestomped :confused:
I found this, which was pretty handy. Not sure if you had something more detailed in mind or not.
0
The trick is finding an addon with an open license, and clean implementation. Even then, this is quite a chore :P