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
Is your feature request related to a problem? Please describe.
Currently gm and players have to tell each other if the use webrtc or not. Because you get timeouts if you try to connect to a server with a wrong connection type.
Describe the solution you'd like
When a server starts it should submit a server type field to the registry. The clients will fetch it from there and know if they should use sockets, webrtc or something else to connect to the server. Maybe something like "supported connectiontypes" would be even better as there may be servers that allow multiple types of connections in parallel.
Describe alternatives you've considered
Just keep it as it is and tell each other if webrtc checkbox should be checked.
The text was updated successfully, but these errors were encountered:
It could help if there was a field where the server can put some information that the clients can use to connect like an IP address for the signaling server.
Is your feature request related to a problem? Please describe.
Currently gm and players have to tell each other if the use webrtc or not. Because you get timeouts if you try to connect to a server with a wrong connection type.
Describe the solution you'd like
When a server starts it should submit a server type field to the registry. The clients will fetch it from there and know if they should use sockets, webrtc or something else to connect to the server. Maybe something like "supported connectiontypes" would be even better as there may be servers that allow multiple types of connections in parallel.
Describe alternatives you've considered
Just keep it as it is and tell each other if webrtc checkbox should be checked.
The text was updated successfully, but these errors were encountered: