Pinski

No, but they might toss out Soulward if they have it vs. not casting it if they don't in certain situations.

__________________
Calaglin, Former Illusionist/Guild Leader of Dissolution on Nektulos
Calaglin, Former Illusionist/Guild Leader of Confirmed on Unrest

Ghazni

I used this guide to make a macro for potm, but it's not working for some reason. The line in custom trigger is:

.*[[[Mandoblast]]]

The name of the trigger (just "Mandoblast") exactly matches the name of the spell timer I created; however, no timer pops up when I use the macro:

/5 %rt [[[JC: 40% reuse speed increase on [[[mandoblast]]] for 33 seconds]]]



Does anyone know what's wrong?

Ghazni

nevermind....i switched the brackets to something else and its working

Samedai

Hey everyone, thought this might be useful. If you're like me, you have about 15 different healers in your guild that get swapped around, which means that you have to set up individual timers for each healer. One of our raid leaders set up a dynamic gravitas timer that will pick up any time you activate gravitas, as long as your macro text is the same. Cut me down from about 25 timers in my ACT to just 4 (one gravitas and 3 cob for me and the other 2 dirges.) I'm pasting the info below. If you like it, be sure to thank Glok on Kithicor (i always knew bruisers were good for something

Step 1: Set up your ProfitUI raid window hotbuttons or a macro so that it announces to the raid when you gravitas your target (I use the raid window buttons, its just easier). Here's a copy-paste from my .txt file (_ProfitUI_QuickRaidButtons.txt):



Quote
<Page Name="Dirge">
<Data Name="Button1" Macro="SpellForMyLevel=&quot;Elegy at Death&apos;s Door&quot;
raidsay REZZING >> Parent.Target <<
useabilityonplayer Parent.Target SpellForMyLevel" Tooltip="(44) Elegy at Death&apos;s Door"/>
<Data Name="Button2" Macro="SpellForMyLevel='Elegy of Awakening'
raidsay REZZING >> Parent.Target <<'s GROUP
useabilityonplayer Parent.Target SpellForMyLevel" Tooltip="(58) Elegy of Awakening"/>
<Data Name="Button3" Macro="SpellForMyLevel='Speech of Sacrifice'
COND=(Parent.Parent.Parent.Parent.Custom.ProfitUI_ QuickRaidButtons.ActualLevel.Text < 78)
SpellForMyLevel=COND ? 'Oration of Sacrifice' : SpellForMyLevel
useabilityonplayer Parent.Target SpellForMyLevel" Tooltip="(65) Oration of Sacrifice
(78) Speech of Sacrifice"/>
<Data Name="Button4" Macro="useabilityonplayer Parent.Target Gravitas
tell Parent.Target Attempting Gravitas on YOU
raidsay Attempting Gravitas on ~~ Parent.Target ~~" Tooltip="Gravitas"/>
<Data Name="Button5" Macro="NONE" Tooltip="NO MACRO CONFIGURED"/>
</Page>


DISREGARD THIS PROFIT SETUP, IT'S FROM AN OLD VERSION. YOU CAN SEE THE MOST RECENT ONE A FEW POSTS DOWN.

as you can see, it sends them a tell saying "Attempting Gravitas on YOU", and says to the raid, "Attempting Gravitas on ~~ HealerX ~~". Once you've got this part working, it's a quick step to get ACT to work with it.

Step 2:
Create a custom trigger in ACT. We're going to use regular expressions here to be versatile, since we're only using 1 trigger for ANY HEALER. Here's the line that matches *my* raid output (with the ~'s)

Quote
, ?"Attempting Gravitas on ~~ (?<attacker>[\w\S]+) ~~"
this trigger is set for NO SOUND, and it triggers the timer "Gravitas".

that might look a little confusing, but what it does is it takes the data inside the ~~'s and creates a variable called attacker (that ACT recognizes in case multiple mobs do the same AOE so you can have more than one instance of a timer going).

