Skip to content

Recover fleet arrival alerts when polling misses warp history - #293

Closed
Guffawaffle wants to merge 2 commits into
playfrom
fix/fleet-arrival-system-view
Closed

Guffawaffle wants to merge 2 commits into
playfrom
fix/fleet-arrival-system-view

Conversation

@Guffawaffle

@Guffawaffle Guffawaffle commented Sep 18, 2026 •

Copy link
Copy Markdown
Owner

Fleet arrival detection could miss Warping -> Impulsing when polling observed an intermediate state or skipped Warping. Captured recall and outbound traces both retain native PreviousState=Warping at Impulsing.

Recover those arrivals using native history, requiring an observed journey and emitting once per journey. Baseline resets and fleet replacement discard saved history. The fallback is independent of view and intermediate state. Other notification rules are unchanged.

Regression cases replay both captured sequences, repeated arrival samples, normal travel, startup, reseeding and fleet replacement. Standalone source Windows build and pure tests pass. Fork Windows release build and all three review lanes passed at 19d405a. Deployed for Windows gameplay smoke; platform CI is running. This is a test candidate, not a play promotion.

@Guffawaffle

Copy link
Copy Markdown
Owner Author

Superseded by the combined Mac candidate #294: its fleet-arrival tracker and regression fixture contain these same two corrections. The fixes have also been carried to STFC-Mod#268. Closing the duplicate play promotion path while retaining its branch/history and evidence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant