wuwi/splatter-tennis - splatter-tennis - Gitea: Git with a cup of tea

wuwi/splatter-tennis

0 Fork 0

T

wuwiandClaude Opus 5 9b9f18d312 LATER item 7: 1v1 multiplayer — shot-relay architecture, ghost match first

Decided with Oliver 2026-08-12. Records why tennis is the friendly case (the
sync unit is the shot, alternation already enforced by ball.lastHit, each
client authoritative for its own contacts), what the codebase already brings
(deterministic sim, fixed dt, beats.js ownership contract), the zero-dep
WebSocket path (~120 lines of stdlib RFC6455 in server.py, friend-code
rooms), the honest cost (reconnect-and-resume is the real work), and that
step one is the GHOST MATCH over plain HTTP — half the netcode falls out of
it as a byproduct. Plus the hook: score-is-the-body on both players, losing
is zombification.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-12 00:13:53 +02:00

Put a real world board behind the RANKINGS button

2026-08-04 17:03:17 +02:00

You aim it yourself now, and no two rounds are dealt alike

2026-08-11 18:16:25 +02:00

First recorded game win, and the rungs flatten

2026-08-11 23:43:57 +02:00

.dockerignore

Stop shipping the sprite pipeline

2026-08-05 07:49:47 +02:00

.gitignore

Put a real world board behind the RANKINGS button

2026-08-04 17:03:17 +02:00

CLAUDE.md

One file owns the court: beats.js, PROJECT.md (né HANDOFF), and tests gate the build

2026-08-11 13:23:27 +02:00

Dockerfile

The code moves into src/: index, server and the test harness keep the root

2026-08-11 13:45:23 +02:00

index.html

First recorded game win, and the rungs flatten

2026-08-11 23:43:57 +02:00

manifest.webmanifest

Feedback round: fire actually spreads, brutes lurch, crowd stops flickering

2026-07-27 05:58:18 +03:00

PROJECT.md

LATER item 7: 1v1 multiplayer — shot-relay architecture, ghost match first

2026-08-12 00:13:53 +02:00

server.py

Load the game once, not on every launch

2026-08-05 07:47:27 +02:00

test.js

The longer racket

2026-08-11 23:40:08 +02:00