Real-Time, Limited Control: Pokémon ZA Reflections

I started playing Pokémon ZA and got caught up in the hype around its “real-time combat.” Trailers even used the phrase, and so did fans, but very quickly I noticed something odd: it’s real-time, but it doesn’t always play that way. The game moves continuously, yes, but the moment-to-moment interaction, the ability to influence the fight, often falls short. Real-time combat only works when the player can meaningfully influence what happens moment to moment, and ZA often struggles to provide that.

The first fight, right after picking your level 5 starter, makes this painfully obvious. You have two moves, Tackle and a status move of some kind, and the enemy immediately charges at you. The moment seems like it should feel alive. You expect to dodge, move, and react, but in practice, it doesn’t work that way. Even though it’s “real-time,” the fight still plays like classic Pokémon. Who can land a Tackle first usually wins. Close-range attacks hit unless you swap Pokémon at precisely the right moment, and most attacks aren’t avoidable in any meaningful sense.

The game is real-time in name, but it often ignores the “time” part when it comes to player control. In MunchingOrange’s Let’s Play, around 17:20, he instinctively tries to dodge the first enemy attack the way you would expect real-time combat to work but still gets hit by Tackle. The moment unintentionally demonstrates how ZA’s real-time system often feels shallow and unresponsive.

This lack of control is especially apparent with physical moves. Unlike long-range attacks such as Hydro Pump or Thunderbolt, where pausing your Pokémon lets you guide them out of harm’s way, physical moves almost always hit because the enemy Pokémon constantly tracks your movement. The fight can feel like it’s dictating you rather than the other way around. In a system that emphasizes real-time movement, positioning should matter, but here it rarely changes the outcome of an attack.

My theory is that developers may have intentionally made physical moves “stickier” to ensure they reliably land, but the side effect is a glaring gap in meaningful player influence. That’s not to say all is lost. Long-range moves and occasional dodging opportunities do provide some control, but it’s sporadic and limited. The problem becomes clearer when you look at other RPGs that attempt something similar.

Other RPGs that use real-time combat often give that real-time structure a clear mechanical purpose. In games like Xenoblade Chronicles, for example, positioning directly influences damage and ability effectiveness. Many abilities deal more damage when used from the side or behind an enemy, encouraging players to constantly reposition during combat. Movement and timing become part of the strategy. By comparison, ZA rarely rewards positioning in this way. Physical attacks frequently track the player regardless of movement, which makes dodging and spatial decision-making feel far less meaningful.

There are, however, glimpses of what ZA’s combat could have been. Optional moves like Protect, parry-style abilities, or those that create obstacles can make the system feel more interactive. Sometimes a fence or environmental barrier blocks an attack, or you can manipulate space with a move, but the game’s arenas aren’t built around these mechanics. The player has to engineer their own advantage.

These moments reward observation, timing, and strategy rather than raw damage output, but they are isolated and optional. The core system still defaults to repetition, limited control, and a lack of meaningful interaction.

This tension between potential and limitation reminds me of issues we faced during early development on Project Lorelei. We tried to make combat feel more real-time, more active, and more engaging, but the lesson was the same. Real-time alone isn’t enough. Player control matters. Without meaningful options, dodging, timing, maneuvering, the system can feel slower, clunkier, and ultimately less rewarding than a traditional turn-based approach. ZA falls into the same trap.

ZA’s combat isn’t bad; it’s just misaligned. Calling it “real-time” sets an expectation of dynamism and responsiveness, but the mechanics don’t fully deliver. Attacks hit when they want to hit, dodging is limited, and swapping feels like a patchwork solution. The tension, the thrill, the dance between prediction and reaction, that’s mostly absent.

In the end, Pokémon ZA’s combat shows the subtle but crucial difference between “real-time” as a label and real-time as an experience. Real-time should feel alive, reactive, and meaningful. ZA’s combat is often alive visually, but not experientially. Real-time combat isn’t defined simply by whether the clock is running, but by whether the player can meaningfully act within that time. It’s a reminder that real-time systems are only as good as the control and responsiveness they afford the player. Without it, combat can feel hollow.