# Hood Warfare 2: Disconnect, Kick or Ban? Read the Notice Use actual messages and failure stages to choose game support or an EAC appeal. A connection error and an anti-cheat removal are not interchangeable. Canonical: https://hood-warfare.com/hood-warfare-2/insights/disconnect-kick-ban-message/ Published: 2026-11-02 Updated: 2026-10-24 Page reviewed: 2026-11-02 Evidence: Source-based editorial analysis; community claims retain their attribution Version scope: Developer announcements: 1.0.2.0, 1.0.1.4. Later builds have not been verified here. ## Quick answer Use actual messages and failure stages to choose game support or an EAC appeal. A connection error and an anti-cheat removal are not interchangeable. ## Which words should you preserve before trying another fix? This article compares message evidence and support destinations. It does not identify an account’s enforcement status or recreate a game error screen. Keep screenshots focused on the relevant notice and avoid posting credentials, private tokens or unrelated account information in public discussions. ## What does “host turned down connection” establish? For a similar present symptom, record the selected joining method, installed version and last successful stage. If the failure occurs before party formation, use the friend-joining article instead of an appeal form. A comparison with another intended session can add evidence, but one successful attempt does not explain the earlier failure’s cause. Reference: https://steamcommunity.com/app/5155360/discussions/0/594069880290953470/ ## What if the notice names an anti-cheat error? Keep the build and whether the error appeared during launch, loading or after entry with the notice. Follow documentation that matches that error through official support. Do not disable protection to make the symptom disappear or describe bypassing a check as proof that the underlying problem was repaired. Reference: https://steamcommunity.com/gid/103582791475829503/announcements/detail/672882996184875072 ## What can a developer ticket add after unsuccessful checks? The same long-running connection thread contains later reports of launch and anti-cheat errors. On October 30, developer-tagged Cole asked those players to open tickets in the game’s Discord. This is a support destination from a named developer reply, not a published diagnosis or a successful repair result. Provide the failed action, message, build and checks already attempted when using the developer’s official support destination. A participant reporting that reinstalling did not help is a reason to retain the failed result, not a reason to promise another reinstall. Distinguish the original October 12 problem from the later posts rather than treating the whole thread as one incident. Reference: https://steamcommunity.com/app/5155360/discussions/0/594069880290953470/ ## When is the Easy Anti-Cheat appeal route appropriate? Use the named issuer when an actual notice identifies an account ban. The official Easy Anti-Cheat appeal page asks for a reference ID and, for games other than Fortnite, says to reference the game’s support channel before submitting there. The support site separately offers error guidance. Do not invent a reference ID from a connection message. If the notice does not identify EAC as the issuer, do not assume the EAC form is the right destination. Keep the notice for the game’s support channel to clarify the restriction. This wiki cannot submit an appeal on your behalf, inspect enforcement records or promise reversal. Reference: https://www.easy.ac/support/contact/appeal ## Do official servers prove why a particular player was removed? Update 1.0.2.0 reports EAC protection on official servers and action against confirmed cheaters. Those developer statements describe the release’s protection and enforcement work. They do not establish that a particular disconnect was a ban, or that a player complaint proves a false positive. In the final report, mark the issuer, error code, stage and comparison result as observed or not established. Keep suspected cheating by someone else separate from your own technical removal. The main anti-cheat-and-joining guide provides the broader support checklist; this message-based comparison helps you choose its relevant branch without assigning an unsupported cause. Reference: https://steamstore-a.akamaihd.net/news/externalpost/steam_community_announcements/1847286114034585 ## Common questions ### Which words should you preserve before trying another fix? Preserve the complete visible notice, the action immediately before it and whether you reached a match. Then separate three questions: did the session end, did a system remove you with a stated error, or did a notice explicitly restrict your account? The word “kicked” in a forum title cannot answer all three. ### What does “host turned down connection” establish? In the Steam thread “cant connect to games,” whitekoolaidman reported “host turned down connection” on October 14. Other participants described a frozen loading screen or an inability to join. Those observations concern the connection path; the reviewed words do not identify a ban issuer or establish a permanent restriction. ### What if the notice names an anti-cheat error? An anti-cheat error deserves its exact wording and any code, not a conclusion based only on being removed. Patch 1.0.1.4 reports a fix for false anti-cheat kicks as well as join and crash fixes. That historical report does not show that a later removal is false or that every remaining failure has the same cause. ## Revision history 2026-11-02 — Compared the named source material and recorded the limits of the conclusions. ## Sources and scope - [Patch 1.0.1.4 · Developer announcement](https://steamcommunity.com/gid/103582791475829503/announcements/detail/672882996184875072): Password private matches, audio output selection, false anti-cheat kicks, join/crash fixes and version check; posted 2026-10-14 UTC; checked 2026-10-17. - [Update 1.0.2.0 · Official servers and fixes](https://steamstore-a.akamaihd.net/news/externalpost/steam_community_announcements/1847286114034585): Full original announcement retrieved through Valve news API; posted 2026-10-23 00:53:58 UTC. 40+ EAC-protected official servers, TheStrip/layout and lower-end FPS claims, map/mode rotation, preferred-mode Quick Play, shotgun nerf without numerical values and listed fixes. Developer reports, not independent current-client measurements.; checked 2026-10-23. - [Connection cases and Cole ticket reply](https://steamcommunity.com/app/5155360/discussions/0/594069880290953470/): Distinct historical join/loading/anti-cheat reports and October30 developer ticket request; no universal diagnosis or verified repair.; checked 2026-11-02. - [Easy Anti-Cheat · Player support](https://www.easy.ac/): Official support destination; checked 2026-10-18. - [Easy Anti-Cheat decision appeal](https://www.easy.ac/support/contact/appeal): Official reference-ID appeal entry; directs non-Fortnite players to game support first. No ban diagnosis or outcome promised.; checked 2026-11-02. Interactive tools are available on the canonical HTML page. This text does not include personal browser notes.