R5Reloaded/r5sdk
1
0
Fork 0
mirror of https://github.com/Mauler125/r5sdk.git synced 2025-02-09 19:15:03 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Amos 2021-05-18 14:15:49 -07:00 committed by GitHub
parent 6a2850bab0
commit 0642eda75e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 14 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
README.md
View File

@ -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.