https://github.com/stanekondrej/vgctl

A utility to enable/disable the Riot Vanguard anticheat kernel space driver.
https://github.com/stanekondrej/vgctl

anticheat cpp valorant vanguard

Last synced: 10 months ago
JSON representation

A utility to enable/disable the Riot Vanguard anticheat kernel space driver.

• Host: GitHub
• URL: https://github.com/stanekondrej/vgctl
• Owner: stanekondrej
• License: mit
• Created: 2024-08-06T18:35:46.000Z (almost 2 years ago)
• Default Branch: master
• Last Pushed: 2024-08-09T19:37:26.000Z (almost 2 years ago)
• Last Synced: 2024-08-09T23:48:24.840Z (almost 2 years ago)
• Topics: anticheat, cpp, valorant, vanguard
• Language: C++
• Homepage:
• Size: 25.4 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.md

Awesome Lists containing this project

README

          
# vgctl [![Hits](https://hits.seeyoufarm.com/api/count/incr/badge.svg?url=https%3A%2F%2Fgithub.com%2Fstanekondrej%2Fvgctl&count_bg=%232600FF&title_bg=%23000000&icon=&icon_color=%23E7E7E7&title=hits&edge_flat=true)](https://hits.seeyoufarm.com)

vgctl is a utility to enable/disable the Riot Vanguard anticheat kernel space driver.

## Why would you want to do this?

Many have voiced their concerns about an anticheat running in the background at all times, and rightfully

so. Why should it need to? Riot doesn't need to know what I'm doing when I'm not playing VALORANT (not

that they'd need to while I'm playing it).

## Usage

Note: this is subject to change to be more simple and accessible in a future release.  

Open a command prompt/Powershell prompt **as administrator.** Then, navigate to the directory with

the executable, and run it with one of the flags:

- `-e`: enable Riot Vanguard (self-explanatory)

- `-d`: disable Riot Vanguard (also kills the process)

- ~~`-k`: kill Riot Vanguard (only kills the process, Vanguard will start on next boot)~~ this has

not been implemented yet.

## Getting vgctl

You can get the binary a few different ways. The following ways are ordered from most stable 

to least stable:

- Download the binary from GitHub releases 

- Download an artifact from GitHub actions 

- Build from source (see [Building](#building))

Building from source is similar to downloading the artifact from Actions, except the build has 

the possibility to fail if the Action has failed as well.

## Building

You can build just like you would regularly using CMake. Then, either execute vgctl directly,

or add it to your PATH. Don't bother trying to build this on something other than Windows, because

vgctl needs the Windows APIs to build, and obviously to function.

## Goals

These are some of the future goals I want to achieve in this project:

- [ ] Implement the Vanguard kill functionality

- [x] Write CI/CD things (e.g. GH actions, tests...)

- [x] Make vgctl open its own console window

- [x] Make vgctl ask for elevated privileges