This repository was archived by the owner on Sep 11, 2026. It is now read-only.
Handle fleet registrations and report actual connected players - #16
Merged
Conversation
ziaxzulu
marked this pull request as ready for review
September 9, 2026 14:37
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fleet registrations can attach one runtime to several Signal Servers and return no single public address. Handle that response without a startup exception, and publish actual connected players from Geyser's session manager independently of advertised server-list status.
This preserves the current five-setting signalling configuration and independent listener shutdown. The generated console configuration is loaded by the real configuration parser in tests. Counts above a lowered admission capacity remain actual observations; only the legacy load fraction is capped.
Depends on NetworkCompatible #15, pinned at
5d0063699be6e037dda8013cf3d7962338a2edc2. Validation: all 46 tests pass and the extension build/shadow JAR succeeds with the pinned local native artifacts. This is build and fixture evidence; no new native gameplay, stock-client or production run is claimed.