Maintenance for the week of December 22:
• NA megaservers for maintenance – December 22, 4:00AM EST (9:00 UTC) - 8:00AM EST (13:00 UTC)
• EU megaservers for maintenance – December 22, 4:00AM EST (9:00 UTC) - 8:00AM EST (13:00 UTC)
• NA megaservers for maintenance – December 22, 4:00AM EST (9:00 UTC) - 8:00AM EST (13:00 UTC)
• EU megaservers for maintenance – December 22, 4:00AM EST (9:00 UTC) - 8:00AM EST (13:00 UTC)
Sorc execute
-
Merlin13KAGL✭✭✭✭✭
✭✭✭✭
You mean it should start at 25%? No, wait, that's NB's...(warning, salty post from a salty man thats over dying to instant sorc mages wrath explosion)
this ability is *** stupid, if its on you and you get low health you are 100% dead, ive even had it kill me above 40% health before, its stupid
i vote give sorcs the ability to stun people with frags & make their execute the same as all the other executes
50%? No, that's templar...
You do understand that there are a host of other executes that scale based on missing health that could drop you just as easily, right?
Just because you don't like the way something is doesn't necessarily make it wrong...
Earn it.
IRL'ing for a while for assorted reasons, in forum, and in game.I am neither warm, nor fuzzy...
Probably has checkbox on Customer Service profile that say High Aggro, 99% immunity to BS0 -
Drummerx04✭✭✭✭✭
✭Only thing I feel is weird about the execute is how it will stay on you for a few seconds.....remove that part and I´m fine with the skill
So you basically want it to work like every other execute? Got it.
Mages wrath counters:- purgeable
- the bolt which applies the execute debuff is dodgeable (and cloakable). (sometimes weird things happen in lag)
- 90% sure the execute damage is blockable
- pretty much a non issue if you can keep your health above 20%
- The delay the skill experiences in lag is extreme. It can take upwards of 3-4 seconds for the bolt to come down and apply damage. I've had people at 5% health heal themselves to safety with the execute in the air.
Sure, if you are on a low sustain low healing gankblade build, then curse and fury are going to give you a bad time.Edited by Drummerx04 on December 19, 2017 2:36PMPC/NA - Nightfighters, Raid Leader and Officer
Lilith Arujo - DC sorc tank/dps/healer - Dro-m'Athra Destroyer, Gryphon Heart, Grand Warlord
Lilith Tortorici - DC templar trials healer
Notable Completions:
vAS (72k), vMoL HM (160k), vAA HM (135k), vHRC HM, vSO HM (141k), vHoF HM (168k), vCR+3(129k), vDSA 45k, vMA 591k
Original Addons:
Lilith's Group Manager
Lilith's Lazy Hacks - Auto Recharge/Repair
Bot Scanner 2000
Lilith's Command History
Maintained Addons:
Kill Counter3 -
Qbiken✭✭✭✭✭
✭✭✭✭✭Only thing I feel is weird about the execute is how it will stay on you for a few seconds.....remove that part and I´m fine with the skill
Thing is, that is just one step away from destroying the whole 'delayed burst' mechanic that sorc has. And if it DID happen, then dmg and execute threshold would need to increase to be on-par with other executes.
If it does change t make the execute less harsh, I'd like it to do more non-execute damage and less execute dmg (same overall when hitting a target below 20%) - so it *almost* gives sorcs a weak spammable.
I would be ok to raise the execute range to 25% everyday
0 -
Idinuse✭✭✭✭✭
✭✭(warning, salty post from a salty man thats over dying to instant sorc mages wrath explosion)
this ability is *** stupid, if its on you and you get low health you are 100% dead, ive even had it kill me above 40% health before, its stupid
i vote give sorcs the ability to stun people with frags & make their execute the same as all the other executes
No no no. The forums were exploding about an execute that was a ranged channel and that effectively locked the caster down for over 2 seconds, rendering the caster vulnerable to interrupts, CCs, bursts and what not (deducting the entire cost of the cast if interrupted and useless) while the victim could block the incoming channel or if possible move out of range.
Oh, this is RD trauma all over again. I'd laugh if I didn't find it so pathetic.Edited by Idinuse on December 19, 2017 2:48PMSed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium dolorem que laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?0 -
ak_pvp✭✭✭✭✭
✭✭✭I don't have any issue with fury, but does getting executed put a bad taste in anyone elses mouth? Drop below 25%, get spammed, try to heal, and your still in the red zone, try stunning, oh no, your rip. I see the necessity but it rubs me the wrong way.MagDK main. PC/EU @AK-ESO
Best houseknight EU.0 -
ToRelax✭✭✭✭✭
✭✭(warning, salty post from a salty man thats over dying to instant sorc mages wrath explosion)
this ability is *** stupid, if its on you and you get low health you are 100% dead, ive even had it kill me above 40% health before, its stupid
i vote give sorcs the ability to stun people with frags & make their execute the same as all the other executes
No no no. The forums were exploding about an execute that was a ranged channel and that effectively locked the caster down for over 2 seconds, rendering the caster vulnerable to interrupts, CCs, bursts and what not (deducting the entire cost of the cast if interrupted and useless) while the victim could block the incoming channel or if possible move out of range.
Oh, this is RD trauma all over again. I'd laugh if I didn't find it so pathetic.
Radiant can not be dodged, deals significantly higher damage than fury outside execute range (which is much larger to begin with). Blocking it costs a lot of stamina and slows you down and the block must be kept up permanently, which makes breaking LOS more difficult. Purging it doesn't help because it can be reapplied instantly. To top it off, it even ignored LOS most of the time when it was being introduced.
In the end, no decent player will spam either of them on targets above 20%-30% HP, but in an outnumbered situation, only one of them becomes a problem due to lack of counters.DAGON - ALTADOON - CHIM - GHARTOK
The Covenant is broken. The Enemy has won...
Elo'dryel - Sorc - AR 50 - Hopesfire - EP EU1 -
VaranisArano✭✭✭✭✭
✭✭✭✭✭It's definitely a skill you need to play around, and I do feel like it could do with a tweak or two, but it's not going to lose you a fight on its own.
In order for Mages Wrath to kill you, an enemy needs to chunk you down to the point where it deals enough damage to kill you.
It's like seeing a Warden put down their beetles, or a Nightblade prep Relentless, you can see the opponent is prepping a big hit, and you need to play a bit defensive to mitigate it, or pressure them so that they can't make use of it.
As far as changes, the only thing I'd suggest is lower the duration slightly, or force the Sorc who casted it to deal damage in order to proc it.
yee i getchya, its just like, im easily able to recover form 20% health fighting other classes, but you cant with sorc? its silly
That's like saying its hard to recover from low health with poison injection or nightblade executes, or 2handed executioner...
Its an execute. Its supposed to make it hard to recover from low health, that's the entire point of an execute. Listen to the Dragonknights whining about their lack of a class execute because it makes confirming kills harder. Maybe you should focus on not falling below 20% health instead.1 -
ku5h✭✭✭✭✭
✭Malamar1229 wrote: »I heard once that good players dont get killed by mages wrath.
They know how and when to use block. For example, you have Mages fury on you and you're about to drop below 20%, block up that fury proc and you wont die....rocket science.0 -
idk✭✭✭✭✭
✭✭✭✭✭It's definitely a skill you need to play around, and I do feel like it could do with a tweak or two, but it's not going to lose you a fight on its own.
In order for Mages Wrath to kill you, an enemy needs to chunk you down to the point where it deals enough damage to kill you.
It's like seeing a Warden put down their beetles, or a Nightblade prep Relentless, you can see the opponent is prepping a big hit, and you need to play a bit defensive to mitigate it, or pressure them so that they can't make use of it.
As far as changes, the only thing I'd suggest is lower the duration slightly, or force the Sorc who casted it to deal damage in order to proc it.
yee i getchya, its just like, im easily able to recover form 20% health fighting other classes, but you cant with sorc? its silly
Start recovering at 30%0 -
MercTheMage✭✭✭✭(warning, salty post from a salty man thats over dying to instant sorc mages wrath explosion)
this ability is *** stupid, if its on you and you get low health you are 100% dead, ive even had it kill me above 40% health before, its stupid
i vote give sorcs the ability to stun people with frags & make their execute the same as all the other executes
Make it the same as radiant destruction from 50%? I'm good with that...
Impale? Hitting for a good 40k? Fine by me.You just going to stand there like a lemon?1 -
Alfie2072✭✭✭MercTheMage wrote: »(warning, salty post from a salty man thats over dying to instant sorc mages wrath explosion)
this ability is *** stupid, if its on you and you get low health you are 100% dead, ive even had it kill me above 40% health before, its stupid
i vote give sorcs the ability to stun people with frags & make their execute the same as all the other executes
Make it the same as radiant destruction from 50%? I'm good with that...
Impale? Hitting for a good 40k? Fine by me.
radiant destruction hasnt been that strong to kill someone from 50% or below for a long time lul
ive never had a problem with implae over 25% health, not to mention they need to use it when you are below 25% not just place it on you and have it completely kill you once you drop health, i dont see why its a delayed explosion, make it the same as other executes, its that simplePvP - Stamina Warden - Stamina Templar - Stamina Dragonknight - Stamina Nightblade
Worst Twitch Streamer Here0 -
Idinuse✭✭✭✭✭
✭✭(warning, salty post from a salty man thats over dying to instant sorc mages wrath explosion)
this ability is *** stupid, if its on you and you get low health you are 100% dead, ive even had it kill me above 40% health before, its stupid
i vote give sorcs the ability to stun people with frags & make their execute the same as all the other executes
No no no. The forums were exploding about an execute that was a ranged channel and that effectively locked the caster down for over 2 seconds, rendering the caster vulnerable to interrupts, CCs, bursts and what not (deducting the entire cost of the cast if interrupted and useless) while the victim could block the incoming channel or if possible move out of range.
Oh, this is RD trauma all over again. I'd laugh if I didn't find it so pathetic.
Radiant can not be dodged, deals significantly higher damage than fury outside execute range (which is much larger to begin with). Blocking it costs a lot of stamina and slows you down and the block must be kept up permanently, which makes breaking LOS more difficult. Purging it doesn't help because it can be reapplied instantly. To top it off, it even ignored LOS most of the time when it was being introduced.
In the end, no decent player will spam either of them on targets above 20%-30% HP, but in an outnumbered situation, only one of them becomes a problem due to lack of counters.
Yeah an execute becoming a problem only when outnumbered is indeed a problem. Zos needs to take a long look at the executes again and fix what's broken, meaning they should be as effective in 1v1 situations as any other execute. Right.Edited by Idinuse on December 20, 2017 2:40AMSed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium dolorem que laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?0 -
Didgerion✭✭✭✭✭
✭(warning, salty post from a salty man thats over dying to instant sorc mages wrath explosion)
this ability is *** stupid, if its on you and you get low health you are 100% dead, ive even had it kill me above 40% health before, its stupid
i vote give sorcs the ability to stun people with frags & make their execute the same as all the other executes
Looks like a L2P issue here.
Sorc execute is loud and very bright - it is not like it was secretly put on your at 40% HP and then you surprisingly insta-died when you hit 20% HP.
Next time consider healing yourself up when at 40%HP as there are other executes in the game that seriously damage you when below 40%HP.
Also you can mitigate lot of execute's damage if you block.
In other words - L2PEdited by Didgerion on December 20, 2017 2:50AM0 -
dsalter✭✭✭✭✭
✭✭my sorc loves the passive, on my stam bleed setup its abysmal, all bleeds, physical damage and shock enchants can proc it
PLEASE REPLY TO ME WITH @dsalter otherwise i'm likely to miss the reply if its not my own thread
EU - [Arch Mage Dave] Altmer Sorcerer
Fight back at the crates and boxes, together we can change things.0 -
Waffennacht✭✭✭✭✭
✭✭✭✭✭my sorc loves the passive, on my stam bleed setup its abysmal, all bleeds, physical damage and shock enchants can proc it
But... You're still a Stam sorc Edited by Waffennacht on December 20, 2017 3:01AM0 -
dsalter✭✭✭✭✭
✭✭PLEASE REPLY TO ME WITH @dsalter otherwise i'm likely to miss the reply if its not my own thread
EU - [Arch Mage Dave] Altmer Sorcerer
Fight back at the crates and boxes, together we can change things.0 -
ToRelax✭✭✭✭✭
✭✭(warning, salty post from a salty man thats over dying to instant sorc mages wrath explosion)
this ability is *** stupid, if its on you and you get low health you are 100% dead, ive even had it kill me above 40% health before, its stupid
i vote give sorcs the ability to stun people with frags & make their execute the same as all the other executes
No no no. The forums were exploding about an execute that was a ranged channel and that effectively locked the caster down for over 2 seconds, rendering the caster vulnerable to interrupts, CCs, bursts and what not (deducting the entire cost of the cast if interrupted and useless) while the victim could block the incoming channel or if possible move out of range.
Oh, this is RD trauma all over again. I'd laugh if I didn't find it so pathetic.
Radiant can not be dodged, deals significantly higher damage than fury outside execute range (which is much larger to begin with). Blocking it costs a lot of stamina and slows you down and the block must be kept up permanently, which makes breaking LOS more difficult. Purging it doesn't help because it can be reapplied instantly. To top it off, it even ignored LOS most of the time when it was being introduced.
In the end, no decent player will spam either of them on targets above 20%-30% HP, but in an outnumbered situation, only one of them becomes a problem due to lack of counters.
Yeah an execute becoming a problem only when outnumbered is indeed a problem. Zos needs to take a long look at the executes again and fix what's broken, meaning they should be as effective in 1v1 situations as any other execute. Right.
Problem in the sense of balance problem; no counter play means no fighting chance.
Though I guess there's no arguing with you.
FYI, Fury mostly isn't even used in dueling. Make of that what you will.DAGON - ALTADOON - CHIM - GHARTOK
The Covenant is broken. The Enemy has won...
Elo'dryel - Sorc - AR 50 - Hopesfire - EP EU0 -
IAVITNI✭✭✭✭✭MercTheMage wrote: »(warning, salty post from a salty man thats over dying to instant sorc mages wrath explosion)
this ability is *** stupid, if its on you and you get low health you are 100% dead, ive even had it kill me above 40% health before, its stupid
i vote give sorcs the ability to stun people with frags & make their execute the same as all the other executes
Make it the same as radiant destruction from 50%? I'm good with that...
Impale? Hitting for a good 40k? Fine by me.
radiant destruction hasnt been that strong to kill someone from 50% or below for a long time lul
ive never had a problem with implae over 25% health, not to mention they need to use it when you are below 25% not just place it on you and have it completely kill you once you drop health, i dont see why its a delayed explosion, make it the same as other executes, its that simple
Magicka Sorc is all about delayed damage, hence the delayed explosion. Literally all of sorc damage skills have a relatively large delay to them. Nobody is going to hard cast frags on a decent player meaning you're waiting for the proc. And when it does proc theres bright purple lights flashing and when you do shoot the frag it is easily dodged/blocked due to the slow travel time.
Compared exclusively to other executes, yes Wrath is powerful, damage wise. But in order to get the target into execute range, the opponent either needs to ignore all of a mag sorcs heavily telegraphed delayed burst (aka be an idiot) or the sorc has to outplay the opponent. A NB can drop their opponent into execute very easily. I play all classes and against guildies, i find magplars and magdks easiest to duel with and I mained mag sorc up until homestead.
Don't homogenize the game simply because you probably run full divines on a stamblade. If anything, Wrath should have a "priming period". It still does the initial 2-3k tooltip damage (lol) but the execute only takes place after 2 seconds. So now it HAS to be proactively cast. Honestly, It's fine as is.
But to argue your point directly, its simply a shift in onus. for a regular execute, there is greater responsibility for the attacker to apply pressure whereas wrath shifts the onus on the defender to avoid further pressure. If someone is spamming reverse slice on my executable nb, i can incap and kill them with my burst but If someone applies wrath I need to avoid further damage and heal but I can't easily turn on the opponent.2 -
Mureel✭✭✭✭✭
✭✭✭Ragnarock41 wrote: »Its a toxic mechanic tho.
Makes it literally impossible to recover when you hit below %50.
I wish it was stronger but harder to apply.
I wish vigor didn't exist.3 -
VaranisArano✭✭✭✭✭
✭✭✭✭✭(warning, salty post from a salty man thats over dying to instant sorc mages wrath explosion)
this ability is *** stupid, if its on you and you get low health you are 100% dead, ive even had it kill me above 40% health before, its stupid
i vote give sorcs the ability to stun people with frags & make their execute the same as all the other executes
No no no. The forums were exploding about an execute that was a ranged channel and that effectively locked the caster down for over 2 seconds, rendering the caster vulnerable to interrupts, CCs, bursts and what not (deducting the entire cost of the cast if interrupted and useless) while the victim could block the incoming channel or if possible move out of range.
Oh, this is RD trauma all over again. I'd laugh if I didn't find it so pathetic.
Radiant can not be dodged, deals significantly higher damage than fury outside execute range (which is much larger to begin with). Blocking it costs a lot of stamina and slows you down and the block must be kept up permanently, which makes breaking LOS more difficult. Purging it doesn't help because it can be reapplied instantly. To top it off, it even ignored LOS most of the time when it was being introduced.
In the end, no decent player will spam either of them on targets above 20%-30% HP, but in an outnumbered situation, only one of them becomes a problem due to lack of counters.
Yeah an execute becoming a problem only when outnumbered is indeed a problem. Zos needs to take a long look at the executes again and fix what's broken, meaning they should be as effective in 1v1 situations as any other execute. Right.
Problem in the sense of balance problem; no counter play means no fighting chance.
Though I guess there's no arguing with you.
FYI, Fury mostly isn't even used in dueling. Make of that what you will.
There's very little counterplay against any properly done execute. The counterplay is to stay out of execute range. So if you are fighting a sorc, you adapt because you know what the execute range on a sorc is and start proactively healing yourself before to get in their execute range. If you are used to starting your recovery at 20% health on other classes, adjust and start your recovery earlier when you know you are fighting a sorc. Its not like someone will suddenly surprise you with "oh, I'm a sorc, ha ha!" at 20%.
And if your opponent, knowing that people know they're a sorc, is properly prepared to burst you down starting at say 40% to bring you into execute range without giving you time for counterplay, well, that's good tactics on the sorc's part. Maybe you should look at what burst combo is bringing you done and adapt accordingly or maybe you should look at your build.
If the execute if a problem when fighting outnumbered, well, I have bad news for you. Anything, applied enough times, is going to kill you when you are outnumbered. Even if ZOS removed all the executes from the game, they'd run you down, corner you, and bash you to death with aoes ticking. If you want to 1vX, complain about executes all you want, but I've got no sympathy for it.2 -
BaylorCorvette✭✭✭✭✭It's def. nice to have on the Stam Sorc, getting a little extra punch. Can't comment on MagSorc sine I've never played it myself.Supreme Leader Corvette - StamSorc
Founder of Dominion Special Forces
YouTube - ESO & Automotive Racing
DC Zerg Busting0 -
ToRelax✭✭✭✭✭
✭✭VaranisArano wrote: »(warning, salty post from a salty man thats over dying to instant sorc mages wrath explosion)
this ability is *** stupid, if its on you and you get low health you are 100% dead, ive even had it kill me above 40% health before, its stupid
i vote give sorcs the ability to stun people with frags & make their execute the same as all the other executes
No no no. The forums were exploding about an execute that was a ranged channel and that effectively locked the caster down for over 2 seconds, rendering the caster vulnerable to interrupts, CCs, bursts and what not (deducting the entire cost of the cast if interrupted and useless) while the victim could block the incoming channel or if possible move out of range.
Oh, this is RD trauma all over again. I'd laugh if I didn't find it so pathetic.
Radiant can not be dodged, deals significantly higher damage than fury outside execute range (which is much larger to begin with). Blocking it costs a lot of stamina and slows you down and the block must be kept up permanently, which makes breaking LOS more difficult. Purging it doesn't help because it can be reapplied instantly. To top it off, it even ignored LOS most of the time when it was being introduced.
In the end, no decent player will spam either of them on targets above 20%-30% HP, but in an outnumbered situation, only one of them becomes a problem due to lack of counters.
Yeah an execute becoming a problem only when outnumbered is indeed a problem. Zos needs to take a long look at the executes again and fix what's broken, meaning they should be as effective in 1v1 situations as any other execute. Right.
Problem in the sense of balance problem; no counter play means no fighting chance.
Though I guess there's no arguing with you.
FYI, Fury mostly isn't even used in dueling. Make of that what you will.
There's very little counterplay against any properly done execute. The counterplay is to stay out of execute range. So if you are fighting a sorc, you adapt because you know what the execute range on a sorc is and start proactively healing yourself before to get in their execute range. If you are used to starting your recovery at 20% health on other classes, adjust and start your recovery earlier when you know you are fighting a sorc. Its not like someone will suddenly surprise you with "oh, I'm a sorc, ha ha!" at 20%.
And if your opponent, knowing that people know they're a sorc, is properly prepared to burst you down starting at say 40% to bring you into execute range without giving you time for counterplay, well, that's good tactics on the sorc's part. Maybe you should look at what burst combo is bringing you done and adapt accordingly or maybe you should look at your build.
If the execute if a problem when fighting outnumbered, well, I have bad news for you. Anything, applied enough times, is going to kill you when you are outnumbered. Even if ZOS removed all the executes from the game, they'd run you down, corner you, and bash you to death with aoes ticking. If you want to 1vX, complain about executes all you want, but I've got no sympathy for it.
There is plenty counterplay against executes, including Fury. Now go back and read my posts, I was talking about RD in an outnumbred situation.DAGON - ALTADOON - CHIM - GHARTOK
The Covenant is broken. The Enemy has won...
Elo'dryel - Sorc - AR 50 - Hopesfire - EP EU0 -
Irylia✭✭✭✭✭
✭The_Brosteen wrote: »
That’s a waste of a skill slot.
Healing is far too prevalent that you will almost never have that bonus damage especially with no in class or skill access to defile.
You either burst one shot or you don’t. There is hardly ever anything between unless the player you are fighting doesn’t understand how to heal and you crushing shock then to death.1 -
Irylia✭✭✭✭✭
✭Waffennacht wrote: »Sorc has open world mobility going for it, and that's about it
Those gap close spam snares and Roots/slows sure help that mobility.
Pretty sure any Stam class is faster and has the ability to pursue for less resources than the sorc can spend trying to be mobile.1 -
WillhelmBlack✭✭✭✭✭
✭✭Malamar1229 wrote: »I heard once that good players dont get killed by mages wrath.
Where? The forums?PC EU0 -
Destruent✭✭✭✭✭
✭✭(warning, salty post from a salty man thats over dying to instant sorc mages wrath explosion)
this ability is *** stupid, if its on you and you get low health you are 100% dead, ive even had it kill me above 40% health before, its stupid
i vote give sorcs the ability to stun people with frags & make their execute the same as all the other executes
No no no. The forums were exploding about an execute that was a ranged channel and that effectively locked the caster down for over 2 seconds, rendering the caster vulnerable to interrupts, CCs, bursts and what not (deducting the entire cost of the cast if interrupted and useless) while the victim could block the incoming channel or if possible move out of range.
Oh, this is RD trauma all over again. I'd laugh if I didn't find it so pathetic.
Radiant can not be dodged, deals significantly higher damage than fury outside execute range (which is much larger to begin with). Blocking it costs a lot of stamina and slows you down and the block must be kept up permanently, which makes breaking LOS more difficult. Purging it doesn't help because it can be reapplied instantly. To top it off, it even ignored LOS most of the time when it was being introduced.
In the end, no decent player will spam either of them on targets above 20%-30% HP, but in an outnumbered situation, only one of them becomes a problem due to lack of counters.
Nice joke man. Radiant at 0% enemy-HP and full magicka does less damage than impale at 25% and mages fury at 20%.
regarding mages fury: it effectively reduces your HP by 20% in pvp...i don't think that's a good execute mechanic at all.Noobplar0 -
VaranisArano✭✭✭✭✭
✭✭✭✭✭VaranisArano wrote: »(warning, salty post from a salty man thats over dying to instant sorc mages wrath explosion)
this ability is *** stupid, if its on you and you get low health you are 100% dead, ive even had it kill me above 40% health before, its stupid
i vote give sorcs the ability to stun people with frags & make their execute the same as all the other executes
No no no. The forums were exploding about an execute that was a ranged channel and that effectively locked the caster down for over 2 seconds, rendering the caster vulnerable to interrupts, CCs, bursts and what not (deducting the entire cost of the cast if interrupted and useless) while the victim could block the incoming channel or if possible move out of range.
Oh, this is RD trauma all over again. I'd laugh if I didn't find it so pathetic.
Radiant can not be dodged, deals significantly higher damage than fury outside execute range (which is much larger to begin with). Blocking it costs a lot of stamina and slows you down and the block must be kept up permanently, which makes breaking LOS more difficult. Purging it doesn't help because it can be reapplied instantly. To top it off, it even ignored LOS most of the time when it was being introduced.
In the end, no decent player will spam either of them on targets above 20%-30% HP, but in an outnumbered situation, only one of them becomes a problem due to lack of counters.
Yeah an execute becoming a problem only when outnumbered is indeed a problem. Zos needs to take a long look at the executes again and fix what's broken, meaning they should be as effective in 1v1 situations as any other execute. Right.
Problem in the sense of balance problem; no counter play means no fighting chance.
Though I guess there's no arguing with you.
FYI, Fury mostly isn't even used in dueling. Make of that what you will.
There's very little counterplay against any properly done execute. The counterplay is to stay out of execute range. So if you are fighting a sorc, you adapt because you know what the execute range on a sorc is and start proactively healing yourself before to get in their execute range. If you are used to starting your recovery at 20% health on other classes, adjust and start your recovery earlier when you know you are fighting a sorc. Its not like someone will suddenly surprise you with "oh, I'm a sorc, ha ha!" at 20%.
And if your opponent, knowing that people know they're a sorc, is properly prepared to burst you down starting at say 40% to bring you into execute range without giving you time for counterplay, well, that's good tactics on the sorc's part. Maybe you should look at what burst combo is bringing you done and adapt accordingly or maybe you should look at your build.
If the execute if a problem when fighting outnumbered, well, I have bad news for you. Anything, applied enough times, is going to kill you when you are outnumbered. Even if ZOS removed all the executes from the game, they'd run you down, corner you, and bash you to death with aoes ticking. If you want to 1vX, complain about executes all you want, but I've got no sympathy for it.
There is plenty counterplay against executes, including Fury. Now go back and read my posts, I was talking about RD in an outnumbred situation.
Fair enough, I missed the part where you were talking about Radiant Destruction.
I still think the last part of my post applies:
"If the execute if a problem when fighting outnumbered, well, I have bad news for you. Anything, applied enough times, is going to kill you when you are outnumbered. Even if ZOS removed all the executes from the game, they'd run you down, corner you, and bash you to death with aoes ticking. If you want to 1vX, complain about executes all you want, but I've got no sympathy for it."
That's true of Radiant Destruction or any other execute, or heck, any other skill when fighting outnumbered. Someone in the back of that group is going to be tagging you with something that will get through, and it'll kill you.1