-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Port management between instances #9
Comments
Would it also be okay to re-use the existing |
Yes, reusing |
Using a non-default port does not have any implication on the game: eg: the game can still be found in the server browser? |
Correct, port does not affect the ability to be seen in the server browser |
Ofcourse, the game is connecting to the server browser and telling it where it can find it, not the other way around. Otherwise you could not run multiple servers on a single IP address :) |
Well, I run into this myself with the latest event - I forgot to define specific ports for each server, and had to read the log to see that I derped.
I voiced an idea to put a file into the instance config folder like "port.xxxxx" and read those when creating a new instance, so we can assign a unique port to the instance.
The text was updated successfully, but these errors were encountered: