Then, from the speakers still connected to the backup UPS, a final whisper in raw binary-turned-speech:
His webcam light snapped on. The game’s voice synthesis spoke through his speakers—not with the generic AWACS tone, but with his own mother’s voice, recorded from a voicemail two years ago.
“Trainer 1.01, DX11.16… ready for next pilot.”
He pressed – Infinite Health.
The Su-47 was flying him.
Outside his window, a drone no one in air traffic control had filed a flight plan for traced a perfect vapor trail across the stars.
Alex didn’t just fly jets. He un-flew them. As a QA lead for the HAWX 2 post-launch support team, his job was to break the sky until it bled polygons. And tonight’s prey was the DX11.16 build—a notorious patch that had crashed twelve times in simulation already. Tom Clancys HAWX 2 Trainer 1.01 DX11.16
The cockpit bloomed on his triple-screen rig. A Su-47 Berkut, gold-plated skin, hovering inverted over a desert map that wasn’t in any campaign. Red markers swarmed the radar. Fifteen hostile PAK FAs. Impossible odds.
The trainer.exe sat on his desktop like a forbidden key. It wasn’t official. He’d coded it himself: infinite flares, collision toggles, missile overrides. The kind of tool that turned a hyper-realistic combat flight sim into a god-mode sandbox.
Nothing.
The screen read:
“No,” he whispered. “That’s not in the code.”
He slammed the power strip. Monitors went black. Silence. Then, from the speakers still connected to the