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
The defintion as to what consititues a CHEAT in so far as Steam or VAC are concerned is the definition SPECIFICALLY AGREED TO WITH VALVE
It's sufficiently vague enough to cover Valve's arse legally in the event of some oversight (not that videogaming media will let them off the hook so easily).
"Any third-party modifications to a game designed to give one player an advantage over another is classified as a cheat or hack and will trigger a VAC ban."
"VAC"
https://support.steampowered.com/kb_article.php?ref=7849-RADZ-6869
if you get a VAC ban it only affects the game you recived the ban in, with the exception of certain Valve Source and GoldSource games.
"What games can I play if I've been VAC banned?
VAC banned accounts can still play single-player games, local LAN games, and multiplayer on non VAC-secured game servers. To find non VAC-secured servers, from the Steam main menu click on View, select Servers, then select Not secure in the Anti-cheat dropdown.
Cheating in one of the following Source games or a Source mod will result in a VAC ban for all games in the list below:
Counter-Strike: Source
Half-Life 2: Deathmatch
Day of Defeat: Source
Team Fortress 2
Similarly, cheating in one of the following Gold Source games will result in a VAC ban for all games in the list below:
Counter-Strike
Condition Zero
Ricochet
Day of Defeat
Team Fortress Classic
Half-Life: Deathmatch
Deathmatch Classic"
From:
https://support.steampowered.com/kb_article.php?ref=4044-qdhj-5691
http://steamcommunity.com/discussions/forum/9/365172547940857079/
I think a simple rule of thumb is, if you are modifying the game, dont play on VAC secured servers.
There are plenty of games that dont use VAC, and allow modding. No point messing around if there is potential for a VAC ban. If its a competative game, and VAC secured, you should, imo, not mod or alter it at all.
What you write = 1) config files are not allowed to edit on VAC servers and = 2C) You can edit any game files (also VAC games) as long you do NOT CONNECT TO VAC SERVERS. Additionally playing campaign and single player is never a problem, only multiplayer.
=> Correct or not correct?
I never played a game with VAC servers so far.
=>> Is it always *clearly* visible that you would be conncting to a VAC server?
Config files are a little different. Normally you change settings in game (resolution etc) and this is stored in the config file. It really depends on the game what is and is not allowed.
I would suggest looking at the individual games before making changes.
Both correct and not correct :)
Some games, in LAN or "offline" mode are still VAC secured.
CSGO is a good example, if you host a local game, its still VAC secured. You see people post here often with bans they claim they got from playing "offline" or vs AI bots.
There are options to launch the game disabling VAC though, but just because its not played online does not mean its not VAC secured. Of course if you disconnect your internet, there is no VAC, but you might have authentication issues.
Games like COD have two seperate exe files, one for campaing/singleplayer (No VAC involved) and one for multiplayer (VAC secured). But if you play a multiplayer game vs AI bots, its VAC secured.
And again, the best thing is to look at the specific games before doing anything as each game may work different. The best thing is to be careful, and if unsure, assume VAC is involved.
2) With CSGO in particular, since all official servers are VAC secureed and ALL GAME SERVERS (including locally hosted and private lobbys) are VAC -secured by default - the "VAC secured server" shield is not necessarily always visible (I think).
3) You can start your client iwth "-insecure" and the server with "-insecure" to ensure the server is not VAC secured. This is recommended if you're testing modificatons.
4) VAC will ONLY detect "cheats" when connected to a VAC secure server. HOWEVER bear in midn tha teffects and remnants forom such cheats, (i.e. modified files or running processes, registry entries etc.) may remain after exiting. So take care to ensure that any potential trces of possible cheats are removed before you next connect to secure server.
5) Typically, Workshop content downloaded directly via the workshop via Steam should not result in VAC bans.
(( I wish I could offer any guarantees of accuracy on point #5 but I have limited expereince there. Sorry.))
CERTAINLY mods that are downloaded from external locations - i.e. non Worskshop - (even suppsoedly 'reputabl'e sites, should NEVER be trusted.
_____________________________________________________________________
It's very good that you are taking the time and responsibilitty to check these things. It's very difficult since there really are no definitive answers - Valve will not ever state "x is safe" "y is not safe" since of course, these things can change and they (understandably) do not wish to offer anything that might help cheat-developers in learning about how VAC operates.
Of course the big factor is that regardless what is said here, if anything happens and a VAC ban is placed on the account, t is only your responsiblity and nothing can be done, so I appreciate how important this may be - I just wish I could give you more reliable, definite information.
This is not a safe assumption for games in general, you could alter a DLL or EXE file manually, as some cheats do, and get a ban for that.
And as the VAC kb states:
"VAC"
https://support.steampowered.com/kb_article.php?ref=7849-RADZ-6869
I assume this mostly is regarding older games though and also it would depend on WHAT is modified. But if you have file corruption, which is in essense a "modification" its unlikely you will get a ban, based on "designed to give one player an advantage over another" and most likely you would just get a kick if you even get as far as connecting to a VAC secured server.
Most cheats just modify your active memory on the heap and stack, or share it. You obviously shouldn't change an .exe or .dll's assembly... I don't think that's what the OP was planning on doing though
Yeah, this is why I assume its older games/cheats. And without getting into details, injection is pretty easy to detect. You could in theory get a ban/kick for using something like a debugger.
You do get some visual effects that work by using modified DLL files, and even if its not a visual effect that gives an advantage, may still lead to a ban.
But as you say, its unlikely this is OP's intention.