-
Notifications
You must be signed in to change notification settings - Fork 465
fix: cap maximum disconnect timeout #3810
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
base: develop-2.0.0
Are you sure you want to change the base?
Conversation
…-Technologies/com.unity.netcode.gameobjects into fix/cap-maximum-disconnect-timeout
|
A more appropriate way to check for overflow would be to use a checked statement. Also while we're modifying that code, we might as well handle the case of the disconnect timeout being 0. In newer versions of UTP, this is now valid and will disable the timeout entirely (which I guess is what users were trying to achieve by setting it very high to begin with). Setting it to the maximum maximum value in that situation makes sense. |
Purpose of this PR
Jira ticket
MTTB-1671
fixes: #3717
Changelog
Documentation
Testing & QA (How your changes can be verified during release Playtest)
Functional Testing
Manual testing :
Manual testing doneAutomated tests:
Covered by existing automated testsCovered by new automated testsDoes the change require QA team to:
Review automated tests?Execute manual tests?Provide feedback about the PR?If any boxes above are checked the QA team will be automatically added as a PR reviewer.
Backports