This guide is player-facing strategy content with source metadata preserved. Patch-sensitive wiki-backed mechanics should be rechecked before turning them into tier lists, best-build claims, or exact-stat references.
This guide helps players use long-term progression as a learning tool. Rogue Command's Battle Archive and archive tokens can improve future runs, but permanent growth should not be used to hide basic mistakes.
The practical question is not "where should every token go?" without testing data. The better question is: what did the last run prove I need to improve?
Start With the Loss, Not the Upgrade Screen
After a run ends, identify the first point where the run became unstable. Did the Engineer die while expanding? Did Crystal stop flowing? Did the army lose too many key units? Did rewards point in several directions without forming a plan?
Only after answering that should you think about long-term growth. If the loss was economy tempo, look for growth that supports stability or gives you more room to recover. If the loss was random reward direction, value tools that help you shape future runs. If the loss was army preservation, consider how your next run can lose fewer important units.
Permanent Growth Should Reinforce Better Play
Good progression makes solid habits stronger. It gives you more margin, more options, or more control. It should not become a substitute for scouting, production, and Engineer safety.
If the Engineer always walks into danger, permanent bonuses will not solve the real problem. If factories sit idle, more unlocks may only give you more things you fail to produce. If every reward choice is unrelated, more options can make the draft harder, not easier.
Choose Growth Around the Run You Are Actually Playing
Spread investment when you are still learning broad systems. Focus investment when you know which identity you enjoy and what keeps breaking it. If you like stable defensive play, support that style. If you like mobility, support the map-control habits it requires. If you like sacrifice mechanics, make sure the economy and production can feed them.
Avoid planning around a future route you cannot yet execute. The Archive should help the next few runs become clearer, not lock you into a fantasy build.
Review Progress in Small Loops
Use a simple loop: play a run, name the first serious failure, choose one improvement target, then test whether the next run fails later or differently. If the same problem repeats, the issue is probably gameplay habit rather than missing progression.
This keeps the Battle Archive tied to learning. You are not just collecting bonuses; you are making better decisions with each attempt.
What Not to Claim Yet
Without recorded testing, do not publish an optimal token route, exact farming path, or universal Archive order. Different players lose for different reasons, and the value of growth depends on the run identity and current skill gaps.
Source boundary: official sources support the existence and broad purpose of archive tokens and Battle Archive progression. Specific upgrade routes need own testing before they become high-confidence advice.
Sources
Source IDs are resolved against the Rogue Command source registry. Internal notes are not shown on public pages.