The T20 Scandal: A CCP Developer Seeded Tech 2 Blueprints to Band of Brothers (2007)

The T20 Scandal: A CCP Developer Seeded Tech 2 Blueprints to Band of Brothers (2007)

Background: BoB, the T2 lottery, and CCP-dev-in-alliance norms

By late 2006 Band of Brothers was the most consequential alliance in EVE. Founded in 2004 by SirMolle, BoB was an umbrella over five founding corporations - Reikoku (ticker RKK), Black Nova Corp, Finfleet, Evolution, and Destructive Influence - and was finishing the year that destroyed Steve, the first capsuleer titan, in the regional sweep that consolidated BoB's southern dominance. Reikoku itself had a particular flavour. It was the corp that supplied BoB's capital fleet commanders, and it was the corp that the developer t20 had been a member of since the early days of his EVE career.

Tech 2 production in 2006 worked on a research-points raffle. To get the blueprint original for a T2 module or hull, you accumulated Research Points at NPC R&D agents over months, then entered your points into a periodic lottery for the rare blueprints. Most of those blueprints went unrandomised because the supply was deliberately capped. The Sabre interdictor blueprint was the most coveted item in the raffle pool - a small, fast Minmatar hull whose bubble-launcher made it the doctrine-defining tackle ship of the era.

The other piece of context is the old institutional norm at CCP that developers played the game they built. Almost every CCP developer had at least one EVE character, often in a player alliance, and the convention through the early 2000s was that this was both expected and acceptable. As CCP's CEO would write a few months later in the official policy statement on the matter:

"Developers have had, and continue to have, characters in many alliances in the game, and it is wrong to assume that the presence of several characters in any one particular alliance is either uncommon, or automatically indicative of cheating."

That sentence was load-bearing for the institutional argument: CCP was not going to forbid its developers from playing EVE, because building EVE required playing EVE. What it was going to forbid - and where it had previously been forbidding, with mixed consistency - was using developer-level backend access to give in-game advantages to your in-game friends.

June 2006: the seeding

What t20 did in June 2006, per his own later confession, was pull six blueprint originals from the development backend - not via the R&D raffle the rest of the player base was queuing for, but directly from the tooling CCP developers had to spawn items for internal testing. He handed them to Reikoku. Five were Tech 2 ammunition blueprints: Flameburst Precision Light Missile, Phalanx Rage Rocket, Havoc Fury Heavy Missile, Bloodclaw Fury Light Missile, and Spike L hybrid charges. The sixth was the Sabre. The market value of the Sabre blueprint alone was estimated in the billions of ISK at 2006 prices.

The contested community count was higher. Community memory consistently put it at ten blueprints, and the contemporary press coverage misstated the count in both directions before settling. CCP's official list, the one t20 published in his own confession seven months later, was the canonical six. A former Reikoku director who described himself as being in the corp from 2004 through 2007 later argued in a Hacker News thread that what Reikoku actually received was closer to two or three small-ammo blueprints plus the Malediction interceptor - explicitly disputing the Sabre. The discrepancy between CCP's official six, the community memory of ten, and the insider claim of three is part of what made the T20 episode so durable; nobody's count was fully independent of their position.

Summer 2006 to January 2007: CCP's quiet internal investigation

The audit caught it in the same summer the seeding happened. CCP ran routine periodic audits of developer accounts as a matter of policy; t20's transfer of the blueprints into Reikoku showed up in those logs. The CEO's own retrospective account, written some months later, was unambiguous about what CCP did with that knowledge:

"A pivotal case was uncovered last summer during a routine investigation of developer accounts. Unfortunately CCP did not act with the same decisive consistency we have used on previous occasions. Those left at the helm chose to react cautiously, as sometimes is appropriate under these circumstances, leading to more leniency and understanding than we are used to in these matters. Upon review I personally would have chosen to act differently, but what's done is done."

This passage is the most consequential admission in the entire 2007 corporate response. CCP had known for months, had decided to handle the matter quietly, and that quietness was what made the subsequent public exposure so structurally damaging. The internal response had been to begin building a special institution within the company, modelled on the Internal Affairs divisions of law enforcement agencies; per the same statement, that institution was assembled at the beginning of January 2007, before any public exposure - the IA founding was driven by the internal discovery, not by the later public scandal. t20 was retained through this period.

