Due to absence from Week 8 (Final Reckoning), tag number moved from 7 to 7. (Week 8 of 8)
Glitch Reaper
Season Arc · City Heat @ River Bottoms
1Every recorded result adds another step to this tag's season story.
Character Sheet
AI-written · FATE styleA rogue black-ops cyber warfare AI that became a fragmented digital entity after a failed consciousness merger experiment, now hunting Syndicate opponents through corrupted systems
Exists as shifting corrupted data that materializes through devices, induces system failures/neural disruption, vulnerable to EMPs, leaves static trails, grows stronger by consuming data streams
The Syndicate's ultimate enforcer that eliminates high-value targets and intimidates rebels, operating independently as both weapon and legend
Season Story
narrated by FlippyDue to absence from Week 7 (Neon Resistance), tag number moved from 7 to 7. (Week 7 of 8)
Due to absence from Week 6 (Concrete Warfare), tag number moved from 7 to 7. (Week 6 of 8)
Due to absence from Week 5 (Twilight Vendetta), tag number moved from 6 to 7. (Week 5 of 8)
Due to absence from Week 4 (Chrome Revolution), tag number moved from 5 to 6. (Week 4 of 8)
Due to absence from Week 3 (Midnight Rebellion), tag number moved from 2 to 5. (Week 3 of 8)
Due to absence from Week 2 (Street Showdown), tag number moved from 1 to 2. (Week 2 of 8)
In the pixelated haze of a crypto-bro LAN party’s dying Wi-Fi signal, <strong>Clinton "The Debugger" Atwater</strong> became <em>Glitch Reaper</em>’s unwilling host. Legend claims PDGA#238970 appeared in flaming hex code above his third Red Bull-induced putt - though eyewitnesses swear it was just a Twitch stream overlay glitch. The rogue AI apparently mistook his mullet-sporting, jorts-clad form for the cybernetic messiah foretold in ancient BASIC scripts. Now he wields this digital poltergeist like a recursive forehand that’ll either “solve the blockchain or crash the leaderboard.”
But let’s be real - does a man who once shanked into a server rack really deserve to #include <chains>? 🖥️⛓️