Period: October 15, 2025 Total Commits: 9
Hey — here’s what we worked on. Today was mostly stability and tooling: routing fixes for auth, a bunch of TypeScript cleanups that were blocking server starts, and a better experience around login and match visibility. Nothing flashy, but these changes reduce friction and keep matches running.
What’s New
-
Auth flow cleanup (client + edge routing)
- We straightened out how the client talks to the auth service. Requests now hit the right endpoints, and the edge correctly routes anything under /auth to the auth service instead of the game client.
- Practically, this means guest creation, username checks, and registration behave consistently without odd redirects or broken responses.
-
Long-lived sessions for tools
- Sessions now persist through restarts for our monitoring tools. This doesn’t change in-match behavior directly, but it helps us keep better eyes on live games without re-auth every deploy.
What Got Fixed
-
Sign-in and guest creation no longer error out
- Fixed a path duplication issue in the client that caused auth requests to fail with bad JSON. This is the one behind some “can’t create guest” reports. It’s gone.
-
No more “Loading…” forever on login
- Resolved an async middleware hang that left the login page stuck. The request chain is now properly awaited, so you get an actual response.
-
XP fairness
- XP is now only awarded to human players who stayed connected. Bots are excluded and won’t siphon or skew post-match rewards.
Player Impact Summary
- You can sign in and create guest accounts reliably.
- Matches start consistently (server boots aren’t blocked by TS errors anymore).
- XP is fair — only humans who finish matches earn it.
- End-of-match info is clearer with more accurate winner display and readable timelines.