Ermelious
Ermelious
Alright so I've found that EOSTransport.DisconnectRemoteClient(ulong clientID) is the way to disconnect a client in this SDK not from NetworkManager.DisconnectClient(ulong clientID). I'm not sure why DisconnectClient(ulong clientID) does not work...
> I'm reopening this because the team has concluded that the resolution to this is not entirely complete. I will follow-up with details. Thanks for the update and anticipating a...
Hi @paulhazen, may I check if you have any updates on this issue? How are current users of this plugin disconnecting the clients?
> Hi @Ermelious - I will look into this today and get you some answers - apologies for the delay. Alright thank you. Hoping for a fix on this.
> > > Hi @Ermelious - I will look into this today and get you some answers - apologies for the delay. > > > > > > Alright thank...
> > > > > Hi @Ermelious - I will look into this today and get you some answers - apologies for the delay. > > > > > >...
> > Interesting, but if DisconnectRemoteClient is the expected behavior and to be used instead of DisconnectClient, than we will be going back once again to the requirement to expose...
> Hello, we have tracked this issue, the problem seems to be a bit more complicated than we expected. The team will have a discussion about how we go about...
Hey, is there a workaround for this issue? How are existing users navigating through this breaking issue?
> Ahoy @Ermelious ! I wanted to make sure I was replicating your set up, so I had a question. You outlined really well and clearly where to call `StartHost`...