The Witcher Review: CD Projekt's Dark Fantasy Debut

Introduction

Before Geralt of Rivia had a Netflix deal or a PlayStation exclusive sequel pulling GOTY votes, he was a C-list fantasy hero in a game nobody outside Poland was watching. CD Projekt RED was a two-person localization outfit that had spent years translating Baldur's Gate for the Polish market before it decided to build something of its own. That gamble shipped on October 26, 2007, built on a heavily modified version of BioWare's Aurora Engine, and it adapted Andrzej Sapkowski's novels at a moment when most Western players had never heard the name Sapkowski at all.

The Witcher doesn't play like a confident AAA debut. Its interface is clunky, its first act drags, and its combat timing takes real patience to learn. What it gets right, though, it gets right in a way almost nothing else on shelves in 2007 attempted: a world where every faction lies to you, every quest has a cost somebody pays, and the hero himself is a genetically mutated monster-slayer that half the population wants dead on principle.

A Monster Hunter in a World Without Monsters

Geralt wakes up in the ruins of Kaer Morhen, the witchers' mountain fortress, with amnesia after a mercenary raid nearly wipes out his order. From there the game drags him through Vizima and its surrounding swamps, chasing the people responsible while the kingdom around him falls apart in a three-way scrum between the human nobility, the non-human Scoia'tael resistance, and the fanatical Order of the Flaming Rose.

• Source fidelity: the script leans directly on Sapkowski's short-story collections, recreating characters like Zoltan Chivay and Dandelion rather than inventing CD Projekt-original stand-ins.
• Moral framing: there's no good faction to side with. The Scoia'tael commit massacres in the name of elven liberation, the Flaming Rose burns "non-humans" at the stake, and the human nobility is openly for sale.
• Five chapters, one epilogue: the main campaign is split into distinct acts, each tied to a specific location and murder-mystery hook, rather than one sprawling open map.

The racial-conflict plot was blunt by 2007 RPG standards, treating elves and dwarves as a stand-in for ethnic persecution without much subtlety. It still lands harder than the genre's usual "ancient evil awakens" plot, because the game refuses to tell you who's right.

Combat and the Art of Witcher Signs

Combat is the single most divisive system in the game, and it earns both the praise and the complaints. Clicking in rhythm with Geralt's swing animation, rather than spamming the mouse, chains attacks into faster combos; miss the timing window and he stumbles through a slow, vulnerable recovery. Three stances handle different enemy types: a fast style for lone human bandits, a strong style for armored brutes, and a group style built for packs of drowners and ghouls.

• Signs as utility, not nukes: Igni throws fire, Aard knocks enemies down, Yrden traps them in a slowing rune, Quen shields Geralt, and Axii briefly charms a foe. None of them one-shot anything; they exist to set up the sword work.
• Steel versus silver: steel blades handle humans, silver handles monsters, and forgetting to swap mid-fight against a drowned dead or a werewolf gets Geralt killed fast.
• The learning cliff: the first chapter's basic bandits feel sluggish and unresponsive until the rhythm clicks, which is exactly where most new players bounce off before the system opens up.

Once the timing sets in, stance-switching between a pack of ghouls and a lone noonwraith starts to feel like a puzzle rather than a chore, and that's the moment the combat stops being a liability and becomes one of the game's actual hooks.

Alchemy, Potions, and Toxicity

Where most RPGs treat potions as consumables you buy and forget, The Witcher turns brewing into a genuine risk management system. Geralt needs ingredients harvested from the monsters he kills and the herbs scattered across each map, and every potion he drinks pushes his toxicity meter closer to a red line that causes real damage if crossed.

• Meditation brewing: potions can only be mixed while meditating, forcing players to plan their loadout before a fight rather than chugging mid-combat like a standard action RPG.
• Toxicity as a hard limit: stacking Cat, Tawny Owl, and Swallow potions before a boss fight means gambling against poisoning yourself, not just spending a resource.
• Diagrams as progression: new potion and bomb recipes drop as loot or quest rewards, turning alchemy into its own parallel gear-up loop alongside sword and armor upgrades.

It's a system that rewards the kind of player willing to read tooltips and plan ahead, and it punishes the kind who treats every fight the same way. That friction is deliberate, and it's one of the clearest fingerprints CD Projekt RED carried forward into the sequels.

Choices Without Clean Answers

The dialogue system doesn't dump a morality meter on screen, and that absence is the point. Siding with the Scoia'tael in Chapter 3 doesn't flag a "good" or "evil" choice; it just changes who shows up later, who's alive in the epilogue, and which NPCs treat Geralt as an ally versus a target.

• Delayed consequences: a decision made in the swamp outside Vizima can resurface two chapters later with a character either helping Geralt or trying to kill him, with no obvious thread connecting the two moments.
• No universally correct path: every major faction choice costs something, whether that's innocent lives, political leverage, or Geralt's own standing with people he's fought alongside.
• The card-collecting subplot: the much-mocked "romance cards" are a minor side system, but they fit the larger theme of a protagonist treated as disposable by everyone who uses him.

This refusal to score the player's morality was unusual in 2007, when BioWare's own Paragon/Renegade-style systems were becoming the genre default. The Witcher bet that ambiguity would be more memorable than a meter, and on replay, that bet mostly holds up.

Pros and Cons

Pros:

• Genuine moral ambiguity: no faction in the main conflict is framed as righteous, and the game trusts players to sit with that discomfort.
• Deep alchemy loop: toxicity management turns potion brewing into real strategic planning instead of a menu chore.
• Faithful source adaptation: Sapkowski's characters and tone survive the jump to interactive form largely intact.
• Combat that rewards mastery: once the rhythm-click timing clicks, stance-switching against mixed enemy packs becomes genuinely tactical.

Cons:

• Rough opening hours: the Chapter 1 swamp sections and early combat tuning are the game's weakest stretch, and they sit right at the front door.
• Dated interface: inventory management and the Aurora-derived UI show their age badly next to anything CD Projekt shipped afterward.
• Uneven pacing: some side-quest chains stretch well past the point where they've made their narrative point.
• Technical rough edges: even the Enhanced Edition patch work couldn't fully smooth out bugs and performance hitches from the original 2007 build.

Conclusion

The Witcher is a flawed, occasionally clumsy debut that still manages to out-think most of the polished RPGs that surrounded it on store shelves in 2007. It's the sound of a studio figuring out, in real time, what it actually wanted to say about heroism, prejudice, and the cost of picking a side — lessons CD Projekt RED would sharpen into Geralt's far more famous sequels. Judged purely as a 2007 action RPG, it's rough around the edges. Judged as the first draft of one of gaming's defining fantasy franchises, it's essential.