rules

The cross-slice constants of BLOCKBUSTER 767 — read-only, and the contract between any two parts of the game that have to agree on a number.

• TABLE — where the play surface is and where its edges are.
• LAUNCH — the launcher's position, how far the heading and elevation trim, and the wind band: how long a notch takes, how many there are, and what the red zone past the last one costs.
• CITY — the band of table the skyline stands in, its seed, and the landmarks.
• PHYS — masses, speed caps, the debris governor, the settle threshold and the margin a measured joint break force is multiplied by.
• SCORE — what a shoved block, a toppled tower and a block off the table pay, the chain window, the landmark and called-shot multipliers, and the star thresholds.
• SESSION — three planes, the round clock, the rest and wreck beats.
• STATES / EVENTS — the only state names and event names the game uses; a typo in either raises at the call rather than going quietly nowhere.
• LAYOUT — the bands every screen anchors into, as shares of the viewport.

Units are metres, kilograms and seconds. The table top is y = 0; +Z is downrange, so the plane launches at LAUNCH.z and flies toward the city.

A number only one slice reads lives in that slice's own files, not here.

Consumed by every slice.