Raax-OG-FN, a universal, internal Fortnite cheat.

If you found this useful, join the Discord and star the project!

Discord Server | Report an Issue

DEVELOPERS READ ME FIRST!

I know the code base for this project is very big, so I've tried to document eveything well in the files, however it still won't be perfect so here are 2 things you NEED to know before you start developing with this source.

Namespaces

There are 3 main namespaces, SDK (you can guess what that is), Actors, Game and Features. Here is the purpose of each:

• SDK: The SDK
• Actors: Cached info's on various actors, as well as the loops for them (AFortPawn, AFortPickup etc)
• Game: Simple functions for drawing menu and ESP, current game frame, screen dimensions etc
• Features: Now I know alot of people clown for using this the nesting can become annoying, but I think it's important for clarity. If you go to Game/Features you will see it simply contains all things like AFortPawn bone IDs, targetting system, exploits (vehicles, pickups etc etc)

Wrappers

I take advantage of wrappers and abstraction alot here, so most of the time like with K2_Project for example, you will not need to get the canvas and call it, there is a wrapper simply called Project in the SDK namespace. I advise you to go to Game/SDK/SDK/Engine_classes.h and look at all the wrappers at the bottom to avoid redundunt code

Overall, just explore the project. There is already tons of code using everything how I intended so you can simply follow that style

Table of Contents

1. About Raax-OG-FN
2. How it works
3. Instructions
4. License

About somethingidk-FN

Out the box, somethingidk-FN comes with some stand out features that make it the perfect base.

• Automatic Offset and VTable updating
• Return address spoofing (don't know who made it)
• Compile time string encryption (skCrypter)
• Windows API function hiding (LazyImporter)

How it works

Depending on the build mode different things are enabled and disabled by default. Release is the safest to use with the least potential traces out of the box.

At Compilation (release)

• Release mode is stripped of all debug info
• A post-build powershell script is run to clear any remaining path strings

On Injection

1. A thread is made using CreateThread (may be a detection vector depending on project), as to not crash by the process being suspended for too long
2. Beep is called so the user knows the DLL was successfully injected
3. GObjects is initalized using one of 2 signatures
4. FName::AppendString...

Instructions

License

Do literally whatever you want. (aside from reuploading the source and claiming it as your own)