Lua Viruses

From GMod Wiki

This page has been nominated for deletion. Deletion is due within approximately 30 days from nomination, unless the deletion has been disputed on the talk page. See more pages nominated for deletion here. Reason for deletion: Garbage Last Edit was made on 11/16/2011

The tone of this page does not meet Garry's Mod Wiki standards. Please rewrite it using an encyclopedic tone. More pages requiring tone cleanup here. Details: Uses second person, rambling

There has been a flurry of something affectionately named Lua viruses, scripts that seem to take control of Garry’s Mod and not allow or force you to do certain things. Naturally this can be quite worrying. How did it get here? Who did this to me? Most importantly, did it infect something else on my computer?

Luckily, unless you received the ‘virus’ from a bad Lua module, it is impossible for it to have infected other files in your computer. GMOD’s Lua engine does not allow the file I/O functions to write or read outside of the Garry’s Mod folder.

Lua Viruses do not affect anything outside of Garry's Mod, unless it is using Binary Modules. Viruses by definition are files that can infect other files, of which is not the case with any malicious lua script we have seen so far. They will usually only rebind your keys or make you say things and possibly crash your game or the server you are on by spamming. Possible sources of a malicious lua script could be a from a bad server or an addon you downloaded, although the latter is more likely. Most of the time the script is written out of mere boredom or more commonly an attempt to ruin someone’s reputation.

The lazy but completely fool-proof way to completely rid yourself of the malicious script is to completely delete your Garry’s Mod folder, which is generally located at C:\Program Files\Steam\steamapps\username\garrysmod. Delete the entire folder; the next time you start Garry’s Mod a fresh vanilla GMOD will be back in it’s place. (This is because Steam automatically uses files from .GCF files if the folders/files are missing) This can be quite an annoyance however as you may have downloaded many things you do not want to have to download again. An alternative would be to meticulously go through your lua folder in \garrysmod and check to see if there are any suspicious files laying around.

VAC Bans from Lua Modules and Scripts

This has been one of the most concerning issues ever since Lua was brought to Garry’s Mod. Some people say that VAC has been disabled completely, while others believe that even using an innocent Lua C++ module could possibly get you VAC banned. Let’s set the record straight.

Lua scripts and Lua modules will not get you VAC Banned!

This has been said multiple times, and people still haven’t gotten it yet. Some comments straight from Garry Newman himself..

• Is VAC going to be enabled in GMod?

It already is enabled. It has been since GMod launched.

• I’m VAC Banned – Why am I not banned from GMod?

Apparently, VAC bans work on a game by game basis. You’ll only get banned from GMod if you cheat in GMod.

• But what about the music modules and all the other awesome Lua dlls!

VAC is Valve Anti Cheat – not Valve Anti DLL. It bans for Cheats, not DLLs.

Please read this blog post by Garry himself to learn more.

Lua is part of the Garry’s Mod engine. Aimbots, ESPs and other such things in Lua can not and will not be detected by VAC. Lua modules will also not get you VAC banned. However, memory editing and using regular hacks that could be used in other source games WILL get you VAC Banned! So for all those who are disabling ScriptEnforcer through memory hacking, there is a possibility you will be VAC banned.