Quick answer

This page lists Shell names and route clues that the reviewed Shell gameplay source makes useful for discovery. Its source is labelled test-build, so it does not publish a strength ranking, numerical talent values, cooldowns or final-balance claims. Use the table to choose a route to investigate, then verify the current in-game description before committing scarce progression.

Shell route evidence

ShellRoute clueAvailabilitySource context
TielEarly graveyard route near the starting village.Early routeTest-build evidence
ProximaEarly makeshift-beacon route beyond a bridge.Early routeTest-build evidence
EredrimGloomshade Grove route after corruption access.Later routeTest-build evidence
SmertOutskirts route using a blood-pool sequence.Later routeTest-build evidence
GenessaA sensor route followed by a return to Marrow Keep.Later routeTest-build evidence
LaszloLate-game route in the reviewed gameplay source.Later routeTest-build evidence
SaryllLate-game dungeon route in the reviewed gameplay source.Later routeTest-build evidence
GroguA tavern route after a Temple of Vatra task.Later routeTest-build evidence

The table is deliberately route-first. A name, a nearby landmark and an availability hint are enough to help a player decide whether to pursue a Shell now or leave it for a later pass. They are not enough to prove a final build, damage profile or universal role in every encounter.

How to use the table

Start with the Shell whose route overlaps with your current beacon or objective. The early reviewed gameplay points to Tiel and Proxima around opening-area routes, while the later entries depend on wider exploration or encounter progress. That gives a first-run player a useful branch: try an early route now, or keep advancing until a later route becomes practical.

The source also describes active abilities, passives and talent structures, but it explicitly uses earlier test-build material. GGSage keeps those detailed mechanics out of this launch page until current build context supports them. The benefit is simple: you can use the page to plan exploration without mistaking an older balance observation for a live rule.

Choose by the next task, not a ranking

If you are learning route navigation, an early Shell route is the better next step than a late route whose access depends on several unrelated systems. If you are already at a later landmark, the table gives a compact way to recognise which entity the source associates with that area. If combat is the immediate blocker, use Harden & Parry before changing your entire route.

The search phrase “best Shell” represents a real decision, but it needs current comparative evidence. At launch, a player is better served by a clear choice process: verify the present description, try the route, test the basic interaction and keep a record of the build context. That process is more durable than copying a creator’s preference.

What this page does not claim

This page does not claim a permanent ability value, an exact talent effect, a cooldown, a complete upgrade cost, a final availability gate or a universal playstyle result. It also does not turn a creator opinion into a public ranking table. A current official update or reproducible launch-build observation is needed for that level of detail.

For a first route, read the beginner guide. For equipment context, open Weapons. Those pages answer different tasks and should not be merged into one generic Shell list.

Frequently asked questions

How many Shells are listed here? The route table has eight named Shells from the reviewed dedicated source. It is a source-labelled discovery table, not a promise about every final-state detail.

Can I use these routes to find a Shell? Yes, use the route clues as an exploration starting point and verify the live in-game prompt or map state when you arrive.

Why is the source label important? The dedicated Shell source is test-build material. Keeping that label visible prevents balance observations from being presented as a final launch rule.

Sources

Last verified: August 19, 2026. Shell names and route clues are recorded as test-build evidence; numerical mechanics and creator rankings are excluded.