Short answer
The launch hotfix says it fixed an issue where Offline Play was affected by the login queue. That does not mean every queue, timeout, or matchmaking failure is resolved for every platform. If the queue still blocks you, record the mode, platform, region, and exact wait step before calling it a server-wide outage.
The primary source is the official Early Access Hotfix 1. Launch coverage also documented the queue as a player-facing issue, but a media explanation is not a live server-status page.
What the launch notes establish
| Observation | Evidence state | What it means |
|---|---|---|
| A login queue appeared | Launch report | A wait screen can reflect authentication or launch traffic; it is not enough evidence for a total outage. |
| Offline Play was affected | Official hotfix | The developer explicitly listed a fix for the queue affecting Offline Play. |
| The queue still appears | Needs verification | Check build, platform, region, and whether the failure happens before or after the menu. |
Access check
- Finish the update.Make sure the client has installed the current launch patch before comparing queue behavior.
- Separate offline from online.Note whether the queue blocks the menu, offline story play, a public match, or a party.
- Run one clean comparison.Check a solo path once, then record whether the same account can reach the online flow.
- Keep the exact failure.Save the wait message, platform, region, time, and whether restarting changed the result.
Login queue FAQ
Why is Halloween: The Game showing a login queue?
Launch coverage connected the queue with early-access traffic, but the queue screen alone does not prove that the whole service is offline. Check the official channel and compare the exact mode that fails.
Does the login queue affect Offline Play?
The official Early Access Hotfix 1 specifically says it fixed an issue where Offline Play was affected by the login queue.
Should I keep retrying the queue?
Use one clean retry after confirming the update, then preserve the result. Repeated blind retries do not tell you whether the problem is account-, platform-, region-, or service-specific.