Startes match 1.1 and after the screen loads i get a grey and black match backround and nothing else loads up.
the objectives are missing in the pause screen.. i had to Quit !!!
not impressed !
OMFG after i quit. i close the game. reload it and tey again…
as it starts loading i get a something went wrong error message and grey and black match background again.
Good thing i checked here. I officially have lost all my first round charges to this glitch. Wonder if the devs will see this before the event supposedly ends
Is there a fix on the way?! Or are we all to crash out in node 1 and take our chances with nodes 2 & 3?! Few players are unaffected, and as such, those player’s coalitions are benefiting whilst the rest of us are simply crapping out to bugs or waiting for a bug fix… either way, both the progression reward and top 10 rank (in a top 10 coalition) for my coalition are in jeopardy.
The team is aware of the issue and looking at what is causing the issue with the first node in today’s event. Thank you for reporting this and we apologize for the inconvenience.
1 - Test before you deploy.
2 - Use a revision control system so you can back off bad updates.
3 - Use telemetry so when everyone suddenly fails the easiest mission and force-quits skyrocket you can back it off because something’s obviously wrong.
Normally I charge for this but I’m telling you for free because I happen to like this game.
Same here, nodes 2 and 3 played 3 rounds in each one without errors. First try in node 1 and get an error thath took my 3 remaining rounds.
The game should control if the player has started the battle before removing a round. It would be nice when network fails (has happened to me befor this bug, loosing a round just because I lost network signal).
Happened 3 times on node 1.
Node 2 and 3 have been fine.
Apologies are great, but it doesn’t help our points on an event with a rare locked behind a reward at 460 points.
There should be a way the devs can adjust point values for the players affected, or speed up the time of the recharge so we have more shots at the other 2 nodes, or lower the price of all the rewards (or at least the final reward by like 60 points or so).
Are the Devs going to do something like that? At this point most coalitions are at least 15% through and many of those are failed first rounds.
And let’s be honest… unless you’re playing a ton and throwing crystals around for cards (or paying money), I’m sure there are many players that can’t even mess with node 3.
Seriously. There is literally zero reason this should have gotten through QA.
And even if it did… a rollback should have been easy to do and implemented immediately.
AGREED!
The loss of round issue is ridiculous when the game crashes during events. This has happened to me several times in the past.
It shouldn’t be hard… it’s just a flag you keep in memory called isMatchStarted and you set it to true after the first gem match.
Or even after the first drawn card since you literally do NOTHING before you get your first card drawn.
You’re connected to the internet the whole time… You should be able to delay the ping back to the server until the first card is drawn.
I love this game and I love the fact that it’s free to play (for the most part) but these types of issues have to stop.
There’s a reason that this game has over 1M downloads (Android) and only 25K people join these events.
You’re losing your player base b/c the game is temperamental … Oh… and it’s gotten to the point where it’s “Pay to not suck”
Not to mention any “starter” players out there who haven’t even gotten to the point where the second, let alone the third, wheel are even considerable. This glitch prevents any new people you want to keep from playing this event.
Q: Why do hairstylists refuse to put “dreads” in the mane of a horse that’s already been put down?
A: Because there’s no sense “beading” a dead horse.
We’re all telling you the same thing from previous events where you put out the event with some play-hampering issue that could easily have been discovered by QA (that usually stands for Quality Assurance, btw) testing before release. Even just a developer testing it, themselves, on an emulator (which, btw, is viable, in this case).
Just try a little harder to show you’re considering the Quality in this game for people who spend money on it, if not everyone, mm’kay?
Seriously - no less than 4 times the first encounter with the enraged giant failed. Causing a delay / time out and limited play. Real.bug… as it didn’t crash due to my device as support will always tell you. This is proved as my avatar lost no health… but my access to the encounter was lost. This game has become.so poorly supported and crashes / bugs so frequently now?