This is for all you fuckers who don't want to use a dll/module to inject your shitty Lua hacks. It's basically a built in exploit to let you run client-side Lua. It uses the Q-menu in sandbox/darkrp to run your own code in the game's Lua state. So you aren't even setting sv_allowcslua to 1.
Installation instructions for the weak:
- Make sure Garry's Mod isn't running
- Download the HTML file
- Overwrite html/saves.html
- Start GMod, join a game, hit the spawn menu and open the "saves" tab
- Check console for confirmation
- yo, corporal_load "scriptname.lua"
Your saves tab will still work as expected, if a patch comes out and it's causing issues then open the file and read the un-installation notes. It most likely wont get patched for a while since the file it uses will most likely need a rewrite to patch the issue, plus updates to Garry's Mod take months (i.e. incrementvar). Also because it's Javascript, you're able look at the source of the file to see how it works.
uses RunString so it's detected by anticheats
nice found though
Code:
concommand.GetTable
^easy way to detect it
Originally Posted by Kona-chan
uses RunString so it's detected by anticheats
nice found though
Code:
concommand.GetTable
^easy way to detect it
How about
Code:
local tab = tab or concommand.GetTable()
concommand.GetTable = function() return tab end
-- Add new concommands below --
concommand.Add("shieeet",function() print("werks!!!11") end)
concommand shieeet wont be in concommand.GetTable as it is tab.
Thats how to bypass dat at least. I am not sure about RunString, gotta take a look in some anti cheats how they handle that. Theres no anticheat which isnt bypassable.
Edit:
The attachment isnt approved yet but why do you think he is using RunString?
Might be include and thats not blacklisted on any anticheat in theory.
nice one
i like ur avatar
and whats the points with this? whats the difference i mean?
bypassing vac and garrysAC?
Originally Posted by articman
nice one
i like ur avatar
and whats the points with this? whats the difference i mean?
bypassing vac and garrysAC?
You don't have to inject a DLL all the time.. But i think servers will be able to easy detect it
Nothing will get you vac/gac banned so don't even worry about that
Originally Posted by kasperbjerby
You don't have to inject a DLL all the time.. But i think servers will be able to easy detect it
Nothing will get you vac/gac banned so don't even worry about that
ye about vac i know for sure
but gac i have no clue even how does it work
/Approved
@DarkShad0w Don't post a video with outside download links.
All attachments must go through the MPGH Attachment System
Links removed from video, may I edit the video back on?
Originally Posted by DarkShad0w
Links removed from video, may I edit the video back on?
Yeah sure, but do not include any outside download links in the video description.
Originally Posted by GameProfi
How about
Code:
local tab = tab or concommand.GetTable()
concommand.GetTable = function() return tab end
-- Add new concommands below --
concommand.Add("shieeet",function() print("werks!!!11") end)
concommand shieeet wont be in concommand.GetTable as it is tab.
Thats how to bypass dat at least. I am not sure about RunString, gotta take a look in some anti cheats how they handle that. Theres no anticheat which isnt bypassable.
Edit:
The attachment isnt approved yet but why do you think he is using RunString?
Might be include and thats not blacklisted on any anticheat in theory.
There's a link in the YouTube video he posted.
If the anticheat loads before that script (which is actually the fact) and if it's proprely done, you won't be able to bypass it with this.
Good shit, corp.
I remember you talking about this a while back, looks sick though.
Originally Posted by Kona-chan
There's a link in the YouTube video he posted.
If the anticheat loads before that script (which is actually the fact) and if it's proprely done, you won't be able to bypass it with this.
right.
would be so awesome if you could store functions in a database or shit so you can call em again, would be no problem then
Nice find..
you should have released it after the update, that way they wouldn't throw in the fix in the dev build
implying they could fix it but honestly i doubt it