Looking for collaborators

[barneygale]

I'm looking for a co-maintainer or two. Mojang are releasing more often than when quarry started, and my life is busier. Mostly requires updating packet lists and publishing new versions, though there's sometimes fun datatype changes.

[N0odlez]

Hi, I would love to be a collaborator, I think it would be good to have a snapshot branch and realise with each snapshot out.

[dries007]

I wouldn't mind checking / releasing major versions. I can setup github actions to automate the actual release process too if you lile. With that in place, releasing for snapshots could be nice too, but ATM it feels like too much work (at least for me).

[N0odlez]

Let me get up to speed with the code base and how this works and then I'll have a shot at creating a snapshot branch

[N0odlez]

@barneygale @dries007 Here are my thoughts after having a look through how this all works.

• Replace csv files for json files
• Instead of putting packets in order of their packet id and relying on this, actually specify the packet id properly i.e 0x00 in the json files.

Im sure ill find some more things but that is what stands out at me for the mean time.

JSON file proposal:

{
    minecraft_version: "1.15.2",
    protocol_version: 578,
    packets: {
        clientbound: [
            ...
        ],
        serverbound: [
            ...
        ],
}

With this we could possibly have a 'patching' system so you can override a json file to add or rename packets for snapshots. i.e the latest snapshots change packet ids. The snapshot json would refer to the 1.15.2 json as the base, anything in the snapshot json would simply override the base json.

[wgaylord]

Might be able to ingest protocol defs from https://github.com/PrismarineJS/minecraft-data This could make it easier to maintain.