-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does VAC detect this? #45
Comments
I have not known VAC to ever ban for opening a handle to a process or for simply just reading game memory, but this could change at any time and may have already changed since I was last familiar with playing around with games that use VAC. You are probably safe, but just be careful and use alternative accounts where possible. Edit: you can also write process memory to be honest and VAC doesn't care, but this is more risky. |
Okay thanks! If I happen to get banned I will let you know, I'm sure users would be curious. If I don't report back, assume I didn't get banned haha. |
For future googlers because I'm sure this question will rise a lot... VAC is mostly just a signature scanner. Simply reading/writing memory and opening handles will not get you banned. You only run into problems when you copy code from sources found online that VAC has generated a signature for. A prime example is the blackbox code for generating angles for aimbot in CSGO that has been shared around online for several years. |
I'm not sure where else to ask this, but if I were to use this to READ (but NOT write) memory of a Steam online multiplayer game, would I get banned? Can VAC "know" if I'm reading a game's memory?
I am not cheating by the way.
The text was updated successfully, but these errors were encountered: