fix(cellular): one action per account a tick, never a refused tick
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / postgres-tools (push) Successful in 1m39s
Foundation / server-image (push) Successful in 5m19s
Foundation / image (push) Successful in 6m54s

Region 16 playtest: a bud showed and was then undone, and several buds were
refused. The client scheduled a discrete action at server tick + lead, but
movement runs ahead of that once the lead shrinks (each movement takes the
tick after the last one sent), so a bud could name a tick a movement already
had. A tick takes one action per account: the region refused the whole tick
and dropped every player's actions on it ("tick stalled ... error=4").

- Server: keep_one_action_per_account keeps each account's discrete action
  (engulf, bud, become, emerge), else its newest, and refuses only the rest.
- Client: a discrete action is scheduled after every tick already sent, and
  movement is held off the tick a queued discrete action owns.
- Failed background commits now log their category, publication error,
  store error and SQLSTATE (never server text), to diagnose ok=0 commits.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-29 08:31:16 -04:00
co-authored by Claude Opus 5.5
parent 2ce8c3afb1
commit 9de55e352d
6 changed files with 90 additions and 4 deletions
+10
View File
@@ -1,5 +1,15 @@
# Project status and next steps
## One action per account a tick - 2026-10-29
Region 16 playtest: a bud was shown, then undone, and several were "refused". The client
scheduled a bud at the server tick plus its lead, while movement had run ahead of that after the
lead shrank, so both named one tick. A tick takes one action per account, so the region refused
the whole tick and dropped every player's actions on it (`tick stalled ... error=4`). The region
now keeps each account's discrete action (else its newest) and refuses only the others; the client
schedules a discrete action after every tick it already sent and holds movement off that tick.
Failed commits now log their category and SQLSTATE.
## Ending a stranded life - 2026-10-29
The portal's account page can end a published life whose reservation was never ended, which