I just installed GYP for the first time today, and the initial scan was SLOW! It would take about 30-60 seconds per item, and at about 2400 items, rough estimates are somewhere between 30-40 hours to complete.
I like the concept of what you are doing, but as the guild's main enchanter, I can't afford to be down for two days waiting for this.
I guess you could say you caught me on bad nomenclature :)
At the time I wrote this post, the only "fubar replacement" I knew of was Statblocks, and that's why I named it as such. At the time, I had no idea that the LDB movement was going to create different front ends like Fortress and Buttonbin.
Anyway, I almost have the addon I want written. It's showing the data right, but now it's down to semantics. It's an ugly add-on, for sure, definitely not even ready for Alpha-1.
Is there a tutorial for making our own Statblocks anywhere? I appreciate all the work you are doing, and I'd like to make a few of my own, even if they are for my own use. Thanks!
I'd love to do some mathematical work with the +spell damage numbers, but there's no way to compensate for them, especially as they keep changing with buffs and debuffs.
Make a new addon. For example, if you wanted to name it "BigWigs_ProcWatch" you'd create a directory by that name in your addons directory. Inside it, you'd create:
Here's something I can't find in BigWigs, and a search around here seemed to find nothing. If someone could point me in the proper direction, I'd appreciate it very much :)
I want to create a local cooldown bar that gets triggered when one of the Shattered Sun pendants procs. I'm not worried about the duration of the pendant, I want to see the internal cooldown. Since the proc on the pendant is automatic, the game doesn't show the cooldown.
my bad pseudocode follows:
If Buff."Light's Wrath" = true
then timerbar.(45,"Light's Wrath Cooldown")
There's still some debate over the actual length of the cooldown, but this would give me a general idea.
Updated to PitBull r61196 and I'm seeing some very strange behaviour in the health bar and incoming heals bar:
I can confirm this. It seems that the latest version if Pitbull has an issue with updating the health bar for (at least) the player and target. If you change targets, the health meter is set properly at the percentage, but it won't move after that.
0
Don't start this program in Dalaran >.<
0
I like the concept of what you are doing, but as the guild's main enchanter, I can't afford to be down for two days waiting for this.
0
At the time I wrote this post, the only "fubar replacement" I knew of was Statblocks, and that's why I named it as such. At the time, I had no idea that the LDB movement was going to create different front ends like Fortress and Buttonbin.
Anyway, I almost have the addon I want written. It's showing the data right, but now it's down to semantics. It's an ugly add-on, for sure, definitely not even ready for Alpha-1.
0
0
0
0
I'd love to do some mathematical work with the +spell damage numbers, but there's no way to compensate for them, especially as they keep changing with buffs and debuffs.
0
Worked like a charm, thank you very much!
0
Thanks Phanx!
Now completely noob question... where do I put this so it won't get overwritten the next time BigWigs updates?
0
Could very well be :) I just thought it might be able to go through BigWigs, since I use this trinket only during a raid.
0
I want to create a local cooldown bar that gets triggered when one of the Shattered Sun pendants procs. I'm not worried about the duration of the pendant, I want to see the internal cooldown. Since the proc on the pendant is automatic, the game doesn't show the cooldown.
my bad pseudocode follows:
If Buff."Light's Wrath" = true
then timerbar.(45,"Light's Wrath Cooldown")
There's still some debate over the actual length of the cooldown, but this would give me a general idea.
Thanks!
0
I can confirm this. It seems that the latest version if Pitbull has an issue with updating the health bar for (at least) the player and target. If you change targets, the health meter is set properly at the percentage, but it won't move after that.
I moved back to 61082 and the problem disappears.