[reported] Cliffy error in Explore battles

No hero looking, game crashed at start of battle with this error code. And game forced to restart. Thank you.

Is this only happening in Explore battles, or elsewhere?

Also, only when trying to start the battle? @yOkO

Not sure about OPs case, but this happens when mashing through the victory screen for a side quest battle. If you spam the button quickly enough, it tries to start the side quest again and cliffycrashes. The node takes a second to “x out” when you get dumped back on the map, and it’s selectable again for that instant. There’s a similar issue in other map-based game modes.

Also, mashing through the initial difficulty selection reopens the difficulty menu instead of starting the first explore battle. That doesn’t cause a crash, luckily.

1 Like

@Jeto it happened once last yesterday before I went to sleep. it was at start of battle in E16, I did not have a chance to see this error in elsewhere yet. Thank you.

it happened again just now beginning battle 3 and crashed with this error codr in E16. Thank you.

It happened again now battle 3 gold side quest finished and begin next battle crashed with this error cold E16. Thank you.

Right, so what if you are not hammering to go through the screens? Cos the original cliffy error here is also triggered when starting the battle, not at the end of it.

Also, doing that is known to break things generally, so I would avoid it if you know that.

Is it only happening in Wild Plains? As all the errors shared here are for that Kingdom.

Also, is this when you start the Side Quest or when you start a normal battle @yOkO

We have tried to copy your data to reproduce it, and we haven’t had any issues. We can start the battles no problem. We also cannot see anything in your data that would indicate something is wrong or that these side quests have been completed.

I only play in Wild Plains E16 exclusively so I do not know if it happens to other kingdom. What I notice is that if I press too fast and the dots to the next battle not fully fill up, it crashed at battle 3 does not matter side quest or not. If I let the dots go through to the next battle node, it seems fine no more crashing.

So just dont play fast. Cool solution huh?

Cliffy issue doesn’t stem from fast gameplay, but rather from incorrect links and the triggering of the wrong battles. Take the bug shown in the screenshots, for example: a side battle is obtained, yet it is labeled “Eternal Dragon.” The subsequent battle—whether it’s the second, third, or fourth one—also plays out as a finale, even though the map indicates that shouldn’t be the case

In screenshot 2: the combat highlighting is missing. Where did it go?

In other instances: the battle menu remains stuck on the side battle stage and does not advance along the map. The next main battle (2, 3, 4, mini) cannot be selected. The user doesn’t notice the problem and clicks the battle button—a “cliffy” ensues.

The interface results in the wrong kind of combat. Button-mashing speed has nothing to do with it

right, so for now.. and everywhere in the game, please don’t spam the buttons waiting for the next screen. You can’t skip this animations to spamming the button is only going to cause a crash.

2 Likes