i was excited to dupe my AOU today, but also not really because of this bug. just had an arena fight against HE where power burn was working and doing damage, but vision wasn't stealing any power
Yes ive completely dropped vision AOU from use and i have him 4* 4/5 duped and i used him for AQ and questing when AQ wasnt up. Now hes pointless to use and had to switch up my roster and everyone knows we wont get compensation for this issue or any appreciation for our patients for there mess up but want us to spend money and waste the precious time we put into this game.
Glad this is a known issue, I noticed a couple weeks ago. Yes, its on/off. Just used him in arenas and he burned, just didnt steal. It didmt even say he stole. Had to verify its supposed to happen every time cus I did his L1 three times.
So either turn poison and bleed off on all node boosts until you guys get this **** fixed, give us a ton of potions for compenstation, or for God's sake just fix it. You realize how many of us forced to use one of the Visions for their bleed/poison immunity in aq, yet no progress here in over a month. And don't give me there are other immune champs ****, maybe we don't have those champs or the means to rank them up if we do. It's funny how when people are collecting extra rewards or completing LOL more easily fixes are pushed within 24 hours, yet **** like this just ferments in the game for well over a month. At this point I am convinced a lot of these "bugs" are intentionally ignored and quite possibly even intentionally introduced.
Hey everyone. The team is aware that it's affecting everyone with Power Burn or Power Drain. It seems to be the most consistent with Vision, however, and that is by far the character we'r seeing the most reports about. Either way, the team is working to fix the issues across the board, not just for Vision. Thank you all so much for bearing with us on this. I know it's a super frustrating bug.
Hey everyone. The team is aware that it's affecting everyone with Power Burn or Power Drain. It seems to be the most consistent with Vision, however, and that is by far the character we'r seeing the most reports about. Either way, the team is working to fix the issues across the board, not just for Vision. Thank you all so much for bearing with us on this. I know it's a super frustrating bug.
3 days from official answer, how much time do the team need to fix this issue?
I can't understand what these kabam programmers are coding into the game. How is it possible to code such a horrific bug into the game and fail to roll back the wrong code afterwards. These bugs don't pop up randomly some changes were made to the code and I can't believe that there is no change tracking...really sad...better recruit some professional programmers..
A bit ridiculous that this is still an issue over a month later. As someone who invested many sig stones (at lvl 99) into vision and uses him in alliance events constantly - this affects me and my alliance greatly. It's not some small bug, and it's honestly pathetic that Kabam hasn't fixed it in over a month. Might be time to start hiring some new folks.
Hey everyone. The team is aware that it's affecting everyone with Power Burn or Power Drain. It seems to be the most consistent with Vision, however, and that is by far the character we'r seeing the most reports about. Either way, the team is working to fix the issues across the board, not just for Vision. Thank you all so much for bearing with us on this. I know it's a super frustrating bug.
3 days from official answer, how much time do the team need to fix this issue?
Comments
Check it out -
this is absolutely AMAZING!
Kabam you did a really GREAT job, I must admit it!
@Kabam Miike please check it out the video, you'll find it really interesting and funny, laugh with all of us!
Hawkeye that is.
Rogue:
Magik:
@Kabam Miike @Kabam Pertinax
Don't worry we know it isn't just Vision. It's most if not anyone who has Power Steal or Power Burn.
yeah I know we know, but do they? xD
We can only hope.
3 days from official answer, how much time do the team need to fix this issue?