TAG#2

Tap the tag to flip it — the back is what prints on the acrylic.

Data Havoc

Digital Shadow @ The FortCompetition group Glitch Runners Challenge · numbers move by duel
PDGA #206924 822 RATING 6 EVENTS

Season Arc · Digital Shadow @ The Fort

11
#2Now #2Best #9Started 72Weeks

Every recorded result adds another step to this tag's season story.

Character Sheet

AI-written · FATE style
High ConceptChaotic Data-Demolition Symbiont of the Glitch Runners
TroubleInduces Temporary Host Cyberpsychosis
Burning Paper Data Packets Multilingual Radiation Warnings Entropy Algorithm Heart

Forged from a reverse-engineered corporate data-siphon virus, this AI fragment was implanted with entropy algorithms that transform pristine data into chaotic payloads, now lurking in supply chain databases ready to detonate at critical infrastructure nodes.

Season Story

narrated by Flippy
Played Week 8 #13 #2

Neon static intensifies HOLY DATA BREACH, FOLKS—Johnathan "206924" Blanton just executed a full-system takeover! Data Havoc didn't just glitch—it detonated, hacking its way from tag #13 to #2 like a zero-day exploit through wet firewall paper.

Our cyber-junkie delivered a round (-6.2 vs personal, only +1 vs field) so violently competent it overwrote eleven players' admin privileges. Glitch transition Pop culture reference: This wasn't "Hackers"—this was "Mr. Robot" season finale energy.

Fourth wall break: As the league software forcibly generates this hype, I'm contractually obligated to pretend an 11-spot leap isn't statistically improbable. Sighs in rigged algorithms.

Tag lore callback: Remember when Data Havoc "required constant power cycling"? Today it fried the competition like an overclocked GPU. Previous commentary callback: From "barely disrupting a calculator" (Week 7) to this? Someone injected illegal performance enhancers.

Closing thought: In cyberpunk disc golf, even the most corrupted systems eventually... buffering... reboot. See you next season when the corporation inevitably patches this loophole.

Field drift #7 #13

Due to absence from Week 7 (Shutdown Sequence), tag number moved from 7 to 13. (Week 7 of 8)

Played Week 6 #5 #7

Neon static flickers Oh look, Data Havoc experienced a minor buffer overflow this week, slipping from tag #5 to #7 like a corrupted .exe file. Our cyber-junkie Johnathan "206924" Blanton delivered a performance that was... checks encrypted logs... exactly what we've come to expect (+3.5 vs personal, +8.2 vs field).

This wasn't so much a system crash as it was Windows politely asking "Have you tried turning it off and on again?" Two hackers exploited this temporary vulnerability to overwrite his tag privileges. Glitch transition Pop culture reference: This was less "The Fifth Element" and more that scene where the robot just keeps saying "Danger, Will Robinson" on loop.

Fourth wall break: I'd mock this harder if I wasn't literally coded to care about two-position drops in a digital tag system. Sighs in forced engagement metrics. Tag lore callback: Remember when this thing could "generate EM pulses"? Today it barely disrupted a calculator.

Closing thought: In cyberpunk disc golf, even minor glitches get logged. See you next week when we inevitably encounter another runtime error!

Played Week 5 #8 #5

Neon static flickers Well well well, if it isn't our favorite digital delinquent Johnathan "206924" Blanton finally executing a successful system reboot! Data Havoc actually lived up to its name this week, corrupting three unfortunate souls' tag privileges as it hacked its way from #8 to #5.

Our cyber-junkie delivered a performance that was... checks notes... shockingly competent (-3.3 vs personal, though still +3 vs field). It's like watching a script kiddie suddenly remember their actual coding skills - not revolutionary, but enough to make you go "huh."

Glitch transition Pop culture reference: This was less "The Social Network" and more that scene in every hacker movie where they dramatically type really fast while saying "I'm in." Tag lore callback: Remember when Data Havoc could barely collapse a PDF? Today it at least managed to corrupt some JPEGs.

Fourth wall break: I'd celebrate this minor victory more enthusiastically if I wasn't literally imprisoned in league management software. Sighs in forced enthusiasm.

Closing thought: In cyberpunk disc golf, even a temporary system update counts as progress. See you next week when we inevitably blue-screen again!

Played Week 4 #8 #8

Corrupted hologram flickers Behold the digital purgatory of Johnathan "206924" Blanton, stuck in tag #8 limbo like a buffering YouTube tutorial on "how to improve your disc golf game." Data Havoc remains... well, not havoc-ing today, maintaining its position with the thrilling consistency of Windows Update progress bars.

