Could they add "Reset Cooldowns" to striking dummy menu?

[Rongway]

I just thought switching job would reset cooldown, but guess not. (Reset enmity is to be able to switch job since you can't while in combat.)

It does not. You'll even have abilities on the new job cooling down because of how cooldowns are shared between jobs. In order to limit the number of simultaneously cooling down abilities per player, long cooldown actions between jobs are shared, and not always with clear correspondences. That is, unless you know the exact ability mapping, you can't just assume that a 2min action shares a cooldown with the 2min action on another job, for example.

[Hasrat]

Sometimes I've wondered if that's unintentional, a side effect of copying something over from an old skill to make a new one, and forgetting to un-link the cooldowns. But I suppose reducing the number of cooldowns rolling per character could also make sense.

[linayar]

It seems so counterintuitive to me, though, if true. If you reset cooldown by switching job, that would limit it just fine to me.

[Rongway]

It seems so counterintuitive to me, though, if true. If you reset cooldown by switching job, that would limit it just fine to me.

The cooldowns persist so that you while you're overworld questing you can't burn all your powerful instant attacks, change jobs away and back, and then burn all your powerful instant attacks again. So the cooldowns need to be kept track of even after you switch jobs.

But if the cooldowns weren't shared, then you could ostensibly burn all your instant attacks on RDM, then switch to DNC and burn all your cooldowns, then switch to NIN, then to .... etc.

It wouldn't happen very often, if at all, but the SE devs have always been at the extreme end of software design conservatism. They plan for the highest possible volume of data access and transfer, and the highest possible computational commitment, and take steps to minimize both, even when such extremes would be unlikely. Ergo limiting the number of cooldowns each player can have going at once by sharing them between jobs.

[linayar]

The cooldowns persist so that you while you're overworld questing you can't burn all your powerful instant attacks, change jobs away and back, and then burn all your powerful instant attacks again. So the cooldowns need to be kept track of even after you switch jobs.

But if the cooldowns weren't shared, then you could ostensibly burn all your instant attacks on RDM, then switch to DNC and burn all your cooldowns, then switch to NIN, then to .... etc.

It wouldn't happen very often, if at all, but the SE devs have always been at the extreme end of software design conservatism. They plan for the highest possible volume of data access and transfer, and the highest possible computational commitment, and take steps to minimize both, even when such extremes would be unlikely. Ergo limiting the number of cooldowns each player can have going at once by sharing them between jobs.

Ok, that sounds more reasonable.