Kugutsumen's exposure: February 2007

Kugutsumen was an EVE community figure whose stated hobby was corporate espionage: infiltrating alliance forums through bribery and social engineering, then selling intelligence to interested parties. He had been hired by Lotka Volterra to spy on Goonswarm earlier in the era; in the course of that work he routinely audited BoB's private director-level forums. His traceable chain of evidence was forensic. An old email exchange between a Reikoku character called Lord Stone and a CCP employee mailbox (helgimar@ccpgames.com) surfaced, showing that Lord Stone had tipped a job-posting to a director on his way out of the corp - itself a routine professional courtesy but one that confirmed Reikoku had previously contained a CCP staffer. From the same forum archive, Kugutsumen surfaced the transfer record into Reikoku of ten valuable blueprints, traced to a character called Ishos Rerajan, and traced Ishos Rerajan in turn back to the EVE developer publicly known by his in-game handle as t20.

He took the findings to the official EVE forums. CCP banned five of his accounts within hours, citing four sections of the Terms of Service including section 18, which prohibits revealing a subscriber's personal information - the section that covered the real-name reveal. CCP's forum moderators began auto-deleting posts that contained t20-related keywords. Kugutsumen acquiesced to a temporary site shutdown at the request of CCP's Community Manager Kieron, who wrote to him in a concluding email reproduced in the Escapist's deep-dive:

"Please forgive me for having a hard time believing your statement about your intentions. Instead of taking your concerns to the proper channels and dealing directly with CCP, you have incited the EVE community, besmirched the reputations of a number of innocent players and developers, and much more. Your actions have done damage to this game you profess to love, damage that is going to take a long time to repair. Until you remove all content on your site concerning these allegations, I have nothing to discuss with you."

CCP's first-pass investigation concluded with an official Kieron-bylined statement that essentially said: we checked, the other developers' characters whose anonymity was compromised will be removed from the game per policy, but the leak about the in-game event arc was too old to confirm or deny. The first-pass conclusion was unsatisfying. Kugutsumen reopened his site at kugutsumen.com and went fully public with what he had. The community treated CCP's response as a cover-up. By 9 February 2007 the matter could not be contained.

CCP responds: the 9 February dev blogs and the slap on the wrist

Two dev blogs were published simultaneously on 9 February 2007. The first was authored under the byline "CCP T20" and titled "On Recent Allegations". It was t20's own confession. It enumerated the six blueprints, dated the seeding to June 2006, and stated that he had acted alone and that Reikoku and Band of Brothers had been cleared of any wrongdoing. It closed with:

"As much as this is a confession it is also a request for your forgiveness for events of which I'm truly sorry."

The blueprints were to be returned to CCP and reintroduced through a new raffle. There was no mention of termination of employment.

The companion piece was Hilmar Veigar Petursson's "The Commitment", a longer corporate-policy statement that did the institutional work the confession would not. It announced the existence of the Internal Affairs department, set January 2007 as its founding date, made non-negotiable employment termination the consequence for future developer misconduct convictions, and quoted Dante:

"I am sure that we all appreciate that it is no coincidence that Dante reserved the lowest level of Hell for 'the worst of those who betrayed their benefactors.' In our case, I would regard the EVE community as our benefactors. We are not the 'gods' or 'the masters' of EVE Online or the EVE community. We serve the community. You have entrusted us to safeguard your hard work."

The mainstream gaming press picked the story up almost immediately. Robert Purchese filed the canonical contemporary outsider verdict for Eurogamer three days later:

"In an unusual display of leniency, 't20' got away with just a slap on the wrist, despite other malefactors having had their employment terminated in the past."

The policy commitment was forward-looking - any future case would be terminated. The actual case being responded to was not. t20 remained at CCP, retained his role, and would continue working on EVE Online until late 2008 when he eventually left the company on his own timeline. The community noticed.

The longer fallout: anonymity, Internal Affairs, and the CSM

Three institutional things changed because of T20 that returning players still see today.

