I made a TF2 plugin to block this back before valve patched it. This
is compiled against the orangebox engine and should work for
garrysmod:

http://www.nephyrin.net/NephCVUH_1.0.zip

It's a plugin that adds the 'ncp' command, which marks the specified
variable as a 'cheat', preventing clients from using it. So install
that plugin as laid out in the readme ( in your case: dll/so in the
orangebox/bin, .vdf in orangebox/garrysmod/addons ), restart your
server or load it directly (plugin_load NephCVUH) and add to your
server.cfg:
ncp sv_benchmark_force_start
(repeat for any other variables to block)
remember to exec server.cfg or reboot after making changes

A better solution might be a simpler garrysmod .lua plugin that hooks
ClientCommands and blocks sv_benchmark_force_start and any other bad
benchmark variables.

- Neph

On Thu, May 8, 2008 at 11:20 AM, P1cwh0r3 <[EMAIL PROTECTED]> wrote:
>
> As the subject says, recently this set of sv_benchmark server cvars have
> been discovered by players and this in itself is causing the servers to
> crash with the error message "This game doesn't support server benchmarks(no
> CServerBenchmarkHook found) when the clients run the command on their
> client. Http://p1c.icannt.org/Engine_error.jpg
> We're using ServerChecker and as the Error box doesn't disappear the server
> doesn't restart. For the love of me I cannot seem to remember if there's a
> way to disable the error box from popping up.
>
> I'm not sure if Garry can really do something about this as I'd assume it'd
> come from the TF2 side of things that updates with Garrysmod.
>
> Any assistance would be much appreciated with this matter.
>
>
>
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives, please 
> visit:
> http://list.valvesoftware.com/mailman/listinfo/hlds
>

_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds

Reply via email to