Quick answer
Build a focused before-and-after record for one attachment challenge. Separate weapon, action, selected setup, session conditions and lost unlock availability.
Source: Trapstar Games / Valve · checked 2026-10-22 ↗What should one unchanged-counter report identify?
The example below is a proposed recording exercise, not a reproduced progression bug. It covers an unchanged attachment counter. A previously selectable item becoming unavailable is a different observation, and the linked level-and-item article explains how to preserve that comparison.
Why is a higher account level not the same result?
An ordinary match result may record several kinds of activity. A kill total alone does not establish which challenge received credit. The official description does not supply every required action, threshold or eligible session type, so do not import a challenge rule from another shooter or assume every target is simply total kills.
How can you rule out comparing the wrong weapon or slot?
For a hypothetical example, you inspect an attachment for A but then use B during the attempt. A’s unchanged counter does not isolate a tracking failure. Keep the weapon used and the target requirement in the same record. If you picked up another weapon, note that change instead of silently counting the whole session as time spent on A.
Reference: 9Puz · Hood Warfare 2 Beginner Guide: First Matches and Weapon Unlocks ↗
What does changing only one condition add?
Keep the same target and weapon while comparing one relevant condition. For example, distinguish an attempt in one ordinary session from an attempt under different room conditions. Record the result under each rather than changing weapon, target, mode and room together. This is an investigation method, not confirmation that a particular room does or does not award progress.
If the requirement names an action or distance, preserve its exact wording. Avoid inventing a distance boundary or assuming an animation proves the action qualified. When the session offers no comparable attempt, mark that comparison unperformed. An empty test cannot establish that the counter works or is broken.
Does an attachment becoming locked again prove the same problem?
KLAYERBEAR’s October 11 Steam post reports repeatedly unlocking a red-dot sight and finding it unavailable after death. The reviewed original has no replies establishing a cause or successful fix. It describes a loss of availability, which should not be silently restated as an observed unchanged challenge counter.
Keep those observations separate even if both feel like lost progress. A counter failing to advance, a counter changing between screens and an item no longer being selectable need different before-and-after records. The old post does not establish that dying normally removes attachments or that today’s version has the same behavior.
What should you retain after a new menu or patch?
Update 1.0.2.2 reports menu redesigns and says ESC now works in the loadout menu. It does not announce a specific repair for the attachment-counter comparison described here. Its statement about retaining unlocked characters as bundles concerns character customization; do not extend that promise to every weapon counter.
For an unresolved report, retain the named item, requirement, two counter observations, weapon actually used, session conditions and build. State whether the issue concerns counting or availability. That is useful evidence for game support without presenting a reinstall, a fixed wait time or an undocumented progression route as a guaranteed repair.
Reference: Update 1.0.2.2 · customization,party,input and fixes ↗
Common questions
What should one unchanged-counter report identify?
Identify one attachment on one weapon, its displayed requirement and its counter before and after a particular attempt. Keep the session and build with that pair. This narrows “progress did not move” to a comparison someone can investigate, rather than mixing several weapons, unlocks and sessions into one claim.
Why is a higher account level not the same result?
The Steam description separates leveling for weapons and equipment, weapon challenges for attachments and weapon kills for skins. An increase in the account level is therefore not, by itself, evidence that the attachment condition was completed. Keep the specific target attached to the comparison.
How can you rule out comparing the wrong weapon or slot?
Marvin Tang’s October 10 9Puz walkthrough points out that editing one loadout slot and entering with another can leave a player using a different gun from the intended challenge. This is a dated menu report, not a current-build demonstration. It motivates recording the actual selected setup rather than relying only on the setup you edited earlier.
Evidence, sources & revision notes
Version & evidence scope: Source-based reference; no game-client build independently tested. How we verify ↗
Revision history
- — Compared the named source material and recorded the limits of the conclusions.
Did this help you take the next step?
Send details to the editor ↗