Super Robot Taisen R Secrets & Hidden Mechanics

How the route system works

The game keeps a table of 37 rows, one per stage, each holding one or two scenario numbers. After every map it looks up the current scenario and moves to the next row, taking the first or second column depending on your last route choice. That is why every split lasts a fixed number of stages and why both groups always meet again on the same stage.

The epilogue changes

The final scene has four versions: one for each hero (Raul or Fiona) on each stage-1 route. The Nadesico route ends with Ruri and Saburota meeting the heroes after a last time jump; the Ra Cailum route shows a different scene, with an extra part if Lancerow joined you on the Space route.

The final Excellence depends on the hero

In stage 32 the script deploys a different final form by gender: Excellence Lightning for Raul, Excellence Eternal for Fiona. You never get both in one game.

What the old guides got wrong

Checked against the event scripts. None of this has been play-tested on every route yet; if your game behaves differently, tell us in the comments.

How retreating works

Each map’s script registers two kinds of events for a named enemy: one when it is destroyed and one when it retreats. The retreat event fires when the enemy’s HP drops under its retreat line; the enemy leaves and takes its part with it. The destroyed event only fires if the attack takes it from above that line straight to zero. Some story checks only listen to the destroyed event, which is why Master Asia must be destroyed in stage 26. The walkthrough marks every enemy that retreats.

Data Weapons come and go

Dendoh’s and Ohga’s Data Weapon attacks (Unicorn Drill, Viper Whip, Leo Circle, Bull Horn, Dragon Flare, Gatling Boar, Kiba, Phoenix Alae) are each switched on and off by a story flag. When the Galfa steal a Data Weapon or Vega is kidnapped, the script clears the flags and the attacks disappear from the weapon list until the story gives them back. That is normal, not a bug in the patch.

Kill counts the game checks

Cut and unused content

• Bright’s lost MAP weapon lines. Four battle lines are stored in the script archive but never referenced by any event: “High Mega Particle Cannon, fire!!” (twice) and two lines for launching a nuclear missile (“We’re using the nuclear missile. All units, fall back!”). No unit in the final game has a nuclear missile MAP attack.
• A placeholder message. The map-weapon quote table starts with “No message is set for the specified map weapon.”, a developer default that is never shown.
• Scenario “Used in No. 4”. The scenario table has a 58th entry with this internal title. It isn’t in the route table, so it can’t be reached.
• Mid-map map swaps. Three extra scenario records reuse the titles of stage 2 (both routes) and stage 35. The game switches to them during those maps when the battlefield changes.
• Travel-map scenarios. Four internal scenarios (“Travel Map: World / Japan / Earth Sphere / Solar Sys.”) hold the movement scenes between maps.
• A system debug menu. The ROM still contains a developer menu (character debug, coordinate display and more) and debug tables that rebuild your roster and story flags for any scenario. We use them to test the translation; they can’t be opened in normal play.

Special battle conversations

Almost every map has special lines when certain pilots fight each other: 206 pairs across all 51 scenarios. They change nothing mechanically (except where the Secret Units page says so), but many are the best scenes in the game. “A vs B” means the lines play when those two meet in battle; “talks to” is a Talk command next to the unit.

Still unverified

Two rewards from the old guides don’t show up as a script flag, so we can’t confirm their conditions yet: the Zambot 3 Ion Cannon (said to come on the GEAR HQ route at stage 29) and new attacks for Shin Getter after the stage 27 awakening. They are probably tied to the stage number or to the unit’s form rather than to an event. If you can confirm either, tell us in the comments.