At a glance
Overall leveling unlocks weapons and equipment, weapon challenges unlock attachments, and kills with a gun unlock skins. Compare the current challenge and attachment description before changing a setup.
Source: Trapstar Games / Valve · checked 2026-10-17 ↗Version & evidence scope
Developer announcements: 1.0.10. Later builds have not been verified here.
Sources checked 2026-10-17. A source review is separate from an in-game test. Evidence standards ↗
Check the right progression track
| What you want | Published unlock route | Record in the current game |
|---|---|---|
| Another weapon or equipment | Overall reputation and leveling | Displayed name, reputation requirement and current level. |
| An attachment | Weapon challenges | Weapon, exact challenge wording and counter. |
| A weapon skin | Kills with that gun | Selected weapon, skin requirement and kill counter. |
These routes are confirmed by the store. Exact challenge counts, compatible weapon/attachment combinations and private-match eligibility are not specified there.
What to examine in each attachment category
| Officially named category | Question to check in your game | Useful observation |
|---|---|---|
| Sights | Can you see the target and nearby movement clearly? | Reticle readability, obstruction and comfort at the same range. |
| Magazines | What capacity and tradeoffs does the current menu actually display? | Displayed capacity and whether reload decisions change in your repeated scenario. |
| Grips | What effect does the menu claim for this compatible grip? | Repeat the same aiming sequence rather than assigning an assumed recoil percentage. |
| Suppressors | What behavior or tradeoff does the current description explicitly promise? | Record the description; do not assume a damage penalty or minimap rule. |
The category names come from the official store. This table proposes what to inspect; it does not assert hidden statistics or effects common to other shooters.
Compare two setups without changing everything
- Pick one weapon and save its exact current setup in the loadout planner.
- Record the installed version, map, mode, input device and a repeatable target or route.
- Keep the same graphics and sensitivity settings. Change one compatible attachment.
- Repeat several comparable attempts and record what you actually observed, including failed attempts.
- Save a second named setup and use the planner comparison to view the recorded differences.
This is an editorial observation method. Bot practice is officially supported, but a bot session does not establish performance against human opponents or competitive balance.
When a challenge appears stuck
Read the exact challenge requirement first: weapon kills, account reputation and an attachment challenge are different counters. Record the counter before and after a session, the weapon used and whether it was online, private or against bots.
Patch 1.0.10 reports a correction to end-of-match progression display and loadout presets not saving. That history is a reason to compare the relevant menu after a session; it is not proof that every missing counter is only a visual bug. Recheck that the intended preset is selected before another test.
Use reported unlocks as a starting point
The community weapon table contains dated secondary reports. A reported unlock level says nothing by itself about damage, time to kill or attachment compatibility. Confirm what your current menu shows before building a recommendation around it.
For an evidence-backed correction, send the weapon and attachment names, exact challenge text, version and dated captures through the contribution guide.
Sources & scope
- Hood Warfare 2 · Steam store ↗
Release, Windows requirements, modes, customization and progression · Checked 2026-10-17
- Patch 1.0.10 · Developer announcement ↗
Voice chat, T push-to-talk default, reporting, spawn adjustments, supermarket reference and preset/progression fixes; posted 2026-10-12 UTC · Checked 2026-10-17
Revision history
- — Published after review of the official store and developer announcement feed; no game-client testing claimed.