Thread: Swift Blade now blade wall with more power consumption?

They will fix the bug in the skill, right?

Originally Posted by Darmokk

This must be a mistake.

Yesterday I had a bad pull from this. My "1" key is now AoE, what the heck?

Originally Posted by Gylve

Huh? Swift Blade was always an AoE. Now it's just a hell of a lot slower.

Swift Blade is always an AoE, it replaces Swift Strike when Swift to Anger is traited, which also adds an extra pip on crit and makes Red Haze permanent while in Ardour. Just to clear up any confusion.

Originally Posted by Rapunzel666

relax, he probably is using cumaeth or the great river bow for stat padding, nothing to worry about

Completely OT - but - It's ironically funny how many so called legendary weapons Cumaeth has out-lasted. Every time there's a stat change Cumaeth gets more useful - now there's a weapon that actually grows with you.

And back on on topic - bad news - the Swift Blade issue is currently not on the known issues list despite the LM, Cappy and Mini bugs being listed as problems to fix. Does this mean it's a WAI change?

It's been three days now since this was brought up, and it's been asked about in at least two threads. Could someone from the dev team please let us know if this is a bug or if it's an intentional change? It's a pretty significant change to a basic class feature. If it's an intended change it should be a simple matter of letting us know. If it's a bug, it's not as though it's difficult to reproduce - you literally just need to use the skill to see the difference.

I understand that there have been a number of issues that have emerged from this update, and if this is a bug, I don't think anyone is going to yell and scream until it is fixed - everyone has been very civil and well-behaved in their queries. Having said that...it's kind of infuriating that no one can take the time to let us know if this change is going to be part of the game going forward or not.

Originally Posted by Moejo

Swift Blade is always an AoE, it replaces Swift Strike when Swift to Anger is traited, which also adds an extra pip on crit and makes Red Haze permanent while in Ardour. Just to clear up any confusion.

Thanks. I can see how I overlooked this when I traited around.

If you're experimenting with traits, know that this issue/bug makes Swift to Anger pretty awful, unless you're traited deep yellows and running in Ardour I suppose (it's still broken even then, but you'd probably still want to slot the trait for the Red Haze effects).

Before this animation change, traited Swift Blade attacked just as fast (i.e. extremely fast) as Swift Strike but with the frontal cone AoE. The extra pip on crit I *believe* applies for every crit, potentially giving you an instant 4 pips if you crit three targets. I'm not 100% sure of that but it seemed to work that way. Regardless, having that and Stalwart Blade slotted made for monstrous AoE dps and unslotting the trait resulted in markedly lower AoE dps parses for me. So yeah, I strongly encourage testing it out yourself as soon as it's fixed as it's a very powerful trait even if you're mostly red-line and live in Fervour.

Originally Posted by Darmokk

You use a bow and you dare show up in the Champ forum?

Yes, because the phys. Mastery and the Crit from the Great River Bow are just too good to miss out on it. Not equipping a bow was probably only useful in the Moors anyway.

Originally Posted by Vodomir

Not equipping a bow was probably only useful in the Moors anyway.

You lost me here. Why would you, past or present, not equip a bow in the Moors?

The theory is that in the Moors, you've often got targets moving just outside of melee range and back into it. Bows attack pretty slowly and you pretty much don't hit anything with them if you're moving. So the theory goes that if you're fighting and something moves out of melee range, you'll take out your bow and start lining up an auto attack that will likely miss anyway. The game mechanics force one bow attack to complete, though, so if you close distance while the bow auto attack animation happens, you've essentially got to wait for that to go off before you pull out your axes and start chopping people up.

Probably some very talented creep players would take advantage of that.

I also do not understand why treated swift blade does not benefit from the +10% damage of AOE skills legacy...

Originally Posted by Thorcar

You lost me here. Why would you, past or present, not equip a bow in the Moors?

Originally Posted by Gylve

The theory is that in the Moors, you've often got targets moving just outside of melee range and back into it. Bows attack pretty slowly and you pretty much don't hit anything with them if you're moving. So the theory goes that if you're fighting and something moves out of melee range, you'll take out your bow and start lining up an auto attack that will likely miss anyway. The game mechanics force one bow attack to complete, though, so if you close distance while the bow auto attack animation happens, you've essentially got to wait for that to go off before you pull out your axes and start chopping people up.

Probably some very talented creep players would take advantage of that.

He's got the right of it. The most important parts are bolded. Even if creeps don't actively take advantage of it, you can easily screw your own rotations up with errant bow shots. The best thing to do is to equip an instrument, and then swap in your bow when you want to use it.

Originally Posted by Jamers

He's got the right of it. The most important parts are bolded. Even if creeps don't actively take advantage of it, you can easily screw your own rotations up with errant bow shots. The best thing to do is to equip an instrument, and then swap in your bow when you want to use it.

Or just turn "accept miss chance while moving"off or whatever the option in your combat options is. Only time I ever pewpew is after let fly.

Originally Posted by Sulfur

Or just turn "accept miss chance while moving"off or whatever the option in your combat options is. Only time I ever pewpew is after let fly.

Word. I always forget that option exists.

