Skip to content

fix: Fixing an issue where OnClientDisconnectCallback was not being called when using UTP #1243

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

Merged
merged 8 commits into from
Oct 1, 2021

Conversation

andrews-unity
Copy link
Contributor

@andrews-unity andrews-unity commented Sep 30, 2021

This PR fixes several issues where when using older transports there was assumptions made that OnClientXXX callbacks were called on the client when a client disconnected from a Server/Host and this was not happening when using UTP.

DST-615

Changelog

com.unity.netcode.adapter.utp

  • Fixed: OnClientDisconnecCallback not being sent on the client when calling DisconnectLocalClient
  • Fixed: Shutting down the NetworkManager as a client and then restarting as a server would not allow the first client to connect

Testing and Documentation

  • No tests have been added.

Copy link
Contributor

@JesseOlmer JesseOlmer left a comment

Choose a reason for hiding this comment

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

lgtm

@andrews-unity andrews-unity merged commit d3408ac into develop Oct 1, 2021
@andrews-unity andrews-unity deleted the fix/utp-disconnect-local branch October 1, 2021 21:29
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.

3 participants