-
Notifications
You must be signed in to change notification settings - Fork 450
fix: networkmanager starts when transport does not #1780
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
fix: networkmanager starts when transport does not #1780
Conversation
…ransport-does-not
…ransport-does-not
…ransport-does-not
IsServer = true; | ||
IsClient = false; | ||
IsListening = true; | ||
var result = NetworkConfig.NetworkTransport.StartServer(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we just kill result
local variable entirely? (also below as well)
and turn if checks into if (NetworkConfig.NetworkTransport.StartServer() == false)
etc.?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor suggestions but looks good otherwise
Co-authored-by: Fatih Mar <mfatihmar@gmail.com>
…ransport-does-not
When the NetworkTransport.StartServer returns false, we need to stop the startup process for both the StartHost or StartServer methods in NetworkManager. Otherwise there are failure to bind error messages and the server or host still thinks it is started.
MTT-2598
Changelog
com.unity.netcode.gameobjects
-Fixed: issue where NetworkManager would continue starting if the NetworkTransport selected failed.
Testing and Documentation