description explains it!

The game simply goes back to round 1 after round 256 - no crazy fanfare or anything!

I think this even happened to me TWICE on the final marathon, too. One of those times I'm pretty sure was caught on stream. I'll see if I can find it

There is a long invulnerability period after getting hit by an enemy, and it was still active from when I got hit by the last anglerfish.

@@Winslinator damn, I didn't know it was THAT long. Anyway, nice run!

Now that is a very interesting level TAS idea and would love to see how that would play out fast! Looks like you would need the assistance of two sets of drips to make the level possible and I agree this could be a nightmare to manipulate. In an earlier comment, I sent you a link to a list of RAM addresses on the Kid Chameleon Wiki, but this game also has a disassembly which has a much more complete cataloguing of RAM addresses here: github.com/sonicretro/kid-chameleon-disasm/blob/master/doc/ram_layout.txt To answer your first and second questions, you can Ctrl+F for the term "rng" to find the RAM addresses which control that. I have never attempted to do a deep-dive into the RNG for this game, and have personally preferred to just use trial and error to get an outcome I like! For your third question, you would want to navigate to the section where it discusses GfxObjects. In RAM, the data for each GfxObject is stored in blocks of size 0x4C, starting at 0x2448. Given the offsets provided in the disassembly, the important RAM addresses for the first object slot are therefore as follows: Object 1 X position: 0x2462 Object 1 X subposition: 0x2464 Object 1 Y position: 0x2466 Object 1 Y subposition: 0x2468 Object 1 X speed: 0x246E Object 1 X subspeed: 0x2470 Object 1 Y speed: 0x2472 Object 1 Y subspeed: 0x2474 Then if you wanted to find the X position of Object 2, you would just do 0x2462 + 0x4C = 0x24AE, and do so on and so forth to save these values for all object slots. You would know when an enemy spawns if there is a sudden change in the values in one of these slots. For instance, if you're moving along and suddenly all the Object 5 RAM addresses change from null or garbage values to things that suddenly make sense, something probably just spawned. As an even more specific example, if 0x2592 (the address for Object 5's X position) changes value from 0 to say 512 (a sensible X position), you know something spawned on that frame.

It's a quick and easy but also risky way of building up experience

Yes, this was played on the Sega Smash Pack 2 port

It was intentional. Many other cheat codes in the vectorman games spell out pneumonics like this, such as: CALL A CAB CALL DAD ALABAMA LLAMA RADAR DRACULA ABRACADABRA UR A BAD LAD

The hoverboard guy automatically moves in the direction he's facing, I don't need to be pressing left or right.