Dmytro Kovtun
/// CEO & CO-FOUNDER
Dmytro co-founded Pingle Studio in 2007. Since then, the company helped the world's best publishers and developers to release more than 60 games for the majority of gaming platforms.
Chances are, you already know what a bad remaster can cost you. I’m talking about disappointed fans. Review scores that follow the IP for years. And don't forget a community that won't let it go. If you want the full picture, we covered why many remasters earn backlash here. This article is for studios that need a repeatable, methodology-driven remastering approach that helps avoid those risks.
Pingle has spent 19+ years working with legacy codebases and custom engines on titles like Life is Strange, Five Nights at Freddy's, and The Eternal Cylinder. The pattern we kept running into — original team gone, incomplete documentation, codebase as the only surviving record of why the game feels the way it does — is what shaped the framework we use today.
The Respectful Remaster: Three principles that guide Pingle
Every remaster decision comes down to three questions: what must survive, what must go, and what can be added. Our framework has one principle for each:
- Preserve feel: protect the systems players care about.
- Fix friction: remove what blocks the game from working well today.
- Modernize selectively: add what helps the original land better on modern platforms.
Let’s look into each one.
Principle 1. Preserve feel: Protect what defines the game
Every beloved game has systems fans have built muscle memory around (even when they can't name them). Physics, timing, controls, combat rhythm, camera behavior, the visual atmosphere of the world. Change any of those without understanding them first and you get backlash. Deus Ex Remastered ran into this in September 2025. The first trailer drew fan criticism over the visual changes, and by December the release was delayed indefinitely to meet the fan’s expectations and give the title proper treatment.

What does “preserve feel” mean in practice? Most often, it calls for keeping old tech alive inside a newer build.
Take The Eternal Cylinder, an open-world survival game which we had to migrate from UE 4.24 to 4.27. The game's whole identity is built around a massive cylinder rolling through the world and shattering every object in its path. That destruction behavior ran on Apex Destructible, a physics plugin Epic had deprecated in newer engine versions.
The obvious move was to replace it with something current. But since Cylinder’s signature destruction was tuned to Apex Destructible's specific physical responses, it’d remove the game’s feel. So instead, we forced UE 4.27 to work with the old plugin. Our project lead called the result a "zombie", glued and screwed together from different versions so the game could run. But that zombie shipped to 89% on Steam and 4.5/5 on Xbox.

Because the gargantuan, planet-spanning Cylinder is rolling and crushing everything in its path, developers engineered a physics-based system where the alien ecosystem is fully destructible. Image credit: Informa
Now, how do you "preserve feel" when source docs are incomplete?
Incomplete documentation is a default with legacy IPs. Teams turn over and technical specs written in the middle of production rarely survive as useful reference material.
For example, Pathea Games' 180-hour life-sim RPG, My Time At Portia, had documentation gaps across core systems: farming mechanics, crafting logic, and terrain interactions. It was enough for us to know what the systems did, but not so to know how they were supposed to feel.

We decided to reconstruct the game's intended behavior from the outside in. The gaming community had documented quest logic, item recipes, and navigation in more detail than the original project files, so fan wikis became our structural map. Our team followed full playthroughs by streamers Squeaking Lion and LadyShelab to validate progression, then manually tested every environment interaction (chopping trees, farming terrain, crafting sequences) to confirm it felt natural on console. The result was first-try certification on PS4, Xbox One, and Nintendo Switch, with 91% on Steam and 4.2/5 on PS4.
Principle 2. Fix friction: Remove what blocks the game from working well today
Friction can be a crashy build, a menu designed for a keyboard that ships on console without a controller scheme, or a frame rate sitting at 15FPS on hardware that should hit 30. The common thread is that it gets in the way of players experiencing the game.
Mafia 2's Definitive Edition shows what happens when friction goes unaddressed. The remaster shipped in 2020 and couldn't hold a steady 30FPS on consoles that were significantly more powerful than the hardware the original ran on in 2010. Players reported the game would stutter to a stop in the middle of car chases, requiring a restart. No fixes afterwards solved that.
But while fixing performance is the baseline expectation, remaster’s real job is to make sure nothing technical gets between the player and the experience the game was designed to create.
Pathologic 2 opens with the player on a stage, introduced to the show by a wicked-looking director and extras in tragedy masks. Then the game begins, people start dying, and the theatrical cruelty follows you everywhere: hunger, exhaustion, disease, dwindling trust. Reviewers called it “one of the worst gaming experiences you can have, but in a good way.”

This is a game that makes you feel like you're performing in something deliberately cruel. When tinyBuild brought us in to make it run on consoles, we had to make sure no technical problems were getting in the way of the game's experience. The PC build was going well below 30FPS on console hardware. Each environment ran multiple overlapping simulations at once (disease outbreaks, NPC schedules, trading systems, faction dynamics), and 8th-generation console GPUs couldn't handle all of it simultaneously. That’s why our team optimized the entire codebase: C# code, heavy 3D assets, textures, memory, lighting, shadows. The game hit 30FPS, passed Sony and Microsoft certification on the first submission, and landed 4.4/5 on PlayStation.
The survival systems that make Pathologic 2 what it is stayed exactly as Ice-Pick Lodge designed them. Console versions were rebuilt around them so new players could actually get to the experience.
Principle 3. Modernize selectively: Add only what helps the original expand
Finally, before adding anything, every remaster needs a clear answer to one question:
Will this help the original work better, or will it change what the game is?
For example, when we brought Life is Strange to iOS and Android, the game needed to work on touchscreens without feeling like a console game awkwardly crammed onto a phone. We rebuilt the controls around touch input, added Tap-to-Move, and redesigned the UI for smaller screens. Android controller support went in because players expected it. The Photo Mode was the one creative addition that wasn’t a technical requirement. We added it because it fit the game that is literally built around photography.

The same principle applies to platform-specific features: they earn their place by fitting the game. While upgrading The Eternal Cylinder for PS5, we implemented DualSense Adaptive Triggers and Haptic Feedback. When the character fills with water, the trigger resistance increases. As they release it, it eases. It's a feature that didn't exist when the game was designed, but it fits the game's physical, tactile world well enough that it feels like it always should have been there.
If we look at some examples from “outside”, one such would be Diablo II: Resurrected, which pushed selective modernization further than most remasters attempt. The game got a new visual layer (3D graphics, modern rendering, 4K resolution). Meanwhile, the actual game logic and engine running underneath stayed exactly as it was in 2000.

Whether your attack connected, where your character stood, how movement worked, and the like are all calculated by the original code. You're literally playing the old game with new visuals sitting on top of it and can toggle back to the legacy version any time.
DNA archaeology: How to know what to preserve, fix, and add
To apply these three principles well, you need to understand the original well enough to know what to preserve, fix, and add. That's often tricky since legacy code is full of things that look wrong. The instinct is to clean them up.
DNA archaeology is the opposite approach. This is what we call studying the codebase the way you'd read a historical document. Three questions drive that read:
- What was this built to do on its original hardware? Legacy engines were designed for constraints that no longer exist: PS2-era memory limits, fixed-pipeline rendering, hardware that couldn't handle real-time lighting.
- What shaped the choices that look strange today? A control response that feels sluggish on a modern controller may have been calibrated for hardware whose input latency was 40ms higher.
- What would break or feel different if you removed this? Not every piece of old code is load-bearing, but you don't know which pieces are until you investigate. In The Eternal Cylinder, Apex Destructible looked like a deprecated plugin worth replacing, but it was running the destruction physics the entire game was built around.
Dive headfirst into the codebase, and you find what isn't visible from the outside. For example, when working on Life is Strange for iOS and Android (the game was running on UE3, an engine past its support lifecycle), we found that the original developers had built a custom shader and lighting system entirely from scratch. UE3 was too old to produce realistic lighting natively, so they'd written their own workaround to achieve the warm, painterly look the game is known for. That system was responsible for everything players recognized as Life is Strange: the soft lighting, the shadows that looked almost brushed on, the golden warmth.

That system had no equivalent in UE4. Although UE4 does have proper realistic lighting built in, it wouldn’t automatically reproduce something a team spent years hand-crafting in a completely different engine. So we had to figure out what the original system was doing, why it was built the way it was, and then rebuild that same effect from scratch using UE4's tools. That meant adding new shading models and modifying UE4's source code directly. It also meant going through every single environment in the game and retuning the lighting by hand — because UE3 measured light in arbitrary units that don't map to UE4's real-world lumen values. Every scene had to be rebuilt until it matched what the original team had created.
Any team migrating to UE4 would have noticed the lighting looked wrong. But understanding that the original system was a hand-built workaround for an engine limitation is what made it possible to reconstruct it correctly.
Before you scope a remaster, answer these questions
Finally, this is what we found worth asking before any remaster project starts.
- What's the actual business goal? There's a big difference between making an old game accessible on modern platforms, testing whether there's still an audience for a dormant IP, and laying the groundwork for a sequel. Each of those leads to a different scope and a different definition of success.
- Which version of the game is the source of truth? If there were patches, regional differences, or multiple platform versions, this matters more than it sounds. The fan-preferred version and the final official build aren't always the same thing.
- What source materials do you have? Source code, final builds, original tools, assets, audio masters, localization files, middleware licenses. Be honest about what's missing or unusable. That's not a blocker, but it changes the shape of the work significantly.
- How well do you understand the original feel? Do you know which systems players have muscle memory for? Have you played it recently? Have you read what the fanbase still talks about? The team doing the remaster needs that context
If you’re considering bringing in an external team, we've covered the list of best remaster companies here. Or, if you'd rather start with a technical read of what you're working with, Pingle offers a free pre-engagement audit. We look at your codebase, the platform requirements, and help you analyse where the risks sit before you commit to a direction.