Plans: the server-run design in the repo, what is left now, and the fork's files
- docs/plans/server-run.md: the server-run design, which lived only outside
the repo, with a status at the top (T1 and T2 merged, T3, T4 and the
integration waiting for the go; the four answers; the questions still
open) and a section on what building T2 changed: a checkpoint needs more
than route memory (rt carries pt, sl, ord and rk), who a worker exit
counts against, the budgets now over, the contract additions, the open
path-window question and what the shared calendar changes. The answers
are marked where sections 0, 1 and 14 ask; probes are named, not pathed.
- docs/plans/next-session.md: rewritten to match main at 3e30621: what is
built, the answers, the holds, the nine open questions, what is in
progress and next, and only the limitations that still hold.
- docs/ARCHITECTURE.md: a table of the fork's own files (build standard,
dark mode, IPv4, IPv6-only, express fiber, satellites, multiplayer,
server-run play, the session server and the engine), kept apart from
upstream's tables so merges stay clean.
- docs/MULTIPLAYER.md: server-run play is being built and not switched on.
This commit is contained in:
parent
3e30621684
commit
8068a45abd
4 changed files with 1578 additions and 63 deletions
|
|
@ -38,6 +38,14 @@ is switched on only when the build is told where the session server lives.
|
|||
Not yet (phase 2): peering, transit and competition between players inside the simulation. The card already carries
|
||||
what that will need (POPs, links, exchanges, transit, peering policy, reach).
|
||||
|
||||
## Being built: the server runs the game
|
||||
|
||||
Work has started on server-run play. In a multiplayer build, the session server will run every network's days, so all
|
||||
players of a session share one calendar and one speed, and the page will only show the network and send the player's
|
||||
clicks. The engine that runs networks on the server is in the source (`scripts/lib/mp-sim-*.js`), but nothing uses it
|
||||
yet and it is not switched on: sessions work exactly as this page describes, with each network simulated in its own
|
||||
player's browser. The design and how far it has got are in [plans/server-run.md](plans/server-run.md).
|
||||
|
||||
## Build
|
||||
|
||||
```bash
|
||||
|
|
@ -209,3 +217,6 @@ Cards are what each player's browser says: nothing on the server checks that a n
|
|||
`src/game/95-modals/48-multiplayer.js` (door, sheets, panel, chip), `src/game/90-actions/92-multiplayer.js`
|
||||
(actions), `src/styles/41-multiplayer.css`. The build stamps `MP_API` into `src/game/00-core/20-analytics.js`.
|
||||
- Tests: `tests/mp-server.test.js`, `tests/multiplayer.test.js`.
|
||||
- Server-run play (being built, not switched on): the act tables `scripts/lib/mp-sim-acts.js`, the engine
|
||||
`scripts/lib/mp-sim-engine.js`, `mp-sim-worker.js` and `mp-sim-realm.js`, the page's side `src/game/98-server-play/`
|
||||
(a comment so far), and the tests `tests/mp-sim-*.test.js` and `tests/server-sim-prereqs.test.js`.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue