Skip to content

fix: client side disconnect incorrect client count on host-server side [MTTB-135] #2941

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

Conversation

NoelStephensUnity
Copy link
Collaborator

This resolves the issue with the client count not being correct on the host or server side when a client disconnects itself from a session.
This also resolves the issue with the host trying to send itself a message that it has connected when first starting up.

MTTB-135

fix: #2927

Changelog

  • Fixed: Issue with the client count not being correct on the host or server side when a client disconnects itself from a session.
  • Fixed: Issue with the host trying to send itself a message that it has connected when first starting up.

Testing and Documentation

  • Includes integration test update.
  • No documentation changes or additions were necessary.

This resolves the issue with the client count not being correct on the host or server side when a client disconnects itself from a session.

This also resolves the issue with the host trying to send itself a message that it has connected when first starting up.
adding change log entries
Adding validation for the connected clients count on the server side when the client-side disconnects.
adding PR number to changelog entries.
@NoelStephensUnity NoelStephensUnity marked this pull request as ready for review June 3, 2024 16:36
@NoelStephensUnity NoelStephensUnity requested a review from a team as a code owner June 3, 2024 16:36
Fixing the fix for a host not sending itself a peer connected message.
Fixing issue with NetworkSceneManager finishing synchronization prior to the server connection timing out.
@NoelStephensUnity NoelStephensUnity enabled auto-merge (squash) June 3, 2024 19:28

peerClientIds[idx] = peerId;
++idx;
if (peerClientIds.Length > idx)
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This assures if the server has not timed out prior to the client synchronizing that it doesn't exceed the allocated peer count.

@NoelStephensUnity NoelStephensUnity merged commit dc021c6 into develop Jun 3, 2024
24 checks passed
@NoelStephensUnity NoelStephensUnity deleted the fix/client-side-disconnect-incorrect-client-count-host-server-side branch June 3, 2024 19:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ConnectedClients.Count hasn't been updated" when OnClientDisconnectCallback is triggered
2 participants