Uber-ping/meta-ping: try different or all pings, return what works #4
Description
The default operation of this module should be to, given nothing but a server address, return generally useful information about it. Including if possible the protocol/game version (for nmp-auto).
FE01 therefore is a good default since it supports 1.4.4-1.9, but if it fails, maybe try the FEFD pings or FE00? (GH-2). If it can make a good guess, detecting the failure mode where a Minecraft server is likely listening, but does not understand FE01.
Of course, individual ping types should still be available on their own.
What about the "modern ping" (status handshake state) on 1.8 (and thereabout)? Maybe if FE01 detects a compatible version, it could send another ping, the modern ping, to get more info. Could be useful since the JSON response may include modinfo, Forge mods, for nmp-forge. Or maybe try a handshake status ping first, if can reliably detect when should instead try FE01 ping. Or try both simultaneously.