The first was from a user named echo_blue , who had no profile picture and no previous posts. Just a single sentence in his DMs: “Your UR on the stream at 01:23:456 is 4.2ms lower than your average on the previous three maps. Wanna explain?”
Then he hit #3.
The cursor hovered over the play button, a familiar tremor running through Kaelen’s fingers. On his second monitor, the leaderboard for “Freedom Dive [Four Dimensional]” stared back. Rank #1: Kaelen . The name felt like a lie.
“I practiced that map for four years. I had just recovered from tendonitis. You didn’t even play it once.” osu autoplayer
By the end of year one, he had thirty top-50 scores. By year two, he was #1 on three of the game’s most infamous marathon maps. Sponsors started emailing. A peripheral company sent him a free keyboard with optical switches. He told himself he’d stop once he hit the top 10 globally.
Too perfectly.
Then he found the autoplayer.
A user named echo_blue had posted a thread in the official osu! forums titled: “The Kaelen Autoplayer: A Technical Breakdown.” It contained everything. The DLL signature. The timing analysis. A side-by-side video of his “live play” facecam overlaid with the autoplayer’s raw input log. The timestamp where his webcam frame rate glitched and showed his fingers perfectly still while the game registered 270 BPM.
He blocked echo_blue. The next day, a new account: echo_blue_2 . This time, a link. He clicked it.
But for the first time in two years, the cursor on the screen was entirely, completely, imperfectly his. The first was from a user named echo_blue
Kaelen closed his laptop. He sat in the dark for a long time. Then he opened a text file and typed a confession. Not an excuse. Just the dates. The scores. The bot’s name. He posted it on his own empty profile, where only the ghost of his rank remained.
Sunday morning, he woke up to 847 notifications.