Late joiners: a network that joins a server session late starts on its date, with a head start
One calendar for a server session (the user's answer to Q1): a network that joins begins on the session's date, and one that joins after day 180, when the shared market starts to move, gets a head start (answered 2026-11-11). Dormant until the host (T3) passes a start day: in the plain build and in single-device play S.day0 is 0 and the game is as before. - S.day0, the calendar day a network began: 0 in newGame(), repaired in sanitize() (at most S.day), so old saves load. netAge() is the network's age; the first-days rules count it: the charter window (and specSanitize), the tutorial's five days, the DDoS grace and early size cap, route leaks, RPKI, the world's bad news, shortages and control-plane events, sold-out routes, the scrubbing customers, loan offers, the broker's first calls, the Speedrun and Blitz badges and the day counts in the win, lose and Glass Baron windows. The market, the calendar and world events stay on the session's date. - beginState() takes o.day for a session network in Normal mode (lateStart()): the day, the first outage and event, the home POP and the first IPv4 block are stamped with it, so the block cannot be sold on day one at the session's price. - The head start (60-features/81-late-joiners.js): starting cash topped up by the rise in hardware prices (START_CASH x (hwTrend - 1), to $1,000, at most $60k, with the market rule only) and the first 365 days of home broadband matched (R.rev.late: what homes pay after the Australian wholesale cut or levy; outside investors' share, inside revMo). A second welcome with a button to the bank, a Goals card, a bank section, a line in a city's broadband pitch and a toast when the year is over; every label in all six dictionaries. - The "since you started" lines (supply chain, bandwidth market, wave prices) measure from the network's own start. - Server-run engine: srvBegin takes begin.day (an integer from 0, else the begin fails), the fake engine begins there and keeps day0 in its saves, CLOCK.off leaves the shape checker and the contract test, and the fixtures' network begins on day 473 (written again with tests/lib/mp-sim-fixtures.js; a second run changes nothing). - Gameplay rule F11, the agent's day0 doc and status age, ARCHITECTURE and the plans (Q1's game side built, open question 1 answered). - tests/late-joiners.test.js; F11 in tests/gameplay-rules.test.js; a late begin in tests/mp-sim-engine.test.js; one calendar in tests/mp-sim-contract.test.js. Merged onto Starblink and Island Wi-Fi: revMo counts both the islands (V.wisp) and the match (V.late), the revenue share base keeps V.wisp and leaves V.late out; F11 sits before F12 in the gameplay rules and their test; the mp-sim fixtures were written again with tests/lib/mp-sim-fixtures.js (a second run changes nothing).
This commit is contained in:
parent
9067bae1ce
commit
dcdb501f16
51 changed files with 476 additions and 76 deletions
|
|
@ -83,9 +83,10 @@ The four questions of the server-run design:
|
|||
## Open questions waiting for the user
|
||||
|
||||
Asked on 2026-11-09, not answered yet:
|
||||
1. **Late joiners' prices and beginner grace.** With one calendar, a friend who joins an old session meets its economy
|
||||
from day one: at day 1868, hardware about 18% dearer and customer prices about 34% lower, with the 180-day beginner
|
||||
grace long over. Keep that, or give a grace or extra starting cash counted from the joiner's own start?
|
||||
1. ~~**Late joiners' prices and beginner grace.**~~ *Answered 2026-11-11 ("late joiners get a late joiners bonus and a
|
||||
year of double income per Gbps of FTTP sold/provided") and built: the day-0 rules count from the network's own start
|
||||
(`S.day0`, `netAge()`), and a network that joins after day 180 gets a hardware top-up and its first year of home
|
||||
broadband matched (`60-features/81-late-joiners.js`, gameplay rule F11). Dormant until T3 passes a start day.*
|
||||
2. **Other players' POPs on the map.** Draw other players' POPs and links on your map (from their cards) as part of
|
||||
the server-run work, or wait for phase 2?
|
||||
3. **The other modes in a multiplayer build.** Sandbox, scenarios, puzzles and the weekly keep running on the device.
|
||||
|
|
@ -110,8 +111,9 @@ Asked on 2026-11-09, not answered yet:
|
|||
## Next
|
||||
|
||||
- **After the user's go:** T3 (host and protocol), T4 (the browser client) and the integration of server-run play,
|
||||
as `docs/plans/server-run.md` describes them, with the corrections at its top. That includes the Q1 work: the game's
|
||||
`S.day0` and day-0 rules, a start day for a new network on the server, and `CLOCK.off` taken out of the contract.
|
||||
as `docs/plans/server-run.md` describes them, with the corrections at its top. The game's side of the Q1 work is
|
||||
built (`S.day0`, the day-0 rules, `begin.day`, `CLOCK.off` gone, the late joiner's head start); T3 sends the start
|
||||
day, checks every network's day after each tick and replaces the line-up of 4.7 ("What Q1 changes").
|
||||
|
||||
## Known limitations of what shipped
|
||||
|
||||
|
|
|
|||
|
|
@ -30,9 +30,12 @@ the plain build is unchanged.
|
|||
4. Phase-1 sessions **start fresh**: nothing is migrated. They keep running as phase 1 in the new build (section 8).
|
||||
|
||||
**Open with the user** (asked on 2026-11-09, not answered yet; `next-session.md` has the full list of nine):
|
||||
- A late joiner meets the session's economy from day one. In a session about five years old (day 1868), hardware costs
|
||||
- ~~A late joiner meets the session's economy from day one. In a session about five years old (day 1868), hardware costs
|
||||
about 18% more and customers pay about 34% less, and the 180-day beginner grace is long over. Keep it so, or give a
|
||||
grace or extra starting cash counted from the joiner's own start?
|
||||
grace or extra starting cash counted from the joiner's own start?~~ *Answered 2026-11-11: "late joiners get a late
|
||||
joiners bonus and a year of double income per Gbps of FTTP sold/provided". Built (see "What Q1 changes"): a network
|
||||
that begins after day 180 gets a starting-cash top-up as large as the rise in hardware prices and its first 365 days
|
||||
of home broadband income matched (`60-features/81-late-joiners.js`, gameplay rule F11).*
|
||||
- Other players' POPs and links drawn on your map (from their cards): part of this work, or later?
|
||||
- Sandbox, scenarios, puzzles and the weekly stay on the device in a multiplayer build (section 1). Is that fine, or
|
||||
should sandbox (or all of them) run on the server too?
|
||||
|
|
@ -198,6 +201,18 @@ ASK, or send a circuit's `l2route` entries on demand. Not decided yet; it is T4'
|
|||
|
||||
The design assumes each network keeps its own date (sections 0 and 1, 4.3 "Calendar", `p.net.off` in 4.6, 4.7, 14 and
|
||||
row F4), and T1 and T2 were built that way. Under the answer:
|
||||
|
||||
**Built (2026-11-12, dormant until T3 passes a start day):** the game's `S.day0` and `netAge()`, every day-0 rule below
|
||||
counted from the network's own start (and the scrubbing offers, the loan offers, the broker's first calls and the
|
||||
"since you started" lines of the supply chain, the bandwidth market and the wave prices), `beginState`'s `o.day`
|
||||
(`lateStart()`: the schedules, the home POP and the first IPv4 block stamped with it), `srvBegin`'s `begin.day` (an
|
||||
integer from 0, else the begin fails), the fake engine's start day, `CLOCK.off` out of the shape checker, the fixtures
|
||||
(their network begins on day 473) and the contract test, and the late joiner's head start
|
||||
(`60-features/81-late-joiners.js`). The card's `day` (`mpCard()`) stays the calendar date, which phase 1 compares; the
|
||||
market and the calendar stay the session's. Left for T3: the host sends `begin.day` (the session's day; a session's first
|
||||
network keeps 0, a fresh network after bankruptcy is late again), checks after each tick that every reply's day is `d`
|
||||
(lost and broken networks excepted), drops `off` from the live session and `p.net`, and replaces the line-up of 4.7;
|
||||
"Move to the server" makes a session of one at the save's own day and keeps its `day0`.
|
||||
- **Begin needs a start day.** `srvBegin` calls `beginState` with no day, and the `begin` message carries none. Both
|
||||
take the session day, passed on as `beginState`'s `o.day`. The fake engine begins at the given day.
|
||||
- **`CLOCK.off` goes,** or is pinned to zeros: in `tests/lib/mp-sim-shape.js`, the fixture generator
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue