The cooldown reset on A8s is unbearable

[Eidolon]

There were videos posted when SSS was first released that showed people with dps cooldowns active and off cooldown to be reused again during the encounter. Abilities such as Raging Strikes which on a normal SSS attempt you can only use once due to it's cooldown period were able to be used a second time. This could have been hotfixed to be no longer possible, but since I never bothered doing this myself (as I and others have stated, doing this only cheats yourself) I can't say for certain if it is still possible. As for how they did it, I would know either as the videos started with the initiation of the SSS combat and did not show how they managed to have the buffs running prior to initiation with the skills themselves off cooldown and available for use.

I mean. Heres the thing, I checked it myself (Because hey, doing research) - and like I said. AT BEST, you can get 1, maybe TWO attacks in if you play it right, with the buff up. It's really not as broken as you're trying to play it out to be. Matter of fact, most the time - those very same buffs (raging strikes) would've been popped before the first hit anyways. So no, it's really not broken to have that, and even if you COULD get a whole 1-2 extra whopping attacks in, you'd likely be screwing up your own rotation doing it, and poorly training yourself for a real encounter.

And you somehow think that people will abuse this in a raid scenario? No. First of all, when you DIE, you lose all your buffs. So that's already out the window. As for what you said - the idea of resetting it based upon the Boss itself resetting, that is indeed available to abuse if they chose to do it that way.

But like you said, read the whole thread. There were counter-suggestions that said it should only happen during the Fade to Black Reset screen, which is ONLY possible in the scenario of a full party wipe. This means things like a5S sadly wouldn't have the benefit, but honestly - I think SE should avoid annoying turns like A1/A5 (Where you have to fight a striking dummy miniboss before an actual boss.)

[Cnidarian]

But like you said, read the whole thread. There were counter-suggestions that said it should only happen during the Fade to Black Reset screen, which is ONLY possible in the scenario of a full party wipe. This means things like a5S sadly wouldn't have the benefit, but honestly - I think SE should avoid annoying turns like A1/A5 (Where you have to fight a striking dummy miniboss before an actual boss.)

Thank you for showing your ability to cherry pick what you want to read. Try reading the first part of my post in response to Jpec07 in which I state that others have come up with solutions to those hypothetical situations. In fact, let me make it easier for you and I'll just re-post it here.

"I'll make the same statement to you as I did someone else, read the entire thread where people have come up with hypothetical situations that a boss reset =/= a full party wipe. Others have developed solutions to those hypothetical situations, but you can't just say that it's a simple fix because all you need to do is this when it comes to programming."

Just spouting off methods to prevent the type of abuse I'm explaining doesn't mean that it is easy to implement or that it is even possible to implement based on the current code. It might be a situation where if they want to do it in one of these methods, it would require the code to be rewritten from scratch. It could also mean that it is just a simple coding addition that is very easy to implement. The end result is, we just don't know the current coding situation so spouting off how easy it is to prevent abuse is meaningless.

Lastly, it doesn't matter if you get 1-2 extra attacks in by abusing the system, the fact that the system can be abused needs to be addressed before implementing changes (another thing I've mentioned at least once already in this thread). Another form of abuse that I personally haven't thought of yet is outlined inPLitz's post below:

The "abuse" that I think they're referring to isn't so much double-stacking CDs or anything exploitative like that. I think it's more along the lines of groups intentionally wiping because they screwed up their opener, or because they had an early accidental death, or heck even if someone didn't get as many critical hits as they wanted to in the first 20 seconds. The reason we want it is to not have to wait after popping cooldowns right before a wipe, they just have to find a way to set it up so that people can't just abort every time they have a bad pull.

Edit - Used the correct quote at the end, originally had the wrong person quoted.

[Eidolon]

Snip

Fair 'nuff, I use stream of thought writing a little too much, so appologies for neglecting that first part. Either way, it kidna bothers me - because if someone wants to waste their time trying to get hte "Perfect Opener", that's not abuse. They're still losing the time that they wasted on their 'imperfect' (a laughable term) opener, they're still losing their time that they have to wipe, get back in, re-buff, and re-pull.

Simply put, this isnt' as abusive as you think it is. Most serious raidgroups probably wouldn't even use this if it was in that short of a time period. The bigger thing they WOULD potentially do, is that they would likely wipe if they missed a DPS check of some sort. There are a few examples of this that can happen in the first few minutes of a fight - such as A5S, someone might decide to wipe if they didn't skip the first prey (But man... I couldn't imagine it, the group I was with just grumbled about having to do a mechanic.)