Beetlemod seems to have nailed a decent solution - and I expect that Mani will follow suit shortly. Pity that Valve continues to rely on mod developers for implementing things it is too complacent to undertake itself.
Having slagged Valve one more time, I will now make a suggestion to them: It is reasonable to allow clients to control how client-side settings are manipulated. It is also entirely reasonable that game server hosts be able to establish and enforce "rules of admittance". Valve has addressed the needs of the client-side part of the community - but has neglected the server side. This is really very simple - implement a change - quickly - that allow game admins to establish configurations that insist on the ability to modify certain client settings. Give them the tools to deny or accept players based on the client's choice to allow the changes. The default setting can still be restrictive - as long as the server side solution provides a means to clearly notify the player why his or her connection has been closed. This way, the player is protected and given choice - and the game hoster is able to deliver an enhanced and balanced play experience to those who CHOOSE to join. If the mod developers can nail this solution with hours of this fiasco unfolding then it can't be that difficult. Frazer _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
