Bløød DK's Clear Drak'Tharon Keep!!!

[jinx08]

Would you guys recommend using castsequence or castrandom macros? I've tried both and personally I prefer castrandom. Just wondered what you guys think?
One thing I have found is that when I spam my macro, once there is a cool down, my slaves will just stand there and not auto attack. Suggestions? (I've already added a /startattack at the beginning of the macro).

[Zerocool2024]

Would you guys recommend using castsequence or castrandom macros? I've tried both and personally I prefer castrandom. Just wondered what you guys think?
One thing I have found is that when I spam my macro, once there is a cool down, my slaves will just stand there and not auto attack. Suggestions? (I've already added a /startattack at the beginning of the macro).

Let see lets see..... I prefer the:
/startattack
/castsequence reset-target Icy Touch, Plague Strike, Pestilence, Howling Blast, Blood Strike, Etc...

Now, I am using Jamba, and the Strobe follow command, so they will attack and follow, they won't stop till I make them stop. If you use:
/startattack
/follow
/castrandom reset=target blah, blah blah, blah... You get the picture
/follow
Then you will have to spam the attack to get them to follow you, and the second they hit the target, they stop following you so now you have to spam it just to get them to follow...
/castrandom is fine, but, say you did Howling Blast, Icy Touch,Plague strike, pestilence... Your Howling Blast just did crap for DPS because it went first.

In the correct order, when mine hits, and it crits often, it's now hitting for 3K to 3.3K *5...

Others have found that having each attack in their separate hotkey is not better than /cast, but more control and or they are just used to that sort of way.
Also, some have stated that their DPS drops because of castsequence, or castrandom... I don't see a difference in my string of attacks.
I did a test dummy attack last night on the same level dummy 75, and I was peaking at 1500DPS (of course, I was hitting 3 mobs) but then again, its not that far off hitting a single target.

[jinx08]

I guess, reading your macro, that you aren't using an FTL setup? Otherwise your castsequence would keep resetting after the first spell due to the reset=target condition. I use the FTL setup, and use reset=combat. (Should i also include a 'time' condition in there too)?
Do you think the constant switching checking of the target to the leader from the slaves is resetting the auto swing timer? its so frustrating when the slaves just stand there being hit when the runes are on cool down.

[Zerocool2024]

I guess, reading your macro, that you aren't using an FTL setup? Otherwise your castsequence would keep resetting after the first spell due to the reset=target condition. I use the FTL setup, and use reset=combat. (Should i also include a 'time' condition in there too)?
Do you think the constant switching checking of the target to the leader from the slaves is resetting the auto swing timer? its so frustrating when the slaves just stand there being hit when the runes are on cool down.

No, not using that system
slaves:
/assist focus
/startattack
/castsequence ETC...

For you.

A problem with using castsequences exists, when you use 'reset=' with conditions which are depending on the actual target or modifiers, namely:
reset=target
reset=alt
reset=shift
reset=ctrl
Some conditions which would work fine with the system are:
reset=3 (time conditions)
reset=combat
for the 'reset=modifier' there is, in the basic ftl setup no real workaround known, because the modifiers are used to identify who the leader is.
The 'reset=target' can be used, if you don't depend on the 'targetless', then you can get rid of the '/targetlasttarget'. Because a simple assist shouldn't change the target of your slave when the leader doesn'T change it.

Not all that familiar with the FTL, I somewhat understand how it works, but I am more of a Focus type of guy, and have not had a problem with it at all.

[Furystrike]

Bleh, quit being lazy and trying to use castsequence commands. That may be cool for casters, but you are playing melee gentlemen. Missing one swing or getting off on your rotations will SCREW YOU in dps and could cost you the fight or losing to a boss. Do it manually and be ready to react to any given situation. By the way, I cleared Ulduar: Halls of Stone last night. Expect a movie soon =)

[Zerocool2024]

Heh, I probably should, but when I come to a point where it fails me, I will switch.

Btw, just cleared Gundrak at 75 with one piece of the Tempered Saronite on the main.
Wont lie, they beat me silly, was doing while my armor was being made.

[Multibocks]

reset=target works with FTL, I forget if you have to use /assist on it or whatnot (since /assist tank1 wont change target as long as your tank doesnt)

I use FTL and I love it for PvP... PvE it has some drawbacks(like really fricking huge macros), but one very nice thing about FTL is if your main dies you can switch immediately to a slave and begin hammering away again without having to change focus, etc.

[Souca]

I use FTL and I use cast sequences. I don't reset on target, but not because of the FTL since I use assist and don't targetlasttarget. The problem is that things die way to fast, and a reset=target would put me back at the start of a rotation with runes on cooldown. I'm currently using a time based reset, but combat might replace that since timing it is tricky. I could also get rid the reset all together since I've staggered my rotations on my characters. I didn't like there not being an Icy Touch to open up with.

As for doing it mannually? How? If one character misses a swing and gets out of synch, I don't want to have to try and micromanage them so that they can correct while the other characters wait or continue on with there rotation. I make sure I don't have anything in my sequence that would have to wait for more than a rune cooldown. I also tune my sequences so that they make correct use of death runes and try to have diseases up before they oblit or ss.

- Souca -