[AdamR]

Really? Was this announced?
I'll have to check how that's happened in the engine source.

[ArabicMan]

Originally Posted by YamiKaitou they have blocked all slowhacking

NOT ALL .

[YamiKaitou]

Originally Posted by AdamR Really? Was this announced? I'll have to check how that's happened in the engine source.

Yes, in 2013 when the SteamPipe updates were released

Originally Posted by ArabicMan NOT ALL .

It is a fairly large list of blocked commands. Anything that wasn't blocked isn't really all that important.

[AdamR]

Oh wow, I see the list of filtered commands. Bind is definitely on there with no workaround (other than some custom engine binaries).

If it helps you plug-in devs, here is the current list of banned commands a server can tell a client to execute:

alias bind cl_filterstuffcmd (see below) connect exec (not blocked in TFC) exit kill quit reconnect retry unbind unbindall writecfg _restart _set

The following commands are only banned if the client has CVAR cl_filterstuffcmd set at non-zero:

cd developer ex_interp fps_max mp3volume rate removedemo say sensitivity setinfo speak_enabled sys_ticrate timerefresh voice_enable volume Anything starting with cl_, gl_, m_, r_, and hud_ Any command string containing ASCII characters lower than index 32, higher than index 127, or is a line feed

cl_filterstuffcmd is zero by default so those will pretty much always be banned too.

Might be better if we put in a command called bindslots to fix players missing their number bindings rather than allowing the bind command to be issued remotely again.