A NuMonk Rework

[Anahlise_Auhn_Giinslai]

Some critiques:

Making it damage neutral will, counter-intuitive thought it may sound, be inherently not neutral, just due to the timings of Twin and Demolish (otherwise being clipped short). (This SS would never be permitted to let Twin drop except on Twin if and only if there are no Chakra spenders to be used in that lull, nor to cause a late Demolish.) Moreover, with it having a 10s PB-but-better attached via Celestial Fist, it's already allowing you to drop further low-ppgcd skills, just as PB itself and Blitz do, which means you'd want to rotate it as often as you could. Your high-SkS rotation might end up something like DK-Twin-Demo-Boot-SSS-DK-SSS-Boot-Twin-Demo, which would make MNK feel slow af. (Remember that BS and LF auto-crit, so they're effectively 315 and 393 ([320+465]/2) ppgcd, respectively.)

Moreover, why make a disengage tool so powerful? It'd then become a matter of just not using it within one of our 9-step rotational strings in order to leave room for a forced 1-GCD+ disengage or, depending on SkS, within the same string as a Blitz (especially a Lunar one).

I'd honestly really rather have this remain situational but just less clunky.


I think this would feel less nuanced and integral without even being any stronger, as we can only milk LF's higher filler ppgcd so long without refreshing Twin or Demolish anyways.

At present, Blitz is just long enough to optimize Twin and Demolish perfectly (so long as one never clips the GCD and is at a ~1.94s GCD or less). It fits great. The problem is simply that the 40s CD on PB makes you want to hold for a fresh DK-Twin-Demo string... which would then force you to delay the PB cast. I'd have to spreadsheet it out, but I suspect a ~30s CD would remedy that.

This would merely trade a desynced 1st TK/PR for a either a desynced 2nd and longer lulls in core job actions, I would think.

I'm also not sure why we need to have TK/PR within the initial raid CD period (instead of merely at the 60, 120, 240, 300, etc., marks). We'd merely be balanced around that slight potency boost, after all, while the slightly more backloaded damage seems to better fit our identities. Unless you make Blitz available every 20s, which would then gut much of its nuance in optimizing Demolish and Twin (or, seen from the opposite end, LF filler between those two), you're going to have at least 1 in 3 RoFs without a TK/PR simply because TK/PR is only 1 in 3 Blitzes.

my thanks for the criticism. The perspectives of other people tends to have a use and help with to refine my ideas...

my response for Six Sided Star:

Making it damage neutral will, counter-intuitive thought it may sound, be inherently not neutral, just due to the timings of Twin and Demolish (otherwise being clipped short). (This SS would never be permitted to let Twin drop except on Twin if and only if there are no Chakra spenders to be used in that lull, nor to cause a late Demolish.) Moreover, with it having a 10s PB-but-better attached via Celestial Fist, it's already allowing you to drop further low-ppgcd skills, just as PB itself and Blitz do, which means you'd want to rotate it as often as you could. Your high-SkS rotation might end up something like DK-Twin-Demo-Boot-SSS-DK-SSS-Boot-Twin-Demo, which would make MNK feel slow af. (Remember that BS and LF auto-crit, so they're effectively 315 and 393 ([320+465]/2) ppgcd, respectively.)

Moreover, why make a disengage tool so powerful? It'd then become a matter of just not using it within one of our 9-step rotational strings in order to leave room for a forced 1-GCD+ disengage or, depending on SkS, within the same string as a Blitz (especially a Lunar one).

I'd honestly really rather have this remain situational but just less clunky.

First, what if we change the durations of Disciplined Fist and Demolish's DoT?, then.
One part of my entire Monk redesign project, would be to extend the duration of Demolish's DoT, and I could just extend the duration of Disciplined Fist, as well; to make it so that neither have such a tight and often refresh demand? Second, I made Celestial Fist to solve a problem... Since Six Sided Star does not break form shifts, but also has no connection to the forms, so it would never be able to interact with the form shift rotation, so I made Celestial Fist be the key for how Six Sided Star would fit into the normal rotation lock...

That said, I do comprehend the problem that you point out here...
I did realize that Six Sided Star would replace True Strike and Snap Punch, more than much else, and that the rotation would be Dragon Kick, BootShine, and Six Sided Star, only broken up by Twin Snakes and Demolish... I did have a.. tentative.. new idea, to deal with that a bit, though. what if Six Sided Star has a short CD?(it would still be a GCD, so this CD does have SkS reduction) It would set the rotation to a back and forth lull, between the BootShine/Dragon Kick/Six Sided Star rotation, the True Strike and Snap Punch instead of Six Sided Star rotation, and then back to the BootShine/Dragon Kick/Six Sided Star rotation, when Six Sided Star comes off of CD...

and.. yeh... I forgot about the Guaranteed critical-hits. >.<
so, this CD tweak.. I think?, would make it so that Six Sided Star's potency only needs to account for True Strike and Snap?, since it would not replace any other part of the rotation, and fit into just that one point in the rotation... as for Disciplined Fist and Demolish's DoT, they could have durations that set their refresh deamnd to always be in the third rotation? Twin Snake/Demolish rotation, into Six Sided Star rotation, into True Strike/Snap Punch rotation, back into Twin Snake/Demolish rotation, and then Six Sided Star comes off of CD for the Six Sided Star rotation; while BootShine and Dragon Kick are the constant, present in every micro-rotation, of the Macro rotation.
would this solve the problems that you see in my redesign's first draft? and do you see any problems with this second draft of my idea?

that said, I am not certain what you mean by that Monk would feel slow, as a consequence... Ideally, and in this theory of mine, Monk has the oGCDs that I plan to give to Monk, so the Monk could single-weave in oGCDs at every GCD, and double-weave after Six Sided Star, for the illusion of high speed to remain intact. before you ask, I have some ideas for oGCDs that Monk would use often, so that Monk is single and double-weaving oGCDs at a constant, for a constant speed of around one attack every 0.8 seconds.

Last, is it not obvious that my redesign idea is for Six Sided Star to no longer be a disengage tool?
my idea is for Six Sided Star to instead be a piece of the normal rotation, to make the rotation more "complex", in the sense of a variation.

my response for Anatman:

I think this would feel less nuanced and integral without even being any stronger, as we can only milk LF's higher filler ppgcd so long without refreshing Twin or Demolish anyways.

At present, Blitz is just long enough to optimize Twin and Demolish perfectly (so long as one never clips the GCD and is at a ~1.94s GCD or less). It fits great. The problem is simply that the 40s CD on PB makes you want to hold for a fresh DK-Twin-Demo string... which would then force you to delay the PB cast. I'd have to spreadsheet it out, but I suspect a ~30s CD would remedy that.

This would merely trade a desynced 1st TK/PR for a either a desynced 2nd and longer lulls in core job actions, I would think.

I'm also not sure why we need to have TK/PR within the initial raid CD period (instead of merely at the 60, 120, 240, 300, etc., marks). We'd merely be balanced around that slight potency boost, after all, while the slightly more backloaded damage seems to better fit our identities. Unless you make Blitz available every 20s, which would then gut much of its nuance in optimizing Demolish and Twin (or, seen from the opposite end, LF filler between those two), you're going to have at least 1 in 3 RoFs without a TK/PR simply because TK/PR is only 1 in 3 Blitzes.

This one is more difficult for me to explain, because it is out-of-context, and makes more sense if you knew my entire Monk redesign project...

BUT, that said.. what made me have this idea in the first place, was that I have seen a lot of complaints about that Monk now has a barren downtime period, between the uses of Perfect Balance. My thought was that this new Anatman, separate from Perfect Balance, could replace Perfect Balance as the main "big burst", so that Perfect Balance can be the "small burst" that goes between the Anatman big burst; which sets Perfect Balance and its blitzes to be straight inside of that "barren downtime" period, and solve the downtime problem...

would it not work out that way? I thought that this idea would work out...
and I have seen other people make that same suggestion, to reduce Perfect Balance's CD down to 30 seconds, of which that I agree with.
while, I have also seen some people repeat the suggestion to just make Perfect Balance have three charges... I am not certain which option is better, while a curious thought for me, would be to ponder and figure out what the potential outcome would be, and what would happen, if both suggestions were given implementation...

also, here is a/the quick summary of another idea that I have had on my shelf:

(still in development)redesign concept for Monks' Chakra resource(just the summary)

The skeleton and backbone of my not-yet-complete redesign concept, takes the 14 Chakra of light and darkness as its base, 7 chakra for each side, to be a 14-point solid-resource dual resource pool, with the 7 Chakra of light as a fast build-up resource that the Monk spends often, with full-independent generation; and the 7 Chakra of Darkness as a slower build-up resource, that the Monk uses less often, albeit to execute more powerful actions; that is half independent in its generation, and half dependent on the Chakra of Light, for its generation...

Also, disclaimer: I came up with that before the Reaper reveal, and before we found out how Reaper resources function. The similarity, other than that one is sold-resource and one is gauges, is a total coincidence... I did not copy the Reaper to come up with that idea.