I've noticed that after the latest patch, even though on hit it honks I don't see the buff icon anymore and I really can't tell by the damage inflicted if it's working or not.
Any comments on this issue?
I've noticed that after the latest patch, even though on hit it honks I don't see the buff icon anymore and I really can't tell by the damage inflicted if it's working or not.
Any comments on this issue?
I think it's true, heard the same from other people.
Luckily everything works just fine on old-gen ![]()
No official comments yet, it's been broken since saarebas release.
I was wondering the same! Glad it's not only me who thought there was an issue with this working correctly. Agreed, I can hear the horn blow every so often when I attack but that's about the extent of it.
Can confirm it is broken. I have never had it proc for me.
![]()
So you are pining for a broken weapon eh?
workingasintended
they patch the game and break other things to balance it out.
So you are pining for a broken weapon eh?
Pronto blows it all way out of proportion. I genuinely don't care about getting it anymore. Yes, I was disappointed when I didn't get it as my fourth, but I have long since accepted it as a fact of life; I will never get it.
Exactly lol but yes happens to me tooworkingasintended
they patch the game and break other things to balance it out.
Ehh, it's probably a combination of not many players having it, plus those that do tend to already be able to kill things so quickly that they don't notice it too much.
That said, Bioware Plz Fix.
I was told on the stream last friday that the devs won't fix bugs unless there is a general consensus that there is a problem by spamming the forums with rage. Otherwise everything is working as intended, since if they try to fix bugs they might create other bugs
I was told on the stream last friday that the devs won't fix bugs unless there is a general consensus that there is a problem by spamming the forums with rage. Otherwise everything is working as intended, since if they try to fix bugs they
mightwill create other bugs
Nice philosophy for BW if true ![]()
I was told on the stream last friday that the devs won't fix bugs unless there is a general consensus that there is a problem by spamming the forums with rage. Otherwise everything is working as intended, since if they try to fix bugs they might create other bugs
Suspicious paraphase is suspicious ![]()
Always watching ![]()
Suspicious paraphrase is suspicious
Second hand news is always the best.

Since I haven't landed the 2H hakkon yet, and likely never will like Snakebite, I cannot attest to the issue, but I don't remember seeing any difference when the weapon proc went off while I was in close proximity.
It will require a patch to fix the issue but it will be addressed (and yes, it does nothing right now save for flashy lights). As for what was said on the stream, as far as I recall - and I'm only half listening on the stream, even to myself - Billy was talking about how issues get prioritized. This doesn't necessarily mean that something like this wouldn't get fixed, simply that other things would take precedence.
It will require a patch to fix the issue but it will be addressed (and yes, it does nothing right now save for flashy lights). As for what was said on the stream, as far as I recall - and I'm only half listening on the stream, even to myself - Billy was talking about how issues get prioritized. This doesn't necessarily mean that something like this wouldn't get fixed, simply that other things would take precedence.
You could have said "Hey Meatheads, game-breakingly insane issues are solved first. Ones that keep are detrimental to the whole. YOUR SWORD STILL GOES *BOMP*"
Related note: did the Blessed Blades proc also come with a 10-15% damage buff and does that (still) work?