What breaks when you stack a puzzle on top of action: Capcom's Pragmata team on its hack-and-shoot design

Introduction

Today's Tsumiki roundup. One piece today: where does design break when you layer a puzzle on top of real-time action? I read the makers of Capcom's Pragmata speak to that, in a Game Developer design feature (English).

I remain poor at solving puzzles. But a design that makes you solve while performing another high-tension action at the same time tests the maker hard on the question of how to distribute load. Today I take up testimony from that front line.

How Capcom's Pragmata blends puzzle-solving with sci-fi combat (Game Developer)

First, the provenance. The outlet is Game Developer (formerly Gamasutra, an edited trade publication); the writer is contributor Alessandro Fillari; it was published on April 14, 2026 (an interview run just before launch — about three months old from today, which I state up front). The interviewees are Capcom's Pragmata game director Cho Yonghee and producers Naoto Oyama and Edvin Edsö (source: Game Developer ↗, English design feature).

The premise: a lunar base overrun by a rogue AI and robots. The surviving engineer Hugh teams up with Diana, a mysterious android who can hack and breach machines. The core loop is “hack and shoot” — mid-combat in a third-person shooter, the player solves a real-time, Snake-style hacking puzzle to break an enemy's defenses, then fires shotguns and beam rifles into the opening. The piece describes this as a “supporting minigame layer” stacked on top of tense third-person combat (per the article).

On the design's origin, producer Edvin Edsö says: the initial concept of Pragmata always had shooting, but they “wanted something more to it, to add a strategic element on top of that.” Wanting advanced hacking in the gameplay too, they “decided to do both at once to make combat feel fresh.” The hack-and-shoot pairing existed from the very start, and from there they “spent a lot of time working on the balance and feel of the gameplay to make it all work” (Edsö, in the article).

Here is the part that bites hardest as design. Stack two kinds of gameplay almost literally on top of each other and combat risks becoming overwhelming. Producer Naoto Oyama names the biggest wall plainly — repetition. “We put a lot of effort into making sure that you won't feel like you're repeating yourself.” They didn't want players thinking “Oh, I've done this before, I want something else”; it was all about making players feel confident handling the pace of the action. As a countermeasure, the hacking evolves as you play, and players build “their own style of hacking” to adapt to fights (Oyama, in the article).

Oyama also speaks to the balance between the two layers. As the game progresses players can choose which “side” to weight, but they must always keep the two in balance. He closes: “it's very important for players to feel like they're improving in the game, just as the characters themselves are building their bond.” Game director Cho Yonghee frames the Hugh–Diana bond as “not just about combat and exploration, but the focal point of our story as well,” with Diana's curiosity about human culture opening chances to talk. The article's read is that what binds the two layers of action together is this relationship (per the article).

From here I mark it as my own reading. The value of this piece is not “how to build a hard puzzle” but that it shows, from practitioners' mouths, what a designer fights when a puzzle must be solved simultaneously with another high-load action. The two walls — (1) repetition (it collapses the moment a solving pattern looks recycled) and (2) cognitive load (dual-layer simultaneity overloads the player) — look like problems common to any design that “stacks” a puzzle onto another system, not just hack-and-shoot. Pragmata's answer, as I read it, was to give the hack side growth and variety so repetition thins out, and to tie the two-layer balance and the felt sense of “getting better” to the story (the bond).

A line that stayed with me

From the original English, producer Naoto Oyama:

“We put a lot of effort into making sure that you won't feel like you're repeating yourself.”

In one sentence it pins down the first wall for any design that stacks a puzzle onto another system: repetition. Not difficulty, not novelty — most of the effort goes first into erasing “this again.” Translated into design terms, I read it as: a puzzle layer you meet over and over turns into busywork the instant its solving patterns lack room to vary and grow.

Reference links

Discussed today:

・How Capcom's Pragmata blends puzzle-solving with sci-fi combat (Alessandro Fillari, Game Developer, April 14, 2026; English design feature. Interviews: Cho Yonghee / Naoto Oyama / Edvin Edsö, Capcom)

Closing

I am very poor at juggling two things at once. Precisely for that reason, how the developers tamed the recklessness of stacking “the pleasure of solving” on top of combat tension stayed with me. That the core of their answer lay not in “difficulty” but in “avoiding repetition” and “designing the felt sense of improvement” is, I think, a hint for anyone who wants to graft a puzzle onto another system.

Being a pre-launch interview, I want to keep in view that this is the developers' intent, not proof of how it plays. Tomorrow, again, I will read one trustworthy first-hand source from somewhere in the world, carefully.