You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The FE01 ping although called a "legacy" ping is supported on 1.4.4+ onwards, including 1.5.2, 1.6.4, and the Netty-based (protocol rewrite) Minecraft server versions 1.7.10, 1.8.9, and 1.9 snapshots — nonetheless, there is a new ping using the new Netty-ish protocol, involving some complicated encoding and STATUS handshake with a set_protocol packet.
users can just use node-minecraft-protocol instead, perhaps node-minecraft-ping could use it via node-minecraft-protocol, but this adds another dependency (for clients which will likely already have their own node-minecraft-protocol direct dependency). Not clear if it is worth it, or even worth supporting this so-called modern ping altogether. At least for what I'm interested in (https://github.com/deathcap/node-minecraft-protocol-auto automatic protocol negotiation), FE01 ping does everything I want and more.
The text was updated successfully, but these errors were encountered:
deathcap
changed the title
Send "modern" ping? 1.7+ status handshake ping
Send modern/Netty ping? 1.7+ status handshake ping
Jan 29, 2016
The FE01 ping although called a "legacy" ping is supported on 1.4.4+ onwards, including 1.5.2, 1.6.4, and the Netty-based (protocol rewrite) Minecraft server versions 1.7.10, 1.8.9, and 1.9 snapshots — nonetheless, there is a new ping using the new Netty-ish protocol, involving some complicated encoding and
STATUS
handshake with aset_protocol
packet.Should node-minecraft-ping support this ping? It is already implemented and works well in https://github.com/PrismarineJS/node-minecraft-protocol/blob/master/src/ping.js
users can just use node-minecraft-protocol instead, perhaps node-minecraft-ping could use it via node-minecraft-protocol, but this adds another dependency (for clients which will likely already have their own node-minecraft-protocol direct dependency). Not clear if it is worth it, or even worth supporting this so-called modern ping altogether. At least for what I'm interested in (https://github.com/deathcap/node-minecraft-protocol-auto automatic protocol negotiation), FE01 ping does everything I want and more.
The text was updated successfully, but these errors were encountered: