Repository navigation
fix(instance): new instances skip classic server numbers and busy ports - #82
Merged
Merged
Conversation
…sy ports Instance N plays on base+10N, the same ports as classic server-N. On a host that still has server-1..3, the lowest free instance number was 1, so a platform-created instance got port 27015 and failed to start. nextFree now skips numbers with a server-N folder or a game port in use. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
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.
On a host with classic server-1..3,
csm instance create(and platform-created servers via the host agent) picked instance 1 → port 27015, colliding with server-1.nextFreenow skips numbers that have aserver-Nfolder or whose game port is in use. Test:TestNextFreeSkipsClassicServersAndBusyPorts; ran on the cs2 box (Linux).🤖 Generated with Claude Code