I have something similar and use sv_visiblemaxplayers as well.

But recently I've been seeing things like 27/24 so it makes me think as
though I'm being penalized because matchmaking puts more players on the
server than it should.

On Fri, Jun 24, 2011 at 4:43 AM, Saint K. <sai...@specialattack.net> wrote:

> Hi,
>
> I am wondering about the same question. We have our servers setup with
> reserved slots, but they are hidden. So essentionally most of the times the
> server is on the correct 24 player limit, although the maxplayers is
> configured as 26 to allow reserved slot owners to join without having to
> kick others out or constantly leave a slot open.
>
> Saint K.
> ________________________________________
> From: hlds_linux-boun...@list.valvesoftware.com [
> hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Ronny Schedel [
> i...@ronny-schedel.de]
> Sent: 24 June 2011 08:53
> To: hlds_linux@list.valvesoftware.com
> Subject: [hlds_linux] Max players penalty
>
> Hello,
>
> we are running a server with maxplayers set to 25, we have 1 reserved slot
> which gets emptied all the time. We have set sv_visiblemaxplayers to 24.
>
> The FAQ says:
> Increasing the max player count above 24 will incur a matchmaking scorking
> penalty, but will not disqualify you from the list.
>
> My question: do you respect the sv_visiblemaxplayers setting or do we get
> a penalty for having one reserved slot?
>
> Best regards
>
> Ronny Schedel
>
>
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> http://list.valvesoftware.com/mailman/listinfo/hlds_linux
>
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> http://list.valvesoftware.com/mailman/listinfo/hlds_linux
>
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux

Reply via email to