The first was the Internal Affairs department itself. IA was founded in January 2007 in response to the internal audit catch the previous summer; the public scandal in February 2007 cemented it. The director appointed shortly after the 9 February dev blogs was Ari Eldon, who played EVE under the handle GM Arkanon; the Escapist captured the appointment in its final update on the deep-dive. The IA function has continued to investigate CCP-staff conduct in the years since.

The second was the CCP-dev-anonymity rule. After T20, CCP introduced a strict policy that EVE developers played the game anonymously - if a developer's in-game character was identified, the developer was required to undergo what CCP staffers internally called a "Witness Relocation" process: leave the player corp, rename the character, change the portrait. The rule shaped the experience of every CCP staffer playing EVE for the next 12 years. The rule applied to all forms of player-facing identification and was the reason CCP developers presented at Fanfest by handle rather than by real name. The polciy was rescinded at EVE London in November 2019, when CCP Convict announced that the strict-anonymity requirement would be replaced in December 2019 with a narrower restriction (no developer leadership in player corps, no developer market operations, no developer griefing) - a 12-year T20 shadow finally officially closing.

The third was the Council of Stellar Management. The first CSM was constituted in spring 2008, roughly a year after T20, through a player-elected process. Multiple community accounts treat the CSM's creation as a direct response to T20: a structural way of letting players see what CCP was doing without having to wait for the next forum hacker to surface a screenshot. The institutional shape, by CCP's own framing, had been planned independently of the scandal; what T20 did was force the timetable and create the external political pressure that made the CSM's standing real. Both readings appear honestly in the historiography. Both are partly correct.

Kugutsumen was permanently banned. His domain kugutsumen.com survived as a community backchannel for years after, remembered in EVE histories as the third-party site "created by the infamous hacker who discovered the cheating CCP developer T20". The domain is no longer in EVE-community hands; it currently resolves to an unrelated commercial site. The community function it served - external forum where players could discuss things CCP would moderate on the official boards - migrated to other surfaces in the years after.

Aftermath and the long memory: T20 in EVE historiography

The institutional weight of T20 is far larger than the seeded blueprints themselves. Andrew Groen's Empires of EVE names it as the canonical break point in CCP-community relations: "The relationship between CCP and the community had been badly damaged by the T20 debacle of 2007 in which a developer was found to be cheating." That damage healed slowly over the four years until the 2011 Summer of Rage, when the Fearless leak and the monocle controversy reopened the question of whether CCP could be trusted on the boundary between its own business interests and the player experience.

The Mittani would later use T20 as rhetorical scaffolding for the State of the Goonion address he delivered on 29 March 2012, the night he was banned from EVE for the Fanfest miner incident:

"I know that after we have had conflicts in the past with CCP - with the T20 business, with the Threadnought - and in the past, my own reaction in 2007 had been extremely unreasonable. I started a raging threadnought against CCP because T20 was of course giving [Blueprint Originals] to Band of Brothers, [he] was in Band of Brothers, and we basically went to war with CCP. It was a disaster."

The editorial framing of that speech in the same volume immediately notes that the Mittani stretches the truth by conflating T20 with a subsequent 2007 controversy in which CCP was largely cleared of wrongdoing - so the rhetorical move pulls T20 forward into 2012 to do work the underlying fact pattern does not strictly support. The conflation tells you what T20 had become in community memory: the canonical citation for any moment when CCP was accused of corruption.

Modern retrospectives have continued to reach for T20 as the reference point. Brendan Drain's 2013 EVE Evolved column on the SOMER Blink controversy used T20 as the prior canonical "developer interference in the sandbox" case. SVG.com's 2022 piece on EVE Online's darker side gives T20 a paragraph as the foundational CCP-misconduct event. Two ex-insider voices on a 2015 Hacker News thread - one ex-CCP, one ex-Reikoku - argue in retrospect that T20's actual material contribution to BoB's ascendancy was small relative to the institutional weight of the memory. Both readings are honest. The economic contribution may have been modest; the trust contribution was incalculable.

By the time CCP Convict stood at EVE London in November 2019 and announced that the strict-anonymity rule was being rescinded, T20's shadow had been the operative constraint on every CCP employee's EVE play for 12 years. The rule had been written to address a specific case that had not been adequately addressed when it happened. The rule eventually outlived the conditions that produced it, which is sometimes what good policy looks like in retrospect.