#108c: the asteroid gauntlet and the dimensional breach #124

New issue

Closed

opened 2026-08-23 17:25:01 +00:00 by metaheavens · 1 comment

metaheavens commented

2026-08-23 17:25:01 +00:00

Owner

Subticket of #108, depends on #108b. The ending, and the handover into the
game proper.

"on the way to the world ship there should be asteroid field, pretty dense,
making navigation hard".
"VFX with shaking screen and thunder appears" - the camera needs a shake at
all; there is none today.
"player loose control of the fleet which goes straight into a dimensional
breach".
"a small colorfull animation moves all the fleet around, destroying all the
ships beside one that should be left, the simple default ship".
Closing line, roughly: "it seems you've lost your way through the space, lost
and abandoned. no communication with the world ship can be heard".
Then the ordinary game begins, with one interceptor and nothing else - the
opening position a new game already has.

The end state has to be exactly what a normal new game starts from, or the
prologue becomes a source of odd save states rather than a scene.

Subticket of #108, depends on #108b. The ending, and the handover into the game proper. - "on the way to the world ship there should be asteroid field, pretty dense, making navigation hard". - "VFX with shaking screen and thunder appears" - the camera needs a shake at all; there is none today. - "player loose control of the fleet which goes straight into a dimensional breach". - "a small colorfull animation moves all the fleet around, destroying all the ships beside one that should be left, the simple default ship". - Closing line, roughly: "it seems you've lost your way through the space, lost and abandoned. no communication with the world ship can be heard". - Then the ordinary game begins, with one interceptor and nothing else - the opening position a new game already has. The end state has to be exactly what a normal new game starts from, or the prologue becomes a source of odd save states rather than a scene.

metaheavens referenced this issue

2026-08-23 17:25:13 +00:00

Introduction scene #108

metaheavens commented

2026-08-23 18:59:37 +00:00

Author

Owner

The belt is 90 rocks laid across the lane ahead rather than scattered around the fleet, so it has to be flown through.

The breach takes the wheel through ONE check in GameController, covering the stick, the keyboard and the released-again path together - three separate gates would have been three chances for one of them to keep steering. The shake is written to camera.offset and never to its position, because GameController owns where the camera is and would smooth a shake written there away.

The vortex whirls the fleet in and takes it apart on a stagger rather than all at once, and the vessel left is chosen as the interceptor rather than whichever happened to be first in the list. The prologue ends on exactly a new game's opening position - one interceptor, waves and asteroids running again, every button back - which the test checks field by field, because a prologue that left odd state behind would be a source of strange saves rather than a scene.

Done in 2091692, landed together with the other two - the frame is useless without a script and the script has nowhere to run without the frame.

Suite: 136/136 green.

The belt is 90 rocks laid across the lane ahead rather than scattered around the fleet, so it has to be flown through. The breach takes the wheel through ONE check in GameController, covering the stick, the keyboard and the released-again path together - three separate gates would have been three chances for one of them to keep steering. The shake is written to camera.offset and never to its position, because GameController owns where the camera is and would smooth a shake written there away. The vortex whirls the fleet in and takes it apart on a stagger rather than all at once, and the vessel left is chosen as the interceptor rather than whichever happened to be first in the list. The prologue ends on exactly a new game's opening position - one interceptor, waves and asteroids running again, every button back - which the test checks field by field, because a prologue that left odd state behind would be a source of strange saves rather than a scene. Done in 2091692, landed together with the other two - the frame is useless without a script and the script has nowhere to run without the frame. Suite: 136/136 green.

metaheavens closed this issue

2026-08-23 18:59:37 +00:00

metaheavens referenced this issue

2026-08-23 18:59:37 +00:00

Introduction scene #108

metaheavens referenced this issue from a commit

2026-08-29 13:22:02 +00:00

#108: the prologue - the convoy, the ambush, and the breach