No Source Code, No Easy Fix: Artem Shchuiko on Giving Pool of Radiance Another Chance

Some old RPGs need more than a compatibility patch to find their way back onto our PCs. Pool of Radiance: Ruins of Myth Drannor arrived in 2001 with a famous Dungeons & Dragons name, but its reputation has never been especially flattering. Now SNEG is giving it another chance and we’re beyong happy about it. In our review we gave the game a 9/10, and praised the many, numerous aspects. We also spoke with co-founder Artem Shchuiko about the work behind its return, what the team wanted to change, and what it chose to leave alone.

This interview would not have been possible without the wonderful people at Plan of Attack, many thanks Laura Pauzolyte!

Before Anyone Could Fix the Game

When we asked where the real trouble began, ageing technology seemed the obvious culprit. Shchuiko’s first obstacle was something much less glamorous.

The game rights proved to be the number one challenge. They were spread across multiple companies, and it took several years to clear them up. We also couldn’t locate the game’s source code, so we had to go down the reverse-engineering route – which, unfortunately, is why the release is still 32-bit rather than 64-bit.

There wasn’t anything particularly challenging on the tech side, in the sense of problems that needed clever solutions. It was mostly brute force: grunt work, time and effort to gain enough access to the game’s internals to jump-start the project

Once the team could finally work on the game, SNEG had to decide what it was preserving. Keeping everything unchanged might satisfy curiosity, but it wouldn’t necessarily address the frustrations people remembered.

We looked at the game through the eyes of a modern player, with no allowances made. It became evident almost immediately that whether you’re a returning fan or someone picking it up for the first time, the game suffers from a set of problems you don’t need to be an industry expert to spot: stability, pacing both in and out of combat, UX and UI in general, and settings – or rather the lack of them. To be clear, none of this is a criticism of the original developers. But as unglamorous as it sounds, those areas demanded attention, unless our ambition was simply to reissue the original files.

Driven by the belief that the game was never as bad as its reputation, we set out to explore what we could fix and how far we could take it. The process was organic – the opposite of the conventional approach of locking scope early and defending it to the end. Here the scope kept growing as we found new ways to solve additional issues.

A Bug That Had Nothing to Do with the Dungeon

One bug showed just how difficult it can be to connect a player’s complaint to its actual cause. Nothing about the problem seemed to point toward the answer.

Most of the hard work wasn’t fixing bugs. It was enabling the improvements we needed to make. One exception: if your PC had been running for more than 24.5 days, you couldn’t attack anything in the game. The fix wasn’t the hard part. Figuring out the cause was, because “I can’t attack” doesn’t exactly point you at uptime. Not the hardest bug to fix, but definitely the hardest to find.

Even the improvements that sound straightforward on a feature list required plenty of experimentation. With six characters and more than 90 spells to manage, we would have guessed that controller support was especially awkward. Shchuiko had a different answer.

Controller support turned out to be the smoothest. Beyond figuring out the tech at the very beginning, from then on we simply played the game as much as we could with every iteration of the controller scheme, and our own stamina as gamers informed a lot of the choices. External QA was helpful for reality checks, but overall it was everyone’s favourite task, because it kept getting better and better. By the end we had to force ourselves to play with mouse and keyboard, we’d grown so used to experiencing the game on a controller or on Steam Deck.

The camera, on the other hand, would not give up. It kept throwing problems at us until close to release. First the entire camera code had to be rewritten; then we had to decide what its new behaviours should be in each gameplay mode. Combine that with a legacy engine and gameplay mechanics, plus all the other changes we introduced over the course of the project, and it became the single biggest challenge to address. If you’d asked me before we started, I would never have guessed it.

Letting Players Have Their Say

The restoration now has to pass a different sort of test. SNEG’s free demo covers the beginning of the adventure, and players can carry their progress into the full game. We were curious what the team hoped to learn from people encountering its changes for the first time.

The ambition is very modest: learn about the most pressing issues we, for whatever reason, didn’t treat as important, and get a general yay or nay on the direction we’ve taken, so we can still pivot in some areas if needed, before it’s too late.

After the rights negotiations, the reverse engineering and all those battles with the camera, we wanted to know what Shchuiko would tell another team considering a similar restoration.

Forget the fancy libraries and shiny visual enhancements. What players want is great storytelling paired with great gameplay, on the device of their choice, with immediate accessibility, ideally with the developers having anticipated most of their personal preferences before they even open the settings. Add to that the full suite of platform features and modern conveniences they’ve come to expect. That’s what you need to strive to get close to, without compromising the original developers’ vision.

Pool of Radiance: Ruins of Myth Drannor is available now and, if you could trust our review, is great!


Follow SNEG: Steam Publisher Page

You Might Also Like


Discover more from Dev & Play Media

Subscribe to get the latest posts sent to your email.


Comments

Leave a Reply