SwitchFade

Agreed, aggro timing needs to be adjusted

So I'm, I built my arch/TA to exemp. Last night I was exemp to a Croatoa team. I ended up carrying the team of 5-8 for hours, alpha up every 16-18 seconds, knockdown, stun/end drain, slows. My defenses at that level were over cap to ranged and 40% s/l... I only mention this, because the perception that archery is behind other blast sets is, from direct play experience, not quite accurate. Granted the damage type is a bit more resisted, but the speed at which it can unload damage and mitigate incoming damage is incredible. That said, if you want to give DreadNock even more uber-leetness, please do. It just makes it easier to hit when I alpha every group and basically wipe everything.

Why?

Aside from my usual Nerf Regen joke, what really plagues Regen powers, like Regen, willpower, etc... Is that if it is hit with -regen, it's a one way ticket to dirt-napping with sweet baby Jesus. What Regen needs as a first pass change is Regen debuff resistance that is scalable, much like SR has for resistance scaling below 50% health. This would have to be balanced with hp/sec so it's not overpowered, but this would allow a Regen power to not suffer cascade so egregiously. Once this is tweaked properly, more could be built upon it. I have played WP extensively on scraps, brutes... and even with the layered mitigation, when Regen debuff hits rttc flops and everything goes south rapidly.

/Jranger humans. Too violences. All your bases are belong to us.

I wonder how Jranger actually feels about being immortalized in CoH lore... Is he as proud as Leroy Jenkins? Is he as proud as J. Emmert?

Knowing is half the battle.

Quick, someone post a Night Ranger meme about someone's sister...

Sorry, no vote.

Absolutely accurate.

Just so we know, the driving reason is because on a normal team of SO using causal players, knock back causes defeat? I'm sorry, this seems highly implausible. If a team of people is getting defeated because SOME foes (because no KB is auto 100%) are not firmly in the AoE taunt radius of a brute, this is not primarily due to knock back. In such a scenario, knock back is merely unmasking the true cause, in that the difficulty is beyond all but one type of tactical play for that team. Now, should this be the preferred and only way said team will play, that's all well and good; however, the reality is, if a brute retaining aggro on all foes is the fulcrum of survivability, this clearly demonstrates that KB is not the issue. Suppose a controller spammed AOE immob before all foes we're in brute AoE radius? Suppose a controller or Dom had singy? Suppose someone used fold space or wormhole? Suppose a stalker could generate more threat than the brute? Suppose someone used burn or fear and foes scatter? There are so many scenarios that it's difficult to imagine them all. Really, if the difference between success and defeat is knock back .. larger issues are at play and the diff is likely too high.

Perspective is an interesting thing. Staring at a tree from 1 inch away tends to obscure one's vision, save the tree. The perspective that knock back is so hugely, engrossingly terrible is quite... Interesting. So, apparently, knocking something back away from you or another is so catastrophically terrible because.... Pressing W is bad? Zergspeed is reduced by 10%? Ack? AoE efficacy is not properly saturated and maximized to the 42nd prime meridian? The humanity? Foes that are ragdolled and unable to drub you about the ears is nonobad? Hmm. Really, knock back is so bad it's like someone flushing documents down a toilet? Or kicking bunnies? Interesting. Perspective, neh?

Sorry, no vote.

IBlap says... Water/elec and become a blappy blapperton.

Nerf Regen. Twice.

Then eat pie? 🥧

Darned typos! You know what he meant 😁😅🤪

Scrap. You're overthinking it. DB animations are very unique, you'll quickly get used to which one is which. So set up your tray 1-7 in the chain. Hit 1, then as it is animating hit and hold 2. While 2 animates, hit and hold 3... Etc. Updates mean if your attack missed you still get combo benefit. So on my scrap, I hit one and it starts Nimble. As the power is animating I have already hit and held down 2, ablating. As ablating is animating I have moved on to 3, and so on. Run up to foes, hit 1, hit and hold 2, hit and hold 3... So on. If you kill something mid chain, like on button 4 it's ok! 1 will already be recharged, run to next baddie and start again.

Scrap or stalker? Scrap - combo route: you're not going to be able to use all combos, pick 2 that you want. Once you have that it's easy to set up your power tray. For example, by DB scrap power sequence is to press button number 1, 2, 3, 4, 2, 5, 6, 7. - non combo route - there's an optimal attack chain that ignores combo in guides in scrap forum, so, just hit the chain and watch animations. I don't have to look, I watch the animations, and that sequence is the power chain. Stalker - a bit more complex, but incredibly powerful, my DB stalker hits 550+ DPS. You largely ignore combos, but get them built in if you build for 170%+ recharge. The attack chain is BU, AS, AB, Sweep, PS, repeat. Also, don't have to look at the tray, just watch your toon play.

I'm all for adding new missions or content where higher end council are, but not in favor of a revamp of the existing missions. Sometimes I just want to thrash some pleeb council or warriors and when I want that it's nice to have milder groups. I never set foot in AE, never PL and play my way to 50 and beyond on all toons. While I thoroughly enjoy fighting Malta, carnies, IDF, arachnos... I enjoy having the option to relax and enjoy fighting factions that are less difficult, i.e. council, warriors, sometimes freaks or sky raiders. Please do not remove this option.

Hard no vote, sorry.

This

Sorry, no vote.

Resist in mids are using the wrong schedule, which is causing the discrepancy. The values posted are with no incarnates. It's pretty detailed as I explained it and simple to verify, if you look at the enhancement schedule live vs mids, it's clear that live is different.

Sorry, hard no vote