update dead wiki.vg links (#209)

1 files changed, 2 insertions, 2 deletions

diff --git a/azalea-protocol/README.md b/azalea-protocol/README.md
index e1923c9e..5b1907df 100755
--- a/azalea-protocol/README.md
+++ b/azalea-protocol/README.md
@@ -12,11 +12,11 @@ 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 [the wiki](https://minecraft.wiki/w/Minecraft_Wiki:Projects/wiki.vg_merge).
 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](https://wiki.vg/Protocol) if you're not sure about how a packet is structured, but be aware that wiki.vg uses different names for most things.
+5. Add the fields from Minecraft's source code from either the read or write methods. You can look at [the wiki](https://minecraft.wiki/w/Minecraft_Wiki:Projects/wiki.vg_merge/Protocol) if you're not sure about how a packet is structured, but be aware that the wiki uses different names for most things.
 6. Format the code, submit a pull request, and wait for it to be reviewed.
 
 ### Implementing packets