Multiplayer Matching, Server Browser
Posted: Fri Dec 18, 2015 5:40 pm
OK I'm really looking forward to test your Server Browser.
But since it is still in development I want to take the opportunity to make some wishes about it.
One major concern for me is the display speed and I thought a lot about which informations should take priority.
(Take SE for example. The Server Browser is functional but really really bad, it takes ages and refreshes every freaking time you do something)
So I came to the conclusion that the first thing I want to know is the Server and Map name next to that is the Player count and very important is: is it dedicated or local?
(A flag like [D] [L] is sufficient. A bonus would be a PW indicator : -)
Those are the information the matchmaking Server should cache (besides the IP obviously) pack and send as one "file" entirely to the client.
(game server should send a "vCard" containing all vital information to the matchmaking server but only once a minute)
This allows an almost instant serverlist where you can browse to your hearts content without wasting minutes of emptiness.
After you click on one entry in the list the client pings it and gets fresh additional information like:
(Alternatively you could send the whole DB it depends what's more valuable to you server CPU or bandwidth)
On the subject of filters please include a search option for all fields.
It would also be nice to tell the game server to send "vCards" and the client "list requests" to additional community matchmaking servers.
This has two major advantages:
First: this enables the community to make specialized matchmaking servers (i.e. total conversion mods)
Second: easy backups if your service at Wube Software is unavailable or discontinued <- hopefully this is in the far far future
This is my input on this topic and I'm curious about your viewpoints be it Wube Staff or community
But since it is still in development I want to take the opportunity to make some wishes about it.
One major concern for me is the display speed and I thought a lot about which informations should take priority.
(Take SE for example. The Server Browser is functional but really really bad, it takes ages and refreshes every freaking time you do something)
So I came to the conclusion that the first thing I want to know is the Server and Map name next to that is the Player count and very important is: is it dedicated or local?
(A flag like [D] [L] is sufficient. A bonus would be a PW indicator : -)
Those are the information the matchmaking Server should cache (besides the IP obviously) pack and send as one "file" entirely to the client.
(game server should send a "vCard" containing all vital information to the matchmaking server but only once a minute)
This allows an almost instant serverlist where you can browse to your hearts content without wasting minutes of emptiness.
After you click on one entry in the list the client pings it and gets fresh additional information like:
- Adv. Player Info
- Server Description
- Ping
- Mods
- Game Mode / Scenario type (for certain types like PvP a game lobby would be necessary, so next TODO pls)
- Tags
(Alternatively you could send the whole DB it depends what's more valuable to you server CPU or bandwidth)
On the subject of filters please include a search option for all fields.
It would also be nice to tell the game server to send "vCards" and the client "list requests" to additional community matchmaking servers.
This has two major advantages:
First: this enables the community to make specialized matchmaking servers (i.e. total conversion mods)
Second: easy backups if your service at Wube Software is unavailable or discontinued <- hopefully this is in the far far future
This is my input on this topic and I'm curious about your viewpoints be it Wube Staff or community