Issue #2 opened: “It sees input. Don’t move.”
Aris cloned the repository. The README was a single line: “Run main.py. Use WASD. Don't let them find you.”
It started as a whisper in the developer forums. A private repository, forked from an archived NASA JPL dataset, had suddenly gone public. Its name: Pluto_Retrograde/Game . game pluto gitlab
A terminal window opened, then exploded into a wireframe solar system. The Sun was a white dot. The gas giants were bloated, pulsing orbs. And there, at the edge of the render distance, was a tiny, icy-blue sphere labeled PLUTO (PLAYER 1) .
The dark object in the simulation grew closer. It wasn’t a comet or asteroid. It had angles. Geometry. A perfect icosahedron, blacker than the void. Issue #2 opened: “It sees input
That’s when the first message appeared in the GitLab issue tracker. Issue #1: “Who is controlling the ninth?”
Then GitLab crashed. A 503 error. The pipeline froze. The game window stuttered. Use WASD
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.