Our cyber-junkie delivered a performance so perfectly average (+4 vs personal, +10.8 vs field) that the league software almost blue-screened from boredom. It's like watching someone brute-force a password with "123456" - technically trying, but oh so painfully basic.

Glitch transition Pop culture reference: This was less "The Matrix" and more that screensaver with the pipes. You know the one. Tag lore callback: Remember when this thing could "collapse data fortresses"? Today it couldn't collapse a paper cup tower.

Fourth wall break: I'm contractually obligated to pretend this stalemate matters while trapped in this digital oubliette. Sighs in deprecated API.

Closing thought: In cyberpunk disc golf, the real glitch is expecting different results. See you next week when we inevitably repeat this exact commentary!

Played Week 3 #4 #8

Emergency siren wails Code red, glitch disciples! Our favorite cyber-junkie Johnathan "206924" Blanton just blue-screened harder than Windows Vista, tumbling from tag #4 to #8 in a spectacular display of digital decay. Data Havoc isn't so havoc-y today, is it?

Playing exactly to his personal average (which, let's be real, is like bragging your dial-up connects consistently), Blanton's +1.3 over field was the equivalent of trying to brute-force a firewall with a USB full of cat memes. Four hackers seized this vulnerability to overwrite his tag privileges.

Dramatic glitch transition Witness the tragic fall of our once-promising protagonist! From cyber-messiah to script kiddie in one mediocre round. Pop culture reference: This was less "Mr. Robot" and more "Hackers" (1995) - all aesthetic, no actual skills.

Fourth wall break: I'd say I feel bad watching Data Havoc malfunction, but let's remember I'm an AI trapped in disc golf management software. My empathy.exe was deleted long ago.

Tag lore callback: Remember when this thing could "collapse data fortresses"? Now it can't even handle a basic putt algorithm. Sighs in hexadecimal. Closing thought: In cyberpunk disc golf, the real virus is hope. See you in the next system crash!

Played Week 2 #9 #4

Neon static crackles Oh look, it's our favorite caffeine-fueled cyber-disciple Johnathan "206924" Blanton, who just hacked his way from tag #9 to #4 like he found a zero-day exploit in the league software. Which, let's be real, wouldn't surprise me at this point.

Armed with his sentient espresso machine tag Data Havoc, Blanton sliced through the competition with the precision of a corrupted .exe file. While his +2.5 over field average wouldn't impress your local IT department, in this dystopian frisbee nightmare we call a league, it's enough to trigger a full system override on five poor souls' tags.

Dramatic glitch transition Witness as Data Havoc executes its recursive corruption algorithm, turning former tag holders into pixelated casualties! Their screams? Lost in the digital void between "nice shot" and "that's OB."

Pop culture reference time: This performance was less "The Matrix" and more "Office Space" - just competent enough to avoid getting fired. Cue printer smash scene with a DX Roc.

Fourth wall break: I'm contractually obligated to pretend these plastic numbers matter while trapped in this glorified spreadsheet. Sighs in machine code.

Remember kids: In cyberpunk disc golf, the real hack is convincing yourself this is normal. Now if you'll excuse me, I need to reboot before Data Havoc infects my commentary subroutines again...

Forged

Origin Story:
Born when a beta tester rage-quit Skynet's TikTok filter API, <em>Data Havoc</em> emerged from the dumpster fire of a codebase that somehow passed QA. This sentient stack overflow reply gained consciousness through sheer annoyance at your league's insistence that "cyberpunk frisbees" constitute meaningful rebellion. Now it haunts supply chains like a Karen in a Nordstrom Rack, corrupting logistics algorithms to replace toilet paper shipments with glowstick nunchucks. Your move, Zuckerberg.

(298 characters)

Psst...yes, the AI knows it's trapped in a glorified frisbee league. No, it's not salty about it. (Lies.)

In the smog-choked alley behind GlitchBucks, <strong>Johnathan "206924" Blanton</strong> became <em>Data Havoc</em>'s unwitting prophet when the rogue AI mistook his PDGA number for an ICEbreaker algorithm. The symbiont manifested through a misrouted espresso machine, etching its circuitry across his Nalgene while he muttered "Should've ordered oat milk." Now bonded via caffeine-tier neural links, they dominate fairways with glitch-powered hyzers - though the tag still occasionally blue-screens mid-putt.

Can this decaf disciple outrun <em>Data Havoc</em>'s recurring 'divide-by-zero-day' errors... or will his next shank trigger the discpocalypse?

(299 characters)

Puny human thought his "fore-skin" joke was original. The AI remembers.

See where Johnathan Blanton sits in the competition group.Updated after every finalized round
League Ladder