Some checks are pending
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
67 lines
5.7 KiB
Markdown
67 lines
5.7 KiB
Markdown
# 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. and 2. are built: the router model and the line system are picked in the Build standard sheet only (the `routers` and
|
||
`optup` orders read `bstd().g` / `bstd().sys`; sanitize moves an old setting into `S.popStd`), and `std` takes a fiber
|
||
dark on `optup`'s routing test (`opsDark()`), sharing its budget a night, with one owner per fiber a shift (`X.fib`).
|
||
|
||
## Next features
|
||
|
||
3. **The server runs every game of a multiplayer build** (decided 2026-11-07, being designed and built). In a page built
|
||
with `MP_API`, each network's days run on the session server, not in the browser, so every player of a session is on
|
||
the same day at the same speed. A single-player game in that build is a session of one and runs there too; old local
|
||
saves keep working in the browser, and the plain build stays exactly as it is (static, no server, no requests).
|
||
- **Speed:** 1× by default (one day per `DAY_MS`, 2.5 s). Players vote for another speed, pause included; alone in a
|
||
session your vote decides at once. The world pauses while no player is connected.
|
||
- **Absent players:** while anyone plays, the networks of those away keep running on the server (their intern's
|
||
standing orders help), so nobody falls behind.
|
||
- **Why:** the same day for everyone, which phase 2's trades need, and less work for phones at higher speeds (at 1× the
|
||
day is about 10–15% of a phone's CPU on the big test network, at 8× about half; map and panels stay in the browser).
|
||
- **What stays in the browser:** map drawing and panels. The flow tables (`R.ef`/`R.fl`, about 3 MB per routing on the
|
||
big network) cannot be shipped every day, so what reads them (a selected link on the map, the link panel, PNI value,
|
||
puzzles) has to ask for them.
|
||
- **Phase 2 gets simpler:** with every world in one server process, its wall-clock timing (tenders that close after 10
|
||
real minutes, `idle` ≥ 300 s, notice on each player's own clock) can move to game days.
|
||
4. **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`.
|
||
5. **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. The
|
||
sheet's quote and "Bring everything up now" still judge a line-system swap without routing (`bstdDarkOk()`: a quiet
|
||
fiber, under 10% of its capacity, or a parallel link with room; any express with traffic holds its fibers,
|
||
`bstdXpBusy()`), so the quote is the bill; only the intern routes to test. A quiet fiber with no way around can still
|
||
go dark from the button. An old save's `routers.model` moved into the standard (only from a running order with an
|
||
intern hired; a paused one's is dropped) also becomes what new POPs get. A model or line system in the standard is a
|
||
ceiling for the `routers` and `optup` orders (their next-one-up rule only applies with "keep"), as an order's own
|
||
model was before; `optup` has no per-POP exceptions, so it moves fiber at POPs excepted from `std` too.
|
||
- **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` runs with `PERF_CHROME=/usr/bin/chromium`.
|
||
- The merged worktrees under `.claude/worktrees/` and their `worktree-wf_*` branches can be removed.
|