cannons: describe the demo that is actually running

The page said eight cannons opening with ICBMs. That scene has always
fired four -- eight SS-20 fireballs arrive together and overlap into one
solid rectangle with the battlefield invisible behind it -- and the
weapon is called an SS-20 in the game itself.

It is also nine scenes now rather than the four it shipped with, two of
them in winter, and their aim points are searched for rather than
written down: cannons_reloaded compiles a scene by simulating every shot
the client can express against the live battlefield and keeping the one
that passes closest.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016Bfw6VZH9wT8qcMDaCa8VF
This commit is contained in:
wes
2026-09-02 00:14:30 -04:00
co-authored by Claude Opus 5
parent a63e2913b3
commit b6c62337ac
+5 -3
View File
@@ -50,9 +50,11 @@ const overTheWire = build ? mb(build.wireBytes) : null;
The battle below the button is a demo, and it has no server at all: the The battle below the button is a demo, and it has no server at all: the
clients packet handlers are ordinary methods, so a scene is just a script clients packet handlers are ordinary methods, so a scene is just a script
of the packets a real match would have sent, fed straight in. Which is why of the packets a real match would have sent, fed straight in. Which is why
it can show you eight cannons opening with ICBMs at once — a thing no it can open with a volley of SS-20s all landing on named cannons — a thing
actual match can produce, because the computer opponents cannot aim a no actual match can produce, because the computer opponents cannot aim a
guided weapon. guided weapon. It runs nine scenes, two of them in winter, and the aim
points are compiled: each one was found by simulating every shot the game
can express against the battlefield as it stood at that moment.
</p> </p>
{ {