Hood Warfare 2 Chain Snatch After 1.0.1.8: Scoring and Denial

The two changes to check before your next match

The developer’s October 17 announcement for version 1.0.1.8 lowers Chain Snatch’s target from 100 to 75 points. It also says that retrieving your own team’s chains no longer awards a point to your team. These are developer-reported rules for the announced update, not results of an independent test by this wiki.

The practical distinction is between earning score and denying an opponent a pickup. If an older guide treats every recovered friendly chain as a point for your side, that scoring instruction needs revision for the announced patch. Check your installed version and the match’s displayed objective before applying a dated guide.

Reference: Patch 1.0.1.8 · Draco, ARP and rule changes ↗

A friendly chain can still matter without increasing your score

The official store describes collecting enemy chains to earn points and recovering teammates’ chains before the opposing gang can take them. Read alongside the new patch, this supports a useful distinction: the friendly pickup can remove a scoring opportunity for the opponent without advancing your own total.

Do not describe the new rule as a reason to ignore friendly chains altogether. Equally, do not describe friendly recovery as a comeback scoring method. The patch specifically removes the point reward from that action. The reviewed sources do not provide a complete current table of every scoring event or custom-room override.

Reference: Hood Warfare 2 · Steam store ↗

Choose a pickup by its purpose and exposure

Our editorial suggestion is to name the purpose before moving: score from an enemy chain, deny access to a friendly one, or leave an exposed pickup until the area is safer. That vocabulary makes a team callout more useful than simply asking everyone to collect everything.

After winning a duel, check whether another opponent can cover the chain. A pickup that requires crossing an open lane can create a second death and another collection opportunity. Support a teammate’s approach or cover the exit when that is feasible. These are general objective-play suggestions, not tested safe routes for a particular map.

A simple way to check what your build is doing

Record the version and visible match settings, then note the team score before and after an isolated friendly-chain recovery. Keep enemy pickups and other simultaneous events out of the observation as far as possible. Repeat the check rather than attributing a score change to whichever pickup happened nearest to it.

If the result differs from the announcement, preserve the recording, match type and relevant settings for a report. A bot or private session may help isolate an action, but we have not verified every supported mode-setting combination or progression rule. Do not confuse a test of match scoring with proof that the session awards weapon unlock progress.

When checking an old video, use the recorded build and date. A launch-week example can accurately show the previous scoring behavior while still being unsuitable as instructions for an updated match.

Revision history

• 2026-10-17 — Compared the named source material and recorded the limits of the conclusions.

Keep exploring