deathcap
deathcap
and/or to https://github.com/PrismarineJS/minecraft-data right? (protocol definition) Plugin channels would also be useful for https://github.com/PrismarineJS/node-minecraft-protocol/issues/114 Forge Support - FML/Forge has several of its own used during handshaking
Another possible use case: - Chunk data: widely differs between protocol releases, would be nice to abstract the `map_chunk` packets away: [mineflayer 1.8](https://github.com/PrismarineJS/mineflayer/blob/7bc78bc7e5d55a6edf1d5fb0af3f272e26f20bff/lib/plugins/blocks.js#L35-L87), [1.7](https://github.com/PrismarineJS/mineflayer/blob/54b5920bed652a1ebbe6e3cd4d2e04ee8740ea1a/lib/plugins/blocks.js#L34-L98), [earlier](https://github.com/PrismarineJS/mineflayer/blob/cc3eae10f622da24c9051268e9fc8ec3fe01ed7e/lib/plugins/blocks.js#L34-L98), [1.8 flying-squid](https://github.com/PrismarineJS/flying-squid/blob/756d3a8d1138fbfae41be546569954244934cff0/src/lib/plugins/world.js#L98-L114), [1.9 minecraft-data](https://github.com/PrismarineJS/minecraft-data/blob/master/data/1.9/protocol.json) (has...
This packet is supported for serialization/deserialization by https://github.com/PrismarineJS/minecraft-data/blob/master/data/1.8/protocol.json#L148: ``` javascript "legacy_server_list_ping": { "id": "0xfe", "fields": [ { "name": "payload", "type": "ubyte" } ] } ``` but nothing currently reads/writes it
Yeah I think needs to be special-cased somehow
Researching the various pings in https://github.com/deathcap/node-minecraft-ping, details in the repo but overall summary of server support: | Minecraft Version | ping_fe01fa | ping_fe01 | ping_fe | Netty status ping(*) |...
Released https://www.npmjs.com/package/minecraft-ping, but it is only for the client-side ping. For server in node-minecraft-protocol, currently gets stuck in the splitter transform. I think we'll need to do something like this:...
The splitter is easy enough to special-case for 0xfe, but not sure how to special-case in the deserializer. Currently, 0xfe 0x01 decodes to varint 254, and 0xfe is an incomplete...
Yeah the `tagHost` client option will allow client plugins to send this BungeeCord proxy information (and perhaps also [Lilypad](https://github.com/GlowstoneMC/Glowstone/issues/569)), but some other change may be needed to let server plugins...
@codeviking @skyhaikuteam browserify now automatically uses `http-browserify` for `http` by default: https://github.com/substack/node-browserify/blob/master/lib/builtins.js ``` exports.http = require.resolve('http-browserify'); ``` the config from the readme is no longer needed (and should probably be...
:-1: for including Minecraft image assets in minecraft-data, not only would bloat the repo unnecessarily but a better solution imho is for graphical clients to support loading arbitrary resource/texture packs...