is hard to say because it’s…rng though sometimes it does feel like you pull the absolute worst combo of four for a handful of battles and then it suddenly turns around.
I want to say no, but sometimes I swear something is going on when you can be winning a battle and the game will suddenly crash or you’ll lose connection out of the blue (even if the connection is stable) resulting in you losing. It’s happened to me more often than not to make me side eyes it whenever I run into it because it’s a little too convenient for the other player.
Within our alliance Discord, we’ve always supported the theory about a hidden algorithm that gives you loss streaks. Regardless this algorithm exists or not, loss streaks are real and follow a regular cycle. When it happens to 50 people in the same alliance, it’s hard to believe that is RNG based. It may be RNG factors (flawed matchmaking, RNG team selection, scarce number of actual players, use of suboptimal team compared to current meta, RNG resistances and dodge system, RNG crit ratios, etc) that combined result in a not RNG at all effect (win/loss streaks). So regardless there is no code for having a loss streak, there’s a lot of code that leads to it.
There’s a well documented hack that allows a player to achieve critical hits 100% of the hits. I have suffered this several times. Several members of my alliance have suffered this from the same player in the arena multiple times. Several of us have reported this player. But still have found him playing and abusing the hack after multiple reports. So…
This analysis may be flawed from the start. Top players run optimal teams. Optimal teams minimise RNG effects, because they’re playing top creatures vs top creatures or top creatures vs inferior creatures. In the first case, RNG will equalise in the long run. In the second case, your top creatures are mostly winning versus inferior creatures. RNG and streak losses have the highest impact when you play suboptimal teams (meaning when not all your 8 team creatures are the top meta creatures of the moment). A very large proportion of the playerbase (+90%) are playing with suboptimal teams and cannot escape from the “not so RNG” loss streaks that I explained in my previous post.
I don’t tend to buy into conspiracy theories, but I do find that occasionally I will have a loss streak of about 300 trophies, and it’ll always come with a lot of battle timeouts (like 2/3 of battles I attempt will time out without ever getting to the AI button when normally I rarely have issues). I wouldn’t be at all surprised if there’s some matchmaking tweak going on during those periods (like maybe the game matching me to a different opponent range) and the game is having a harder time matching me to opponents, hence the timeouts.
Funny enough, our loss streaks usually drop us around 300 trophies before the streak ends (talking from a bunch of our alliance members’ experience). I do experience the timeouts not linked to loss streaks, but I may experiece them as well during one of those loss streaks.
I sometimes think #1 has to be happening, but then I realize - if they were that good at coding the game wouldn’t be as glitchy, buggy, and awful as it is… and I think that’s more to the point. It’s not that they’re so sophisticated to program in such things, it’s that they’re NOT and that’s why things are the way they are
You enter a battle, start winning then a pink screen appears and you are thrown back to the map. If you restart the app, you will get back to your battle where the opponent has already taken 1 or 2 of your creatures, probably depending on the speed at which your phone starts the app.