aboutsummaryrefslogtreecommitdiff
path: root/azalea-protocol
diff options
context:
space:
mode:
authormat <github@matdoes.dev>2022-07-29 15:50:11 -0500
committermat <github@matdoes.dev>2022-07-29 15:50:11 -0500
commit0f380f1a129fbba936605990959f0cf4878c36a8 (patch)
tree67397555ab4c73b878425870260a0ec378f9a562 /azalea-protocol
parentf22a386c78ed6cae638d35888a5376cfa48c1a90 (diff)
downloadazalea-drasl-0f380f1a129fbba936605990959f0cf4878c36a8.tar.xz
grammar issue
Diffstat (limited to 'azalea-protocol')
-rw-r--r--azalea-protocol/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/azalea-protocol/README.md b/azalea-protocol/README.md
index d2ad356e..b4f6660c 100644
--- a/azalea-protocol/README.md
+++ b/azalea-protocol/README.md
@@ -12,7 +12,7 @@ Unfortunately, using azalea-protocol requires Rust nightly because [specializati
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](https://github.com/hube12/DecompilerMC).
-1. First, you'll need the packet id. You can get this from azalea-protocol error messages, or from wiki.vg.
+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`.