Account Level vs Responder Level

Account progression opens options

Account Level is the broad progression signal in this guide's current Armageddon source boundary. It represents access to gear and Skills across the account. Treat that access as the pool of options available when preparing a roster, not as a summary of what one character has done. If an item or Skill appears to be unavailable, check the account-facing requirement before assuming that a Responder lost it during a mission.

This page does not publish an experience table, an unlock schedule, or a fastest leveling route. Those values can move with later updates and are not present in the attached source record. It can confirm the distinction between account access and character progression; it cannot turn that distinction into an unsupported promise about how many runs an unlock requires.

Responder progression carries risk

Each Responder begins with a background and starting Skill, gains character experience through successful play, and can be shaped for a role. The roster supports up to three Responders. Character experience and the risk of losing the character therefore belong to a named roster slot rather than to the account-wide access layer.

That separation matters after a run. Account access remains the broad set of gear and Skill options described above, while the returning Responder carries the individual progression earned on that character. A Responder who does not return cannot be treated as though the roster slot still has the same personal progression. Use the roster screen to verify the actual result instead of inferring it from the account number.

Difficulty also changes how seriously to treat that risk. The related permadeath guide records staged return opportunities on Beginner and Normal and immediate permadeath pressure on Hard and Nightmare. This page does not duplicate every difficulty rule; it uses that relation to explain why account access and a developed Responder should never be read as the same asset.

Make the distinction before deployment

Begin by naming the decision. If the question is "Can the account use this option?", inspect Account Level and the listed requirement. If the question is "What has this character earned?", inspect the selected Responder's experience path, background, and starting Skill. If the question is "What is equipped for the next run?", inspect the loadout rather than either level label.

Then decide which roster slot matches the run. A lower-risk learning slot can be used while route or control knowledge is still uncertain. A squad-support slot can be prepared around the role the group expects. A more developed slot can be reserved for a run where its individual progression justifies the added exposure. These are planning uses for the visible fields, not claims that one roster layout is optimal.

Avoid concentrating every important choice on one Responder when that would leave no suitable replacement after a loss. The three-slot boundary makes specialization possible, but it does not guarantee that a replacement inherits the former character's experience. Confirm each slot separately before treating the roster as interchangeable.

Check the correct screen

When an unlock seems missing, first identify whether it belongs to account access, Responder experience, or a purchased loadout. Confirm the value on the matching account, roster, or loadout screen before treating it as lost progress. A mismatch between screens is a classification problem until the relevant field has been checked.

After a successful return, review the selected Responder and the account separately. The guide can tell you which type of progression each screen represents, but it cannot observe your match result or local profile. If the expected state is absent, record the exact screen, Responder slot, mode, and visible requirement before consulting newer official notes or troubleshooting material.

After a loss or a Rescue Beacon trigger, use the same sequence. Confirm whether the Responder remains, whether the Beacon is still present in the loadout, and whether the account-wide option is still available. Do not use Account Level alone as proof that the individual character survived.

Apply the current source boundary

The attached official Armageddon feed supports the account-versus-Responder distinction used here: account access, individual backgrounds and starting Skills, character experience, three roster slots, and character-loss risk. It does not supply a complete level table, exact experience awards, or a ranking of the best progression method.

For currency questions, continue to the related Credits, Merits, and Weekly Assignments guide. For character-loss and protection questions, use the permadeath and Rescue Beacon guide. Keeping those topics on their own dated pages prevents an account label from being stretched into a claim about rewards, difficulty, or recovery that this record cannot verify.