You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 17, 2022. It is now read-only.
Since back in the early betas, the netcode has used the "drop" call for generic, supposedly nice, player quitting. This does not always work and causes hangs when a player quits often. If the NET_PLAYER_LEAVING signal actually got sent/received, these incidents would drop by many magnitudes.
Issue migrated from trac:3897 at 2022-04-16 10:49:46 -0700
The text was updated successfully, but these errors were encountered:
Added a patch (for master) that is functionally identical to the temporary solution used by Legacy. This works because NETshutdown() slams the door properly if you are a client.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
type_bug
| by bendibSince back in the early betas, the netcode has used the "drop" call for generic, supposedly nice, player quitting. This does not always work and causes hangs when a player quits often. If the NET_PLAYER_LEAVING signal actually got sent/received, these incidents would drop by many magnitudes.
Issue migrated from trac:3897 at 2022-04-16 10:49:46 -0700
The text was updated successfully, but these errors were encountered: