CD Projekt Red Fixed Cyberpunk's Crafting Tree — The Crunch That Built It Didn't Change

Picture the crafting menu in the original release of Cyberpunk 2077: a bloated grid of components, tiers, and recipe unlocks that rewarded players for spec-ing into a progression path that — by the mid-game — mostly produced diminishing returns and inventory clutter. It was not a system that felt designed so much as assembled under pressure.

CD Projekt Red spent years patching Night City into a more coherent state, and the 2.0 overhaul that arrived alongside the Phantom Liberty expansion dismantled and rebuilt that crafting tree almost entirely. The new version ties into the perk rework, strips out the component-hoarding loop, and makes crafting feel like an intentional choice rather than a tax on your inventory management. It works better. That part is not really in dispute anymore. What is worth sitting with is the context around how the original system got shipped in the state it did — and whether fixing the game changed anything about the studio's structure.

What the 2.0 Rework Actually Changed

The pre-2.0 crafting system asked players to invest heavily in the Technical Ability attribute to unlock tiers of crafted gear, with the implicit promise that hand-crafted weapons and armor would outpace loot drops. In practice, the scaling broke down in the late game, and the component-to-result ratio felt punishing unless you were vacuuming up every piece of scrap in every apartment you cleared.

After 2.0, the system is flatter and more readable. Crafting integrates with the overhauled perk trees instead of sitting alongside them in parallel, and the itemization philosophy shifted away from gear-score chasing. Players who ignore crafting entirely are no longer punished for it. That sounds like a small thing, but it removes a persistent low-grade anxiety that shadowed almost every looting decision in the original release.

The Crunch Record Is Still There

CD Projekt Red's pre-launch crunch on Cyberpunk 2077 was documented extensively. Studio heads acknowledged mandatory overtime in the months before the December 2020 release. The game shipped across four console generations simultaneously, with the last-gen versions in particular failing to meet basic performance expectations on launch day. The Polish studio — celebrated for The Witcher 3's scope and polish — took significant reputational damage, and the conversation about crunch in AAA development sharpened around them specifically.

What has not followed the mechanical improvements is any structural announcement about how CDPR builds games now. The studio has spoken in general terms about improving conditions, and there are reports of a more deliberate pace on The Witcher 4's development. But general terms are easy. The 2.0 patch proves the team can revisit and correct design mistakes. It does not, by itself, confirm that the production environment that generated those mistakes has been redesigned with the same rigor.

Why the Crafting System Specifically Is a Useful Case Study

Crafting trees are, by design, systemic. They have to interface with itemization, progression pacing, enemy scaling, and economy loops all at once. When a crafting system ships broken, it is rarely because one developer made a single bad call — it usually reflects time running out on the iteration phase. The component-hoarding problem in Cyberpunk's original crafting was not an oversight; it was a symptom of a system that did not have enough runway to be properly balanced against the rest of the game.

FromSoftware ships systemic economy loops — Souls, runes, upgrade materials — with a coherence that suggests those systems were playtested against the full game for long enough to find the load-bearing joints. The gap between that and what Cyberpunk launched with is not purely a talent gap. It is a time gap. That distinction matters when you're evaluating what a post-launch fix actually represents.

A Studio Repairing Its Reputation, One Patch at a Time

To CDPR's credit, they did not walk away. Some studios release a broken game, issue one or two hotfixes, and quietly sunset support. Cyberpunk got years of sustained work: performance patches, the free next-gen upgrade, the 2.0 systems overhaul, and a full paid expansion. The commercial turnaround has been well-documented, and the game currently holds a strong standing on PC storefronts that would have seemed implausible in January 2021.

That trajectory is genuinely worth acknowledging. It is also, if you are being clear-eyed about it, a form of debt repayment rather than a transformation. The game that needed three years of repair work to reach its potential is still the game that was released in the condition it was released in. Praising the patch notes is reasonable. Treating them as evidence of institutional change is a different and less supportable claim.

What Follows Cyberpunk Matters More Than Cyberpunk's Recovery

The real test for CD Projekt Red is The Witcher 4 — currently in development and, by all available signals, being built with more pre-production groundwork than Cyberpunk received. The studio is working with Unreal Engine 5 for the first time, which carries its own integration costs, and the pressure to deliver a title that confirms the studio's rehabilitation will be substantial. That pressure is exactly the kind of condition that historically produces crunch.

The crafting tree in Cyberpunk 2077 is finally good. That sentence would have been unthinkable at launch. But game design fixes and labor practice fixes are different categories of problem, and conflating them does a disservice to the developers who actually worked those hours. Whether CDPR has genuinely changed how it operates — or just gotten better at fixing things after the fact — is a question The Witcher 4's development cycle will answer more honestly than any patch ever could.