Monk Macros with Proper Rotation!

[Frowny]

Using false math calculations will not change me from providing my information to those that would like to use for midcore to casual content.

Yet you ignore the raw numbers showing it is a DPS loss PERIOD. Macros shouldn't be used in any content as a midcore player may not be the best, but they understand their class. Again, any avoidable handicap IS NO COMPETITIVE. Give it a break, you discovered nothing new and if this was remotely viable people would have posted macros by now.

[HyoMinPark]

I read until about page 7, and I'm a little sleep-deprived, so hopefully my post is coherent, and I was understanding this thread...

I disagree with this. The use of macros and the practice of macroing your rotation, like others have said, is a DPS loss. Regardless if it's 5% or 50%, it's still a loss. And really, that 5% could make or break a DPS check. Macros do not allow for ability queuing. They do not allow for fractional wait times. Take a normal GCD: 2.5 seconds. You can't macro:

/ac "Bootshine"
/wait 2.5
/ac "Twin Snakes"
/wait 2.5
etc...

You have to do 3 seconds instead. With two moves, that's already a 1 second delay. May seem minuscule now, but those seconds quickly add up the more a fight progresses. Again, a DPS loss is a DPS loss. And no DPS loss can ever be considered good, no matter how small.

You said you didn't design these macros for use in endgame/savage content, yet you are challenging any and all who disagree with your macros, to use them in endgame/savage content, and then make a judgment? That seems a little contradictory. Addition here: When people talk about "competitive" content in this game, they are generally talking about current EX primals/Savage raids. Not FATEs, not story/leveling dungeons, not guildhests, trials, etc. Not even Expert roulette. Current EX Primals and Savage content. Because, really, those are the numbers that make their way onto FFLogs. MAYBE the current 24-man raid, but competitive players upload competitve numbers to their FFLogs page. Not their DPS numbers for Sastasha.

You bring up human error. You say everyone makes mistakes. That is true. Compound the naturalness that is human error with macros that already have the potential to break and fragment a rotation. That could lead to even more of a DPS loss.

I agree with the other posters that macros should be reserved for ground AoEs, alert macros (i.e., "Berserk used! Pacification in 20 secs!"), and, if you're a healer, maybe even a Swiftcast+Raise macro. I use Swiftcast+Raise macros on my heals, and they sometimes break, and do not go off properly. Pretty annoying actually. I really can't imagine that happening during my entire rotation if it's macro'd.

I am not a good or decent monk by any means. I'm actually pretty bad at monk, I think, though I'm told otherwise. But I think I know enough to say that this is generally just bad practice. And while, yes, it's your sub/your $15/you'll play how you want, that's a pretty poor attitude to have given the way you are responding to some of these posters. The burden of proof lies with you. It's up to you to prove your macros work and are competitive. Not tell us to make a video and prove you wrong.

For the record, I did not watch your video, but, based on the comments I read, I don't really feel like I have to, to know that I will still disagree with it. And just because a system is implemented in a game doesn't mean that it has to be used as much as you seem to think that it does. The sample/default macros when you make a new character aren't even for skills--they're for greetings and emotes! You can macro your rotation, just like DRKs can cross-class Flash--but it doesn't mean that you should.

[Caitlyn]

Take a normal GCD: 2.5 seconds. You can't macro:

/ac "Bootshine"
/wait 2.5
/ac "Twin Snakes"
/wait 2.5
etc...

There is a difference between

/macroicon Demolish
/ac Internal Release <wait.3>
/ac Blood for Blood <wait.3>
/ac Steel Peak <wait.3>
/ac True Strike <wait.3>
/ac Demolish <wait.3>
/ac Bootshine

and

/macroicon Demolish
/ac Internal Release
/ac Blood for Blood
/ac Steel Peak
/ac True Strike
/ac Demolish
/ac Bootshine

.

The first macro is used as some kind of "press Button X one time and wait until its finished". In this case, you definitely have a HUGE DPS loss, because you have to wait 3 seconds instead fo 2,5 (or less). Time is Damage (kinda).

The second macro is use as some kind of "mash Button X repeadly to activate all skills when your GCD is finished". This works for Monk ONLY because "True Strike" and "Demolish" can only be activated, when you re in the right stance. This will work as to merge your 2 CDs, 1 OFFGCD and 1 combo into 1 Button. Bootshine will not be executed, when "Demolish" or "True Strike" is activate because of their GCD. Or to be clear:

Skills executed in order:

1. Internal Release
(skip because of GCD) Blood for Blood
2. Steel Peak
(inaccessable, wrong stance) True Strike
(inaccessable, wrong stance) Demolish
(skip because of GCD) 4. Bootshine

(on cooldown) Internal Release
(on cooldown) Steel Peak
3. Blood for Blood
(inaccessable, wrong stance) True Strike
(inaccessable, wrong stance) Demolish
(skip because of GCD) 4. Bootshine

(on cooldown) Internal Release
(on cooldown) Steel Peak
(on cooldown) Blood for Blood
(inaccessable, wrong stance) True Strike
(inaccessable, wrong stance) Demolish
4. Bootshine

(on cooldown) Internal Release
(on cooldown) Steel Peak
(on cooldown) Blood for Blood
5. True Strike
(inaccessable, wrong stance) Demolish
(skip because of GCD) Bootshine

(on cooldown) Internal Release
(on cooldown) Steel Peak
(on cooldown) Blood for Blood
(inaccessable, wrong stance) True Strike
6. Demolish
(skip because of GCD) Bootshine

This is quite different to OPs macro, but shares the same mechanic. Like previously said, even when it does works somehow, its still risky and not recommended to use it.

[SmallHobbit]

was try out this macro stuff yesterday and i notice not just a dps lose the most problem with this stuff is how to see which skill will be excuse with atm when you press the same button all time.
monk rotation is based on shine buttons which tells you "PUSH ME NOW look i am shining so nice!!!" so the problem is i have no clue which skill excuse atm and do i need change postion already? no idea because it dosent show you in macro (only one icon but many skills) this makes just even harder to do a good monk rotation like without macros.

regards hobbit

[ReplicaX]

Using false math calculations will not change me from providing my information to those that would like to use for midcore to casual content. Thats all I way say in regards to this subject!

All I have to say is you are not providing anything useful to casual or midcore players with this. Basic math isn't even required to disprove the basic logic that your macros are detrimental in combat.

If you do not want to use Macros, then dont....leave it at that!

It instills poor habits for players and provides zero education with their job or how to change on the fly or alter your rotations due to mechanics.

If you truly want to help anyone playing Monk, take the time to make a visual guide with step by step of rotations with an explanation of actions. Expand on it, showing examples of mechanics and changing on the fly with footage of the actual mechanic. Not just a striking dummy.

[Littlevegeta]

Pls tell me how this is wrong.. the longer the fight the bigger the difference will be.. the dps doesn't magically even out after 2 mins or it would be even the whole time.. do you even math?

[Roth_Trailfinder]

Pls tell me how this is wrong.. the longer the fight the bigger the difference will be.. the dps doesn't magically even out after 2 mins or it would be even the whole time.. do you even math?

If Player A is doing 1000 DPS, and Player B is doing 800 DPS, Player B is doing 80% of Player A's DPS, right?

So at 2 minutes, aka 120 seconds, Player A's total damage should be 120000 damage. Player B will be at 96000 damage.
96000/120000 = 96/120 = 80%
So at 2 hours 15 minutes, aka 135 minutes or 8100 seconds, Player A's total damage should be 8,100,000 damage, and Player B should be at 6,480,000 total damage.
6480000/8100000 = 648/810 = 80%

The total damage numbers will increase over time. But as long as the two DPS numbers remain constant, the percentage difference between the total damage numbers will remain constant. Where you will see variances is due to cooldown use. Neither Player A nor Player B will use their cooldown exactly the same way, especially when comparing various methods for doing things! And so their constant 1000 DPS and 800 DPS, or whatever the actual DPS comes out to be for any given period, will not be the same for all such given periods.

[Powe]

ok so a basic summary, macros are bad. If you use macros you aren't using the jobs full potential, don't macro( some macros are ok like saying I'm raising this guy) just press the buttons, its more fun that way.

[Littlevegeta]

But with macros the gap between the number gcds used versus a non macros rotation increases over time.. there for increasing the dps gap

[Sphinx12]

Those macros are so wrong, lol xD i see clippin/waitin everywhere, bad use of ogcs, opener is shit i dont play monk and still i would kick your macro ass anytime in dps