These solutions are borderline useless. If someone wants to increase their maxplayers without paying they will find a way. There's plugins that do this on running servers so your aliases won't do anything against that.
In fact you don't even need a plugin to change maxplayers on a running server. Simply do: rcon disconnect rcon maxplayers 64 rcon map cs_office It is a non issue and nothing that Valve should worry about. It's rather something that game hosts and game panel developers should look into. I know TCadmin had a maxplayers monitoring feature years ago, so others should too. If Valve "locks" it, someone will just release a plugin that unlocks it :). 2012/1/3 Andre Müller <[email protected]> > Participants in this list who have no idea should be better not comment on > the issue. > I'm not a provider, so this is not my fucking problem. The autoexec.cfg is > a useful file. People who say to prevent access to the autoexec.cfg doent's > know how the sourceengine works and I think they don't have any customers. > Monitoring is at the moment one solution. Other solution is to add one line > to the top of valve.rc: > > alias "maxplayers" "Forbidden Cvar" > > With some FTP rules you can prevent the access to the valve.rc. Providers > should know how to wrtie this rules. Other way is to prevent access with > chattr +i valve.rc on ext filesystems. There are some other funny things > you can do with simple plugins to override the FTP. So don't think that a > simple trick with chmod and forbidding chmod works. > > I think it is the best way when valve locks -maxplayers > > > 2012/1/3 Eric Riemers <[email protected]> > > > If they change it, just charge more.. put it in that "thing that nobody > > reads when they say agree" ;-) > > > > -----Original Message----- > > From: [email protected] > > [mailto:[email protected]] On Behalf Of Asher > > Baker > > Sent: dinsdag 3 januari 2012 12:41 > > To: Half-Life dedicated Linux server mailing list > > Subject: Re: [hlds_linux] please lock maxplayers > > > > Nope, monitoring and disabling malicious customers is the best solution. > > There are plenty of ways to change maxplayers. > > > > autoexec.cfg has plenty of legitimate uses. > > > > On 3 Jan 2012, at 11:35, Drogen Viech <[email protected]> > wrote: > > > > > I'm a total newbie at linux, but couldn't you have crownjobs running, > > > querying servers and sending e-mails to customer support if customers > > > changed maxplayers to something too high? Just saying, chmodding > > > autoexec.cfg to 444 and disallowing chmod is the better solution of > > > course > > > > > > 2012/1/3 Ulrich Block <[email protected]>: > > >> Also you can move, chmod and edit files with serveplugins. It is not > > >> hard to replace a file with antother using sourcemod. To prevent such > > >> a behavior the user also should not be able to change the chmod. > > >> > > >> Am 03.01.2012 10:00, schrieb Emil Larsson: > > >> > > >>> Yup, you can probably just simple do "chmod 444 autoexec.cfg" and > > >>> it's basically solved. Or "chmod 744 autoexec.cfg" and then change > > >>> ownership with chown to someone that isn't the "customer". > > >>> > > >>> I admit though, autoexec.cfg is a useful configuration to edit so > > >>> it's probably better still to be able to lock the playercount if you > > >>> lease servers. > > >>> > > >>> 2012/1/3 Björn Rohlén<[email protected]> > > >>> > > >>>> ...or just don't let your customers edit autoexec.cfg? > > >>>> > > >>>> 2012/1/3 Andre Müller<[email protected]> > > >>>> > > >>>>> You can change the cvar maxplayers before the game starts. > > >>>>> When you put this two lines in your autoexec.cfg the maxplayers > > >>>>> cvar is overwritten and fixed (tested with css): > > >>>>> > > >>>>> maxplayers 64 > > >>>>> map de_dust > > >>>>> > > >>>>> Maybe Valve can lock maxplayers, when it is set with -maxplyers in > > >>>>> the start command. > > >>>>> _______________________________________________ > > >>>>> To unsubscribe, edit your list preferences, or view the list > > >>>>> archives, please visit: > > >>>>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux > > >>>>> > > >>>> _______________________________________________ > > >>>> To unsubscribe, edit your list preferences, or view the list > > >>>> archives, please visit: > > >>>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux > > >>>> > > >>> _______________________________________________ > > >>> To unsubscribe, edit your list preferences, or view the list > > >>> archives, please visit: > > >>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux > > >>> > > >> > > >> _______________________________________________ > > >> To unsubscribe, edit your list preferences, or view the list > > >> archives, please visit: > > >> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux > > > > > > _______________________________________________ > > > To unsubscribe, edit your list preferences, or view the list archives, > > please visit: > > > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux > > > > _______________________________________________ > > To unsubscribe, edit your list preferences, or view the list archives, > > please visit: > > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux > > > > > > _______________________________________________ > > To unsubscribe, edit your list preferences, or view the list archives, > > please visit: > > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux > > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
