Star Wars - Racer Revenge

The first thing you notice is that the other pods can be killed. Not spun out, not nudged off the racing line, but wrecked outright, engines flaring and coming apart against a canyon wall while the debris scatters behind you. Rainbow Studios built a damage meter into every racer in the field, yours included, and that single decision separates this 2002 sequel from the Episode I game that preceded it. Podracing stopped being a test of nerve and became a demolition event with a finish line attached.

The fiction supports it. Eight years after Anakin's win at Boonta Eve, Sebulba has spent the intervening time nursing a grudge, and the circuit he races on is meaner for it. What that means in practice is a handling model that rewards aggression: side-slamming a rival at full throttle costs you speed and integrity, so there is a genuine calculation in whether to spend your own hull on someone else's. Engines overheat if you hold boost too long. Repair happens gradually, which makes the middle third of a long race a question of how much you can afford to still be angry about.

Speed is where it holds up best. The tracks are wide, fast tubes of Tatooine rock, ice canyons and industrial scaffolding, and the sense of velocity comes from field-of-view distortion and blur rather than from raw polygon count, a trick the PS2 was well suited to. Two-player split screen survives that intact, which was not guaranteed at the time. The tournament structure is thin by modern standards, essentially a ladder of circuits that unlocks racers and mirrored courses, and the AI has a habit of rubber-banding hard enough to undo a clean lap.

It is a short game, and it never pretends otherwise. What it does have is a specific, physical pleasure that very few licensed racers of the era found: the moment where you stop trying to out-drive someone and simply decide they should not finish. That is not how Star Wars usually behaves, and Racer Revenge is better for the meanness.