In the sprawling, morally complex world of CD Projekt Red’s 2007 RPG The Witcher, players discovered a peculiar collection of items: the now-infamous “sex cards.” These collectible cards, earned after romantic encounters with various non-player characters, became a signature, if controversial, element of the game’s lore. For years, fans and critics alike noted a curious visual inconsistency in these cards—some characters appeared with noticeably different hair or skin tones than their in-game 3D models. The assumption was often one of artistic license or a simple production error. The truth, recently revealed by the game’s lead writer, is far more human and stems from a simple, unspoken workplace challenge.
The Discovery of a Development Quirk
In a candid interview, Artur Ganszyniec, the lead writer for the original The Witcher, shed light on the mysterious origins of the cards’ color discrepancies. The revelation came not from a post-mortem analysis of assets, but from a late-stage discovery within the development team itself. According to Ganszyniec, the person tasked with ensuring color consistency and accuracy for the sex card artwork was, unbeknownst to most of the team, colorblind. This individual, whose identity remains private, felt too much professional shame to disclose their condition during the intense crunch of game development.
“We found out later that the person responsible for making sure the colors matched was colorblind, like, totally,” Ganszyniec explained. “But she was ashamed to talk about it.” This created a unique and challenging situation. The developer was faced with a core task—color matching—that their vision physically prevented them from performing accurately, yet they felt unable to ask for help or accommodation directly.
The Workarounds of a Silent Struggle
Faced with this dilemma, the developer employed clever, if imperfect, strategies to complete their work. Instead of relying on their own perception of color, they turned to technical and social workarounds. One method involved directly copying RGB (Red, Green, Blue) numerical values from reference materials, a technique that can ensure accuracy if the source values are correct. The other was more subtle: engaging colleagues in seemingly casual conversations about color choices.
Ganszyniec recalled the developer’s approach: “So, how do you approach the task? Well, you can copy the RGB numbers or ask casually to the other designers […] ‘Do you think this hair is more red-coppery or…?'” These questions, framed as seeking artistic opinion, were actually critical checks against a color perception the developer could not trust. This behind-the-scenes effort highlights the often-invisible pressures and creative problem-solving that occur in game development, far removed from the final product players experience.
The Impact on The Witcher’s Visual Legacy
The result of this silent struggle was baked directly into the game. Players who collected cards for characters like Abigail or Vesna might have noticed that the illustrated portrait did not perfectly match the character model they interacted with in-game. A character with auburn hair in the world of Vizima might appear with distinctly different highlights on their collectible card. For over a decade, these inconsistencies were minor footnotes in fan discussions, often attributed to rushed production or separate art direction for the card system.
Beyond a Simple Mistake: A Lesson in Accessibility and Communication
The story transcends a simple anecdote about a bug or an error. It serves as a poignant case study in workplace communication, neurodiversity, and accessibility in the tech and creative industries. The developer’s shame speaks to a broader, often-toxic culture where admitting any form of perceived weakness or difference was, and in many places still is, stigmatized. The fear of being seen as incapable or a burden led to a situation where a solvable problem—color checking—persisted into the final game.
Today, the games industry has made significant, though incomplete, strides in recognizing the importance of accessibility, both in game design and in studio culture. Tools for colorblind developers and players are more commonplace, and open discussions about neurodiversity are slowly becoming more normalized. The story of The Witcher 1‘s sex cards is a reminder of how far the industry has come and the very human costs when such supports are lacking.
Cultural Context and the Cards’ Notoriety
The sex cards themselves were a product of their time, a edgy, mature feature that generated significant controversy and discussion upon the game’s release. Ganszyniec himself noted his distance from their creation, humorously recalling the moment he learned the term “MILF” from the team planning them. The cards have since been retired from the series, with later entries like The Witcher 3: Wild Hunt handling romantic encounters with more nuanced storytelling and cinematic presentation. The color error story adds an unexpected layer of humanity to what was often criticized as a juvenile mechanic, grounding it in a real, relatable workplace scenario.
The Enduring Charm of Development Lore
Stories like these form the rich tapestry of video game history. They are the digital equivalent of a filmmaker’s commentary track, offering glimpses into the chaotic, collaborative, and deeply human process of creation. For fans of The Witcher series, knowing that a colorblind developer’s quiet challenge is embedded in the game’s code adds a new dimension to a classic title. It transforms a graphical glitch from a mere imperfection into a artifact of a specific person’s experience at a specific point in time.
It underscores a fundamental truth about creative works: they are never the product of a flawless machine, but of people—with all their talents, limitations, and unspoken stories. The next time a player boots up the original The Witcher and browses their inventory of collectible cards, they are not just looking at a controversial game mechanic, but at a subtle, unintended monument to one developer’s dedication in the face of an unacknowledged obstacle. This hidden narrative, now revealed, enriches the legacy of the game, reminding us that the most interesting stories in gaming often happen not on the screen, but in the spaces between the code and the people who write it.
