Series-wide guide resource
Super Robot Wars Z Hidden Units & Secrets | Checklist
Use this Super Robot Wars Z hidden units guide to separate Original Z, Hakai-hen, Saisei-hen, Jigoku-hen, and Tengoku-hen conditions before you follow a route note.
Searching for Super Robot Wars Z hidden units is easier when the exact game is fixed first. Original Z, Hakai-hen, Saisei-hen, Jigoku-hen, and Tengoku-hen share a family name, but their scenarios, routes, joining times, choices, kill counts, survival checks, and reward timing are not automatically shared. This page gives a series-wide checklist, then points you to the game-specific guides. Treat an untested condition as a note to verify, not a guarantee.
Set the boundary first
Super Robot Wars Z hidden units: fix the game before you follow a secret
Hidden units can mean mechs, pilots, weapons, upgrade parts, special conversations, alternate routes, joining conditions, or second-playthrough rewards. Choose the reward, then write the exact game title beside it. A note that only says Super Robot Wars Z may mean Original Z, a Z2 game, or a Z3 game. Fixing the title prevents a condition from the wrong route entering your checklist.
This page is an index and verification guide, not one giant scenario table. It explains what to record and which game page to open next. For an exact victory condition, route split, or scenario requirement, use the matching guide and compare its title, platform, route, and save state with your playthrough.
- Target: write whether you want a unit, pilot, weapon, conversation, route, or replay reward.
- Game: spell out Original Z, Hakai-hen, Saisei-hen, Jigoku-hen, or Tengoku-hen.
- Status: label the note confirmed, likely, or unverified.
- Boundary: ROMs, modified saves, unofficial patches, and file distribution are separate intents.
Identify the title
Confirm the game, platform, and scenario before reading a condition
Start a Super Robot Wars Z hidden units note with the full game name and platform. The Z family includes an original PlayStation 2 title, the PSP Z2 pair, and the PlayStation 3 / PS Vita Z3 pair. This helps with story order, but does not prove that a joining condition, scenario number, or kill threshold carries over. Add the scenario, route, branch position, and test save.
Similar package art or returning characters do not prove that a secret is shared. The image below only helps identify the title; it does not reveal a hidden-unit condition. Prefer the in-game result, the correct scenario, and a reproducible save over a number copied from another title. Use official information to identify the game and treat strategy notes as records to check.
- 1. Write the full titleRecord whether the note is for Original Z, Hakai-hen, Saisei-hen, Jigoku-hen, or Tengoku-hen.
- 2. Add platform and editionSeparate PlayStation 2, PSP, PlayStation 3, and PS Vita notes when the source does so.
- 3. Add scenario and routeKeep the scenario number, branch, pre-split or post-split state, and test save together.
- 4. Record the resultMark only an observed join, event, weapon, reward, or no-change result as confirmed.
Break down the condition
Break a hidden unit or pilot condition into seven fields
A note that only says join in scenario 25 is rarely enough. A secret may also depend on a choice, a pilot's kills, deployment, a conversation, survival, an SR Point, or the earlier route. Record target, timing, actions, result, source, and verification separately so you can see whether the condition is one trigger or several steps.
Keep the starting point for counts visible. A kill total may begin at game start, a route split, or the character's joining time. If a report cannot be reproduced, keep it unverified rather than turning a community number into a universal rule.
| Field | Record | Why it matters |
|---|---|---|
| Target | Unit, pilot, weapon, event, or reward | Prevents similar names from different games being merged |
| Timing | Scenario, joining window, before or after a split | A chapter label alone may be ambiguous |
| Route | Choice, destination, or team branch | A route-specific note may not be universal |
| Actions | Kills, deployment, talk, target defeat | Shows whose number and action are being counted |
| Extra checks | SR Point, turns, order, survival | Keeps challenge goals separate from a normal clear |
| Result | Joined, gained, triggered, or unchanged | Records what actually happened |
| Status | Confirmed, likely, or unverified | Leaves a trail for the next test |
Use it during play
Do not merge a normal clear, an SR Point, and a secret goal
A normal scenario clear, an SR Point, and a hidden-unit check can require different priorities on the same map. Record victory and defeat first, then add the SR Point's turn limit, defeat order, or target. Keep conversations, deployment, target defeat, survival, and joining results in a separate hidden-content column. If a test fails, you can see which goal failed.
Make a branch save before testing a theory and change one condition at a time. If you change route, deployment, conversation, and kill count together, you cannot tell what caused the reward. A series-wide Super Robot Wars Z hidden units checklist directs you to the correct game page without merging unrelated scenario notes.
- Normal clearRecord victory, defeat, reinforcements, retreats, and the next objective.
- SR PointRecord turns, defeat order, and special targets in a separate field.
- Hidden contentRecord the target, choice, talk, kills, deployment, survival, and result.
- RetestReturn to the branch save and change one hypothesis at a time.
Choose the right guide
Move from the series checklist to the correct game page
After using the series-wide Super Robot Wars Z hidden units checklist, open the guide for the exact title. Hakai-hen and Saisei-hen form the Z2 pair, but their scenarios, joining windows, routes, and secrets remain separate records. Jigoku-hen and Tengoku-hen are both Z3 games, but a condition from one is not automatically valid in the other. Keep Original Z outside Z2 and Z3 notes.
When a page does not confirm a condition, keep it unverified instead of filling the gap with a number from another title. A useful record contains game, scenario, platform, route, and save state. That boundary is better than a long list that cannot be reproduced.
| Game | Guide entry | Boundary to check |
|---|---|---|
| Original Z | Series index | Keep its platform, scenarios, and conditions separate from Z2/Z3 |
| Hakai-hen | Hakai-hen guide | Z2 first-part route, joining, kill, and conversation notes |
| Saisei-hen | Saisei-hen guide | Z2 sequel carryover, branches, and secret conditions |
| Jigoku-hen | Jigoku-hen guide | Z3 first-part scenarios and route checks |
| Tengoku-hen | Tengoku-hen guide | Z3 second-part late-game and replay checks |
Verification and replays
Keep uncertain reports and replay results useful
Secret guides can combine reproduced tests, old guidebook notes, community reports, and conditions from another game. Before following one, compare title, platform, scenario, route, and condition type. Official sources identify the game and its series relationship; check the actual reward against the in-game result and a matching save when possible.
For a first and second playthrough, record cycle, carryover state, funds, upgrades, kills, and unlocked status. If the reward does not appear, write no change instead of deleting the failed test. Super Robot Wars Z hidden units research is stronger when it preserves both working and failed conditions.
- Use official information to confirm title, platform, and series identity.
- Use the game screen to confirm scenario, conversation, joining, reward, or no change.
- Keep unverified values and possible cross-title confusion visibly labeled.
- Do not provide ROMs, piracy, modified saves, unofficial installers, or patch files.
Summary
Super Robot Wars Z hidden units are easier to verify when game and condition stay separate
For Super Robot Wars Z hidden units, lock Original Z, Hakai-hen, Saisei-hen, Jigoku-hen, or Tengoku-hen first. Then separate the scenario, route, choice, kills, deployment, conversation, survival, and SR Point fields, and label the result confirmed, likely, or unverified.
This page is a series-wide organization guide and a route into the game-specific pages. If a condition does not match the exact title and save context, do not present it as universal; return to a branch save and test one variable at a time.
Frequently asked questions
Super Robot Wars Z hidden units FAQ
What are Super Robot Wars Z hidden units and secrets?
They include hidden mechs, pilots, weapons, upgrade parts, special conversations, alternate routes, joining conditions, and replay rewards. Check each game separately.
Are Original Z and Hakai-hen conditions shared?
Not automatically. Match the title, scenario, platform, route, and joining window before using a number or choice.
What should I record first?
Write the target, game, scenario, route, choice, kills or deployment, result, source, and verification status.
Should I chase an SR Point and a hidden unit at the same time?
Only if your plan allows it. Keep the normal clear, SR Point, and hidden-content goals in separate fields.
Why make a save before a route split?
It lets you compare a choice, route, defeat order, or conversation without losing the original test state.
Can I trust a kill-count number from a guide?
Check game, route, edition, and counting start. If you cannot reproduce it, label it unverified.
Is this an official hidden-units list?
No. Super Robot Wars Z Wiki is an independent fan guide. Official pages are used for title identification and basic references.
Does this page provide ROMs or modified saves?
No. It covers legitimate route planning, scenario notes, SR Points, and hidden-content verification.
References
References for title checks and secrets research
- Official Super Robot Wars series information Use the official lineup to identify titles, platforms, and basic series relationships.
- Super Robot Wars Z secrets reference A non-official English reference used for comparison; it is not an official source.
Conditions may depend on game, scenario, platform, route, edition, or replay state. Prioritize the in-game result and the matching save.