Super Robot Wars Z3 Jigoku-hen Guide | Routes, SR Points, and Secrets

Game identification

What is Jigoku-hen? Lock the exact title before following a route guide

Jigoku-hen is the first part of Third Super Robot Wars Z. The Z series shares a large part of its naming, so searches can place Original Z, Hakai-hen, Saisei-hen, Jigoku-hen, and Tengoku-hen next to one another. Scenario numbers, route branches, joining timing, and SR Point conditions are not automatically transferable between those games.

At the top of a guide note, write the full game title, platform, scenario number, and current route. Package art and familiar unit names are useful for recognition, but they are not proof that a condition belongs to the game you are playing. Check the official series listing and the in-game display before applying a detailed Jigoku-hen walkthrough.

• Game: write Third Super Robot Wars Z: Jigoku-hen in the note header.
• Platform: record PlayStation 3 or PS Vita.
• Scenario: keep the number, route, choice, and victory condition together.
• Boundary: do not treat Hakai-hen, Saisei-hen, or Tengoku-hen conditions as confirmed Jigoku-hen data.

Route preparation

Make a save before the split and record where Jigoku-hen sends you

Create a separate save immediately before a route choice or a decision that can change the next scenario. On a first playthrough, this protects a reliable clear. On an SR Point run, it gives you a clean state for testing turn limits, defeat order, reinforcements, and retreat timing. A branch save is especially useful when an external note does not match your current progress.

A scenario number alone is not enough to reproduce a result. Add the choice, destination route, normal victory condition, defeat condition, reinforcements, retreats, deployment limits, and the extra SR Point condition. Mark whether the result was reproduced, supported by several records, or still unverified.

1. 1. Confirm the title and scenarioWrite the full title, platform, scenario number, and current route before the walkthrough details.
2. 2. Save before the choiceKeep a separate branch save so another route or condition can be tested without losing the comparison point.
3. 3. Separate normal and extra goalsUse different lines for the normal clear, SR Point, and hidden-content requirements.
4. 4. Label verification stateMark a note confirmed, likely, or unverified and keep its source beside the condition.

Scenario notes

Keep normal clears, SR Points, and hidden conditions in separate columns

A useful Jigoku-hen walkthrough starts with the normal victory condition and then adds the SR Point or hidden-content checks. Finishing a map and meeting an extra requirement may require different turn counts, target priorities, attack orders, or survival states. When every goal is merged into one sentence, it becomes difficult to tell why a challenge failed and what should be tested on the next attempt.

Use a small record like the table below to keep the first clear and the challenge run readable on the same page. For a new condition, add the platform, route, source, and reproduction status. Do not fill an unknown number just because a community note sounds confident.

Upgrades and deployment

Choose upgrades and deployment roles for the late game

Choose upgrades from the units you actually deploy rather than copying a ranking from another game. A front-line unit may need accuracy, durability, and a way to keep countering. A support unit may need movement, range, support attacks, or support defense. A boss-damage role may depend on weapon power, EN, spirit commands, and the support setup around it.

The important choice is often whether to concentrate funds on a small core or spread them across several roles. Record why you upgraded a unit, how often it deploys, what it struggles against, and what the next route demands. Recheck the priority when the route changes; a community ranking is advice, not a universal answer for every save.

• Front line: check accuracy, armor, evasion, EN, and repeated-counter options.
• Support: check movement, range, support attack or defense, and deployment slots.
• Boss role: compare weapon power, EN, spirit commands, and support combinations.
• Budget: record the reason and next deployment so the spending decision can be reviewed.

Hidden content

Turn hidden-content rumors into conditions you can actually check

When you look for a hidden unit, pilot, weapon, conversation, or route result, define one target first. Then split the note into scenario, route, choice, kills, deployment, conversation, SR Point, timing, and result. This shows whether several requirements are needed in the same run or whether multiple community records have been combined into one unverified sentence.

Even if several pages repeat a condition, label it confirmed only after it matches your title, platform, route, and save state. Use confirmed, likely, and unverified labels, and keep the source beside the note. ROMs, unofficial patches, cheats, and file distribution are different intents from a strategy guide, so this page does not turn them into download content.

• Target: name the unit, pilot, weapon, conversation, or route result.
• Timing: record the scenario and whether the check is before or after a split.
• Conditions: separate choice, kills, deployment, conversation, survival, and SR Points.
• Evidence: keep platform, route, source, save, and reproduction state together.
• Result: write only the reward or change that the check actually confirmed.

Series boundary

Do not copy Hakai-hen, Saisei-hen, Tengoku-hen, or Rengoku-hen conditions into Jigoku-hen

Jigoku-hen and Tengoku-hen are often searched together because both belong to Third Super Robot Wars Z, but their scenarios, route checks, joining timing, and hidden requirements still need separate verification. Saisei-hen belongs to Second Z, so even a connected story or returning unit does not prove that the same SR Point or hidden condition works here.

Rengoku-hen can also appear beside Z3 searches as a related side-story topic. Keep it in a series-boundary note or a future dedicated page rather than merging its conditions into a Jigoku-hen table. Match the exact game, scenario, platform, and route before treating a record as reusable.

• Keep Hakai-hen, Saisei-hen, and Jigoku-hen saves and scenario notes separate.
• Tengoku-hen is a sequel, but route and hidden conditions do not automatically carry over.
• Treat Rengoku-hen as a related topic, not as a confirmed Jigoku-hen condition table.
• Verify a condition in this order: game, platform, scenario, route, then result.