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 Aug 15, 2022. It is now read-only.
Do not send connect messages to clients from server
Actual behavior:
There are connect messages being relayed to the client. This was causing this error: #201 which is resolved.
This bug does not cause any immediate problems and should be able to continue as normal even with this.
Steps to reproduce:
Host a server and 4 clients. Put a breakpoint in the CachedUdpClient on the client machine where it does DoSend when the [0]th byte is 71 and the [1]th byte is 69. Notice that the client will send a confirmation for this message which was causing the previous issue which is now resolved.
[Optional] Discord Username:
Brent#6969
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Version Number and Operating System(s):
Found in commit: ff31f67
Expected behavior:
Do not send connect messages to clients from server
Actual behavior:
There are connect messages being relayed to the client. This was causing this error: #201 which is resolved.
This bug does not cause any immediate problems and should be able to continue as normal even with this.
Steps to reproduce:
Host a server and 4 clients. Put a breakpoint in the CachedUdpClient on the client machine where it does
DoSend
when the[0]th
byte is71
and the[1]th
byte is69
. Notice that the client will send a confirmation for this message which was causing the previous issue which is now resolved.[Optional] Discord Username:
Brent#6969
The text was updated successfully, but these errors were encountered: