aboutsummaryrefslogtreecommitdiff
path: root/azalea-buf
diff options
context:
space:
mode:
authormat <git@matdoes.dev>2025-12-11 20:52:49 -1100
committermat <git@matdoes.dev>2025-12-12 02:53:08 -0500
commit7c3a5768cda78cb9590aac1e1469d36333cd95ac (patch)
treeacecd4f57831e0fff47a8f96a1a30f6edb8825ed /azalea-buf
parentf4a3c53eee7d29bade0c074f402c4a45aa98eca8 (diff)
downloadazalea-drasl-7c3a5768cda78cb9590aac1e1469d36333cd95ac.tar.xz
polish readmes
Diffstat (limited to 'azalea-buf')
-rw-r--r--azalea-buf/README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/azalea-buf/README.md b/azalea-buf/README.md
index 378f3e05..371f0772 100644
--- a/azalea-buf/README.md
+++ b/azalea-buf/README.md
@@ -1,5 +1,5 @@
-# Azalea Buf
+# `azalea-buf`
-An implementation of Minecraft's FriendlyByteBuf. This is used frequently in the game for serialization and deserialization of data.
+An implementation of Minecraft's `FriendlyByteBuf`. This is used frequently in the game for serialization and deserialization of data.
Note that there are some minor implementation differences such as using unsigned integers in places where Minecraft uses signed integers. This doesn't cause issues normally, but does technically make usage of azalea-buf detectable if a server really wants to since it won't error in places where vanilla Minecraft would.