Repository navigation
Measure and share connection lag using Core.Ping - #175
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Measure connection round-trip time every five seconds using the existing IRE GMCP Core.Ping contract. Show the latest RTT in the status bar and report the average of the last five samples to the game on subsequent pings. Start after network GMCP negotiation, including before login, and clear samples/timers on disconnect or GMCP disable.
Keep one untagged request outstanding so resume probes and late replies cannot corrupt measurements. Expire unanswered requests after 15 seconds and encode initial pings without a body. Local WASM sessions remain unsampled. Document the game-side session telemetry API and its 30-second freshness limit.
Validation: 149 Vitest files / 2170 tests passed; npm run typecheck; npm run test:audio-cache, including real Monaco/browser journeys and lazy audio cache checks.