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
There are six recorded instances of incorrect detections, which were fixed and rescinded:
VAC1: On its initial release, VAC would issue bans for faulty memory. Valve quickly updated VAC to only kick for faulty memory.[19]
VAC1: Running a VAC-protected game through the Cedega software compatibility layer for Linux.[20]
VAC1: An apparent server-side glitch on April 1, 2004.[21]
VAC2: Over two weeks in July 2010, approximately 12,000 owners of Call of Duty: Modern Warfare 2 were banned when Steam updated a DLL file on-disk after it had been loaded into memory by the game. Those affected received a free copy of Left 4 Dead 2 or an extra copy to send as a gift.[22][23][24]
VAC2: In January 2011, owners of Call of Duty: Modern Warfare 2 or Call of Duty: Black Ops were banned due to their computers being infected by the trojan Win32/Spyeye.H.[25]
VAC2: In June 2011, an unknown false positive detection caused a handful of Team Fortress 2 owners to become banned.[26]
There are four recorded instances of game plugins that are not considered cheats triggering bans. These are:
VAC1: HLamp, which allowed the user to control Winamp from the game's interface.[27]
VAC2: The X-Spectate tool, which allowed server administrators to enable a translucent wallhack effect while spectating to help decide if another player was doing the same. Later downgraded to a kick from the server, but bans not rescinded.[28]
VAC2: Some Half-Life modifications, such as Paranoia[29] and Half-Life FX which made changes to the engine's renderer that propagated to multiplayer games. This still triggers a ban and no bans caused by it have been reversed.
VAC and VAC2: sXe Injected, an anti-cheat system for Counter-Strike.
Explain yourself. 2012 is way after the event.
Vacbanned only shows when someone has SEARCHED for that account. That's why it says "First SEEN" and not "Ban date". You could be banned in 2004 and if no-one searched and updated the vacbanned database, it would show 2013 when someone searched for it.