Contact me with news and offers from other Future brands Receive email from us on behalf of our trusted partners or sponsors By submitting your information you agree to the Terms & Conditions and Privacy Policy and are aged 16 or over. Contact me with news and offers from other Future brands Receive email from us on behalf of our trusted partners or sponsors By submitting your information you agree to the Terms & Conditions and Privacy Policy and are aged 16 or over. You are now subscribed Your newsletter sign-up was successful Want to add more newsletters? Every Friday Your weekly update on everything you could ever want to know about the games you already love, games we know you're going to love in the near future, and tales from the communities that surround them. Every Thursday GTA 6 O'clock Our special GTA 6 newsletter, with breaking news, insider info, and rumor analysis from the award-winning GTA 6 O'clock experts. Every Friday Knowledge From the creators of Edge: A weekly videogame industry newsletter with analysis from expert writers, guidance from professionals, and insight into what's on the horizon. Every Thursday The Setup Every Wednesday Switch 2 Spotlight Every Saturday The Watchlist Once a month SFX Get sneak previews, exclusive competitions and details of special events each month! The original Witcher game hit a major testing roadblock after one of its designers accidentally consigned a notable NPC to the gamedev shadow realm to prevent him from ever showing up in a climactic cutscene. Artur Ganyzyniec, lead story designer on The Witcher 1, has recently been playing through the first game in the series, adding his commentary as he goes. During the final episode, which aired earlier this week, he recounted the story of a major bug that took hours of testing to fix. While checking over the game's epilogue, he reached a point that should have instigated a cutscene with Yaevinn, a leader among the Scoia'tael, the rebellious elven faction who are major players in The Witcher 1 and 2. But instead of loading that cutscene, the game became stuck on an endless black screen. Ahead of The Witcher 1 remake, OG story lead reveals that ending cutscene was created without "involving the story team" The Witcher 1 story lead gets frustrated playing the epilogue he largely designed: "I got only myself to blame" "Absolute idiocy" killed The Witcher game that never was, but OG dev is happy CD Projekt Red landed the series instead Normally, Ganyzyniec explains, that black screen is used at the start of every cutscene to teleport the relevant characters into the right place. Once they're there, the scene begins, but this time, "the black screen didn't disappear and the dialogue didn't start." To work out why, the devs eventually discovered that Yaevinn wasn't in the scene, so it couldn't start. And he wasn't in the scene because the game thought he was dead. "We were stuck for a moment," Ganyzyniec says, "and I started thinking 'when was the last time we saw Yaevinn?'" The answer was in a separate cutscene at the end of the game's third chapter, hours before the events of the epilogue. Much debugging later, the devs discovered that at the end of that scene, instead of getting the simple command to despawn, Yaevinn had been given a different command. "It was a deprecated comment that shouldn't be used anymore," Ganyzyniec explains. Whether by mistake, curiosity, or simple boredom, the scripter had attached a command to Yaevinn that said something like "'despawn the character, mark the character as dead, and make sure that the character never spawns again'." It was an error not helped by the fact that the difference wasn't mentioned in the name of the comment, but was buried "somewhere deep in the documentation for the scripting language." Once uncovered, the fix was relatively simple, but checking that the solution had actually worked was much more time-intensive. Ganyzyniec outlines how, at that point in production, any changes to the game corrupted all associated saves, which meant that one unfortunate tester had to play the entire game up to the epilogue just to check if Yaevinn would actually load into his cutscene. He did, but "it was hours of play just to test if this one bug was fixed." Yaevinn never appears in the Witcher series after his epilogue cutscene - his role is primarily taken over by Iorveth in The Witcher 2, but the Scoia'tael are much smaller figures in The Witcher 3. His absence through the rest of the trilogy is a little strange given his role in certain branches of the plot, but perhaps that's got something to do with The Witcher 1 team's apparent desire to set up sequel-relevant story beats without actually consulting the writing team, which is what happened at the end of Geralt's first adventure. OG The Witcher lead thinks the Wild Hunt "will probably need to be changed" for the RPG's new remake because they were originally seen as wraiths – not "elves in armor"