Skip to content

fix(instance): new instances skip classic server numbers and busy ports - #82

Merged
sivert-io merged 1 commit into
masterfrom
fix/instance-number-skips-classic
Sep 29, 2026
Merged

sivert-io merged 1 commit into
masterfrom
fix/instance-number-skips-classic

Conversation

@sivert-io

Copy link
Copy Markdown
Collaborator

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. nextFree now skips numbers that have a server-N folder or whose game port is in use. Test: TestNextFreeSkipsClassicServersAndBusyPorts; ran on the cs2 box (Linux).

🤖 Generated with Claude Code

…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>
@sivert-io
sivert-io merged commit 318d3a2 into master Sep 29, 2026
2 checks passed
@sivert-io
sivert-io deleted the fix/instance-number-skips-classic branch September 29, 2026 18:21
@github-actions github-actions Bot locked and limited conversation to collaborators Sep 29, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant