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

Would make practicing rotations a whole lotta easier when you bungle something up.

EDIT: Just because it got brought up twice already, I'm talking about an option to reset your skill cooldowns when you're training on a dummy, not resetting enmity. This was taken care of already. Idk how they would code this but my best guess is either on the dummy itself or maybe some pop-up menu that appears when you engage one.

there is a function for this. if you right click there is a "reset enmity" function.

Quote:

---

Originally Posted by DrWho2010

there is a function for this. if you right click there is a "reset enmity" function.

---

Does that reset all your cooldowns though?

Quote:

---

Originally Posted by SenorPatty

Would make practicing rotations a whole lotta easier when you bungle something up.

---

It's been a while, but if you use the ones at Stone, Sky, Sea then whenever you teleport back in to do one, it automatically resets your CDs as far as I remember.

Quote:

---

Originally Posted by Shibi

Does that reset all your cooldowns though?

---

ah, misinterpreted the question. there is no reset for your own cooldowns in an open setting. just have to wait.

Reset enmity -> switch jobs?

Quote:

---

Originally Posted by Vyrerus

It's been a while, but if you use the ones at Stone, Sky, Sea then whenever you teleport back in to do one, it automatically resets your CDs as far as I remember.

---

Yeah I'm aware of this. My issue is with remembering SSS locations (which I just end up using google) and more importantly, exiting and re-entering SSS through npcs. This QoL would work out not just for local training dummies but SSS dummies too (if you're not making use of the timer there)

Quote:

---

Originally Posted by linayar

Reset enmity -> switch jobs?

---

We're not talking about enmity reset. That's been addressed anyways with a recent patch. We're talking about cooldown timer on your skills.

That's honestly not a good idea.. with the bots already using teleport hacks all they would need to do is copy the packet files sent from the system when reseting the skill and send that command each time they attack, thus letting them spam any big attack without a cooldown.

Quote:

---

Originally Posted by SenorPatty

Yeah I'm aware of this. My issue is with remembering SSS locations (which I just end up using google) and more importantly, exiting and re-entering SSS through npcs. This QoL would work out not just for local training dummies but SSS dummies too (if you're not making use of the timer there)



We're not talking about enmity reset. That's been addressed anyways with a recent patch. We're talking about cooldown timer on your skills.

---

Huh, strange. SSS dummy locations are always right outside the endgame hub areas. HWs outside Idyllshire, SB outside Rhalgr's Reach, and the current one is right outside Eulmore. :o

I'd think you'd want to use them so there's actually some sense of urgency, over a standard training dummy.

As a work around, you could always solo unsync queue into any duty, and it will reset your cooldowns. Then you just leave the duty, and they should be all set. Kind of a hassle, but resets any of your longer cooldowns in less time than they take to come back, unless your load times are just super bad.

Quote:

---

Originally Posted by SenorPatty

We're not talking about enmity reset. That's been addressed anyways with a recent patch. We're talking about cooldown timer on your skills.

---

I know that.

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.)

Quote:

---

Originally Posted by linayar

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.

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.

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

Quote:

---

Originally Posted by 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.

---

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.

Quote:

---

Originally Posted by Rongway

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.