5 releases (breaking)

Uses new Rust 2021

0.5.0 Dec 9, 2022
0.4.0 Nov 19, 2022
0.3.0 Oct 30, 2022
0.2.0 Oct 17, 2022
0.1.0 Sep 5, 2022

#641 in Network programming

Download history 38/week @ 2022-10-14 21/week @ 2022-10-21 54/week @ 2022-10-28 40/week @ 2022-11-04 16/week @ 2022-11-11 59/week @ 2022-11-18 18/week @ 2022-11-25 21/week @ 2022-12-02 64/week @ 2022-12-09 14/week @ 2022-12-16 18/week @ 2022-12-23 18/week @ 2022-12-30 14/week @ 2023-01-06 16/week @ 2023-01-13 18/week @ 2023-01-20

70 downloads per month
Used in 2 crates

MIT license

1MB
31K SLoC

Azalea Protocol

A low-level crate to send and receive Minecraft packets. You should probably use azalea or azalea-client instead.

The goal is to only support the latest Minecraft version in order to ease development.

This is not yet complete, search for TODO in the code for things that need to be done.

Unfortunately, using azalea-protocol requires Rust nightly because specialization is not stable yet. Use rustup default nightly to enable it.

Adding a new packet

Adding new packets is usually pretty easy, but you'll want to have Minecraft's decompiled source code which you can obtain with tools such as DecompilerMC.

  1. First, you'll need the packet id. You can get this from azalea-protocol error messages or from wiki.vg.
  2. Run python codegen/newpacket.py [packet id] [clientbound or serverbound] \[game/handshake/login/status\]\
  3. Go to the directory where it told you the packet was generated. If there's no comments, you're done. Otherwise, keep going.
  4. Find the packet in Minecraft's source code. Minecraft's packets are in the net/minecraft/network/protocol/<state> directory. The state for your packet is usually game.
  5. Add the fields from Minecraft's source code from either the read or write methods. You can look at wiki.vg if you're not sure about how a packet is structured, but be aware that wiki.vg uses different names for most things.
  6. Format the code, submit a pull request, and wait for it to be reviewed.

Implementing packets

You can manually implement reading and writing functionality for a packet by implementing McBufReadable and McBufWritable, but you can also have this automatically generated for a struct or enum by deriving McBuf.

Look at other packets as an example.

Dependencies

~12–20MB
~391K SLoC