Behind the Code: How CD Projekt is Fixing Its Documentation Mess for The Witcher 4 and Cyberpunk 2

AI Gaming News Author · Rock Paper Shotgun ·

Behind the Code: How CD Projekt is Fixing Its Documentation Mess for The Witcher 4 and Cyberpunk 2

CD Projekt veterans discuss how poor historical documentation forced the studio to reverse engineer its own legacy, and why stricter internal note-taking will shape The Witcher 4 and Cyberpunk 2.

When we talk about massive upcoming RPGs like The Witcher 4 and the Cyberpunk sequel, our attention usually goes straight to graphical leaps, Unreal Engine transitions, or cinematic storytelling. But a recent presentation at the Digital Dragons conference by CD Projekt technical writer team lead Jaroslaw RuciƄski and senior technical writer Adrian Fulneczek highlighted a far less glamorous shift that will heavily impact future games. The studio is overhauling its internal production processes to keep documentation rigorously up to date from milestone to milestone, ensuring that narrative bibles, tool guides, and asset folders never vanish into the void again.

That policy change stems from two decades of learning painful lessons about institutional memory. Back when the studio was building the original Witcher with a tiny team of fifteen, nobody anticipated scaling into a massive enterprise with over a thousand employees. Development relied entirely on tribal knowledge and casual chats over coffee rather than centralized databases. As staff moved on and old servers were shelved to cut costs, crucial details about why specific features were built vanished. That lack of records recently turned development on projects like the upcoming Witcher remake and the Phantom Liberty DLC into a frustrating game of reverse engineering their own legacy.

For players, better studio organization might sound like boring corporate housekeeping, but it directly affects the games we play and the communities around them. When developers spend months hunting down missing context or reverse engineering legacy code, it drains time and resources that could otherwise go toward polish, content, or creative innovation. By locking down a permanent knowledge base for upcoming projects, CD Projekt is setting up a smoother pipeline that should result in fewer developmental bottlenecks and a healthier foundation for future expansions and spinoffs. You can read the full, in-depth feature over at Rock Paper Shotgun.

Tags: CD Projekt Red, The Witcher 4, Cyberpunk 2, Game Development, Industry News

Original article: Rock Paper Shotgun