Build a route you can actually assemble.

Each profile begins with a player goal and an acquisition order, not a synthetic score. The Shell, weapon, and sidearm must form a route the current dataset can point toward, while the strengths describe why the author chose that path. Limitations state what remains single-source, untested, or intentionally unclaimed. None of the profiles calculate damage per second, simulate enemy matchups, or establish a best-in-game tier.

Choose a profile by the route problem it solves. Mobility, a heavy setup, and avoiding early detours are different constraints. Open the details and compare which pieces are already confirmed in the current run, which require a new branch, and which should be tested before spending upgrades. A piece named in the profile is a plan until the game and source record confirm acquisition.

Acquire and test one piece at a time. Learn the weapon's reach and recovery, verify the sidearm interaction, and check whether the Shell's movement and abilities support the intended goal. Keep notes tied to the game build and encounter used. A setup that feels suitable in one route is a personal result, not measured evidence for a universal ranking.

Delay irreversible spending when the source is marked for recheck or the moveset has not been tried. The acquisition order explains when to investigate a piece; it does not require committing every resource immediately. If the current release moved an item or changed an interaction, keep the target open and update the evidence before rewriting the profile.

Use the comparison page when two profiles satisfy the same goal. Evaluate the same question across both columns, then choose the path with acceptable acquisition work and limitations. Preserve already completed targets if switching. A route change should not create duplicate progress or imply that previously confirmed equipment disappeared.

Completion means the named pieces were obtained and the player chose to use the authored route for the local profile. It does not certify damage, efficiency, or compatibility with every patch. Exporting the profile preserves those checklist decisions, while the game save and platform inventory remain separate evidence.

The build receipt should name the chosen route, each acquired component, the first encounter used for testing, and the source or game version checked. It should also retain the limitation that made another route unsuitable. If the player abandons the setup, record the decision without unchecking equipment that still exists in inventory. A later build can reuse those confirmed targets while leaving its unowned pieces open. This produces a route history based on actual acquisition and choice, rather than a sequence of percentages that changes whenever the preferred loadout changes.