Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
If the game is Vac protected, *every server* is enabled for it. The only time it's not is if you add the -insecure search and use one that other cheaters can play on.
If you got BOTH an Overwatch conviction AND a vac ban, YOU CHEATED no doubt in any way shape or form.
Duh.
Valve will not disclose the exact cheat that was detected, and VAC bans are delayed in application. So it really makes no difference "WHEN" the ban was applied. It was delayed.
Also, Cheat Engine will not cause a VAC ban unless you actually inject into the game to................cheat.
Simply left open and running in the background causes a VAC error instead, not a ban.
https://support.steampowered.com/kb_article.php?ref=2117-ilzv-2837#software
"What typically causes this error?"
There are a number of common software conflicts that can cause this error. If you are running any of the following software, please disable it while playing:
CCleaner
Powershell
Sandboxie
Cheat Engine <----------------------------------------
IObit Start Menu 8
Process Hacker
DLL Injectors
Hypervisors
Steam Idlers
Overwatch is a different system than VAC. Each has zero to do with the other.