Savestate to try to analyse/disassemble the behaviour of the elixir glitch. This glitch consists on equiping the GreenDream (auto-revive) on one character and have the entire party wiped out. Occasionally, when the character with the GreenDream is revived, the menu will be messed up and you can launch items on enemies. Launching an elixir on Lavos is an insta-kill (HP overflow probably). The problem is to make the glitch happen. It is very rare and sensible to a lot of factors: battle start RNG (for enemy attacks, ATB start, criticals, etc.), equipments, timing of commands... :(
This savestate is just before the Inner Lavos fight, and the glitch will happen. You can see it working if Crono lies down for a few frames after being revived. I also provide some savestates where the glitch does not happen by changing something.
I managed to reproduce the Lavos shell skip.
However, I didn't know which setup I need for the elixir glitch, which is faster to do before the skip :(
So now, I need to determine everything for the elixir glitch and probably do the shell skip again. It's really not hexedit frendly because it's based on making the game lag to make the other characters behind.
#13473109920628245 - Chrono Trigger any% no corruption -> Tyranno
For the fight against Tyranno, I can either kill Azala or make him sleep. I tried here to optimise the second choice, and I will do the same with the first one.
I hex-edited half of the run to grab a SpeedTab before Masamune, and spent hours to sync everything again, which has the consequence of saving and loosing random frames here and there (this game : ).
#13226432307013465 - Chrono Trigger any% no corruption -> after Magus