Open ghost opened 4 years ago
This issue has a lot of aspects. Implementing the client side is probably the easiest task. But there's more to it, like organizational and user experience questions. It will be important to show users which server is coming from which master. Also, how to handle situations where a server is on more than one server? One might be more strict than the other. I could imagine just showing some "tags" like Bootstrap's "pills" with the master addresses where the servers are listed.
I would like to combine all master related ideas with a larger rewrite of the master protocol client.
This issue has a lot of aspects.
Which is why I used #143 to list related issues. There are probably other lacking, but people are encouraged to add some there.
Also, how to handle situations where a server is on more than one server?
Client-side, the duplicated entries would be merged with current codebase, which is, imo, the sane thing to do. The server should probably indicate which master is it's "main" one, since it's not really possible to programmatically decide which master is the stricter, but this solution opens other issues, too.
Currently the game client can only ask a server update from a single "masterserver". This disallows people hosting a master server with different moderation rules.