13 Sentinels: Aegis Rim by Vanillaware, published by Atlus/Sega depending on platform and storefront, mixes side-scrolling adventure scenes with top-down Sentinel battles and an Analysis mode that organizes the mystery.
Content warning: ESRB rates 13 Sentinels: Aegis Rim T for Teen with Fantasy Violence, Language, and Partial Nudity. This guide keeps fictional teen sci-fi material non-graphic and focused on play.
Spoiler note: This is a spoiler-safe fundamentals guide. It explains how the three modes work together, but avoids route solutions, late Mystery File contents, culprit-style reveals, and final battle details.
Essential Tips
1. Treat the Three Modes as One Loop
Remembrance, Destruction, and Analysis feed each other.
Remembrance gives you character scenes and context. Destruction gives you battles, Meta Chips, Mystery Points, and combat rewards. Analysis stores the clues, files, and event history that make the non-linear story easier to follow. If one mode feels dry, spend time in another instead of forcing progress from the same screen.
2. In Remembrance, Search Before You Guess
The usual answer is on the current screen or in the Thought Cloud.
Move through the area, check every person and object that looks interactive, and watch for new keywords. When you get a keyword, try it on the people or objects tied to the current problem. Some route moments bend the normal rules, but most progression starts with patient screen reading.
3. Watch Topic Changes, Not Just Dialogue
A conversation can become a different puzzle after one line changes.
Some scenes loop until you catch the useful moment, stand in the right place, or use a Thought Cloud term at the right time. If repeated dialogue is not advancing, look for a changed topic, a new keyword, or a person moving into a new state.
4. Use Analysis Before Looking Up Spoilers
The game gives you a built-in evidence board.
Mystery Files and the Event Archive exist to make scattered routes readable. Before opening a solution page, check whether Analysis has a character entry, event order, or terminology note that reframes what you already saw.
5. Build Around Terminal Defense
Destruction is not just about chasing enemies.
The terminal is the center of every normal battle. Kill threats quickly, but do not drag every pilot away from the objective. Keep enough coverage near the terminal for enemies that slip through, spawn from another direction, or appear as incoming meteors.
6. Rotate Pilots Before Overload Forces You To
Favorite teams can become unavailable at the wrong time.
Repeated strike-team deployment causes Brain Overload, which makes a pilot sit out a battle. Use a rotating bench so several pilots remain usable. A slightly weaker fresh team is better than arriving at a harder wave with your best answers unavailable.
7. Spend Meta Chips on Reliable Value
Early upgrades should help in many fights, not one flashy moment.
Terminal upgrades, core armaments, and generally useful Sentinel tools are safer early investments than narrow experiments. The exact best loadouts differ by platform and playstyle, but the beginner rule is stable: make your common actions stronger before over-specializing.
8. Keep Different Sentinel Generations Ready
Objectives and enemy types reward variety.
Destruction asks you to handle ground swarms, aerial threats, tougher targets, support enemies, and bonus conditions. Do not let one generation carry every upgrade while the rest fall behind. A balanced roster makes restrictions and surprise waves easier to handle.
9. Use the Pause When Choosing Actions
Destruction moves in real time, but action selection gives you room to think.
When a pilot is ready, check the map before spending EP. Look at incoming landing zones, terminal pressure, pilot position, and whether the action leaves that Sentinel exposed. Fast decisions matter less than correct ones.
10. Stay Spoiler-Disciplined
A full answer list can solve the route and weaken the mystery.
If you are stuck, search for the smallest hint that names the mechanic, not the reveal. For 13 Sentinels, the difference between “use a Thought Cloud keyword differently” and “here is the route answer” is the difference between guidance and a major spoiler.
Mode Flow
| Mode | What You Do | Beginner Habit |
|---|---|---|
| Remembrance | Explore scenes, talk, inspect, and use Thought Cloud keywords | Exhaust the screen and watch for new keywords before assuming a lock |
| Destruction | Select pilots, defend terminals, spend EP, and clear kaiju waves | Protect the terminal while rotating pilots and managing EP |
| Analysis | Review Mystery Files and Event Archive entries | Use it after major scenes or battles to reconnect story threads |
The game is built to be non-linear. You do not need to force one character route until it stops. When story progress slows, run a few battles. When battles unlock files or context, review Analysis. When Analysis clarifies a character or term, return to Remembrance with better orientation.
Remembrance Habits
-
Sweep the whole screen: Walk left and right before using every keyword. Some scenes expect position changes, not only menu choices.
-
Use keywords intentionally: A Thought Cloud term is usually meant for a person, object, or situation. Try the obvious match first, then reconsider distance, timing, and current topic if that fails.
-
Notice loops: If a scene repeats, the route may be asking you to interrupt at a specific moment, change the conversation topic, or choose a different person to follow.
-
Track character percentages lightly: Progress percentages can tell you that a route has moved, but they should not become the main way you experience the story.
-
Avoid route-by-route spoilers early: The first draft goal is understanding the mechanics, not solving every branch from a checklist.
Destruction Combat Habits
| Situation | Good Response | Why It Helps |
|---|---|---|
| Battle starts | Check terminal position and incoming landing zones | Prevents tunnel vision on the first enemy group |
| Strike team selection | Bring a mix of ranges, mobility, and support | Covers more enemy types and objectives |
| Pilot has low EP | Defend or use a cheaper action when the fight allows it | Preserves availability for the next threat |
| Multiple enemies pressure the terminal | Use area attacks, interceptors, sentries, EMP, shields, or Meta-Skills as available | Buys time before the terminal takes critical damage |
| A favorite pilot is near Brain Overload | Bench them before the next important fight | Keeps the roster flexible |
| Bonus objective looks risky | Clear safely first, then replay for the bonus later | Protects progress while learning the wave |
Terminal defense is the through-line. You can send melee Sentinels forward, keep ranged units back, and use support tools, but every move should answer one question: does this make the terminal safer?
Analysis and Mystery Files
Analysis is not a bonus menu to ignore. It collects Mystery Files and Event Archive entries from your Remembrance and Destruction progress. Use it like a spoiler-safe notebook.
Check Analysis when a term appears repeatedly, when two characters seem connected across routes, when a battle reward unlocks new files, or when the event order feels scrambled. Mystery Files can include useful background, but they can also touch story reveals, so read newly unlocked entries with care and avoid browsing late-file lists outside the game.
Common Mistakes to Avoid
-
Do not ignore Analysis - The mode exists to organize information gathered from Remembrance and Destruction.
-
Do not brute-force every Remembrance scene - Look for changed topics, new keywords, positioning, and interaction timing.
-
Do not chase every enemy away from the terminal - A clean kill far from the objective is not worth losing the center.
-
Do not deploy the same strike team every battle - Brain Overload will eventually make repeated pilots sit out.
-
Do not spend all Meta Chips on one favorite pilot - Team restrictions, enemy variety, and overload make a broader roster more reliable.
-
Do not treat Switch and PS4 build advice as automatically identical - Source research notes platform balance differences; validate exact builds before committing to a platform-specific route.
-
Do not open full Mystery File lists unless you accept spoilers - The system is useful, but external file lists can reveal more than a beginner needs.
Summary
| Category | Top Tip |
|---|---|
| Overall Flow | Rotate between Remembrance, Destruction, and Analysis |
| Remembrance | Use Thought Cloud keywords after checking people, objects, and topic changes |
| Destruction | Defend the terminal first and clear enemies second |
| Pilots | Rotate strike teams before Brain Overload forces a bench |
| Upgrades | Favor terminal and broadly useful armament value early |
| Analysis | Review Mystery Files and Event Archive entries before using spoiler guides |
| Spoilers | Seek mechanical hints before route answers |
Did this answer your question?
Your feedback helps keep the useful answers visible.Next answers
Community notes0
No community notes yet.
Sign in to contribute