Plans: multiplayer phase 2 design, and what is left after this round
Some checks failed
CI / test 1/4 (push) Waiting to run
CI / test 2/4 (push) Waiting to run
CI / test 3/4 (push) Waiting to run
CI / test 4/4 (push) Waiting to run
CI / build (push) Waiting to run
CI / test (push) Blocked by required conditions
CI / translations (push) Waiting to run
Container image / test (push) Waiting to run
Container image / publish (push) Blocked by required conditions
Auto-release / release (push) Has been cancelled

This commit is contained in:
jvanvik 2026-11-07 01:12:23 +01:00
parent e1ae8e0164
commit b533f3baa8
2 changed files with 459 additions and 0 deletions

View file

@ -0,0 +1,55 @@
# What is left (as of 2026-11-07)
Work in this fork, pushed to the `vanvik` Forgejo remote (never to `origin`). Built so far: the build standard, multiplayer
phase 1, dark mode (#80), IPv4 address space (#150), express fiber (#58) and satellite teleports (#83). Everything below is
planned or known, not built.
## Promised and not done yet
1. **Router model and line system set in one place only.** The build standard (`S.popStd.g`, `S.popStd.sys`) and two
standing-order settings say the same thing: the `routers` order's `model` (upstream 1e7638c) and the `optup` order's
`sys` (upstream 647e302). Neither ever steps down, so they do not fight, but a player can pick two different targets.
Plan: the Build standard sheet becomes the only place to pick them. The `routers` order reads its model from the
standard, and `optup` its line system (their lists turn into a line "from the build standard: X, change"); sanitize
moves an old `model`/`sys` setting into `S.popStd` when the standard has none.
2. **One owner per fiber for line systems and optics.** `std` (sys/opt targets: a quiet fiber, or a parallel link with
room) and `optup` (one full routing without the fiber, one a night) can each darken a fiber in the same shift. Let `std`
use `optup`'s check (`opsDarkOk`) for line-system swaps, or skip fibers `optup` is working on. Today `std` also holds
any fiber that carries an express with traffic; `opsDarkOk` would handle that case by itself.
## Next features
3. **Wave B: #97 co-op companies** (several players run one network with roles, budgets and approvals), host-authoritative
over the multiplayer server, and **multiplayer phase 2** (players as carriers in each other's simulations: transit,
peering, PNIs, shared fiber): design in `docs/plans/multiplayer-phase2.md`.
4. **Wave C: #144 directional traffic**, last and on its own: keep the totals, split them by traffic profile, utilization is
the busier direction. It comes after #58 because both touch link capacity (express channels now count too).
## Known limitations of what shipped
- **Multiplayer:** other players' POPs are not drawn on the map (no clean hook yet); cards are what each browser reports,
the server does not verify them; a save over ~60 KB sends only the card when the tab closes; the HUD chip in phone
landscape wider than 760 px was not measured. Behind a reverse proxy, run the server with `--trust-proxy`, or every
player shares one address for the rate limits.
- **Build standard:** the game menu has 8 tiles in a multiplayer game (7 otherwise), so the last row is not full; a wave
the standard just upgraded can still be handed back the same day by `decom` if a bigger parallel link carries it.
- **Dark mode (#80):** red error text on dark tinted cards is about 3.8–4.3:1 (bold, but below AA 4.5); the share card PNG
and the web manifest stay light; the WebGL map was checked by tests only, not by eye in a real GPU browser.
- **IPv4 (#150):** the intern does not manage addresses (optional in the issue); transfers are instant; lease-out income
is not in the investor revenue share; blocks granted to old saves can be sold after two years (a one-off windfall);
CGNAT annoyance costs refunds but does not slow broadband growth; the NOC window's address-space button does nothing.
- **Express fiber (#58):** splicing a whole fiber pair through a city was left out on purpose (every fiber end is a POP;
expresses cover the need); loss and MTU incidents on a fiber do not reduce the expresses on it; the fiber panel's
"n of max channels" line does not count express slots (the Express section does); regen sites added later do not charge
regen cards for express channels.
- **Satellites (#83):** no WISP zones, no satellite incidents (rain fade, sun outage), no footprints on the map, no
satellite tab in the drag-to-link window (ordering is from the city panel); GEO/MEO losses and prices are design
numbers; well-cabled islands (Wellington, Hobart) also count as "can be served"; MEO needs 5° elevation (10° would drop
416 pairs); Pitcairn's $120k satellite grant stays Pie-only.
## Housekeeping
- `npm run perf -- --browser` needs Chromium (`sudo pacman -S chromium`, then `PERF_CHROME=/usr/bin/chromium`); only the
jsdom benchmark has been run.
- Upstream release tags are not on `vanvik` yet: `git push vanvik --tags` if wanted.
- The merged worktrees under `.claude/worktrees/` and their `worktree-wf_*` branches can be removed.