05-05-2015, 12:00 AM
(This post was last modified: 05-05-2015, 12:12 AM by LogicParrot.)
I'm currently maintaining the active server list, and I have to rely on (secret
) network poking to guess if the server is an MCServer or not, these rely on bugs that'll eventually be fixed, when that happens, I'll no longer be able to tell if it's an MCServer or not unless I manually log in and test things. So here are the possible ways to overcome this:
) network poking to guess if the server is an MCServer or not, these rely on bugs that'll eventually be fixed, when that happens, I'll no longer be able to tell if it's an MCServer or not unless I manually log in and test things. So here are the possible ways to overcome this:- Have a simple "non standard" simple, raw tcp procedure which would allow MCServer to be identified. e.g.
The merit of a raw TCP connection is that it allows dumb clients, such as my bash script, to identify MCServer with ease.Code:<tcp stream>
Client: WHO_ARE_YOU
Server: MCServer
<Connection closed by server>
- A server command which only spits "MCSERVER". This would mean that I'll have to find a Linux Minecraft Bot and is kind of inconvenient in comparison to the first one, also, I do not have an authenticated Minecraft account right now, so I won't be able to log in at all to some servers.