Chilly-McFreeze wrote: »usmcjdking wrote: »Should do 5% of current health for 4 seconds and the set should be renamed to something relevant.
Totally agree. Make it a new debuff so the issues with stacking are dealt with too.
and have a longer cooldown and i would agree with this.
Originally posted this in a different forum but it was brought to my attention it should be posted here
A 15% damage reduction is completely useless for starters, thats 130 less damage per tic. The biggest issue tho is this can still stack and needs a longer cooldown because, while it cant proc itself anymore ( great dont thing it was suppose to do that in the first place) The cooldown as of right now allows it to proc back to back giving healing ward no way to keep up with that. You fixed it for nbs but left sorcs screwed. Also I cant believe I need to say this but unmitigated damage should not stack.
And for the love of god can we do it this pts cycle instead of the one for murkimer cause they arnt fixing it once its live and 1 dlc was long enough for the worst designed set by zos yet
People who defend this broken set are either using it or they know someone who's using it. They probably already made it legendary too so they don't want it to be turned into a balanced set otherwise they won't be able to kill anyone anymore.
JPcrazysquirrel3 wrote: »This makes for a frustrating pvp experience. How can the same individual proc it 3 times in a row, (stacking, of course with a second player also wearing Sloads) in the time it takes me to only take one other ability of damage in a fight.
Why is there no cooldown on this proc set? Other proc sets do. Not only can it stack and cannot be mitigated in any way, and recasts itself, there's no cooldown?!
Fun game, ZoS. Really thought this one through.
Yeah, after doing Battlegrounds with three other guildies, I see what these calls for Sloads nerfs are about.
It should not proc 3-5 times after itself and stack 5-8 times on top of itself, as well.
Kept seeing Sloads on our recap screens. They would use a cheap ability to get it to proc over & over. No real skill whatsoever.
In Cyrodiil, Sloads hasn't seemed to be an issue, but Battlegrounds on the other hand,...
Yes, ZOS, please nerf Sloads. Truly nerf it. Give it a cooldown or something, ffs. It's not that hard.
Premades are stacking sloads and it's frustrating
JPcrazysquirrel3 wrote: »This makes for a frustrating pvp experience. How can the same individual proc it 3 times in a row, (stacking, of course with a second player also wearing Sloads) in the time it takes me to only take one other ability of damage in a fight.
Why is there no cooldown on this proc set? Other proc sets do. Not only can it stack and cannot be mitigated in any way, and recasts itself, there's no cooldown?!
Fun game, ZoS. Really thought this one through.
Yeah, after doing Battlegrounds with three other guildies, I see what these calls for Sloads nerfs are about.
It should not proc 3-5 times after itself and stack 5-8 times on top of itself, as well.
Kept seeing Sloads on our recap screens. They would use a cheap ability to get it to proc over & over. No real skill whatsoever.
In Cyrodiil, Sloads hasn't seemed to be an issue, but Battlegrounds on the other hand,...
Yes, ZOS, please nerf Sloads. Truly nerf it. Give it a cooldown or something, ffs. It's not that hard.
Premades are stacking sloads and it's frustrating
Had an entire team running Sloads and Skoria yesterday. These were people who would barely last a few seconds in a fight without those set sets but because of the enormous amount of damage they can just turtle up and use a skill here and there and it provides an equal amount of pressure to fighting a much more experienced player. This is at least as bad as the viper/Selenes debacle, except that at least was relegated mostly to gankers and NBs. This is just bad across the board on all classes and doesn’t even require a play style.
Class reps are just like our politicians. They promise mountains made of gold for us, but in the end, whenever they can they try to push their own agenda.
People who defend this broken set are either using it or/and they know someone who's using it. They probably already made it legendary too so they don't want it to be turned into a balanced set otherwise they won't be able to kill anyone anymore.
People who defend this broken set are either using it or they know someone who's using it. They probably already made it legendary too so they don't want it to be turned into a balanced set otherwise they won't be able to kill anyone anymore.
lower tier players have to protect tier crutch
Class reps are just like our politicians. They promise mountains made of gold for us, but in the end, whenever they can they try to push their own agenda.
This makes for a frustrating pvp experience. How can the same individual proc it 3 times in a row, (stacking, of course with a second player also wearing Sloads) in the time it takes me to only take one other ability of damage in a fight.
Why is there no cooldown on this proc set? Other proc sets do. Not only can it stack and cannot be mitigated in any way, and recasts itself, there's no cooldown?!
Fun game, ZoS. Really thought this one through.
also ya see how the first guys proc pack to back... needs to not do that
Also I cant believe I need to say this but unmitigated damage should not stack.
A shielded character with multiple sloads on it isn't any worse off than an unshielded character with multiple normal dots on it, so i don't see why the former should not stack when with the latter stacking is fine.
usmcjdking wrote: »Should do 5% of current health for 4 seconds and the set should be renamed to something relevant.
That is worse. On an average 25k health build its 1250/s. So even more pressure.
usmcjdking wrote: »usmcjdking wrote: »Should do 5% of current health for 4 seconds and the set should be renamed to something relevant.
That is worse. On an average 25k health build its 1250/s. So even more pressure.
@ak_pvp For sanity purposes let's say you get healed to the initial amount of health when proc starts to make teh math easy on me. Let's say you actually have 25khp.
My proposal says it maxes out at 5k damage which is still less than the current damage it does.
Now let's say you are at 10khp (40%) and you have 3 sloads magically appear on you at the same time.
On live you eat a wonderful 17.2k worth of damage over those 7 seconds which, paired with other damage, you are unlikely to ever recover from.
With my proposal that would be reduced to 6k damage total for all 3 of those sloads during 4 seconds. Far more manageable to deal with and more importantly, you won't die.
On the flip side of my proposal, let's say you have 40khp. Sloads dot now does 2k a tick when you are at max health, significantly more than before. When you reach 20k, it will do 1k a tick, 18k it'll do 900 so on and so forth. Each tick only will reduce your current health by 5%.
This gives the set identity, it becomes fairly solid at outright whittling down high health targets, and decreases dramatically as the opponents health lowers to dangerous levels. The only downside to my proposal is the straight up forum revolt from golded out sloaders.
This makes for a frustrating pvp experience. How can the same individual proc it 3 times in a row, (stacking, of course with a second player also wearing Sloads) in the time it takes me to only take one other ability of damage in a fight.
Why is there no cooldown on this proc set? Other proc sets do. Not only can it stack and cannot be mitigated in any way, and recasts itself, there's no cooldown?!
Fun game, ZoS. Really thought this one through.
also ya see how the first guys proc pack to back... needs to not do that
How do you know it's back to back? Maybe this guy is running, streaking or line of sighting?
Also I cant believe I need to say this but unmitigated damage should not stack.
A shielded character with multiple sloads on it isn't any worse off than an unshielded character with multiple normal dots on it, so i don't see why the former should not stack when with the latter stacking is fine.
You dont see the difference between normal dmg and oblivion dmg?
SidewalkChalk5 wrote: »The real problem is Sload stacking. Irresistible damage from multiple sources should NEVER stack. That's mind-numbingly stupid game design and the developer responsible for it should either learn to do better or retire in shame.
Also I cant believe I need to say this but unmitigated damage should not stack.
A shielded character with multiple sloads on it isn't any worse off than an unshielded character with multiple normal dots on it, so i don't see why the former should not stack when with the latter stacking is fine.
You dont see the difference between normal dmg and oblivion dmg?
For a character without shields, there is no practical difference between being affected by a normal DOT and an oblivion DOT.
If my stamina DK can be affected by multiple vipers ticking for ~800 each, i don't see why a sorc should not be affected by multiple sloads ticking for ~800 each.
Having a shield does not make one special.
SidewalkChalk5 wrote: »If my stamina DK can be affected by multiple vipers ticking for ~800 each, i don't see why a sorc should not be affected by multiple sloads ticking for ~800 each.
Having a shield does not make one special.
The difference is that Sload's is irresistible. There's nothing whatsoever you can do about it but die if too much gets stacked onto you. Resistible damage is categorically different from a design perspective. One can choose to invest in resistance strategies to mitigate it. It takes MUCH more of that kind of damage for death to become inevitable. Making those mitigation investments (shields or armor or defensive buffs or CP or whatever) comes at a cost, making it balanced and acceptable that such damage can stack. You can either acknowledge the objective difference or you can play denial games. The facts won't change: these two things are different and nobody benefits from pretending that they are the same when they obviously aren't.
Mystrius_Archaion wrote: »Also I cant believe I need to say this but unmitigated damage should not stack.
A shielded character with multiple sloads on it isn't any worse off than an unshielded character with multiple normal dots on it, so i don't see why the former should not stack when with the latter stacking is fine.
You dont see the difference between normal dmg and oblivion dmg?
For a character without shields, there is no practical difference between being affected by a normal DOT and an oblivion DOT.
You mean for a character WITH shields there is no difference.