I never understood how that particular bit of logic could have been coded that way - it seemed so unnatural.
As kids we didn't know why this would happen, we just knew that it did and used it every game.
However, I missed that this part was the key and after a bunch of deaths I went on to level up my character past what the developers had probably intended at that stage of the game and subsequently managed to kill the Jester (he was strong enough that it was hard even when fully powered up).
Killing him probably lacked proper codepaths so the game crashed/blacked out and wiped the savegame forcing me to start over (quite an unusual thing to see in a SNES game).
If you deal 3 damage, it goes to 196. 196+60=256.
This overflows to zero and you win.
Chrono Cross is a very interesting game on its own but it's a terrible sequel that is remarkably spiteful to its senior. (The thing with FATE and Robo, the Porre thing, the fate of Crono and co., it's a terrible fanfic made canon).
Trigger only worked because of Toriyama gathering the all-star staff (look up the interview with Torishima giving the details). Cross was out of his hands and it shows.
Is it worth playing today? (I don't have any gaming consoles, and use macOS)
(I've never played an RPG, except for Disk 1 of the original Final Fantasy VII, which I really enjoyed).
- in Pokemon gen 1 you can wrap your stats back to zero by buffing them too much
- In FF7 you can overflow the damage calculation to kill Ruby in one hit
- Mario 64 has a mountain of usable glitches; "parallel universes" let you skip collisions at high speeds
- GTA 3/VC/SA have crazy mission/wrong warp corruptions involving parallel game simulations
- NES Mario can be corrupted to execute arbitrary code in TAS
- OOT can be heap-corrupted so badly you can write a loader for an entire DLC via controller ("triforce%", my choice for most insane controller based hack of a game)(I still need to finish the FoE romhack though)