Dark Knight Megathread

[Archwizard]

We could remove the cooldown from TBN, but then its ability to be used against two different TBs only 10-12 seconds apart, without even needing careful pre-popping for the first, would mean both reduced skill ceiling and TBN having to be tuned more around the extremes of what it can do. I'm not sure what, if anything, that would improve, either.

Ignoring that that's something PLD can do already... fairly certain they weren't implying removing the CD (low) from TBN.

[Shurrikhan]

Ignoring that that's something PLD can do already... fairly certain they weren't implying removing the CD (low) from TBN.

Removing the MP cost is the FAR more problematic, for reasons that have been covered several times by now (in either removing any unique interactions from TBN and forcing a longer cooldown, as the threat of no MP refund is what really constrains its timing, or forcing the job to be balanced around n TBN pops per minute), which is why I went with the less destructive (though still not necessarily positive) change.

[Archwizard]

Removing the MP cost is the FAR more problematic, for reasons that have been covered several times by now (in either removing any unique interactions from TBN and forcing a longer cooldown, as the threat of no MP refund is what really constrains its timing, or forcing the job to be balanced around n TBN pops per minute), which is why I went with the less destructive (though still not necessarily positive) change.

Which is understandable, but in the event of a rework and a choice forced between TBN losing its Dark Arts "counterattack" to be freed of its MP cost and balanced properly against other on-demands versus remaining as-is with its primary defensive skill weighed against two attacks, the fact it keeps coming up seems to mean most would be happier with the former.

[Shurrikhan]

Which is understandable, but in the event of a rework and a choice forced between TBN losing its Dark Arts interaction to be freed of its MP cost and balanced properly against other on-demands versus remaining as-is with its primary defensive skill weighed against two attacks, the fact it keeps coming up seems to mean most would be happier with the former.

I don't know why you keep trying to sell this idea. The MP cost constrains its available timings, keeping it more in line per average minute with the likes of other on-demands despite the added flexibility, but TBN is not, unless used poorly, weighed against Edge/Flood.

In fact, it carries a potency advantage once per raid buff cycle specifically because of that MP cost, as you can essentially push the Edge/Flood's MP cost to earlier -- where it prevents MP overcapping -- while allowing the damage itself to be dropped later, into raid buffs.

Just get level the job and this much quickly becomes apparent. Even in normal mode content, there is virtually zero risk of TBN not popping at any point that wouldn't also be a waste of any other on-demand (save for Nascent, as it just doesn't give a damn when damage is incoming since some 90+% of its value is from healing). In practice, TBN's MP cost is a subtle constraint (though with a decent knowledge requirement in dungeons), with a commensurate subtle advantage available to it -- no more.

You aren't choosing to use TBN over Edge/Flood. At most, you might choose to use TBN when you would barely have taken damage anyways for... reasons? But it's a matter of choosing to use it when no other on-demand would likely bother (if even available), holding it instead for the next actual spike of damage or not doing that -- choosing between a fluff TBN and a solid one, not between TBN and Edge/Flood.

[Archwizard]

I don't know why you keep trying to sell this idea.

And I don't know why you are trying to have it both ways of saying

the threat of no MP refund is what really constrains its timing

while also using the catch-all that the refund justifies it having a cost.

From what I see, from a design perspective, the fact that we're always holding a big portion of our MP back in the event of needing TBN constrains our already over-simplified rotation. It being cost-neutral isn't the same as it being free.
And for what? The flavor of a "counter"attack that we could have cast anyway, because not having such ability would be a detriment to our damage output if we're not the main tank?

[Undeadfire]

From what I see, from a design perspective, the fact that we're always holding a big portion of our MP back in the event of needing TBN constrains our already over-simplified rotation.

You don't need to hold a portion of your MP for TBNs, everything can be planned with maths in 14, some people use TBN just to add extra Edge/Flood for the raid buffs.

TBN without the MP cost and cooldown kept the same is broken OP.

[Shurrikhan]

And I don't know why you are trying to have it both ways of saying

Because it constrains usage subtly, in a way that'd keep us from prepopping for TB1 to then eat up all we can for 8s just some (15-prepop time) seconds later and still have it available again for yet another TB before anyone else would have access to their on-demand. Instead, we get particular bonus opportunities, but not so limitlessly as to require that TBN be tuned down. The CD and MP cost together keep it flexible without making it OP.

From what I see, from a design perspective, the fact that we're always holding a big portion of our MP back in the event of needing TBN constrains our already over-simplified rotation.

If it's oversimplified, then the last thing it needs is even fewer constraints, uniqueness, or elements of complexity.

Moreover, it's hardly some huge portion of resource; it consumes (ultimately, shifts the timing of) just 1 of 3.33 charges of Flood/Edge.

No, being ultimately cost-neutral isn't the same as being directly free, but for any Edge/DA you're unable to spend within the raids buffs themselves due to unfortunate TB timing, you're effectively able to spend another Edge/Flood that would otherwise have been used outside of buffs just to prevent overcapping within the next raid buff cycle. Yes, that's not immediately free, and it's good that it's not, but your concern has already been addressed, making it free-in-effect even in that rare scenario, so long as there are another 2 minutes within the given fight.

And for what? The flavor of a "counter"attack that we could have cast anyway

No. It's for its ability to be as flexible as it is. That's it.

The DA mechanic is what can deal with your concern of a lost Edge/Flood within raid buffs without bringing in the issues of it being directly free. (Should it be allowed to stack? Probably not, if to be perfectly balanced. Should it only use the DA if you're under X MP? Yeah, that would probably be a good change, as not to waste a DA's benefits in abnormal circumstances (though abnormal they would have to be for this to form a concern). But it's not there just as a counterattack gimmick.)

[Archwizard]

TBN without the MP cost and cooldown kept the same is broken OP.

Nobody's going to argue for it to have a 15 sec CD and be free. At worst I've only ever seen requests to go up to 25 sec in lieu of MP/DA, like WAR and GNB's.

If it's oversimplified, then the last thing it needs is even fewer constraints, uniqueness, or elements of complexity.

True, but from a design perspective, the idea of having any new MP abilities, or reworking the properties of the ones we have, must be constrained against the value of TBN and its potential interactions on the same resource.

We cannot, for instance, discuss having new skills that cost more/less MP, altering our MP gain abilities like Blood Weapon, or reducing the MP costs of Flood/Edge without that affecting the economy of TBN. We cannot discuss putting AD on an MP system (as you have in the past) without discussing if it's affected by DA/DS. We can't discuss situational alternatives to TBN (like old RI vs NF, or Cover vs Intervention) without discussing how to implement a DA-like aspect or make up for not having one.

Under the current system, we're locked into only having Edge/Flood on MP.

For a skill that doesn't compete for its resource, we're constrained to base everything in that resource around it.

[The_User]

TBN has been treated as a tool to prevent mp over cap rather than being treated as a mitigation is what went wrong. You're forced to use a mitigation even if you don't really need a mitigation just to prevent the cap and it is more like an extra task because there is no real reward. It is the same with tied a damage with healing and make a certain attack button get treated as a heal action rather than an attack action.
It is also not a display of skill since a tank buster is scripted and that mean your're also scripted and dictated, led to believe that you accomplish something. The 4s window of the short cooldown of other tank at least take more effort to timing.

[Archwizard]

TBN has been treated as a tool to prevent mp over cap rather than being treated as a mitigation is what went wrong.

... Huh? You have that completely backwards, we have Edge/Flood to prevent overcapping.

To use TBN if you or your target aren't taking heavy enough damage to fully absorb it is inherently a waste.