Mags permanent unstoppable bug returned

BuggyDClownBuggyDClown Member Posts: 2,352 ★★★★★
Mags heavy unstoppable bug was patched but new way of keeping the unstoppable have emerged.
If you heavy charge and instantly throw Sp 1, he will keep the buff. I tested it 5 different times and in different modes. Worked everywhere. This is not a good sign. I don't wanna face a bugged mags in t2/t3 war where he can go permanent unstoppable while I am being stucked in corner. Plus exploiting bug intentionally or unintentionally doesn't matter if game dev drops the punishment.
Or may be I am missing something if it was intended in this way.
(Before someone jumps at my throat, Mags works fine without any bug. But exploitation leads us to undesirable results and affects other areas. I have already mentioned the AW problem too)

Comments

  • Angryneeson52Angryneeson52 Member Posts: 449 ★★★
    Old news. Kabam is looking into fixing it
  • BuggyDClownBuggyDClown Member Posts: 2,352 ★★★★★
    edited May 2022

    Old news. Kabam is looking into fixing it

    Idk if it was mentioned here before. The bug earlier was with heavy use method. This is completely different. But if someone mentioned it earlier, my apologies
  • AverageDesiAverageDesi Member Posts: 5,260 ★★★★★

    Old news. Kabam is looking into fixing it

    Idk if it was mentioned here before. The bug earlier was with heavy use method. This is completely different. But if someone mentioned it earlier, my apologies
    Yeah. It's kinda known? But who knows how many threads before kabam acknowledges it
  • PapaMidnite007PapaMidnite007 Member Posts: 1,622 ★★★★
    Yes I noticed it too
  • BuggyDClownBuggyDClown Member Posts: 2,352 ★★★★★

    Old news. Kabam is looking into fixing it

    Idk if it was mentioned here before. The bug earlier was with heavy use method. This is completely different. But if someone mentioned it earlier, my apologies
    Yeah. It's kinda known? But who knows how many threads before kabam acknowledges it
    Fair point. I am just worried that even it is 1% Chance, I still don't wanna face him in AW at that state. Plus new players or some players who don't know mags fully or just rely on such bugs makes fuss tok much when it gets fixed. So if game dev can acknowledge it and giver proper insight,it can solve some if issues before hand
  • Raichu626Raichu626 Member Posts: 934 ★★★★

    Old news. Kabam is looking into fixing it

    Idk if it was mentioned here before. The bug earlier was with heavy use method. This is completely different. But if someone mentioned it earlier, my apologies
    Yeah. It's kinda known? But who knows how many threads before kabam acknowledges it
    Fair point. I am just worried that even it is 1% Chance, I still don't wanna face him in AW at that state. Plus new players or some players who don't know mags fully or just rely on such bugs makes fuss tok much when it gets fixed. So if game dev can acknowledge it and giver proper insight,it can solve some if issues before hand
    As far as I'm aware defenders can't cancel heavy charge into special. Even if they could, get him to throw another heavy and the unstoppable will fall off correctly.
  • Nightkiller7314Nightkiller7314 Member Posts: 117

    Mags heavy unstoppable bug was patched but new way of keeping the unstoppable have emerged.
    If you heavy charge and instantly throw Sp 1, he will keep the buff. I tested it 5 different times and in different modes. Worked everywhere. This is not a good sign. I don't wanna face a bugged mags in t2/t3 war where he can go permanent unstoppable while I am being stucked in corner. Plus exploiting bug intentionally or unintentionally doesn't matter if game dev drops the punishment.
    Or may be I am missing something if it was intended in this way.
    (Before someone jumps at my throat, Mags works fine without any bug. But exploitation leads us to undesirable results and affects other areas. I have already mentioned the AW problem too)

    you didnt even test his bugs properly lol, u just need to cancel heavy into any special attack(even sp3) for this bug to work, not sp1 only...
Sign In or Register to comment.