# TODO
https://github.com/orgs/rust-game-hacks/projects/1/views/1

Ideas:
- Inject into discord
- Hook v8
- WASM: Run loop {} -> Can't block.
- Async?

# Cheat development
## Crates
### overlay

pub struct Frame;

impl Frame {
    pub fn draw_line(&mut self, p1: Vector2, p2: Vector2);
}

- Discord shared memory
- Steam shared memory
- Discord overlayURL
- XBOXGameBar
- DirectComposition
- Kernel GDI
- pass mutable ref to frame to functions that draw

### memory
- mouse (because you are already dealing with the kernel api)
- GetAsyncKeyState
- Getforegroundwindow
- reading / writing memory
- PEB stuff
- something to figure out if the process is still running
- Base Address
- keys (get them)
- processes -> LIst of processes and which one to pick
### injector?
- many ways to inject, but this crate would expose an api like so:

pub fn inject(pid: usize, dll_bytes: &[u8]) -> anyhow::Result<u64> {}

### runner
- runs cheat webasm modules and connects them to the memory crate using cheat-api
- if cheat is internal, use injector crate to inject
- uses cheat-api crate

### driver:
- trait Bypass { fn install() -> Result<(), E>; }
- Private bypasses (charge for that?)
- Rotate bypasses (per game?)
- Hypervisor bypass

### cheat-api
- Connects memlib and overlay
- Crate that contains functions that the cheat needs to interact with the host
- add feature for webasm and feature for internal
- if webasm feature is not enabled then crate uses webasm imports, otherwise calls the functions directly
- This crate would be used to standardize the api between external cheats and crates that interact with the actual system. using this you could make a cheat for a game and either compile it to webasm (using the webasm feature it would translate to webasm export calls) or compile it to native which would directly call the driver functions, or compile it targeting an internal cheat where read_memory etc would simply read the memory inside the process
- Figure out if we want to use traits or #[cfg] blocks or both because we have 3 different impls

pub mod exports {
  pub fn read_meomory(...) {}
  pub fn move_mouse(...) {}
  // either run with unicorn or run natively if internal
  pub fn run_function(address: usize, args: Vec<usize>) -> usize {}
}

### Crate for each cheat

/// This function will run every overlay frame
pub fn run(frame: &mut Frame) {}
pub
- maybe use a workspace with one crate for sdk and another crate for cheat impl

## Cheat Crates:
### https://github.com/rmccrystal/offset-dumper
### math

pub struct Vector3 {}
pub struct Vector2 {}
... etc

- Prediction code
- any pure math code
### cheat-features
pub struct
- some kind of util crate that contains math,
    - for example:

pub trait Player {
fn get_origin(&self) -> Vector3;
fn get_health(&self) -> i32;

pub struct EspConfig;

pub fn esp(camera_pos: Vector3, players: &[impl Player], frame: &mut Frame, config: EspConfig);
pub

    
## Ui
- Dynamic GUI per game -> Define UI Layout (templating engine?)
    - ImGui (internal)
    - Overlay
    - Browser (imgui in browser is possible with webasm)
- Radar: 
    - Browser? Host html on GH Pages with WS
    - Overlay? 

## Repos
- utils (TODO: Change name)
    - memory
    - overlay
    - injector
    - cheat-api (?)
    - runner
- cheat-util
    - math
- repo for each game
- driver
- loader
- research

CI/CD: cargo fmt && cargo clippy
Automatically build: main and push

# Loader stru
- Option A: Github Pages, load WASM directly
- Option B: VPS, login, encrypt wasm (tigress), send and run on client 

## Hosting
- Docker container for host
- GitHub pages?
    - Statically host the encrypted by **hwid** game wasm
    - can someone detail how that would work here

## Loader
- HWID: 
    - cpuid
    - C:/Users/username
    - GetCurrentHwProfile
    - https://www.unknowncheats.me/forum/anti-cheat-bypass/333662-methods-retrieving-unique-identifiers-hwids-pc.html

- Ban people ahead of time? 
    

## Protection
    
- IP: Don't allow customers inside office
- https://github.com/LordNoteworthy/al-khaser
- Custom wasmer runtime
    

# Branding / Marketing

- Referral based
- Same cheat under different names? 
    - prevents us from making a name
-   
- Slot system (certain amount of slots available) vs Invite system (friend has to refer you)
    - I kind of like invite system better 

## Where to sell
- Discord is an option, alot of p2cs use
    - if you get caught discord will shut down your server b/c it breaks the rules
- make a website (probably a better idea)
- fo
## Opsec

- we don't really want to get caught, game companies will sue
- sell under a domain that has no connections to us
- Legality is a grey area
- Tor
- TODO: For later when we are ready to run and sell

## Payment
- Crypto
    - Automate this? Discord bot? 
- stripe (this is a problem for opsec)


# Games to work on

## Fortnite
- Older game, might start dying but it should be pretty easy beacuse it's unreal engnie

## CS:GO
- Super popular although there is already a super big market for cheats
- None of us are really that experienced with HvH features
- Could aim for making a super legit cheat
- Entire source code leaked ~2 years ago: https://github.com/perilouswithadollarsign/cstrike15_src

## Valorant
- Market is pretty small already
- Super hard to make a cheat for, might have to do some testing to see if the stuff we have already bypasses vanguard
- I already know some people who have valorant cheats so it shouldn't be too bad

## Apex
- Super easy to work on as long as you have a bypass
- based on source engine
- we might want to go internal 

## Battlefield 2042
- casper already has a cheat for it

## PUBG
- recently became free to play so large market share

    

- pretty easy to paste from unknowncheats


## R6

I (Matthias) already developed a cheat for that a while ago.

# Roadmap

-