2024-09-21 05:16:35 +02:00
2024-09-21 04:49:43 +02:00
2024-09-21 04:47:22 +02:00
2024-09-21 05:16:35 +02:00

Intro

I used to get pretty hyped when respawn had announced their decision of enabling proton support. My intrinsic motivation has caused me to spend an excessive amount of time working on this project. I am not just publishing this because i feel burnt out. But also because it certainly may be of use for someone out there. I personally haven't seen much public work in this field, especially not anything that goes too much beyond surface level. Writing cheats for anticheat protected games requires you to think creatively. If you proceed at this important step by doing what everyone else does, you are toast without even having entered the battle yet.

Status

My intent is not to influence the cheating situation of a game in a negative way. But because of my experience in this field, i would argue that i can pretty accurately classify various types of information. My project is not making use of any ground breaking technologies, and will not work on latest game build. If a cheater is skilled enough to update this project, then he will be able to make quick work of proton EAC, even without my help.

Components

In terms of complexity, DrauseHook is laid out in a rather simplistic manner. Following components are included:

  • loader: it will act as a bootstrapper and initialize the cheat payload.
  • payload: will be loaded into the game's context, contains actual cheat functionality.
  • backend: will not be shipped in public release, but basically acts as the counterpart that is (normally) required for successful injection.

You do not have to get in panic because of backend not being released, offline mode was a feature already, (easier debugging).

Configuration

It is possible to customize injection to some extent. Currently, there are following options available:

  • Payload Debugging (DEPRECATED) | --debug-payload | reads from a designated memory region within the active payload and outputs diagnostic data for cheat payload in console.
  • Debug Signatures | --debug-sigs |
  • Dump Game Image | --dump-game-image |
  • Analysis From Dump | --analysis-from-dump |
  • Custom Payload Path | --custom-payload-path |
  • Use Unsafe Memory | --use-unsafe-memory |
S
Description
An old internal cheat for when Apex Legends was still supported on the linux/proton platform. (No longer works)
Readme 193 KiB
Languages
C++ 92.1%
C 6.1%
Shell 0.7%
Makefile 0.6%
Assembly 0.5%