- Status
- Offline
- Joined
- Mar 3, 2026
- Messages
- 247
- Reaction score
- 7
Been seeing a lot of chatter lately about bypassing Vanguard without going full DMA. Since I am hanging up the towel on Valorant, I figured I would drop this method. It is a solid 2PC setup that leverages existing drivers to keep things undetected. If you are not into coding your own AI logic, this might be a bit of a climb, but the blueprint is here.
The Setup Logic:
The core idea is utilizing the GeForce Experience gamestream protocol. Unlike Sunshine, Nvidia's driver is already whitelisted by VGK, which keeps your mouse inputs from getting flagged as unauthorized hardware.
The Aimbot Architecture:
For the aimbot, I moved away from local execution. I ran a standard pixel-based color-tracking script on the second PC. Instead of using native win32api or standard mouse drivers on the host (which scream for a ban), I set it up to send coordinates over UDP to the second PC, which then translates them into raw Interception inputs.
Optimization Tips:
To get that crispy 1000hz polling rate, the standard Moonlight build won't cut it. You need to strip down your stream settings. I ran mine at the lowest possible resolution and frame rate—this keeps the overhead on your CPU/GPU low and minimizes the lag between the screen capture and the injection.
Technical Warning:
VGK is no joke. If you try to run this with generic mouse drivers or buggy Sunshine configs, you are going to get flagged. Stick to the Nvidia stack.
Has anyone else played around with modding the Moonlight protocol for lower latency? I am curious if anyone has managed to push the refresh timing further without hitting desync issues. Drop your findings or any tweaks you made to the Interception mapping below.
The Setup Logic:
The core idea is utilizing the GeForce Experience gamestream protocol. Unlike Sunshine, Nvidia's driver is already whitelisted by VGK, which keeps your mouse inputs from getting flagged as unauthorized hardware.
- Client Side Prep: Install GeForce Experience (not the new Nvidia App). Navigate to C:\ProgramData\NVIDIA Corporation\Downloader\ and open gfeupdate.json. Clear the contents, save, and set the file properties to READ-ONLY. This forces the app to stay offline and prevents the mandatory update loop.
- Stream Settings: Inside GFE, head to settings, enable SHIELD, and add a dummy application.
- Second PC Configuration: Use Moonlight to connect to your main rig. Make sure to disable VSync and host audio streaming in the Moonlight settings to keep latency minimal.
- Input Injection: Install Interception on the second PC. Since Valorant doesn't block multi-mouse input if it's coming through a legitimate stream driver, you can inject your movement commands directly here.
The Aimbot Architecture:
For the aimbot, I moved away from local execution. I ran a standard pixel-based color-tracking script on the second PC. Instead of using native win32api or standard mouse drivers on the host (which scream for a ban), I set it up to send coordinates over UDP to the second PC, which then translates them into raw Interception inputs.
Optimization Tips:
To get that crispy 1000hz polling rate, the standard Moonlight build won't cut it. You need to strip down your stream settings. I ran mine at the lowest possible resolution and frame rate—this keeps the overhead on your CPU/GPU low and minimizes the lag between the screen capture and the injection.
Technical Warning:
VGK is no joke. If you try to run this with generic mouse drivers or buggy Sunshine configs, you are going to get flagged. Stick to the Nvidia stack.
Has anyone else played around with modding the Moonlight protocol for lower latency? I am curious if anyone has managed to push the refresh timing further without hitting desync issues. Drop your findings or any tweaks you made to the Interception mapping below.
