Reaching Armory level 100 is less about finding one perfect farm and more about proving what each task sentence actually credits. “After a weak-point hit,” “assist within 10 meters,” “flinch,” “while using cover,” and “while aiming” combine a trigger, a distance or stance condition, a kill window, and a weapon-credit rule. If you test all four variables at once, a zero on the counter tells you nothing.
Check each task against the PC/Steam client from Season 2 Phase 1, available on August 26, 2026. A detailed community Armory record updated on August 25 and current-client footage document the task behavior. Some observations may be bugs or undocumented behavior, so test every shortcut with one kill and trust the live Armory panel if a later phase changes the rule.
Rewrite every Armory task as four fields
Before choosing an activity, translate the wording into a test card:
| Field | Question to answer | Proof to record |
|---|---|---|
| Trigger | What must happen first: weak-point hit, flinch, tag, reload, cover entry? | Visible hit feedback, stagger animation, or state change |
| Position | Must the agent be aiming, in cover, or inside a distance limit? | Stance and range at the trigger, not after the kill |
| Finisher | Does the same weapon need the kill, or is any later source allowed? | One controlled target and one counter increment |
| Credit holder | Which equipped or inventory weapon receives progress? | Before/after values for every candidate weapon |
Take a screenshot of the exact task and its starting counter. Kill one suitable enemy, return to the Armory panel, and compare the number. Only after a single increment is proven should you scale the method to a mission, Nest, event, or bounty.
Decode weak-point, assist, distance, and flinch language
The community record gives useful working interpretations, but they should be treated as hypotheses with readbacks:
- After hitting a weak point: a headshot or a hit that produces the yellow weak-point indicator can satisfy the setup. The target must then die inside the task’s accepted window. Do not assume every headshot is also a distinct breakable weak point.
- Assist: tag the target at least once, then allow another weapon, skill, teammate, or other valid source to finish it. Prove credit with one enemy before spreading tags across a room.
- Assist within 10 meters: the field report indicates that proximity is checked when the target is tagged; the later kill may happen from farther away. Test that sequence and then reverse it. If only the close tag increments, you know which moment owns the distance check in your client.
- Flinch: look for the enemy’s stagger reaction rather than ordinary damage. Leg or groin pressure at close range, a weak-point explosion, or a Cleaner fuel-tank reaction may create the required animation, but only the Armory counter proves it.
- Proxy targets: deployed hostile objects such as small robotic cars or turrets were reported to count as enemies for some tasks. Test one object separately; do not plan a full run around a proxy category that the current task rejects.
A phrase such as “kill after a weak-point hit” is especially easy to misread. The community author estimated a short completion window, but no official duration is published. Instead of writing down an unverified number, fire the setup shot and finish immediately. If that works, add a deliberate delay in the next test until you learn the current boundary.
Prove cover and aiming credit with inventory readbacks
“While aiming” and “while using cover” do not necessarily distribute credit the same way. A current community test reports that cover-based tagging can advance some eligible weapons carried in the inventory, while aiming-in-cover tasks may require the weapon to be equipped. That behavior is powerful if it still exists and dangerous if you assume it survives a patch.
Use a disposable four-step test:
- Equip one weapon with the cover task and leave another eligible weapon in the inventory. Record both counters.
- Enter cover, tag one durable enemy with the equipped weapon, and let a controlled source finish it.
- Open Armory and compare both counters. A change on the stored weapon proves spillover for that exact task and phase.
- Repeat while aiming manually. If only the equipped weapon moves, keep the two task families separate.
Do not call inventory spillover a permanent feature. The source itself expects undocumented multi-weapon behavior to be patched. If a batch suddenly stops progressing, rerun the one-enemy test before changing difficulty, build, or activity.
Stack two weapons only after one weapon works
Assist tasks can often share the same targets. Tag a durable enemy with weapon A, switch to weapon B, tag again, then allow the finisher. Check both counters. If the group kills targets too quickly for two clean tags, using one weapon per fast run can outperform a slow solo setup.
Class-wide progress is easiest to audit when every weapon reaches the same task family before the farm begins. Move Assault Rifles or LMGs to a shared cover-assist stage, for example, then test whether the carried set advances while another equipped class handles the visible tagging. The important optimization is not the number of guns in a screenshot; it is the number of counters that demonstrably move from one controlled encounter.
Death and weapon swapping were also reported not to erase an existing assist tag before the target dies. That can make crowded encounters useful, but it is fragile. Never rely on dying as part of the method. Treat a post-respawn increment as an observation, not a required step.
Match the activity to the task, not to a universal “best farm”
The current community route names several repeatable activities. Availability, enemy level, rewards, and event schedules can change, so choose by target shape:
- Open-world events: useful for ordinary tags, assists, and weak-point practice when enemies survive long enough to show the trigger. Daily reward limits do not necessarily stop the enemies from being useful, but the current event panel decides whether the time is worthwhile.
- Weekly Bounties and Nests: combine dense combat with gear, weapon-mod, boss, or specialization-material goals. Use Challenging or Heroic only when the group can keep targets alive long enough for the required tags.
- Wall Street Woes: the field record uses a Heroic replay and isolates Carl after clearing lesser enemies, then works from the server-rack area for reload or weak-point repetition. Confirm the mission and boss phase still behave that way before committing a long counter.
- A New Enemy: the opening boss encounter on Challenging was used to find armored NPCs. If the needed armor type is absent, reset only after confirming the task did not count another target type.
- Team Nests: a four-player Challenging or Heroic Nest can produce multiple enemies of the day’s armor type. Team damage is also the main failure mode: tell the group you need tags, or select a slower encounter.
Current-client footage shows mission replays, Wall Street Woes, Nests, Dark Zone menus, and high-level combat, but it does not show a controlled Armory counter before and after every technique. Confirm each task rule with the live counter.
Turn reload requirements into a repeatable cycle
Reload tasks fail when talents or magazine behavior change the cycle. Remove bullet-return effects while testing. Favor reload speed and fire-rate support only after confirming they do not alter the task’s required state.
For pump-action shotguns, the community test uses a partial cycle: begin empty, load a small number of shells, fire them, and repeat. For magazine-fed shotguns and Assault Rifles, an empty-magazine reload may be required. Do not generalize one weapon’s behavior to the whole class. Record the counter, perform exactly one partial reload, read back, then perform one full empty reload and compare.
Skills can create a stable firing position, but they can also steal kills. If a Vanguard Smart Cover setup or another deployed skill keeps the agent safe, watch whether the skill damage changes the finisher source. A Commando Tactical Link can make tagging faster, while the field record warns that scoped ADS credit may still require manual aiming rather than link-assisted hits.
Protect upgrade materials before the late Armory push
Do not level every weapon merely because it has an unfinished task. The community author reports that later upgrades consume scarce purple materials and that dismantling does not restore the full investment. Exact costs, recovery rates, boss drop rates, and the number of weapons can change, so the current upgrade panel is the only safe calculator.
Use this spending gate:
- Advance cheap or material-free Armory stages across as many usable weapons as the current panel allows.
- When the next level introduces a new material color or quantity, stop and screenshot the cost.
- Test dismantle recovery with one expendable weapon only if losing the difference is acceptable.
- Spend rare materials on a weapon that will also serve a mission, bounty, Nest, or specialization objective.
- Pick up mission materials before leaving; never assume every reward is mailed to storage.
This converts the level-100 push into a sequence of verified thresholds. It is slower than trusting a fixed cost table and much safer than discovering that a live update changed the economy after dozens of upgrades.
Diagnose a frozen counter without changing everything
| Observed failure | Next isolated test |
|---|---|
| Weak-point task stays at zero | Use one enemy with a visible yellow weak-point response, then finish immediately with the same weapon. |
| Assist task does not move | Fire one body shot, stop dealing damage, and let one teammate finish while the target remains alive. |
| Close assist fails | Make the first tag from clearly inside the distance limit; move away only after the hit registers. |
| Flinch task fails | Ignore damage totals and choose a target whose stagger animation is unmistakable. |
| Stored weapons stop progressing | Reequip one candidate and repeat a single cover tag; assume spillover was changed until disproved. |
| Reload count stalls | Remove bullet-return talents and compare one partial cycle with one empty-magazine cycle. |
Change only the field named in the right column. Switching difficulty, activity, weapon, range, stance, talents, and finisher at the same time may produce progress, but it will not tell you why.
Recheck tasks after each live-service phase
Use the official Steam page to confirm the Windows release, specializations, skills, missions, and open-world activities. Before repeating a farm, check Ubisoft’s Season 2 Phase 1 announcement for the August 2026 phase boundary and current event schedule. Compare each community Armory observation with the live counter; do not assume undocumented shortcuts, fixed drop rates, fixed costs, or permanent “best” routes.