Ilia Denisov 9d52885a6e fix(matchmaking): re-enqueue opens a new game, not the caller's own ...

A second "random opponent" enqueue with the same variant and per-turn
rule, while the caller's first game was still open (awaiting an
opponent), returned that same open game, so a player could never start a
fresh random game while one was still searching.

Drop the own-open short-circuit (step 1) in store.OpenOrJoin: a
re-enqueue now joins another player's open game or opens a fresh one.
Accumulation stays bounded by MaxActiveQuickGames, which counts open
games. Update the matchmaker/service/store doc comments and
ARCHITECTURE.md, and flip the pinning test to assert the new behavior.

2026-06-18 10:18:44 +02:00

..

config.go

feat(lobby): enter the game immediately and wait for the opponent inside it

2026-06-12 16:00:22 +02:00

invitations.go

feat(lobby): keep lobby/game caches fresh from any screen + invitation delta channel

2026-06-14 11:22:47 +02:00

lobby.go

feat(robot): per-game display names from a wide name corpus

2026-06-16 12:28:04 +02:00

matchmaker_test.go

feat(robot): per-game display names from a wide name corpus

2026-06-16 12:28:04 +02:00

matchmaker.go

fix(matchmaking): re-enqueue opens a new game, not the caller's own

2026-06-18 10:18:44 +02:00

store.go

Stage 4: lobby & social (matchmaking, friends, blocks, chat+nudge, invitations, profile, email, multi-player drop-out)

2026-06-02 19:29:30 +02:00