How Mega Cat Studios Adapted God of War Into a Retro Pixel Art Game
Mega Cat Studios discusses how it worked with PlayStation and Sony's Santa Monica Studio to bring Kratos’ early Spartan years to life through a hand-crafted 2D pixel art action platforming experience.
Mega Cat Studios recently partnered with PlayStation and Santa Monica Studio to create God of War: Sons of Sparta, a side-scrolling pixel art action game prequel that explores an untold chapter in Kratos’ early life during his brutal Spartan training. Development lasted roughly two years and involved collaboration between Mega Cat’s teams in Pittsburgh and the Philippines, with Santa Monica Studio closely involved in shaping the story, lore, and overall authenticity of the project.
Built in Unity, the game relies heavily on hand-crafted pixel art and thousands of animation frames to capture the weight and brutality associated with the series. Mega Cat developed internal tools to support large-scale 2D production, including systems for frame-accurate combat tuning, animation event synchronization, and efficient sprite iteration. Character sprites were created by converting original 3D assets into pixel form using a custom capture pipeline before adding additional keyframes and animation polish.
The idea was to create a "What If?" game that feels like it could have released in an era long before the series actually began. We spoke with Mega Cat Studios CEO and founder, James Deighan, to learn all about its development.
Can you start by talking about how this project came together?
James Deighan, Mega Cat Studios CEO: This project came together around a shared belief: every legend has a beginning. Before he was a god, before he was a father, Kratos was a young Spartan enduring the brutality of the agoge alongside his brother Deimos. We've had this franchise on our wishlist, as the number one dream franchise to work on from the team as a whole since the origin of Mega Cat.
When we began discussions with Santa Monica Studio, the core idea was clear for us. We want to tell an untold chapter from Kratos’ youth in a way that feels authentic to the God of War experience while adapting it to a new genre. Mega Cat Studios has deep expertise in side-scrolling action games, and this format felt like a natural fit for exploring Spartan training, brotherhood, and raw survival. Reading about the agoge and what it meant to a Spartan checked several boxes for us.
Santa Monica Studio was closely involved, and even more so on story and lore. The writing team behind God of War (2018) and God of War Ragnarök crafted this tale of duty, honor, and brotherhood, and a number of SMS team members helped bring this project to life. Their guidance and direction ensured the narrative, tone, and character portrayals were fully canon and true to the franchise.
From combat cadence to returning enemies and VO, authenticity was the guiding principle.
How long was the game in development, and how large was the team?
Deighan: Development ran for around two years.
Mega Cat Studios operates out of Pittsburgh and the Philippines, and this project was built across those teams with close collaboration from Santa Monica Studio. We have a few hundred cats across Mega Cat, and this was a coordinated effort between departments to deliver something worthy of the franchise.
What do you think of the feedback and reception to the game thus far?
Deighan: We’re incredibly proud of the reception. What means the most is hearing players say it feels like God of War, even in 2D. Experiencing Kratos before he was a god-killer, in a different genre and aesthetic is a serious leap for many.
This was always about adapting the signature spectacle, action, and heartfelt storytelling into a retro-inspired format. Seeing players connect with Kratos and Deimos’ relationship, and embrace this earlier chapter of their journey, has been deeply rewarding.
We were excited to announce and release on the same day, and we hope fans enjoyed the surprise.
Can you walk us through the production pipeline?
Deighan: We began with combat and mapping. So much of this genre is about the mapping and how it ties into the player abilities, skills and reward schedule that all tie back to combat.
Before any final art, we built a tight gameplay prototype focused on movement, impact, and responsiveness. In a God of War game, combat has to feel deliberate, weighty, and powerful.
From there, we moved into a vertical slice that combined:
- Early agoge training sequences
- Environmental puzzles
- A returning enemy type
- A boss encounter
That slice set the tone for production. Our day-to-day workflow was highly collaborative:
- Design greyboxed levels and encounters.
- Engineering supported combat systems and tooling.
- Art translated environments and characters into pixel form.
- Animation and VFX layered in impact and spectacle.
- Audio and VO integration reinforced scale and emotion.
We maintained constant cross-disciplinary integration. Combat feel isn’t just code or animation. It's timing, anticipation, VFX bursts, audio transients, and camera work operating in harmony.
What engine powers the game, and what custom tools or middleware did you build?
Deighan: The game engine is Unity. We built internal tooling to support 2D production at scale, particularly around sprite integration, encounter scripting, and animation event timing. Because of the fidelity expectations tied to the God of War name, our tools focused heavily on:
- Frame-accurate combat tuning
- Animation event syncing
- Efficient sprite sheet iteration
- Level scripting and validation
Our goal was production velocity without sacrificing quality. There are thousands and thousands of frames in the game, and the amount of hand-drawn animation was significant for our team.
How were character sprites produced?
Deighan: We’re really proud of the hand-crafted pixel art.
One of the most interesting aspects was the pipeline. We used original 3D assets and translated them into sprite form, frame by frame with a camera capture tool, added our own key frames and tweens, and brought them back to life in a new way. This allowed us to preserve the proportions, armor detail, and visual authenticity of the franchise while adapting it to a semi-realistic pixel aesthetic.
As our Game Director Zack [Manko] puts it:
“We asked, ‘What would God of War ‘zero’ look like on PlayStation 1?’ And then combined that with modern expectations players have from a God of War title.”
That philosophy defined the visual direction.
How did you tune combat responsiveness to achieve the sense of weight from the 3D entries?
Deighan: We approached combat by adapting the core formula fans know and love into a new package that fits within the main series.
Even though this is a younger Kratos, the brutality and intensity had to feel authentic. We tuned frame timing, hitstop, impact feedback, and cancel windows to reinforce deliberate action. Big swings require commitment. Successful strikes deliver an undeniable payoff.
In 2D, readability is everything. Clarity of silhouette, timing of keyframes, and visual reinforcement were critical to selling weight.
What did your level design workflow look like technically?
Deighan: We began with greybox layouts to test traversal flow, puzzle placement, and encounter pacing.
Once a level proved fun in its simplest form, we layered in tilemaps, environmental detail, secrets, and final collision passes. Ancient Laconia, the harsh and mysterious land surrounding Sparta, needed to feel vibrant and dangerous.
Traversal was next. Running, leaping, and climbing were tuned to feel athletic and responsive while reinforcing the harsh Spartan training environment.
How did you approach lighting, shaders, and visual effects in 2D?
Deighan: We treated lighting cinematically. Ancient Greece needed to feel vibrant and full of depth. We used layered parallax backgrounds, atmospheric effects, and value separation to maintain clarity while preserving spectacle.
Effects like embers, dust, sparks, and magical bursts helped translate God of War’s signature scale into pixel art form. Every frame was crafted with meticulous attention to detail.
Were any procedural systems used?
Deighan: Core content had no procedural content. The encounters, levels, boss fights are all hand-authored to preserve pacing and narrative intent. Where systems supported that vision (camera smoothing, environmental ambiance, encounter logic), they were implemented carefully to enhance consistency without replacing craftsmanship.
Did the team use any AI tools?
Deighan: We have not used any AI for any of our games, including God of War: Sons of Sparta.
What were some of the biggest challenges you faced?
Deighan: The biggest challenge was honoring a franchise known for massive cinematic scale while adapting it into a retro-inspired 2D format without losing its identity.
We solved that by focusing on:
- Authentic combat weight
- Faithful story integration
- Returning enemies
- Semi-realistic pixel visuals
- Brotherhood at the emotional core
At its heart, this is about Kratos and Deimos enduring brutal Spartan training and discovering what it means to be brothers and warriors.
If you were to break down one specific sequence from concept to final implementation, what would that look like?
Deighan:
Let’s take an early agoge training sequence:
- Narrative intent defined: show brutality and brotherhood.
- Concept art established tone and environment of Laconia.
- Greybox layout tested traversal and combat pacing.
- Enemy encounter scripting implemented.
- Combat tuning pass refined timing and difficulty.
- 3D asset translation into pixel sprites.
- Animation and VFX are layered in impact.
- Lighting and atmospheric polish added scale.
- Audio and VO integration reinforced emotion.
- Final QA pass ensured performance and readability.
That iterative process ensured every moment felt worthy of the God of War name.
