Private match · build 1.0.1.4
Play Hood Warfare 2 with Friends
Patch 1.0.1.4 added a password-only private lobby. Both PCs need that build in the bottom-right of the main menu. Pick the situation you are in. Every lane says what to check, where to look, and what to do next. Menu labels the developer did not publish stay marked unverified.

I’m hosting
You are creating the Hood Warfare 2 private match. Finish the version check before you hunt for a button.
01
Both players are on 1.0.1.4
- Check
- The main menu shows 1.0.1.4 in the bottom-right corner, on the host and on the joining PC.
- Where
- Main menu, bottom right. That placement is the developer’s own instruction for patch 1.0.1.4.
- Then
- If either menu shows an older number, or no number, stop and update before anyone shares a password.
Developer postPatch 1.0.1.4 post, 14 October 2026, 01:03 UTC.
02
Quit Steam completely if the build is old
- Check
- Steam was closed from its own menu, then opened again, then Hood Warfare 2 was launched.
- Where
- Top left of the Steam window: Steam, then Exit Steam. The developer named that path, not a dock or tray shortcut.
- Then
- Read the bottom-right version again. Do not treat a still-open Steam client as updated.
Developer postSame 1.0.1.4 post. Trapstar signed it Trap$tar.
03
Host a password-only private lobby
- Check
- The host has a private lobby that requires a password, on build 1.0.1.4.
- Where
- The patch says private matches are in the game. It does not name the button. Look in match setup for a private or password lobby. If your labels differ, this click path is unverified.
- Then
- Set a password you can read aloud. Avoid 0 and O, and 1 and l.
Not confirmed in-gameThe lobby’s existence is from the developer. The menu labels are not.
04
Send the password outside the game
- Check
- The joining player has the exact password.
- Where
- A text, a call, or a Discord message. The patch does not describe an in-game invite button.
- Then
- The joiner uses the password field. A pre-patch guide that only says to click a public lobby is the wrong path for this update.
Not confirmed in-gamePassword lobbies are confirmed. An invite button is not.
05
Wait until the friend is actually in
- Check
- The second player is in the lobby with you, not just “trying to join.”
- Where
- The password lobby on the same build.
- Then
- If they cannot see a room, the join errors, they get kicked, or the audio dies, switch lanes. Repeating “create lobby” does not answer those.
Not confirmed in-gameLane routing is this site’s checklist, tied to the fixes named in the patch.
I’m joining
You are entering someone else’s password lobby. Match their build first, then the password.
01
Both players are on 1.0.1.4
- Check
- The main menu shows 1.0.1.4 in the bottom-right corner, on the host and on the joining PC.
- Where
- Main menu, bottom right. That placement is the developer’s own instruction for patch 1.0.1.4.
- Then
- If either menu shows an older number, or no number, stop and update before anyone shares a password.
Developer postPatch 1.0.1.4 post, 14 October 2026, 01:03 UTC.
02
Quit Steam completely if the build is old
- Check
- Steam was closed from its own menu, then opened again, then Hood Warfare 2 was launched.
- Where
- Top left of the Steam window: Steam, then Exit Steam. The developer named that path, not a dock or tray shortcut.
- Then
- Read the bottom-right version again. Do not treat a still-open Steam client as updated.
Developer postSame 1.0.1.4 post. Trapstar signed it Trap$tar.
03
Get the password from the host
- Check
- You have a password the host just set on 1.0.1.4, not a room code from an older afternoon.
- Where
- Ask them directly. This site has not confirmed an in-game invite.
- Then
- Enter that password in the private-lobby join. Do not scroll a public list and assume their room is posted there.
Not confirmed in-gameThe developer said the lobby is password only. They did not say it appears in a public browser.
04
Join on the same build
- Check
- Your menu and the host’s menu both read 1.0.1.4.
- Where
- Bottom right of each main menu.
- Then
- If the join fails, you get kicked, or you load into silence, open the matching fix lane.
Developer postVersion placement is from the patch. The join result still has to be checked live.
Join fails
Patch 1.0.1.4 says it fixed various join failures and crashes. That only helps if you are actually on that build.
01
Both players are on 1.0.1.4
- Check
- The main menu shows 1.0.1.4 in the bottom-right corner, on the host and on the joining PC.
- Where
- Main menu, bottom right. That placement is the developer’s own instruction for patch 1.0.1.4.
- Then
- If either menu shows an older number, or no number, stop and update before anyone shares a password.
Developer postPatch 1.0.1.4 post, 14 October 2026, 01:03 UTC.
02
Quit Steam completely if the build is old
- Check
- Steam was closed from its own menu, then opened again, then Hood Warfare 2 was launched.
- Where
- Top left of the Steam window: Steam, then Exit Steam. The developer named that path, not a dock or tray shortcut.
- Then
- Read the bottom-right version again. Do not treat a still-open Steam client as updated.
Developer postSame 1.0.1.4 post. Trapstar signed it Trap$tar.
03
Verify the game files if 1.0.1.4 still fails
- Check
- Steam finished an integrity check and you launched the game again.
- Where
- Steam Library, right-click Hood Warfare 2, Properties, Installed Files, Verify integrity of game files.
- Then
- Try the password lobby once more. If it still dies, report it instead of cycling random settings.
Steam clientStandard Steam repair. It is not a sentence in the patch note.
04
Report a join that still fails on 1.0.1.4
- Check
- You told the developer the menu version, the map or mode if you got that far, and whether a friend could join.
- Where
- Steam discussions, or trapstargames@protonmail.com. Patch 1.0.10 also points bug reports at the developer’s Discord. This site does not have a verified invite link.
- Then
- Stop installing unofficial repair tools. They are not part of this fix.
Steam storeSupport email is the address on the Steam store page, checked 14 October 2026.
I get kicked
A kick after the 1.0.1.4 patch is a different case from a kick on an older build.
01
Both players are on 1.0.1.4
- Check
- The main menu shows 1.0.1.4 in the bottom-right corner, on the host and on the joining PC.
- Where
- Main menu, bottom right. That placement is the developer’s own instruction for patch 1.0.1.4.
- Then
- If either menu shows an older number, or no number, stop and update before anyone shares a password.
Developer postPatch 1.0.1.4 post, 14 October 2026, 01:03 UTC.
02
Treat an old build as the known false-kick bug
- Check
- You updated to 1.0.1.4 before deciding the anti-cheat is still broken.
- Where
- Bottom right of the main menu, then a full Steam exit if the number will not change.
- Then
- Launch again and rejoin the password lobby.
Developer postThe post says false anti-cheat kicks were fixed. It does not publish error codes.
03
Do not confuse a ban review with the false kick
- Check
- You are not installing a bypass. A report review is a different system from the false-kick bug.
- Where
- Patch 1.0.10 added a Report control in the pause menu. The developer said they review reports and ban players they decide are cheating.
- Then
- If 1.0.1.4 still kicks you instantly, write the developer with the version on screen. This site cannot see your account.
Developer postReport and bans are from the 1.0.10 post on 12 October 2026. The store page also lists Easy Anti-Cheat.
Audio is wrong
No game audio and a dead microphone are different fixes. Pick one lane on the troubleshooting page instead of mixing them here.
01
Both players are on 1.0.1.4
- Check
- The main menu shows 1.0.1.4 in the bottom-right corner, on the host and on the joining PC.
- Where
- Main menu, bottom right. That placement is the developer’s own instruction for patch 1.0.1.4.
- Then
- If either menu shows an older number, or no number, stop and update before anyone shares a password.
Developer postPatch 1.0.1.4 post, 14 October 2026, 01:03 UTC.
02
Split the symptom before you change settings
- Check
- You know whether the guns and menu are silent, or whether people cannot hear you.
- Where
- Silent guns and menu: no-sound lane. You hear the match but voice does not work: voice-chat lane.
- Then
- Open the troubleshooting page on that lane. The output-device fix will not repair a microphone, and push-to-talk will not repair silent guns.
Developer post1.0.1.4 covers the missing-audio output device. 1.0.10 covers voice chat.
What this page will not pretend
- It does not name a button the 1.0.1.4 post never named.
- It does not claim the password room appears in the public browser.
- It does not treat “no sound” and “mic dead” as one bug.
- It does not count a bot match as progress. That rule is unverified.
