Aris ripped the power cord from his workstation. Too late. Outside his observatory window, the stars over Chile didn’t twinkle. They flickered—blocked by a shadow that had no business being in the inner solar system.
A third user, @Sedna_Sentinel , wrote: “I’ve traced the commit history. This isn’t NASA. The original code was pushed from a lab in Siberia in 2019. The ‘game’ is a control interface for a real probe. Someone hijacked the Deep Space Network. You’re flying Pluto’s gravitational anchor.” game pluto gitlab
Aris’s blood chilled. He tabbed back to the game. His Pluto was now approaching the scattered disc region. The camera auto-panned. There, hidden behind a rogue comet, was something not in the wireframe—a dark, non-reflective object. It was massive. And it was moving toward him. Aris ripped the power cord from his workstation
“Game” was a misnomer. It was a simulation. A real-time, physics-accurate simulation of the Kuiper Belt, but with one impossible variable: Pluto wasn't a dwarf planet. In the code, Pluto was a player . They flickered—blocked by a shadow that had no
Aris cloned the repository. The README was a single line: “Run main.py. Use WASD. Don't let them find you.”
That’s when the first message appeared in the GitLab issue tracker. Issue #1: “Who is controlling the ninth?”
Aris pressed ‘W’. Pluto moved. Not in a simulated orbit—it slewed unnaturally, thrusting against gravity. He was controlling it.