User Files from FatRatKnight

BackJumps into Perma-Sprint. If ever you wanted to see just how powerful Perma-Sprint is, here you go.

The start here is to pick up a Mortar weapon early in the stage. Then the BackJumps are used to reach 4+ pixels per frame, so that we can peacefully charge up Sprint mode while outpacing the camera. We go for a swim right after, triggering Perma-Sprint and you can see what that means for our hero. We even found a door we can simply clip through because the terrain there is hollow, and Perma-Sprint is so fast we can pick up the Mortar in there and continue on our merry way all before the camera catches up.

After that, I'm not entirely sure what precision planning is happening for the last two victims. Disorganized notes, I say. It reflects where I stopped in my TASing of this particular stage as well.

This little segment was worked on by me before we just sort of dropped things. I wanted to see how early we can spawn a snail, didn't attempt to manipulate the luck to have it going west quickly.

As far as we can tell, it's best to mostly follow T8's route through this level. A few early items are picked up. The second key we pick up is called the Embedded Programming Key, where we BackSlide into a terrain embed to grab it off the desk rather than jump. The first actual wall we clip through is actually "hollow," with a single tile gap inside it that allows us to bypass it with a speed much lower than 16 pixels/frame. We then work our way north and stopped at the snail manipulation.

The rest of the route is basically planned to be T8, except that we set up Perma-Sprint on a bench while waiting for the imps to kill victims for us advance upon victims that we horrifyingly are unable to save.

This was the script we developed in the DTC. Has hitboxes, position, and speed. And a few random things. This was my version, without the side-radar.

All this one does is look at a few addresses to figure out when stages begin or end, as an assist to figuring out when we completed them.

Shows terrain boxes. Has an incomplete thing I was trying, the list of special terrain IDs are at the top, but that table wasn't used. Has something else I hacked together to show special IDs I'm looking for instead, rather critical in attacking the Sky World boss where I wasn't supposed to.

Colored boxes are used to point out bits of terrain I'm not sure about. Otherwise, the white boxes are close to accurate of what I think they are. Busies up the emulator a bit.

Shows hitboxes and a bunch of information. It's also our RAM Watch, but that was underutilized anyway. It has my guess on Ronald's hitbox rather than anything firmly known.

It also has my early guess on the wall hit detection, although now I realize the magic pixel is just at the feet level and not the vertical orange bars I put down. The green vertical bar was to assist in figuring out the item collection, and seems mostly accurate.

The "average speedometer" and "distance check" on the left needs to be calibrated to the start of each stage.

Skipped a few money pick-ups, but I still have $190 to spare when I get Mega Engine. There doesn't seem to be that many slow choices to skip now.

I have no idea why there are two invisible nitros in track 24. I happened to be viewing the CPU's nitro count when I saw it climb to 1 when I thought I picked up all the nitros. Sure enough, when I drive over that spot, I get a nitro. The location is after the sequential pair of zippers, the first ones you come across after starting the race, the ones right before the first time you fly past the crossover. As you hug the far wall, the same side as the zippers you will pick up two mystery nitros, the second one being near that dirt patch ahead.

If a CPU car drives over rough terrain, and no one is around to see it, does it slow?

Well, manipulation worked. Apparently the RNG was already set up correctly. At least enough for my script to find some possibilities when I left my last upload.

50540 cash after race 15. Enough to ditch a few money bags I picked up and still get Mega. 46140 cash after race 14, the difference between Black and Silver would mean an earlier Mega. 42090 cash after race 13. Skip Red and Skinny's, get Black, and we might have Mega then!

It does feel right to get Red for r2, Silver for r4, Skinny's for r5, and Mega for r16. Black for r3 and Mega for r14 is apparently possible, but then it's Black+Standard vs. Silver+Skinny's for r5 to r13, among other differences.

... Yeesh, the lag. It's the reason I went into that side spot for the extra life in race 13. Not taking it meant lag. It might be that taking every money bag I did avoids lag, so who knows?

This is what race 5 looks like when you manipulate a few letters to be exactly what you need. All those times where that yellow car frustrated you in the first game, watching this yellow car speed ahead is probably making you remember those times.

Four Score used because I needed player 4. Player 4 needed because of luck manipulation. Said luck was looking at player 4's letters collected for two of race 4's packs. By the arrangement I had for race 4, my script claimed there was only 2 possible timers out of 256 that could have worked. It's possible selecting a different player could work, but being player 4 maximizes chance of things working out in race 4.

Race 6 might be next to impossible to manipulate. There are six letter packs, two of them linked to each other on the same manipulation. Since these two are the same, they must be I, as that's the only one I can collect two of. The other four must be R O A M, as none of the remaining letters can pick player 4, and the other cars all have cheated their letter P by now.

Next to impossible doesn't actually mean impossible, there's some theoretical code path that will make it work. It's just a matter of finding a practical code path.

Mostly just trying optimal turns and such.

Apparently you don't lose speed for turning sharply? But only when at max speed? And not with the default engine?

I messed up in the Tug-o-Truck challenge. Well, sure. I win it pretty fast. I just haven't accounted for the speed dropping down a notch when you try to speed up beyond some threshold.

No real planning was done when TASing this. I just sort of dived in and got this so far.