The cooldown reset on A8s is unbearable

[Cnidarian]

Well... a wipe (i.e. death) removes all buffs anyway, so...?

I suggest you read the entire thread, as others have provided hypothetical situations in which a boss wipe does not necessarily equate to a full raid wipe. Granted those are hypothetical situations, the Devs would have to account for their possibility when implementing a cooldown reset. Don't get me wrong, I'm all for cooldown reset after a wipe as it's annoying having to wait. But, I'd rather they did it in a way that prevents it being abused instead of just doing it and fixing the abuse after the fact.

[Nestama]

My post stated that people do in fact abuse the cooldown reset and then I go into stating essentially everything you said in the first half of your post.

Which is why people (like myself) suggest that you only get CD's reset if you release (so you need to be KO'd and then be removed from the battlefield). This way the only thing you're waiting on is MP.

[spellsnare]

what about doing a cooldown reset like ''your all need to stay alive like 3 minute after the beginning of the fight'' if wipe after the 3 minute spend well all cooldown going to reset in that way no abuse at all

[Noxifer]

I suggest you read the entire thread, as others have provided hypothetical situations in which a boss wipe does not necessarily equate to a full raid wipe. Granted those are hypothetical situations, the Devs would have to account for their possibility when implementing a cooldown reset. Don't get me wrong, I'm all for cooldown reset after a wipe as it's annoying having to wait. But, I'd rather they did it in a way that prevents it being abused instead of just doing it and fixing the abuse after the fact.

and yet others have provided solutions to those hypothetical situations (as in, don't combine the cooldown reset with boss reset, but with the reviving; that way only the people who actually engaged the boss and died would "benefit" from it).

Edit: Reviving at start, that is. Not being Raised. So in case of a "partial wipe", you couldn't have someone raise them to just outside to save them the run back. If you did, they'd have cooldowns on any CDs they'd used AND have the rez debuff.

[Nekodar]

Prediction: When they do add this, people will quickly figure out how to abuse it for unintended purposes.

[ruskie]

I don't really care if someone will try and abuse it. I'm just fed up with wasting half an hour or more waiting on CDS during the 2 hours that we are raiding... Which is 10 wipes and wait for 3 min CDs(we never wait for the 5min or higher ones). True overall it seems like a minor thing but it does zap focus because instead of constantly focusing on the fight you now have 3 minutes to stare at nothing, watch youtube, get distracted etc...

As someone said - make them reset on release or everyone dead reset.

[Teiren]

WoW has been doing this for years with no exploits or problems. Technically speaking, WoW resets cooldowns upon engaging, not wiping from, a boss to ensure there's no abuse. The only flaw with it is that they only applied it to cooldowns longer than 3 mins. for some bizarre reason, but I think recently they applied it to all cooldowns. However, WoW does play slightly differently from FFXIV, so I don't think resetting cooldowns upon engaging a boss is a good idea for FFXIV because hardcore raiders would feel encouraged to still wait for cooldowns before engaging so that everyone gets a double-use out of them. For FFXIV, cooldown reset should obviously happen upon a KO Return.

The devs really seem to have no clue what they're talking about in regards to this specific issue if they're still discussing this as anything more than a no-brainer. It's gotten especially worse ever since Heavensward made FFXIV fights considerably longer than most of WoW's fights. Note: I can't speak to Warlords of Draenor raids, only everything before that.

[Sicno]

Hey everyone,

The dev. team is aware that there is a large demand for cooldowns to reset after a wipe. During the Niconico Chokaigi event held in Japan recently, Yoshi-P mentioned that while there are some concerns about the possibility of players abusing the cooldown reset, that they are actively looking into this.

We'll be sure to follow-up once we have more information.

If you want to avoid it being exploited in any way you can do this:

-Reset the cooldowns along as removing any possible buffs and debuffs.
-Apply it only on certain duties, like Alex savage or Seph ex. Not on dungeons.
-Apply it only if all party members were present in the fight that wiped.

Under those conditions I don't think it could be exploited in ANY way.

[Alistaire]

People do abuse the reset on SSS already. The difference is that abusing this on SSS doesn't have an impact anyone outside of the person cheating the system. Just because you do not know of the methods to abuse it, does not mean it doesn't exist. There are a few videos that have been published where this abuse was obvious (i.e. having buffs running when the SSS starts allowing them to double dip on those buffs).

Wait...so you're saying the abuse is doing SSS with double buffs? LOLOLOLOLOLOL....

...lol

[Neophyte]

Hey everyone,

The dev. team is aware that there is a large demand for cooldowns to reset after a wipe. During the Niconico Chokaigi event held in Japan recently, Yoshi-P mentioned that while there are some concerns about the possibility of players abusing the cooldown reset, that they are actively looking into this.

We'll be sure to follow-up once we have more information.

I don't think it's hard to prevent abuse.

• Only apply it on Ex-Primals and savage (maybe only apply it as long as the content is new, i.e. until it's accessible per df with less than 8 players).
• Either don't reset on entering or make all players lose their buffs by entering (like when you get synched down and lose Protect/Stoneskin/Defiance) and reset CDs (like in SSS)
• make every player stay dead, until the instance is resetted (like in A6S).. there is no benefit in staying in front of the boss gate anyway.
• reset CDs, when instance is resetted (like how you get Echo in old Content on reset)