pp_PixelRender

[Mr. Gash]

With cheaters being a big issue in Garry's Mod, a lot of them are attracted to TTT servers. If they don't buy a cheat, they resort to making one or finding out methods to cheat. The "pp_PixelRender" is a post-processing command that isn't meant for cheating, but can be used for such, and is in GMod by default (When the GMod 13 update is released, this will be removed). I've noticed most TTT servers don't disable this, and I'm posting this thread just to help those who care to fix it.

To disable this command, navigate to (root)/lua/postprocess/pixelrender.lua and edit the file. On/Near line 224 you should see this:

local function OpenWindow()

    if ( ValidPanel( PixelRenderWindow ) ) then
        PixelRenderWindow:Remove()
    end
    
    PixelRenderWindow = vgui.CreateFromTable( pnlPixelRender )
    PixelRenderWindow:InvalidateLayout( true )
    PixelRenderWindow:MakePopup()
    PixelRenderWindow:AlignBottom( 50 )
    PixelRenderWindow:CenterHorizontal()
    PixelRenderWindow:SetKeyboardInputEnabled( true )
    PixelRenderWindow.CodeEdit:SetCode( "// Read the pixel at x, y \
local r, g, b = render.ReadPixel( x, y )\
\
// Draw the exact pixel back to the screen - with twice as much red!\
surface.SetDrawColor( r*2, g, b, 255 )\
surface.DrawRect( x, y, 1, 1 )\
" )

end

concommand.Add( "pp_PixelRender", OpenWindow )

From this point on you can either remove it, or replace it with something else.

[BipolarDiZ]

Yeah, I was just recently informed of this. We now block the command and log it so admins can see who tried to do it! Really nice of you to spread the word! :D

[Handy_man]

This was a known thing on ECG for the longest time, in fact im pretty sure we still have an automatic ban on this command as there is no reason for anyone to use it in TTT, also this is a useful tool for testing scripts and various things on the fly just saying.

[Cush]

This was a known thing on ECG for the longest time, in fact im pretty sure we still have an automatic ban on this command as there is no reason for anyone to use it in TTT, also this is a useful tool for testing scripts and various things on the fly just saying.

What if someone does it purely to see if it is on the server so they can warn the owners?

I just do

SendLua('concommand.Remove("pp_PixelRender")')

in some other code that gets sent to the client.

[Emo Panda]

If they don't buy a cheat, they resort to making one or finding out methods to cheat.

People actually pay for scripts?

[Handy_man]

What if someone does it purely to see if it is on the server so they can warn the owners?

I just do

SendLua('concommand.Remove("pp_PixelRender")')

in some other code that gets sent to the client.

Well unban requests for these reasons can be made, but why would they bother? lol players are players they should not try and "warn us" against an exploit/ hack by trying it warning has better methods.

[Cush]

Well unban requests for these reasons can be made, but why would they bother? lol players are players they should not try and "warn us" against an exploit/ hack by trying it warning has better methods.

They dont need to do anything with it, just see that its enabled. I'm just saying it seems silly to ban people just for typing the command, they could just be seeing if it is enabled.

Funnily enough I found out about this ages ago when some guy came on my server and tried it, then told me.

[Shifty Pete]

Thanks.

[Shifty Pete]

Knocked up my own replacement for it:

function Cheater(ply, roletext)
	PrintMessage(HUD_PRINTTALK, Format("\nCheaters never win. " .. ply:Nick() .. " loses.\n", roletext))
	ply:ConCommand("+left")
	ply:ConCommand("+forward")
	ply:ConCommand("+jump")
	ply:ConCommand("+duck")
	ply:ConCommand("+attack")
	ply:ConCommand("+attack2")
end

concommand.Add( "pp_PixelRender", Cheater )

Have fun.

[Anonymous]

Knocked up my own replacement for it:

function Cheater(ply, roletext)
	PrintMessage(HUD_PRINTTALK, Format("\nCheaters never win. " .. ply:Nick() .. " loses.\n", roletext))
	ply:ConCommand("+left")
	ply:ConCommand("+forward")
	ply:ConCommand("+jump")
	ply:ConCommand("+duck")
	ply:ConCommand("+attack")
	ply:ConCommand("+attack2")
end

concommand.Add( "pp_PixelRender", Cheater )

Have fun.

Wouldn't

function Cheater(ply, roletext)
	PrintMessageAll(HUD_PRINTTALK, Format("\nCheaters never win. " .. ply:Nick() .. " loses.\n", roletext))
	ply:ConCommand("+left")
	ply:ConCommand("+forward")
	ply:ConCommand("+jump")
	ply:ConCommand("+duck")
	ply:ConCommand("+attack")
	ply:ConCommand("+attack2")
end

Meh,

[Tommynator]

What?

[Handy_man]

It would in theory as the player tries to use pp_pixelrender in game print to the server that they are attempting to cheat and then make them constantly go left, forward, jump, crouch attack1 and attack2.

Meh i would stick with banning or kicking these people automatically on this command but any "anti-cheat" (use the term loosely) will do fine and can generally be more entertaining.

[Anonymous]

ply:Kick('Go Fuck something')

[SovietX]

useful, I'm sure alot of people have already learned about this thou.

[Mr. Gash]

useful, I'm sure alot of people have already learned about this thou.

Thread didn't need to be bumped.