Originally Posted by ckaotik
I just found that library last week myself. Also, besides talents and gear, there are also achievements and who knows what else. Maybe that's just me but I don't really like having one library that does too many things - e.g. I only care about talents, for buff suggestion, but it stores and manages gear as well. Depends on how much overhead this would create.
|
Feature Creep & Bloat
It's really weird how much data is returned to the client about a player. Are achievements pulled back in the same call? Statistics? Gear? Talent Groups? Reputations? Yesterday's Lunch?
Sometimes, all I want to know is the player's active talent group. That shouldn't take 5 seconds! It would be absolutely rad if the Inspect data could be segregated and/or sped up. Or at least, if i could just get some quick data that could potentially change every 10 seconds.
Taking a specific example, I can cache a player's gear and talents. I can persist that across sessions; awesome. What I
can't cache, is the currently active talent spec. I can't even persist that within a session.
If a party member gets summoned with a summon stone, addons can scan their talents & gear when they pop up. if the player then zones in...addons have to wipe the slate. While the player is sitting waiting inside the dungeon, the party member at the stone could be futzing with their talent spec, of flipping gear around. Any time the party member leaves the client zone of awareness, things get out of sync...when the party member comes back into sight, addons need to ask for ALL the inspect data again, JUST to see if the party members changed spec or gear while they were AWOL. That's retarded!
To Solve: Decouple inspect data that is highly variable: gear & active spec