The game plays exactly as before; only what holds the page changes.
* mapStill() tells three cases apart: still (drawn once a second), ambient (only the animation clock moved: drawn at
most every 29 ms, so 30 fps on 60 and 120 Hz screens) and moving (camera, pointer, selection, network: every frame).
The animations follow the clock, so they keep their speed.
* save() skips the storage write when the text is the one the slot already holds (SLOT.txt) and no write is on its
way; leaving the page still writes. A big autosave that moved on is packed, turned into text, stamped and
compressed in the route worker (rwSave(), rwGzip()); the page only writes what comes back. A lost worker hands its
pending saves back to the page (rwSaveBack(), rwGzBack()).
* Less crosses back from the worker: R.efg stays there while R is its own last answer (RW.wR, efg 0), R.egDesc comes
as 0 or as the entries that changed (rwDescOut()/rwDescIn()), what crossed each link travels as typed arrays decoded
on demand (rwLOut()/rwLIn()), and the full ports (hotMap) come along with R. Every message is read in order
(rwMsg()), so both sides always hold the same last answer.
* Idle frames build the diverse-paths map and the latency floors a millisecond at a time (diversityWarm(),
latWarm()), before the first offer asks.
* Diagnostic info shows how fast days really come: speed asked, speed held, how long a day takes (15-day-pace.js).
* perf-bench: "The NOC intern's shift: opsDay()" and, in Chromium, "One game day in play: page time only", a day
played with the real route worker counting only the time it holds the page.
Tests: frame-pacing, day-pace, save-size, persist, route-worker (efg as typed arrays, hotMap from the worker),
day-steps (a second page plays the worker: answers without R.egDesc, with only its changes, posts without R.efg,
renewal haggles answered through the worker), intern-dark-fiber-worker, webgl-zoom-sprites, speed.
Towns with no road in (Russia's Arctic and Kamchatka, Juneau and Alaska's
Arctic coast, Greenland's towns) keep their own landmass, which now says
which land it is really part of. isSub() lets two cities of one country on
that land build over land; other countries still need the sea. Inside one
country, Europe to Asia (Moscow-Vladivostok, Istanbul-Ankara) is no longer
a crossing between continents.
North and South Korea join Kyiv-Moscow in a table of pairs nobody sells a
circuit between: the link window says so, the actions refuse, and neither
the diversity map nor the latency floor counts a link there.
The ceiling came from the straight-line distance, and nothing checked that a
path could reach it: Pevek-Anadyr asked for 4.3 ms over a 7.7 ms sea route.
latFloor() is the fastest a build could get, over own fiber on land and the
routes of cables that land at both ends; an offer whose ceiling is below that
and below what you already have is not made, as diverse offers are not.
Adapted to main: Globe is main's Globe-Trotter Telecom (now a Philippine
carrier in Cebu and Davao) instead of a second AS4775, the new Philippine
networks buy transit from NTT and Tata like main's other island networks,
cities and networks carry their country, and Philippine transit sits in the
new pricing. Cable names no longer pile up where short cables crowd.
Routes with both ends in the Philippines get their own subsea market rate,
PH_WAVE 3.7 instead of Asia's 1.5, so a 10G Manila–Cebu wave costs about
$7,900 a month: twice Manila–Hong Kong and level with Manila–Singapore.
International routes out of the Philippines keep the Asian rate. Leases
already signed keep their price.
Manila's 100 GigE transit is $2.25 per Mbps against Jakarta's $1.21
(TeleGeography, 2026), so Manila, Cebu and Davao get PH_TRANSIT 4.7, about
1.9 times the 2.5 every other Asian city pays. PLDT Home's full-year 2025
ARPU was PHP 1,447 a month (about US$25), so Philippine homes pay 0.7 of
the base broadband rate.
Under the scenario's new sender rule, Seoul transit carries a sender-pays fee per
Gbps, the Korean incumbents take traffic only over a paid PNI, home broadband pays
less, and Korean users mind any far exit, peering included. The goal asks for
700 Gbps, Seoul 92% served well, 99% reach and a monthly profit. Korea outside
the scenario is unchanged; older Gangnam saves pick up the rule.
Mind the Gap, Cape to Cairo and Order and Progress count cities and IX.brrr ports only
when your network joins them up (island POPs won without crossing anything). Fibre to
the Basement also needs 500 Gbps served (it was won on day 2). Anchors Away: nobody sells
transit in Tallinn, ships really do cut the Baltic links about three times a link-year,
and the 99.5% streak no longer counts Great Firewall losses. In the Cogentle Spat, Goggle
peers only once you send it eight times the usual traffic. Flood Season's terabit floods
count when scrubbing or Flowspec took them. Days cut where a reference won in a tenth of
the time; Stepping Stones and Mid-Atlantic Accent start with 5M; Mid-Atlantic Accent's
description no longer claims Lisbon to Lagos is too long for 1.6T.
tr('pnis.delivery_2_to_6_weeks') instead of tr('Delivery: 2 to 6 weeks'): the
English lives once, in src/i18n/en.js (inlined into the page at build, so no
extra request), and it/pt/fr map the same labels. Changing English wording no
longer renames a key in every dictionary.
- 2,899 labels, made from where each text is used and its first words; short
shared words are common.*
- plurals are one label with {one, other}: trn('label', n)
- static markup: data-i18n="label", data-i18n-aria-label, data-i18n-title
- saves from 1.33 and older stored English text in a few places; tr() still
resolves it
- i18n-check: undefined/unused labels, markup drift, plural shape; i18n-add.js
works on labels and --rename updates src/ too
- the old-branch port tool gives old English-keyed code and dictionaries the
same labels
site/index.html (900 KB of HTML, CSS and JS in one file) becomes src/: a shell
(src/index.html), styles/ and game/, concatenated in path order by
scripts/lib/page.js. The assembled page is byte-identical to the old file, so
load time and in-game performance are unchanged.
- scripts/build.js replaces build.sh (same env vars, same output)
- npm run dev: a zero-dependency dev server that assembles on every request
- tests assemble the page in memory; npm test runs every tests/*.test.js
- perf-bench takes --base-ref to build a git ref's page
- scripts/legacy/split-index-html.js is the splitter, kept for older branches