From 9d4478815d2c6d931b1e212e537c1e238c9cea99 Mon Sep 17 00:00:00 2001
From: Raymond <101374892+raymonable@users.noreply.github.com>
Date: Mon, 30 Jan 2023 21:04:57 -0500
Subject: [PATCH] Create RakNet Removal of Authorization.md
---
.../RakNet Removal of Authorization.md | 20 +++++++++++++++++++
1 file changed, 20 insertions(+)
create mode 100644 docs/Common Issues/RakNet Removal of Authorization.md
diff --git a/docs/Common Issues/RakNet Removal of Authorization.md b/docs/Common Issues/RakNet Removal of Authorization.md
new file mode 100644
index 0000000..0c8415e
--- /dev/null
+++ b/docs/Common Issues/RakNet Removal of Authorization.md
@@ -0,0 +1,20 @@
+# RakNet: Removal of the authorization requirement
+Guide created by Raymond, with lots of help by Yakov
+
+
+
+We're jumping around a function inside of RakPeer.cpp.
+Note that this method is more secure than setting the FFlag, but it *could* cause issues down the line (*client incompatibility, so on*)
+
+Pattern used: `6A016A088D45` (This was created from a 2017L build, it may have been changed in newer builds, but that's unlikely.)
+
+You'll know when it's the correct set of instructions when a few lines above there's a `mov` ending in `5`.
+
+
+
+Instructions to modify, starting from the first `nop` above the `push 1 & push 8`:
+ 1. First `je`, simply change it to `jmp`
+ 2. First `jne`, should be the **same instruction** as the `je` we just changed *(make sure the address to jump is modified too.)*
+ 3. And the first `jne` above the `nop`, of which was mentioned earlier.
+
+Save the patches, and try launching RCC. It should be able to connect without having to authorize your client passwords.