Games/WARDOGS/Incorrect bans

WARDOGS FIELD MANUAL

Check the message.

A calm access triage page for launch-state kicks, queue failures and incorrect-ban reports. Capture the evidence, use the official channel and do not turn uncertainty into an account claim.

ACCESS / INCIDENT TRIAGE

The official launch notes changed the behavior around ban messaging, and the stability hotfix addresses connection failures. No reviewed source establishes an active false-ban incident. This page helps you file the right symptom; it cannot promise an appeal result.

SNAPSHOTSeason 1.0 launch + Stability Hotfix #1SOURCE CHECKED 12 SEP 2026Official launch notes · no individual account diagnosis

FOUR-WAY TRIAGE

Name the
failure first.

A precise report starts with the text on screen. Use one card, collect one clean timeline and link the official source that matches the symptom.

MESSAGE / BANNEDOfficial

The client explicitly says banned

Treat the exact wording as the first fact. Do not publish an appeal as resolved until the official channel confirms the account state.

REPORT CHECKLIST

  • Capture the full message, timestamp and current client version.
  • Do not change hosts files, anti-cheat files or account settings while the evidence is fresh.
  • Use the official report or appeal area and keep personal account details out of public posts.

SOURCE CHECKED 12 SEP 2026Official source

Steam · Pre-Load Live & Season 1 Changelog
MESSAGE / KICKEDOfficial

Check the exact kick message

The Season 1 changelog says the kicked-from-server message is now shown only for a ban. Separately, the stability hotfix targets unexpected disconnections. Save the exact wording and ask support to confirm your account state; this wiki cannot diagnose a ban from a symptom alone.

REPORT CHECKLIST

  • Capture the full message and installed client version.
  • Check whether this is the documented kick message or a different connection error.
  • Submit the message and match context to support if the account state is unclear.

SOURCE CHECKED 12 SEP 2026Official source

Steam · Pre-Load Live & Season 1 Changelog
QUEUE / AUTHOfficial

The symptom is a queue or login failure

Failed authentication, a long queue and a ban message are different reports. Use the symptom that actually appears so the report reaches the right troubleshooting path.

REPORT CHECKLIST

  • Check that the current hotfix is installed.
  • Wait for the server rollout rather than repeatedly relaunching sessions.
  • Note region, time, server and whether Steam itself is reachable.

SOURCE CHECKED 12 SEP 2026Official source

Steam · Launch Stability Hotfix #1
SUPPORT / FOLLOW-UPEditorial guidance

Check for a matching official update

Look for a developer post matching your exact error and client version. A general community hub does not establish that a false-ban incident exists or that an individual appeal has been accepted.

REPORT CHECKLIST

  • Compare your message with the latest official update.
  • Submit one complete report instead of duplicating partial appeals.
  • Keep the confirmation or ticket reference so follow-ups stay attached to the same case.

CURRENT-BUILD TEST PENDINGNeeds in-game verification

Steam community hub · live updates

REPORT TEMPLATE

Make the
timeline useful.

Copy this shape into the official report area:

CLIENTVersion / platform / regionEVENTTimestamp / server / match stageMESSAGEExact on-screen wordingREPEATWhat happened on the second attempt

Do not include passwords, authentication codes or unnecessary personal information.

SAFETY RULE

Do not use unverified hosts edits, anti-cheat changes or account workarounds as a default fix. The goal is a reproducible report that lets the official team distinguish a ban from a launch failure.