Resto UI Discussion - Page 15

Norfair · 03/21/09, 10:04 AM

Originally Posted by Niliyu

However, I have a different problem. This the NS/HT macro I use:

#showtooltip
/stopcasting
/cast Nature's Swiftness
/cast [target=mouseover,help][target=target,help][target=player] Healing Touch

Now, this casts NS fine, and most of the time it also casts HT. But I have the feeling that the HT cast lags behind a bit, and sometimes it does not cast at all. Could this be connected to the mouseover macro? Should I just keep it as targetted heal maybe? I'd be happy about any advice, since a malfunction usually means a dead tank (but at least I can instantly rez him afterwards :P ).

As far as I know it depends whether you are moving or not. If you stand still it will cast instantly, if you are moving you have to press it twice. I don't think you can change the macro so that it will always cast instantly, so therefore I use a castsequence macro where I always have to press twice.

Niliyu · 03/21/09, 10:18 AM

Thanks, I will try that.

Baa · 03/21/09, 4:30 PM

Regarding Inovindil's lifebloom counter problem:

Edit Interface\AddOns\GridStatusHots\GridStatusHots.lua
change line 1453 to

					string.format("%.1f", lbtime)

The code also mixes up the stack and duration colours. Replace "lifebl" with "lifebl_stack" on lines 550, 554, 567, 571, 582, and 584. You should end up with:

line 550:
			local color = GridStatusHots.db.profile.alert_lifebl_stack.color2
line 554:
			local color = GridStatusHots.db.profile.alert_lifebl_stack.color2
line 567:
			local color = GridStatusHots.db.profile.alert_lifebl_stack.color3
line 571:
			local color = GridStatusHots.db.profile.alert_lifebl_stack.color3
line 582:
		get = function () return GridStatusHots.db.profile.alert_lifebl_stack.totshow end,
line 584:
			GridStatusHots.db.profile.alert_lifebl_stack.totshow = arg

Inovindil · 03/23/09, 10:57 AM

Thanks a lot Baa, changed the lua file and now I have enabled Buff: Lifebloom Stack Colored and Buff: My Lifebloom on the center text 2. No extra hot counters and Lifebloom changes color depending on stacks

Exactly what I wanted!
Thanks again!

Fishendruid · 03/26/09, 1:14 PM

Got a slightly problem with my grid, In the guide theres center text*2 i only have one center text somehow..
Anyone got a clue if i got some older version orso?

natice · 03/26/09, 7:17 PM

Originally Posted by Fishendruid

Got a slightly problem with my grid, In the guide theres center text*2 i only have one center text somehow..
Anyone got a clue if i got some older version orso?

Go to frame ->advanced-> and click on enable center text 2.

Fishendruid · 03/26/09, 8:30 PM

Gah, dumbass i am.. Thanks for help!

atliens · 04/14/09, 3:47 AM

Originally Posted by Norfair

According to my .toc file I am using a pretty old version, version 2.3b. I downloaded 3.11 and I'm guessing you could fix it as well by going into the local function updateUnit and find the following line:

local bname,brank,btexture,bcount,btype, bdur, bexptime, bismine = UnitBuff(unitid, i)

Then beneith it, insert the following piece of code:

if bismine == "player" then
 bismine = true
else
 bismine = false
end

Not completely sure about the syntax though. I'll try and test it later.

Anyone know the similar fix for ElkanoBuffBars? I use it to track Lifebloom/Rejuvenation and we have another resto druid in the raid.

Inorrri · 04/15/09, 10:56 AM

