[Jheshka]

How would I go about hooking a client's cvar change... To block it from being changed.

[alien]

Hello Jheshka,

you can use alias to block it but this method is far from graceful. Use it only if you really have to.

Using alias:

public client_connect(id) {
  client_cmd(id, "; cl_yawspeed 210; alias cl_yawspeed \"\"");
}

You can also do regular client_cmd(0, "cl_yawspeed 210") using set_task but it's ugly as well. Simply put, there is no nice way of dealing with client cvars.

[Exolent[jNr]]

you can use a cvar checker

[Wilson [29th ID]]

To block cvar changes, use AMX CVAR Guard. It's the most effective way possible.

[alien]

Hmmm ... I have no experience with plugin above but from a brief look at the source code, it does check on client_putinserver and rechecks cvars every 60 seconds (configurable by define). 60 seconds is in my opinion quite a gap ... and setting it to something lower (10 seconds) makes a plugin calling asynchronous query_client_cvar on every player for every cvar in the cvar configuration file every 10 seconds. Whoah. But as I said, there is no nice way of doing this.

Wilson's plugin is using an alias to block them. I would stick with that. At least it's least resource consuming (no looping).

[[X]-RayCat]

http://wiki.amxmodx.org/Scripting_Cvars_%28AMX_Mod_X%29

[Jheshka]

I'm afraid alias is the best method, I need to block the client from changing the CVAR all together.

Thank you though

[Exolent[jNr]]

The only bad thing about the "alias" method is that the client has to restart their game for the cvars to work again, so wouldn't it be a form of slowhacking?

[alien]

It's developer's choice what method to use ...
Alias method is definitily the safest one.

[Jheshka]

Originally Posted by X-olent The only bad thing about the "alias" method is that the client has to restart their game for the cvars to work again, so wouldn't it be a form of slowhacking?

I know, it's sucky...