After Digivolution, the Move indicator stops working

[AndreaJens]

This bug only applies to Rookies: the memory address where the frames and the move index after a Digivolution is stored in another set of memory addresses, thus not allowing the script to use this information. A possible fix is finding the relative values for the evos and hope that there is a consistent rule behind them.

[AndreaJens]

After a quick test, it appears that the memory location where move indicator and frame indicator for the Evo are stored, after a Digivolution, depends on the match-up, like the size of the lifebars. It might be impractical to make it work without some time around it. One needs to test all 24 characters in mirror matches to retrieve the offset for this feature.