Zainstaluj Steam
zaloguj się
|
język
简体中文 (chiński uproszczony)
繁體中文 (chiński tradycyjny)
日本語 (japoński)
한국어 (koreański)
ไทย (tajski)
български (bułgarski)
Čeština (czeski)
Dansk (duński)
Deutsch (niemiecki)
English (angielski)
Español – España (hiszpański)
Español – Latinoamérica (hiszpański latynoamerykański)
Ελληνικά (grecki)
Français (francuski)
Italiano (włoski)
Bahasa Indonesia (indonezyjski)
Magyar (węgierski)
Nederlands (niderlandzki)
Norsk (norweski)
Português (portugalski – Portugalia)
Português – Brasil (portugalski brazylijski)
Română (rumuński)
Русский (rosyjski)
Suomi (fiński)
Svenska (szwedzki)
Türkçe (turecki)
Tiếng Việt (wietnamski)
Українська (ukraiński)
Zgłoś problem z tłumaczeniem
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.