At a glance
Reconcile launch-week killstreak reports with the developer’s Crashout rename, Homies fixes and Drive By durability change without inventing new statistics.
Source: Trapstar Games / Steam · 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 ↗
Look for Crashout when following an older bomber guide
Patch 1.0.1.8 says the bomber killstreak was renamed Crashout. That gives readers a reason to check the current menu name before deciding an older guide refers to a different or missing reward. The announcement describes a rename; it does not supply a new activation requirement, blast radius or damage figure.
An old label in a recording is not automatically an error in that recording. Preserve the recording date and explain the later terminology change. We have not independently opened the current game menu, so the exact displayed wording and requirement should still be checked in your installed build.
Drive By durability changed, but the patch gives no health number
The same announcement reports a substantial increase in Drive By health. This supports saying that the developer changed its durability. It does not support calculating a percentage increase or publishing a fixed number of bullets needed to destroy it.
The earlier 1.0.10 announcement also mentions adjusted Drive By locations on some maps. A demonstration from an older build may therefore differ in both placement and durability. Treat a creator’s successful use as one dated example rather than proof of a universal route or counter.
Homies changes affect how old footage should be interpreted
The 1.0.1.8 post reports a fix for Homies passing through ceilings on some maps and an adjustment to their colors in Chaos. Those are specific developer-reported changes. They do not establish that every pathfinding problem is fixed or that a visually similar incident in an old clip still occurs.
When reporting a possible remaining problem, include the map, mode, installed version and what the AI actually did. A reproducible sequence is more useful than a statement that the reward is always broken.
Use launch-week menu reports as evidence pointers
HoodWarfare2.org’s killstreak guide identifies recordings by Legends6K and Ears and provides time offsets for its launch-week menu reports. Those pointers are useful when checking where an old name or requirement came from. Its listed thresholds and duration remain secondary reports here; this review has not independently replayed the cited menu footage.
Do not combine an older reported threshold with a new name and quietly label the result a verified current specification. Check the current menu or an appropriately dated recording before updating that row. Similarly, a favorite three-reward setup in a creator’s match is a preference, not evidence that it is best for every mode.
What to record before comparing two reward setups
Our suggested comparison record is deliberately small: version, map, mode, exact reward names, displayed requirements and the situation in which you used each reward. For durability observations, add the weapon, distance and repeated attempts; do not infer a health total from one chaotic encounter.
Keep these observations separate from the developer’s announced changes. That makes a later guide useful even when another patch adjusts the reward again, and avoids presenting a new name as a new numerical database.
Sources & scope
- Patch 1.0.1.8 · Draco, ARP and rule changes ↗
Original developer announcement retrieved via Valve news API. Developer-reported additions and changes; no independent game-client test. · 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
- Hood Warfare 2 Guide · Killstreak report ↗
Secondary menu report; thresholds and behavior are community-reported, not an official specification · Checked 2026-10-17
Revision history
- — Compared the named source material and recorded the limits of the conclusions.