A return to topic would be nice guys as the devs have still yet to answer whether this is WAI or a Bug. We're on what? Day 4 or 5 without a reply?

Originally Posted by cutlass81

A return to topic would be nice guys as the devs have still yet to answer whether this is WAI or a Bug. We're on what? Day 4 or 5 without a reply?

Don't hold your breath, I'm pretty sure it's WAI. Just swap in a better trait.

Keep bugging this, guys. I really doubt that it's WAI, but I'd love a dev response one way or the other, hopefully with a fix in the pipes. Those deep claws won't AoE themselves!

Just another response hoping for a dev to address this. Call me naive but I'd like to think they would not try to sneak in a stealth nerf and simply never mention it. Would be wonderful if a dev could give a simple "It's a bug" or "It's WAI" in response...

Oh Orion, mighty fixer of all that needs fixing, your champions eagerly await your words on the undisclosed change in swift blade!

There was a thread in the general discussion subforum that listed all things NOT posted that were changed. A couple of them had constant dev responses saying yes/no, it is/isn't bugged. The champ swift blade animation was a constant question, of which the devs are LOUDLY silent.

Get used to the new swift strike animation. Devs don't respond if there's bad news.

I'll only accept this as WAI if they rename the trait Slow to Anger then. This is garbage. I'm gonna keep this thread alive for as long as needed for one of the devs to respond. I absolutely refuse to be silent on this one.

I completely understand your frustration, and I know every single champ who has noticed this change is crying foul, but you must understand the devs don't have to respond. They should. Sometimes they do, when it suits them or the store. But considering how big an issue this was, and how it hasn't been answered in numerous unique threads, you'll probably be waiting a loooong time.

I am well aware of that. However I refuse to accept their silence on a matter important to me and others as well. They just fixed ardour and made it useful. This change hurts that considerably. In the words of the Irishman from Braveheart "Just answer the .... question."

7.1 patchnotes are up for Bullroarer with no mention of this bug. I guess that's to be expected since we haven't even had a hint of a dev response on the issue yet.

Looks like they consider this WAI.

The easiest solution for Turbine is to change the names of certain of the Champion skills. Most notably change 'swift' strike to power strike and change sudden defense to delayed defense as there is nothing swift nor sudden about them. Of course I would prefer the skills to do what they are supposed to but considering they have not made it into known issues implies they are not seen as a problem. Now if only our champs momentarily disappeared when using SS then it could receive some attention.

D'oh...the captain buffing bug, which was also not listed in the patch notes, got a dev response in the patch note thread saying that it's getting fixed, but still no reply re: Swift Blade despite my post being right below the guy with the comment about the captain bug.

Originally Posted by Fralin

Just out of curiosity, what are the longest standing bugs (that makes a big difference) that have not been fixed? The ones that spring to mind are

Balrog in rift (stuck in combat) since release
Draigoch - still on brains after ½ year

\\\ Offtopic\\\

I personally think the longest standing bug that affects multiple players EVERY day since release is the distance bug in the ettenmoors.

Distance Bug: The fact that infamy/renown rewards are divided by the ENTIRE membership number of a group that hits an opponent but only awarded to those in proximity. If other rewards, loot drops, exp, coin, worked that way it'd have been fixed immediately.

The solution...divide by those present at the time of the reward. Anyone outside the range of the reward, or even the zone should not count towards the denominator when dividing the reward.

Ugh...terrible. I personally lost hundreds of thousands of renown this way. Back in the day I didn't ever think I'd stick with LotRO PvMP all these years and I ran my first 9+ ranks almost exclusively while grouped with friends playing alts outside of the moors, this was before we had a vent server and we used in-game voice to chat while I hunted solo in the moors and they leveled alts.


----

But to swift blade...ugh I wish they had never even touched swift strike.

Swift blade was the single best aoe trait, don't knock it 'cause you couldn't figure it out.

This thread would be a lot more helpful if I knew what "WAI" stood for....

Originally Posted by MommaNinja

This thread would be a lot more helpful if I knew what "WAI" stood for....

Works as intended. Aka, its not broke, so they're not going to fix it.

Originally Posted by MommaNinja

This thread would be a lot more helpful if I knew what "WAI" stood for....

Company mantra

Originally Posted by Gylve

D'oh...the captain buffing bug, which was also not listed in the patch notes, got a dev response in the patch note thread saying that it's getting fixed, but still no reply re: Swift Blade despite my post being right below the guy with the comment about the captain bug.

A dev finally responded to inform us that this is in fact bugged. However there is no ETA on a fix but at least we know that they have acknowledged it and it is not WAI.

Here's a link to the dev response on the swift-blade bug...

Aww yeahhhh o/

Originally Posted by Caffeinatedlife

Here's a link to the dev response on the swift-blade bug...

On the downside there is still no acknowledgement of everything else in the RoI issues thread.

Atleast they finally responded that they know about it and they are working on a fix for it.

Up.

Ok, nothing yet?

Huh? There was no patch or anything today. Just server maintenance.

Ya, but I think they aren't working to fix it. What now? 1 month?

do they even know this ??

Yeah, they know.