Master Server etiquette
Master Server etiquette
OK so I've got my master server up and working (after way too long trying to understand UDP sockets in C#). But I've got a bit of a dilemma, it should be reasonably trivial to allow my master to aggregate server information from other masters and add it to my own server list. This would be great for clients as they get a really detailed list of available servers, but it might be seen as a breach of etiquette by other Master server maintainers... what does anyone think of this? Would you be for or against such a feature?
people who run master servers are generally courteous people who would rather strengthen the community than to drive traffic to their personal server.
At least two of the QW master servers do not respond to server heartbeats, purely using other masters for their info.
Either way, each server ought to directly subscribe to at least two masters, to ensure that they're still visible if one of the masters goes down.
At least two of the QW master servers do not respond to server heartbeats, purely using other masters for their info.
Either way, each server ought to directly subscribe to at least two masters, to ensure that they're still visible if one of the masters goes down.