From 0642eda75ed74bad7b8480202f7de4b00ab301f1 Mon Sep 17 00:00:00 2001
From: Amos <48657826+Mauler125@users.noreply.github.com>
Date: Tue, 18 May 2021 14:15:49 -0700
Subject: [PATCH] Update README.md

---
 README.md | 23 ++++++++++++++---------
 1 file changed, 14 insertions(+), 9 deletions(-)

diff --git a/README.md b/README.md
index 14603d62..5b68d9cf 100644
--- a/README.md
+++ b/README.md
@@ -1,17 +1,22 @@
-# apex
+## Note [Important]
+This is **NOT** a cheat/hack/esp/aimbot or the like, this is a utility to debug earlier version of the game,
+and create offline mods/other cool stuff for the game. Do not attempt to use this on the latest version of
+the game, or on the official servers.
+
+# Apex
 
 APEX Legends / R5 Server Engine research
 
- * detours-based Visual Studio project for hooking the game engine
+ * Detours-based Visual Studio project for hooking the game engine
 
-## r5dev
+## R5Dev
 
-to use the vs project / engine hooking, here are some basic instructions
+To use the vs project / engine hooking, here are some basic instructions:
 
-1. build the solution
+1. Build the solution
 	* or get the binaries from the releases page of this repo
-2. copy `r5dev.dll` and `r5launcher.exe` to the apex game folder
-3. copy the unpacked version of `r5apex.exe` over the original in your game folder
-4. run `r5launcher.exe`
+2. Copy `r5dev.dll` and `r5launcher.exe` to the apex game folder
+3. Copy the unpacked version of `r5apex.exe` over the original in your game folder
+4. Run `r5launcher.exe`
 
-the game will pop a debug terminal, that will forward your commands directly to the in-game source console backend. SQVM prints are also enabled, and the hooks will attempt to load game vscripts out of `platform\` relative from the game executable before falling back to the SearchPath's defined in GameInfo.txt or the in-memory VPK structures.
+The game will pop a debug terminal, that will forward your commands directly to the in-game source console backend. SQVM prints are also enabled, and the hooks will attempt to load game vscripts out of `platform\` relative from the game executable before falling back to the SearchPath's defined in GameInfo.txt or the in-memory VPK structures.