We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Explicit disconnects are handled properly but if a connection times out or ambient is simply killed then the player is still seen as connected.
Add an explicit player disconnected callback OR Add handling inside proxied connection and report an error there to let Ambient handle disconnection
The text was updated successfully, but these errors were encountered:
You could have the proxy send a Disconnect frame on behalf of the timed out user
Disconnect
See: https://github.com/AmbientRun/Ambient/blob/f4e68976e77dac06268883acad0bcd82aaf7f493/crates/network/src/proto/mod.rs#L10
Sorry, something went wrong.
Feel free to add more variants to that enum if you need, it will be backwards compatible anyway as long as they are added after the existing variants
I'd prefer proxy to be more transparent and not to rely too much on Ambient protocol.
pierd
No branches or pull requests
Explicit disconnects are handled properly but if a connection times out or ambient is simply killed then the player is still seen as connected.
Add an explicit player disconnected callback
OR
Add handling inside proxied connection and report an error there to let Ambient handle disconnection
The text was updated successfully, but these errors were encountered: