GuildXP
Simple DataBroker plugin to display current GuildLevel, current GuildXP, max GuildXP & percentage actually earned of daily capped experience.
You must have a Data Display addon(which inherits LibDataBroker-1.1) to use this such as:
- ChocolateBar
- Fortress
- ButtonBin
- Bazooka
Comments
-
_ForgeUser818274 Owner
-
View User Profile
-
Send Message
Posted Dec 18, 2010-
View User Profile
-
Send Message
Posted Dec 17, 2010I don't understand the purpose of the GX:GetSuffix() function. Seems like it just complicates the strformat(),
-
View User Profile
-
Send Message
Posted Dec 17, 2010The icon is not showing.
If you toggle the label off and icon on nothing shows, but the tool-tip does pop up if you point to where the icon would be.
-
View User Profile
-
Send Message
Posted Dec 14, 2010-
View User Profile
-
Send Message
Posted Dec 13, 2010is there a data display that's all around better than bazooka? or is it just preference?
-
View User Profile
-
Send Message
Posted Dec 13, 2010After Fubar went into it's slow death spiral I tried several other bars looking for a replacement.
I liked Bazooka best, but it's probably personal preference ultimately.
-
View User Profile
-
Send Message
Posted Dec 14, 2010-
View User Profile
-
Send Message
Posted Dec 13, 2010Thats great news :)
BTW-You might want to comment out the other print command at line 81. It popped once on me late last night (no big deal, just being informative).
-
View User Profile
-
Send Message
Posted Dec 13, 2010-
View User Profile
-
Send Message
Posted Dec 13, 2010last one is an issue regarding something i tested ... which is no longer necessary - so i will rewind to the previous one ... should be fixed in r22-release / r21
-
View User Profile
-
Send Message
Posted Dec 12, 2010I just happened to also notice that Titan is outputting the following error twice in chat each time I login:
<Titan> Set button text error GuildXP | Interface\AddOns\Titan\TitanUtils.lua:305: attempt to concatenate local 'text' (a function value)
Titan and GuildXP both seem to be working just fine....
-
View User Profile
-
Send Message
Posted Dec 12, 2010After initial upgrade to r18, GuildXP is outputting numbers to chat twice at login, and once each time I mouse over it. I'm displaying it via that latest release of Titan Panel. It looks like the print command at line 102 is responsible.
Edit: fixed in r20, Thanks!
-
View User Profile
-
Send Message
Posted Dec 12, 2010-
View User Profile
-
Send Message
Posted Dec 12, 2010-
View User Profile
-
Send Message
Posted Dec 12, 2010+ add an icon - make it green or something when EXP cap is reached, an a kind of red if not
+ add options to choose which text to be shown as "icon-text"
great work, keep on :)
-
View User Profile
-
Send Message
Posted Dec 12, 2010yeah i will review the whole stuff - seems like some leak ... in there ... I've tested with InterfaceUsage but it seems not as accurate/outdated as OptionHouse
seems fixed (CPU usage) OptionHouse atleast now shows 0.00%
the LibDataBroker-1.1 is now also embedded;
-
View User Profile
-
Send Message
Posted Dec 12, 2010Great mod idea.
But needs more work; has two problems. One big enough to prevent usage here, as well as another. Biggest problem: it consumes far (far) too much CPU time for what it does.
NinjaPanel LDB display (what I use for testing), disembedded libs (except LDB-1.1), OptionHouse (the test mod) & GuildXP r15-release. GuildXP uses 0.800-0.900 CPU/second on character idle in a 60+ person guild with only me online. Which is pretty hefty; very hefty for something that ideally should use 0 CPU on idle (as personal XP/info mods often do).
It spikes to an even heftier 1.6-1.8 CPU/second when mousing over GuildXP's LDB display. But that's standard behavior for most LDB info mods. What isn't standard behavior: when you remove your mouse from the LDB display, that CPU amount doesn't decrease to its former amount. It continues to eat 1.6-1.8 from then on. Highly unusual, don't remember any LDB mod I've ever tested doing that.
Instead update the XP data...every 30 seconds (or more) out of combat only? So that it will spike only momentarily when getting the data (as well as have it spike less than its currently using on idle)? Or an option to _only_ update the data when mousing over the LDB display? As well as fix the second part of the problem.
Second problem: LDB mods should really embed/package LibDataBroker-1.1. Its the standard method. What is done currently with this mod...print a warning message ("GuildXP loading failed. LibDataBroker-1.1 missing.") if someone is lacking that library installed...is not standard LDB behavior.
-
View User Profile
-
Send Message
Posted Dec 12, 2010-
View User Profile
-
Send Message
Posted Dec 11, 2010-
View User Profile
-
Send Message
Posted Dec 8, 2010yeah i know - it was an error/misunderstood of blizz implementation is fixed in r6; r7-release
was busy with leveling :x