How did this get past testing? AW bug
Scottryan
Member Posts: 475 ★★★
I'm just wondering how something like this can be allowed to get past testing. Remember when we got the patch that fixed the global? Well guess what? Not a great fix! It still doesn't work. Thanks for killing me in war twice when I use my special attack
I'm just flabbergasted that a bug this serious can get past testing and get put into what's supposed to be the most serious and competitive mode in the game
Please fix this.
This is probably the worst season of Alliance War ever, and it just keeps getting worse
This happened twice BTW (:
https://youtu.be/FZU-BxVDWOg
I'm just flabbergasted that a bug this serious can get past testing and get put into what's supposed to be the most serious and competitive mode in the game
Please fix this.
This is probably the worst season of Alliance War ever, and it just keeps getting worse
This happened twice BTW (:
https://youtu.be/FZU-BxVDWOg
Post edited by Kabam Zibiit on
6
Comments
All games have them.
MCOC is complex and constantly being updated with new champs, nodes, abilities, quests. Bugs are expected.
If you expect this game (or any game) to be bug free, then you are living outside of reality.
Any response would be awesome
Please?
Doc ocs heal block (when he is dupped) works by letting them regen, and doing red damage equal to the regen automatically.
Conduit is trying to heal back from the red damage which is creating a loop.
That's what causes the crash. The game can't do the math fast enough so it just freezes.
Tell your programmers to either make the red damage from doc ocs heal block an exception for the conduit regen, or put a cap on how many times it can trigger the regen in a second
Either way the problem is with your node. You let it loop. That's the first thing you're supposed to look out for when programing. This should not have gotten past testing. Use doc oc once and you would have found the issue
@Kabam Miike @Kabam Zibiit @Kabam Jax please make sure this information gets passed to someone in charge of programing. Please. I'm trying to help. I've told you why the bug happened, so PLEASE go and have someone fix it
Real money equates real solutions. If you can't be bothered to fix things, then don't offer products that don't work as intended.
Full stop.
Not to mention, OP's device isn't listed which is another variable that isn't accounted for in this post. Obviously tested should happen but there really isn't a way someone can say this exact scenario should have been found during testing.
But I understand, I'm your eyes, testing should catch everything.