This is sort of a workaround for ACT's lack of built in support for this sort of thing, but what it does is: First Gravitas, you get a generic timer called "Gravitas". 2nd Gravitas, you get a 2nd timer, and both the original plus your new one get a dash added to them with the player's name after it. If you set your warning to "tts" with nothing after it, it will even say the players name (unless there's only 1 timer running at that time, then the name is unlisted)

Step 3 (Last step!):
set up the "Gravitas" timer in your spell timers in ACT. to get to this window, click the "Show Timers" button next to "Show Mini", and then right click inside the blank area to open up the spell timers options window.

Under the "Timer Specific Settings" section, type in "Gravitas" in the first text box.
Timer Period: 120 seconds
Warning Period: 5 seconds (this is your preference, this is how long before their immunity wears that you want to be notified)
make sure none of the boxes underneath that are checked, then click Add/Edit. You should see the timer "Gravitas" show up in the list on the left with (120) after it.

Guess what? you're done! Test it out if you want to make sure its working/get used to how it shows the timers, but it works with any name you cast it on and dynamically will create as many timers as you want.

If you don't use the ~~'s, its obviously just a matter of overwriting those characters in the custom trigger with the ones you do use. And if you don't use the ProfitUI Raid buttons, then just make sure your generic gravitas macro says something with the same output, and it still works.

Samedai

I had someone asking me about timers for CoB in ACT so that you can use it to time your overlap with other dirges. Being in a 2 dirge guild means working out your timing well to keep it running non-stop. So, here are some screens of my ACT timers and setup page:

In the first screen are the triggers I have setup. The first is for my own CoB, next for our MT dirge's CoB, and then for one of our leaders alts who sometimes fills in.

The next two are of the timer options page (get to it by right clicking on your timer window). On my own timer I have the warning set for 13 seconds, so that I know when CoB has gone down. On the other dirges' timers I have the warning set for 15 seconds so that when I get the warning I can launch my own with overlap and no downtime between CoB's.

Attached Images

	ACT Timer Page 2.jpg (150.4 KB, 222 views)
	Spell Timer Options 1.jpg (177.8 KB, 169 views)
	Spell Timer Options 2.jpg (144.4 KB, 125 views)

ijoodunk

just want to say a huge thanks to samedai for the above post and for also posting the cob one too, as it was me that asked him about it.

setting these up has helped me out massively as i also run in a 2 dirge raid.

BubbaCajun

PM with info? Im new to ACT and profitui and customui, so it all seems like jibber jabber jibberish to me.

Is there any way i could get one of these programs to notify me when stun/stifle/dmg procs go off so i can be aware of these other then looking at my enemies buff/debuff window under their name?

Orani

Gravitas is about survivability. When the encounter is about to go bad, then all 3 Dirges should be casting Gravitas. I figure there's a line ya gotta draw between efficiency and survivability.

The single macro approach is definately the best way to quickly whip out Gravitas amongst 2 or 3 Dirges when things go bad. When things go bad, ya gotta make split second decisions. Ya take few seconds too long to make a decision then a group or healer could be dead or another player is still waiting for a rez.

All of group 4 health is down to 40% and group4 priest still has immunity for another 30 seconds. Group3 priest is good to go for Gravitas. 30s can be a long time in hard times to make sure the right priest receives Gravitas.

When fight goes sour, dirges should be spot healing the healer or chanter. This is a must especially since the intro of the Shadow AA.

When the encounter is not hairy, only the MT Dirge should use Samedai's implementation to maintain a cycle amongst the priests. This will hopefully add a little prevention to hairy encounters.

Also, assuming the raid is not in trouble ... When a player dies, the 2nd or 3rd Dirge should broadcast the cast of Gravitas on the primary Rezers.

ALOT of coordination. I bet no problem tho if the dirge player(s) can keep up.

Survivability of the raid should have priority over the dirge DPS parse numbers.

Orani

The apostrophe in "<<'s" broke the group rez raid button for me so I just removed it for a quick fix. heh.

I screwed up somehow when I copy and pasted the code the first time causing a bug that made my custom UI to temporarily unregister. So if this happens to ya, then it's something ya did wrong in copy and pasting Samedai's code or ya accidentally changed something else.

Samedai

thanks for pointing that out orani. that was an older version of my quickbutton config. if anyone wants it, here's what the new config looks like with confront fear in button 5. definietly make sure that you use notepad++ to edit, as just about anything else will corrupt the files on profit and you'll get dumped back to your default ui.

<Page Name="Dirge">
<Data Name="Button1" Macro="SpellForMyLevel=&quot;Elegy at Death&apos;s Door&quot;
useabilityonplayer Parent.Target SpellForMyLevel
raidsay Rez on Parent.Target
gsay Rez on Parent.Target" Tooltip="(44) Elegy at Death&apos;s Door"/>
<Data Name="Button2" Macro="SpellForMyLevel='Elegy of Awakening'
useabilityonplayer Parent.Target SpellForMyLevel
raidsay Group Rez on Parent.Target
gsay Group Rez on Parent.Target" Tooltip="(58) Elegy of Awakening"/>
<Data Name="Button3" Macro="SpellForMyLevel='Speech of Sacrifice'
COND=(Parent.Parent.Parent.Parent.Custom.ProfitUI_ QuickRaidButtons.ActualLevel.Text < 78)
SpellForMyLevel=COND ? 'Oration of Sacrifice' : SpellForMyLevel
useabilityonplayer Parent.Target SpellForMyLevel
tell Parent.Target Lifetapping to you" Tooltip="(65) Oration of Sacrifice
(78) Speech of Sacrifice"/>
<Data Name="Button4" Macro="SpellForMyLevel='Gravitas'
useabilityonplayer Parent.Target SpellForMyLevel
tell Parent.Target Hey Parent.Target You have Gravitas now" Tooltip="(80) Gravitas"/>
<Data Name="Button5" Macro="useabilityonplayer Parent.Target Confront Fear
tell Parent.Target Your Rez Effects are Removed
say Rez Effects Removed from Parent.Target" Tooltip="Confront Fear"/>
</Page>