-
Notifications
You must be signed in to change notification settings - Fork 101
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
Issue connecting from WinQuake #34
Comments
From WinQuake via Steam I get No Response. |
Please look at the network traffic first to see if packets even arrive. |
May be some change in Node.js itself, I don't know, but it also fails for me now :( |
Got a PR for it - Node no longer allows mutating Arraybuffers directly (you never were supposed to anyway) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just tried hosting this on my local server and it works great. Server runs great and so does the client.
I've also read here that the server accepts connections from WinQuake and GLQuake. So, I fired up WinQuake and tried connecting. It fails 5 seconds in with only a "client to server keepalive" message. Looking at the server-console, it displays the message
SV.ReadClientMessage: unknown command char
and proceeds to remove the player.I don't know if this is an issue with the server or my setup!
The text was updated successfully, but these errors were encountered: