Buff gone wrong?

[(PSN)Angel_OfSolitude]

Hey so I was super excited for that miter buff after I saw the stat changes and after it dropped on PS4 I was expecting the better charge rate and occasional crits to further my excellently scaling set-up (groups of level 140+ heavy grineer in 5-6 shots) but instead it actively hurt it. I'll link the video and explain further below please watch the whole thing. (sorry there's no audio I decided to spare you my horrible voicing)

 

https://www.youtube.com/watch?v=6_IJDMfNY7Y

 

on the pre-buff test it took out 8 level 140 heavy gunners with 5 shots that did something and a sixth that looks like it did nothing, on the post buff run it took 14 shots and I had to cover my &#! with a crush at the end, granted I did have a helminth for the first try but it didn't make enough difference to justify more than double the shots. both the mag and miter builds are exactly the same in both clips. After looking closely it seems to be the blade's interaction with magnetize, they no longer fly outward and then back in they just break and fall to the side. I'm not expecting DE to devote time to fixing one guy's problem (would appreciate it though) just want them to be a little more careful with future "buffs". 

Anyone else had issues caused by buffs? feel free to share below.

 

Side note: I liked the flashy blades why would they get rid of those. watching the blades fly around was half the fun of the build.

Edited May 1, 2017 by (PS4)Angel_OfSolitude

[Airwolfen]

No problems on my side. Buzlok has joined the ranks of one of the strong weapons in my arsenal.

[Fallen_Echo]

Most buffs felt weak or nonexistant (glaxion ammo usage).

There were a great video somewhere where the creator showed the difference between pre and post buff on weapons.

[Xekrin]

38 minutes ago, (PS4)Angel_OfSolitude said:

After looking closely it seems to be the blade's interaction with magnetize

Sounds like an issue with the punch through to me.  Panthera is similarly affected and although they said it was fixed in 20.0.9 I do not believe this to be the case.

In other words, its a bug and will hopefully be corrected soon.  Of course this doesn't help you as you'll likely be waiting another month for an update.