Triggerflow-Client

A Triggerbot for CS2 using memflow.
This is a fork of https://github.com/superyu1337/radarflow2.
Clone the repo on your vm:
git clone https://github.com/lukrei/Triggerflow-Client.git
Go to /src/dma/mod.rs at line 239 and change ip 192.168.50.3 to the ip of your Windows VM. let server_address = "192.168.50.3:1337"; Make sure Windows VM is bridged so in the same Network as the Hypervisor.
change directory into Triggerflow-Client
chmod +x *.sh
Then Update Offset:
./update.sh
Compile it again:
./rebuild.sh
Run CS2 inside the VM
Run the program:
./run.sh
Start Wireshark inside your Windows Client VM and put in the displayfilter udp.port==1337. Now go into the game and put the crosshair onto 4 Teammates then on an Enemy. It should display the packets in Wireshark.
Start to write your own client which accepts the udp packets and trigger shoot via shoot offset of cs2.
For testing purposes if Wireshark prints packets comming from your hypervisor on UDP Port 1337 you can use Powershell Script Triggerflow-Server.ps1 on your Windows VM to test behaviour.
This Powershell script is the "auto-fire" part of the Triggerflow program. Use it at own risk it should work as expected on non vac servers.

But be aware use this dummy Triggerflow-Server.ps1 Script only on VAC Insecured Servers since VAC may not be happy with emuleted things like mouse emulations.

Iam not responsible if you get vac banned by this.

If you want to manually update your game if cs2-dumper provides old files in the git repository then git clone a2x cs2-dumper and run following command on your hypervisor while cs2 is running inside VM.
sudo ./cs2-dumper -c qemu
After that look at update.sh script and copy the generated files from output directory of cs2-dumper to the directory where the files are copied in update.sh script.

Be aware you need a self coded client to receive the udp packets and this can get you vacced because the client relies on the builtin shoot function in cs2. You can find the offsets for shooting via cheat engine. Use it at your own Risk and only on VAC Insecured Servers.