Il_JooO wrote: » Vision doesn't still any power, against ALL opponents, arena principally
Richy809 wrote: » To make things even more fun and interactive, OG Vision now inflicts damage on himself after any specials performed. Check it out - https://youtu.be/DtSFwNeQcHE
AreG wrote: » And Nighthawk. Huge huge issue, this should have been a priority and not taken as long as it has. Pathetic.
Il_JooO wrote: » It's not only Vision guys! Rogue:https://www.youtube.com/watch?v=ZArrCXm0PEs Magik:https://www.youtube.com/watch?v=kicBGBQco24&feature=youtu.be@Kabam Miike @Kabam Pertinax
Jon8299 wrote: » Don't worry we know it isn't just Vision. It's most if not anyone who has Power Steal or Power Burn.
Il_JooO wrote: » Jon8299 wrote: » 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
Il_JooO wrote: » Richy809 wrote: » To make things even more fun and interactive, OG Vision now inflicts damage on himself after any specials performed. Check it out - https://youtu.be/DtSFwNeQcHE 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!
Kabam Wolf wrote: » 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.
Il_JooO wrote: » Kabam Wolf wrote: » 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?