such as CS:GO, apex, PUBG, etc.

Currently, each game backend includes all the UI elements in a cpp file. It's not so convenient for the developer. So I want to move the UI elements to each service module.

the implementation of interfaces is not standardized and needs to be improved

add more comments about the core code

support remote/internal call, so we can call functions of the game such as trace line

add option for d3dx11 internal and a d3dx11 external overlay.

1. add PID aimer
2. add visible aimer
3. add prediction aimer (considering weapon trajectory)

using the MSVC linker option /SUBSYSTEM:WINDOWS can solve this problem

the pointer type should be consistent with the game, not the compiling architecture

I'm back. Keep writing code.

In some cases, we cannot read or write game memory directly in ring3, so we need to use a driver to do this.

when we use dll injection method, the exception will be difficult to handle

adjust line length

Since the Vec and Mat structs are not well compatible with glm, the original vector and matrix structures are replaced with the vectors and matrices provided by glm.

hook dwm.exe to draw the menu and other things