The screen went white. Then black. Then the normal F-ZERO 99 title screen returned, music blaring, menu options intact. His hands were sweating. His Switch said the playtime for the session was 0 minutes.
The pixel exploded into a grid—a faint, wireframe outline of a track floating in absolute darkness. His machine, the iconic Blue Falcon, materialized not in the colorful, chaotic pack of 98 other racers, but alone. The UI was stripped bare. No speedometer. No boost meter. No position indicator. Just the hum of his own engine and the ghostly outlines of the track.
The Blue Falcon didn’t crash. It pierced .
Kael pressed A.
He extracted it. No readme. No crack. Just a single, oddly named file: MUTE_CITY.ovl .
His Switch, a patched V1 model he’d jailbroken years ago, sat in its dock. He loaded the base F-ZERO 99 NSP, then applied the 1.5.5 update via DBI. The system didn’t reject it. It didn’t ask for a signature check. It just… absorbed it. Silently.
By lap 30, he saw the first ghost.
Most wrote it off as a server glitch. Kael knew better.
He launched the game.
Lap 99. The final straightaway. The wall loomed. He closed his eyes and pressed the boost button. F-ZERO 99 -NSP--Update 1.5.5-.rar
He navigated to his stats. Everything was normal—except one new entry at the bottom:
He’d seen the telemetry data once, while doing freelance QA for a contractor. Fragments of code labeled “GHOST_DYNAMICS_v2” and a new flag for “MOMENTUM_SURGE” that referenced a track not in any known game files: Silence: Loop-42 .
The date of the phantom update.
By lap 10, the track began to change. A second set of tire marks appeared on the asphalt—not his. Faded, glowing a faint, sickly orange. They wove erratically, sometimes cutting corners, sometimes slamming headlong into walls.
Lap 80. His boost gauge flickered. It wasn't depleting anymore. It was inverting —building a dark, purple charge he’d never seen. The voice again, clearer now: