Skip to content

Prune expired multiplayer matches on startup - #12

Draft
Innygr wants to merge 7 commits into
feature/multiplayer-persistencefrom
feature/multiplayer-startup-expiry
Draft

Innygr wants to merge 7 commits into
feature/multiplayer-persistencefrom
feature/multiplayer-startup-expiry

Conversation

@Innygr

@Innygr Innygr commented Oct 26, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • Remove matches older than the existing 12-hour lifetime immediately while restoring saved state at server startup.
  • Share the same expiry logic with periodic cleanup, including safe handling of invalid/missing timestamps.
  • Persist the cleaned snapshot before the server begins handling requests.
  • Add an integration test that ages a saved match, restarts the server, and confirms the match is gone from both the API and private snapshot.

CI

  • Expanded the workflow's pull-request target filters to include feature/multiplayer-persistence.
  • Added a push trigger for updates to that persistence branch so its checks can run as the stack evolves.
  • The GitHub connector did not return a workflow run for this head when checked, so the new test is not yet verified as passing. Please check the Actions tab for the run before merging.

Stack

This draft PR is based on feature/multiplayer-persistence and should be reviewed/merged in dependency order with the earlier multiplayer PRs. It has not been merged.

This branch has not been deployed

No deployments
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