Discussion: solutions for game freezes and open petition for "unstuck" feature

Elektrophorus

I'm bumping this post because it's ridiculous why this hasn't been implemented yet.

Unknown

This content has been removed.

arNero

The only thing I must disagree with you, OP, about this matter is that "Android users only can click the back button to return to the game". As an Android user I can say that I think it did work to an extent some time ago with stuck cards, but recently, this solution does NOT work at all. I suffered two soft-locks earlier (one from Serpentine Strike completely ignoring my Not Now command and disallows me to even kill my own creature, forcing me to forfeit, and the second one if from Demolish destroying one support and a total of eight gems, and the remaining gems hung in the air, forcing me to forfeit); In neither situation does the back button work.

That one thing aside, I appreciate this thread. This game has one of the buggiest game clients among the many games I've played, and frankly, rather than suggesting a "fix", I firmly would rather we have a fresh, brand new client which hopefully is thus free from whatever bugs that have completely ruined the game in this iterations. I know, to be frank that is an impossible order; we are talking about a company that is nowhere the scope of Microsoft or Disney or the like (do excuse me for exaggerating) who should have more than enough manpower to think up a better game client in an acceptably short enough time. There is no resource, so much as I hope the game's problems can be fixed, fresh client is definitely out of the question.

Elektrophorus

arNero said:

The only thing I must disagree with you, OP, about this matter is that "Android users only can click the back button to return to the game". As an Android user I can say that I think it did work to an extent some time ago with stuck cards, but recently, this solution does NOT work at all. I suffered two soft-locks earlier (one from Serpentine Strike completely ignoring my Not Now command and disallows me to even kill my own creature, forcing me to forfeit, and the second one if from Demolish destroying one support and a total of eight gems, and the remaining gems hung in the air, forcing me to forfeit); In neither situation does the back button work.

So the thing is: I wrote this post originally in August of 2018.

Back then, soft locks felt much rarer, with things like art freezes or stuck confirmation windows more common. The thread still applies, though, that Android users have one more option to fix these types of errors.

WiLDRAGE

starfall said:

DBJones said:

Having it auto-save at the beginning of each player's turn (possibly at each extra swap too) would be a huge help in freeze recovery. Also, it would be very difficult to abuse as long as you can only go back to the start of the turn. Just have the server save the date modified (a tiny amount of data, you'd only need one per player) and you could have the save file on the player's device.

I'm afraid I don't like this either. If you don't get a cascade that you like, you could endlessly reset the game until you do. There's a way around that problem, of course, which is to pre-generate the gems which are going to drop in for you in each column... but again, this is information which you can learn by repeatedly resetting your game, and use it to your advantage.

I'm not suggesting that players are going to be resetting their games all the time to gain tiny advantages, but they will if they're nearing the end of a 3 day coalition event and 100+ jewels are on the line for them.

Personally, I would rather it be seeded so that the exact same gem cascades occur each time after a crash/freeze/reset but have save points after each card successfully resolved and after each individual creature attacks.

I understand there's a lot to track: hands, decks, graveyards, exile, jump-start mana, gem board state, gem cascade state, loyalty count, but given that all this is required to play, there's no reason I can see, without having access to the source code, not to be able to save it.

There's another reason this would be incredibly useful.  If a game truly gets into a state where it simply cannot continue (constant soft-lock for example), the devs would have a literal copy of the game state available to them for debugging purposes.

Brigby

*Closed this thread as bumping old threads to "revive" them is against the forum rules.

While I understand that many players are passionate about their ideas and would love to see them become implemented, bumping old threads back to the main page obscures newer posts and ideas from other players.

In other words, we want threads to remain on the top pages through organic engagement and popularity, as opposed to the author bumping it back up. If it was another player that discovered it though and wanted to contribute to the conversation, that would not be considered a bump and it would be allowed to stay on the main page, provided that all the information in the thread is still correct and relevant.

Thank you for understanding.