HoundDawg wrote:
> 
> Ok, here's another one that we should address.  Apparently, there is a
> growing number of admins that are abusing the client execute features of
> addons in order to rebind player key binds.  Should the addons refuse client
> exec commands that have "bind" in them or should HLDS handle this?  I think
> HLDS would be the best place for this.

I disagree that it should be handled by HLDS. But I agree that
this is an issue needing to be discussed. I have to correct Alfred
in that Admin Mod currently does allow 'bind'. We do block 'alias'
tho, for apparent reasons. 

As GeSpot said 'bind' can be used for valid reasons and to help
clients so simply locking it down isn't the best option. I have
been pondering over this for some time now and am thinking about
something along the following lines.

I would allow to bind the console command to a key to give admins
the possibility to help clients enable the console as GeSpot
explained. I would restrict all other bindings and only allow them
on an opt-in basis. This means that the client can set a setinfo
variable which the addon can read. Only if this variable is set,
will other binds be sent to the client. This way an admin can
enable the console for the client and tell him to set the variable
in order for the client to allow the admin to set further
bindings. This way you keep admins from binding user's keys
without their consent but give them the possibility to help their
clients who are less proficient with the HL console and bind
system.

Also does Admin Mod issue a message upon connect that the server
is set to allow the execution of commands on clients. A much hated
feature by some admins but I hope the clients appreciate it. :)

Florian.


-- 
Want to produce professional emails and Usenet postings?
http://www.netmeister.org/news/learn2quote.html
_______________________________________________
hlds_apps mailing list
[EMAIL PROTECTED]
http://list.valvesoftware.com/mailman/listinfo/hlds_apps

Reply via email to