Ban Wiccan from Battlegrounds Until He is Fixed
DalBot
Member Posts: 1,632 ★★★★★
Title says it all. It sucks having to perma-block a mediocre champ because the game crashes every time you fight him. Garbage move to leave such a broken mechanism in the game
Post edited by Kabam Zanzibar on
6
Comments
Having said that, the issue persisted for something around 3 years. Reported multiple times, never ended up being fixed. I wouldn't expect this one to be
I ban him every time but it sucks having to waste a ban based on a glitch that is known and is inherent to literally thousands of iPhone users. It puts the opponent at an immediate measurable disadvantage since we only get three bans.
It really shouldn't be that difficult for Kabam to block his ability to be put in to battledecks at all.
He is a pretty good champ but he would be a mediocre BG defender if not for the glitch. At high levels nobody would be banning him if he functioned as intended.
Dr. Zola
https://forums.playcontestofchampions.com/en/discussion/321169/wiccan-bug-is-back-and-it-just-cost-me-an-attack-bonus
https://forums.playcontestofchampions.com/en/discussion/306898/event-quest-glitch-uncollected
https://forums.playcontestofchampions.com/en/discussion/313011/game-crashes-when-fighting-wiccan-in-side-quest
https://forums.playcontestofchampions.com/en/discussion/306347/game-crash-during-final-eq-wiccan-fight
Seriously, when something tends to break on either certain hardware or certain software configurations, but not in general, the two most often causes of that sort of problem are either a race condition - where the software was written on the assumption that two different events will always happen in a particular order, but in rare cases it can happen in a different order (keep in mind: multiple CPU cores and multiple execution threads means it isn't hard for the order of things to sometimes happen differently than designed) - and resource contention, where the software has a hidden dependency for certain resources to be available at a very specific moment, and in certain rare hardware/software configurations those resources happen to not be available, whereupon the software barfs.
I saw a problem years ago where two different platforms running almost identical software had a situation where a server process was crashing on one and not the other, and the problem was traced to the fact that while both had the same amount of memory, that memory was getting more fragmented on one of the platforms due to some very minor differences in execution, and that fragmentation ended up causing that platform to run into a problem the other wasn't seeing. Even though they had the same amount of memory and was using the same amount of memory, *how* they were using it was slightly different, and that's all it took.
Insert mobile-phones-are-very-complex-things speech here.
There's generally some fundamental bug that causes this, but because bugs are often addressed by seeing them and then fixing them (i.e. debug by compiler, debug by customer) when a bug is hidden by the fact the software coincidentally works with the bug most of the time, it can be very difficult to find and fix.
But sure, I'm being irrational here 🤷🏻♂️
Dr. Zola