Actually it's just "FE", for 1.3: http://wiki.vg/index.php?title=Protocol&oldid=933#Server_List_Ping_.280xFE.29 1.3.1 protocol - https://gist.github.com/barneygale/1235274

    //Send 0xFE: Server list ping
    fwrite($fp, "\xFE");

    //Read as much data as we can (max packet size: 241 bytes)
    $d = fread($fp, 256);

sending this works on 1.2.5, getting back:

�A Minecraft Server�0�20

FE01 also works, but the full FE01FA... I'm sending for 1.6:

    socket.write(new Buffer('fe01'+
        'fa'+ // plugin message
        '000b'+'004D0043007C00500069006E00670048006F00730074'+ // MC|PingHost,
        '0007'+ // 7+len(hostname)
        '4a'+   // protocol version (74, last)
        '0000'+''+ // hostname TODO
        '00000000' // port TODO
        ,'hex'));

trips up 1.3.2 and earlier. 19712 is 4d00 hex, so it looks like it is falling over on the MC|PingHost varint length (no varints in 1.3.2).

Could remove everything after fe01 and just send those two bytes — this works with 1.2.5 (at least, probably earlier — would test, but requires more manual installation steps, ref PrismarineJS/node-minecraft-wrap#9), 1.3.2, 1.4.4, 1.5.2, ...., 1.7.10, 1.8.9, 1.9. It partially works on 1.6.4, but since 1.6.4 expects the full MC|PingHost, it takes a while (about 2 seconds) to (presumably) timeout read, and return a response. Probably not worth giving up performant 1.6.4 pings to support ≤1.3.2.

Next question: can 1.3.2-failed FE01 MC|PingHost pings be reliably detected, allowing a reasonable fallback to FE ping?

Support pinging 1.3 and earlier servers (FE ping) #2

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions