Monk rotation now?

[Zakard]

hum you shouldnt use rear rotation that early.doing 1 rotation of DK-twin and after directly starting bootshine+true strike isnt that good since you wont have DK debuff up.you need to do 2 rotation of dragon kick since debuff wont apply if you are not in the correct stance.

personaly i do TOD-DK-twin-demo-dk-twin-snap-boot-true-snap

[Koopatroopa]

Good point about the DK debuff, I always forget about that. Thanks

[Shaone]

Has anyone tested optimal ToD positioning in the rotation with regards to GL3 stacks? I'm thinking now with the 27% damage increase for GL3 it might be holding off until later in the rotation, as the next move after GL3 is reached.

I think demolish would still be worth applying ASAP regardless of current GL3 stack level, because it doesn't slow down building GL3 and has a short duration.

Thoughts?

[Allyrion]

Has anyone tested optimal ToD positioning in the rotation with regards to GL3 stacks? I'm thinking now with the 27% damage increase for GL3 it might be holding off until later in the rotation, as the next move after GL3 is reached.

I think demolish would still be worth applying ASAP regardless of current GL3 stack level, because it doesn't slow down building GL3 and has a short duration.

Thoughts?

This was always the case IMO.

[Shaone]

Yeah I'm already working on the assumption that ToD is best after GL3 stacks, would love to get it confirmed

So presently my max DPS boss opening on 2.1 goes something like:

Shoulder Tackle -> PB -> Snap, Snap, Snap*, Twin, Dragon, Death, (B4B), Boot, (Internal Release), True, (Steel Peak), Demo, (Howling Fist), Dragon, Twin, Snap, Boot, True, Snap, continue normal position dance and keeping up DoTs.

*Yes this Snap could be a Demolish, but I'm assuming even though it would take me to GL3, it would still be applied with GL2 modifier, so I hold off a little... And no, I don't use Fracture, although I have dabbled in it at times.

[EasymodeX]

Fracture is a DPS loss post-patch.

[Rochetm]

Fracture is a DPS loss post-patch.

I had gotten that feeling but had not tested it but after testing it out Fracture isn't worth it anymore.

[hamsteak]

nothing really changed for me except i have to remember to use demolish from behind

i feel bad for those monks who only did the side rotation, it'll take a while for them to get used to the changes

[Powercow]

Fracture is a DPS loss post-patch.

How do you figure? It's still as strong as the crit bootshine with about 15.3% crit (which is not really that hard to get) and it still beats out Dragon Kick, Twin Snakes, Snap Punch and the buffed True Strike in terms of damage/use.

In a longer fight it's too expensive TP-wise, but how is that any different from 2.0? You still didn't use it when TP was a concern.

Edit - Unless you meant Impulse Drive. And yeah ID sucks now.

[EasymodeX]

I had gotten that feeling but had not tested it but after testing it out Fracture isn't worth it anymore.

Oh, my bad, I just checked other timing options and the scenario where FR is a dps increase is when you use it alternated with Touch of Death if you are not maintaining 100% TOD uptime. I originally added the FR after the TD which causes buff loss unnecessarily which was my error.

Basic Monk cycle:

DK TW DM
BS TR SP
DK TW SP
BS TR DM
DK TW SP
BS TR SP

In this cycle, the main thing is that DK+TW both have a 15s buff duration (which apply for ~15.3 effective duration if the lag and snapshotting this patch is the same as last). With that assumption, the cycle accomodates 7 GCDs. E.g. you can add 1 bonus GCD every 2 rows in the above. For reference, the above rates as "159.1" PPS (autoattacks not factored).

Adding 1 TD boosts that to 161.9.

DK TW DM TD
BS TR SP
DK TW SP
BS TR DM
DK TW SP
BS TR SP

However, TD uptime isn't optimal with this. Ignoring that for a moment, adding Fracture every other DM cycle (for easier timing) ... ?

DK TW DM TD
BS TR SP
DK TW SP
BS TR DM FR
DK TW SP
BS TR SP

This results in 162.8.

But, the timing constraint here is not DM. It is DK/TW. So we should be alternating every DK pair, not every DM. In order to accomodate a proper loop to cycle back to the top, have to extend the set like this:

DK TW DM TD
BS TR SP
DK TW SP FR
BS TR DM
DK TW SP TD
BS TR SP
DK TW DM FR
BS TR SP
DK TW SP TD
BS TR DM
DK TW SP FR
BS TR SP

This results in 162.9. Gained a lot for that optimization and increased TP/s? ... >_<.