mate, its published on wowinterface.com
just use search for trinketmenu, the latest version is an early 2007 one, it is working perfectly and have absolutely no need to be replaced.
on damage meters - Violation is king for memory consumption (i mean, for lack of it), and i tried loads of other damage meters.
recount is very nice in terms of individual ability tracking, but it eats loads of memory. good to parse things tho.
closet gnome for outfitting, very low memory usage and pretty straightforward.
It looks like the culprit is in Blizzard's WorldMapFrame.lua:
function MapUnit_OnUpdate(self)
local texture = getglobal(self:GetName().."Icon");
if ( texture ) then
if ( MapUnit_IsInactive(self.unit) ) then
texture:SetVertexColor( 0.5, 0.2, 0.8);
else
texture:SetVertexColor( 1.0, 1.0, 1.0);
end
end
end
... I *think* this is there to support the 'afk in battlegrounds' feature, where 'inactive' players change color. It basically resets the color every time the map updates. Unfortunately, it sets it to that hardcoded value of (1,1,1)
If you don't care for that feature, and want your colors back:
/script function MapUnit_OnUpdate(self) end
thanks a lot, and i second hardcore option for that.
well its no prob, i use bugsack for the moment so it take care of it.
would be just thankful if it gonna be solved anytime, may be when Ace3 comes out and mass porting occurs :D
yes of course i tested it, currently with FubarUsage (or how its called). and you know its logical to have more memory usage when you have 2 almost identical framesets running at the same time.
again, dear WowAce community, please, read my first post. It has nothing with flaming Rock, ckknight, authors in general or Holy Jesus guy. this is a request, if you dont support it - then please dont say anything uncosntructive, for example, teaching me or telling that i should be thankful for that, or write artistic notes full of metaphor.
thank you, i really appreciate anything constructive said on topic.
i have a guess that upcoming ace3 isnt gonna come anywhere soon
btw its almost insulting to me when someone say "to end user there is no difference bla bla"
i switched to ace (1) because they were good for performance.
now having basically 2 almost identical framesets loaded - well, for me, enduser, it matters a lot - 1/3 more garbage gain and pretty much bigger initial load.
subj.
please, ckk, do it, or at least give your blessings to community to do it, so people can still develop it and dl with updaters.
of course same goes to others addons.
please dont force people to do what they dont want to.
thanks a lot, you are a great developer and your work is appreciated by thousands of wow players, and i am sure a lot of people would thank you for that.
I think he should have upped the version of the addons that are going to use rock, and just have let the addons that use Ace2 be - so they keep working as people upgrade to what would be FuBar2, Cartographer2, Pitbull2, etc.
never thought i would feel so much solidarity with you, Indy.
no, honestly. cant agree more, just dont understand why he did the either way :(
Mage's Frostbolt is reflected.
Mage hits Mage for 1874.
The source of the damage is from the mage, and you're filtering out damage not caused by you, so you don't see it.
I see. I have damage done by the target enabled in the combat log, does it just not display damage done by the target if that damage is also done to the target?
same issue here, i am dont quite understand how to make it work.
0
mate, its published on wowinterface.com
just use search for trinketmenu, the latest version is an early 2007 one, it is working perfectly and have absolutely no need to be replaced.
on damage meters - Violation is king for memory consumption (i mean, for lack of it), and i tried loads of other damage meters.
recount is very nice in terms of individual ability tracking, but it eats loads of memory. good to parse things tho.
closet gnome for outfitting, very low memory usage and pretty straightforward.
0
FubarAce work just as it should tho.
0
thanks a lot, and i second hardcore option for that.
0
looks like it is blizzard playfile (or smth) bug, posting it here to letting you know.
0
would be just thankful if it gonna be solved anytime, may be when Ace3 comes out and mass porting occurs :D
0
0
again, dear WowAce community, please, read my first post. It has nothing with flaming Rock, ckknight, authors in general or Holy Jesus guy. this is a request, if you dont support it - then please dont say anything uncosntructive, for example, teaching me or telling that i should be thankful for that, or write artistic notes full of metaphor.
thank you, i really appreciate anything constructive said on topic.
0
people come here and try to teach me instead of being constructive on topic
could you please let me decide how what is efficient to me and what is not?
0
btw its almost insulting to me when someone say "to end user there is no difference bla bla"
i switched to ace (1) because they were good for performance.
now having basically 2 almost identical framesets loaded - well, for me, enduser, it matters a lot - 1/3 more garbage gain and pretty much bigger initial load.
0
please, ckk, do it, or at least give your blessings to community to do it, so people can still develop it and dl with updaters.
of course same goes to others addons.
please dont force people to do what they dont want to.
thanks a lot, you are a great developer and your work is appreciated by thousands of wow players, and i am sure a lot of people would thank you for that.
0
never thought i would feel so much solidarity with you, Indy.
no, honestly. cant agree more, just dont understand why he did the either way :(
0
no, really.
again, as funkeh and indy already said in different threads, i just cant understand why ckk didnt upped rocked versions.
0
same issue here, i am dont quite understand how to make it work.
0
about /litmus standby - i know that, but automatic option would be nice (like it is done in violation and omen)
good luck with the error :D
(and yeah, sometimes it spams me and sometimes there isnt for hours)
0
i use it only in PVE or Arena, and doubt anyone really need it in AV.