Credits, Merits, and Weekly Assignments

Credits come from mission value

Supplies collected by the team are converted into Credits at final extraction. Credits can be spent on loadouts, Skills, and customization. This is a team-value boundary: the guide does not assign a private Credit amount to a single carried object or promise a payout before the run reaches its recorded result.

Use the post-run screen to confirm what the current match awarded. The attached official feed establishes the role of Supplies and Credits, but this page cannot observe what the squad collected, what reached final extraction, or whether a later patch changed a value. If the balance differs from an expectation, record the visible result before repeating the same route.

Credits and character experience are also separate. Final extraction can support both account-facing practical progression and the returning Responder's experience, while early extraction has the narrower preservation result described later. Do not use a Credit balance as proof that a specific Responder advanced.

Merits are the assignment-only alternative

Merits are earned only through Weekly Assignments in the current Armageddon economy boundary. They are an alternative currency, not the exclusive cosmetic side of a strict practical-versus-cosmetic split. Merits can unlock cosmetics and selected items such as the Rescue Beacon, while Credits can also cover customization alongside loadouts and Skills.

This page does not list prices, conversion rates, or a way to exchange one currency for the other. The current source boundary does not support those claims. Read the currency shown on the selected item before spending, then verify the displayed balance and cost on the same screen instead of inferring the accepted currency from the item category.

If a cosmetic option or practical item appears unavailable, separate the failure into three checks: wrong currency, unmet access requirement, or a value that did not update after the last result. The first two can be checked on the current screen. A suspected update failure needs the exact post-run or assignment state and newer official troubleshooting evidence.

Weekly Assignments define the short plan

Read the assignment before choosing a mode, map, or Responder. The assignment text is the visible definition of the current task; this guide does not infer unstated conditions from its title. Solo can progress Weekly Assignments, which provides an independent option when the task itself does not require squad coordination.

Turn the visible requirement into a pre-run checklist. Identify the stated action, choose a mode where that action is actually available, and avoid exposing a developed Responder when a lower-risk slot can verify the condition. After the match, return to the assignment screen and confirm that the counter changed before repeating the same setup.

A missing counter change does not prove one universal cause. The action may not have matched the written condition, the run may not have reached the required result, or the displayed state may need newer live-service guidance. This page can direct the check; it cannot diagnose an account or server it cannot observe.

Match the reward goal to the extraction choice

Before deployment, state whether the run is primarily for Responder preservation, character progression, Credits from team Supplies, or a visible Weekly Assignment. More than one result may matter, but naming the priority prevents the squad from treating every exit as equivalent.

Final extraction is the documented route for converting collected team Supplies into Credits and for character experience. Early extraction preserves the departing Responder, grants no character progression, and returns only a small portion of Credits in the current release description. The source does not publish a universal amount or percentage here, so this guide does not calculate one.

If the assignment is the priority, read its current condition rather than assuming early or final extraction is always required. If Credits are the priority, do not describe a preserved character as proof that the intended mission value paid out. If preserving a developed Responder becomes more important than the original reward goal, acknowledge that the decision changed and evaluate the result on that basis.

Avoid reward confusion

Use a four-part post-run review. First, confirm whether the Responder returned. Second, inspect individual character progression. Third, inspect the Credit and Merit balances under their correct labels. Fourth, inspect the current Weekly Assignment counter. These fields describe different results and should not be collapsed into one idea of "progress."

When one value did not change, keep the report specific. Record the mode, extraction result, visible assignment wording, and the screen that remained unchanged. Do not spend another run reproducing an assumption that has not been checked against the current field.

The attached official Armageddon launch and economy feed supports the currency roles described above. It does not establish current prices, exact reward quantities, optimal farming routes, or guaranteed assignment credit on this page. Consult a newer official note when a time-sensitive value conflicts with this dated boundary.

For the difference between account access and individual character progression, continue to the related level guide. For the exit consequences that decide whether mission value is realized, use the extraction guide. Those relations keep each reward statement attached to the page that can explain its own source limits.