After 3.1 release my grid is concidering all hots as my own for no particular reason ( didn't change anything in the addon itself). Anybody else experienced this/know how to fix it?

[e] Don't mind me, didn't read carefully previous posts.

For people like me: a temporary fix before official addon update -
Addons Showing Multiple Druid's Hots *FIX!*

tbsp · 04/15/09, 11:11 AM

Originally Posted by Inorrri

After 3.1 release my grid is concidering all hots as my own for no particular reason ( didn't change anything in the addon itself). Anybody else experienced this/know how to fix it?

I'm experiencing the same thing. Also, before I updated it, my dotimer was reflecting every buff anyone cast (on anyone, including themselves) as something I had cast. Something was likely changed in how the caster of a buff is identified. Hopefully gird and the associated components are updated soon.

Akomos · 04/15/09, 11:52 AM

My grid's all kinds of broken =\ Could be the plugin I'm using as well; didn't have time to mess around and just healed with the (barf!) Blizzard raid frames. Which was horrible.

Incidentally, has anyone seen a change to Wild Growth targeting behavior? I use the same mouseover macro for WG that I do for all my heals:

/cast [target=mouseover, help][help][target=player] Wild Growth

And it only wants to target my actual target, not my mouseover target. All my other heals, macroed the exact same way, behave normally.

Knolte · 04/15/09, 3:36 PM

Originally Posted by Inorrri

After 3.1 release my grid is concidering all hots as my own for no particular reason ( didn't change anything in the addon itself). Anybody else experienced this/know how to fix it?

I have the same problem. With that bug it's really bad to raid with more than one resto-druid (me) in the raid group. It would be great if somebody could fix that

InSaen · 04/15/09, 3:46 PM

Originally Posted by Akomos

Incidentally, has anyone seen a change to Wild Growth targeting behavior? I use the same mouseover macro for WG that I do for all my heals:

/cast [target=mouseover, help][help][target=player] Wild Growth

And it only wants to target my actual target, not my mouseover target. All my other heals, macroed the exact same way, behave normally.

Yup, it seems to do a range-check off you selected target. So say you have the boss targeted and he's 40+ yards away and you try to WG someone with clique it will give you an error message saying the target is out of range.

I also was testing some other odd behavior with WG last night. I had our MT stand 15 yards from me and a group of other people, i selected myself then WG'ed our tank with clique, WG applied to him and 4 other people standing around ME. It was pretty strange. Oddly, i couldn't repeat those results every time. sometimes it would only apply to the tank like it should have, other times it would apply to myself and 5 people around me.

Lenaldo · 04/15/09, 7:57 PM

Originally Posted by Norfair

According to my .toc file I am using a pretty old version, version 2.3b. I downloaded 3.11 and I'm guessing you could fix it as well by going into the local function updateUnit and find the following line:

local bname,brank,btexture,bcount,btype, bdur, bexptime, bismine = UnitBuff(unitid, i)

Then beneith it, insert the following piece of code:

if bismine == "player" then
 bismine = true
else
 bismine = false
end

Not completely sure about the syntax though. I'll try and test it later.

Just wanted to confirm this works for everything but lifebloom. Im not seeing WG/Rejuv/Regrowths from anyone but myself now.

I do have grid lifebloom so a similar change probably needs to be made in there.

Kysse · 04/15/09, 8:15 PM

Originally Posted by Baa

Regarding Inovindil's lifebloom counter problem:

Edit Interface\AddOns\GridStatusHots\GridStatusHots.lua
change line 1453 to

					string.format("%.1f", lbtime)

The code also mixes up the stack and duration colours. Replace "lifebl" with "lifebl_stack" on lines 550, 554, 567, 571, 582, and 584. You should end up with:

line 550:
			local color = GridStatusHots.db.profile.alert_lifebl_stack.color2
line 554:
			local color = GridStatusHots.db.profile.alert_lifebl_stack.color2
line 567:
			local color = GridStatusHots.db.profile.alert_lifebl_stack.color3
line 571:
			local color = GridStatusHots.db.profile.alert_lifebl_stack.color3
line 582:
		get = function () return GridStatusHots.db.profile.alert_lifebl_stack.totshow end,
line 584:
			GridStatusHots.db.profile.alert_lifebl_stack.totshow = arg

Can you explain how to find, for example, line 1453? I am opening GridStatusHots.lua with Notepad.