Skip to content

Instantly share code, notes, and snippets.

@LuisMayo
Last active April 6, 2022 22:29
Show Gist options
  • Save LuisMayo/bbdef8821459250ee44cd3ba20c18ddc to your computer and use it in GitHub Desktop.
Save LuisMayo/bbdef8821459250ee44cd3ba20c18ddc to your computer and use it in GitHub Desktop.
Notes about clash of heroes bugs

Bugs

Ilegal saving.

Ilegal saving has proven itself worthy of several side-effects. Like cutscene characters duplicating, game crashes and (Extended) battle bypass. You perform ilegal saving by opening the pause menu using the back button on your android device. Note that the ingame pause button is non-existent or disabled when you cannot save, like in cutscenes and animations, but the back button will open the pause menu anyway

Battle bypass

BB is performed by saving the game while we are on the walking animation towards a node occupied by an enemy. After reloading the game, the enemy will be dead. Sometimes it's still alive but their death consequences will fire (giving you an object, letting you go past them, etc). This may be because the game on loading interprets you being in a node where an enemy should be as you having won the fight. Battles bypassable with BB will be called Type 1

Extended Battle Bypass

EBB is a variant of the Battle Bypass bug. Which let's us bypass several battles that are not skippable using BB.

To perform an EBB bug, we first need to attempt a BB bug.

Some fights, like Sir Varkas do not play well with BB. When attempting BB in this fight, the fight will immediately start when reloading the save. For this battles, we might use EBB glitch.

First we set BB up. This means than loading the save game should lead to the fight starting. Once done we load the game. Just as the game is loading we must immediately start moving towards any other node and save the game during the moving animation (like in BB). This is exactly like performing BB two times in a row

After reloading we will have bypassed the fight. This comes with a caveat though. While in BB the game acts as if we'd won the battle, this isn't the case in EBB where story may not progress and certain flags may not properly work. For instance, extended-bypassing the Sir Varkas fight doesn't let you progress through the logs puzzle.

Battles bypassable with EBB will be called Type 2 Non-bypassable battles will be called Type 3

Aplications

Unless specified, it is assumed that battles are Type 1 (bypassable using BB bug)

  1. Sawing tree fight: This fight is Type 2. Bypassing it using EBB won't set the required completion flags and the top of the tree fight/cutscene won't be triggered
  2. Sir Varkas fight: This fight is Type 2. Bypassing it using EBB won't set the required completion flags required for the logs puzzle to properly work. More specificalñy the puzzle can be done but not restarted and completing it properly won't unlock the path anyway
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment