I can confirm this. Some weird is going on.
Before the update, our website status for servers shows player counts
correctly (0/30 and 0/24) but steam browser shows one less while replay
is enabled.
After this latest update, these look ok if no players are in but if
replay is enabled and someone joins server, the server shows 0/30 (or
0/24 on browser with 1 player and 1/31 (or 1/25) on the website. I
coun't test this now with more players but slot count rises +1.
-ics
13.5.2011 5:04, Ross Bemrose kirjoitti:
OK, I'm seeing a lot of weirdness going on with slot counts.
I tested this on a password server I use to test SourceMod plugins
On Steam:
I see 0/25 players when the Replay bot is active.
I see 0/25 players when the SourceTV bot is active.
I see 0/25 players when the Replay AND SourceTV bots are active.
In TF2:
I see 0/24 players when the Replay bot is active
I see 0/24 players when the SourceTV bot is active.
I see 0/23 players when both bots are active.
Now, these numbers tell me some funny interaction with the Steam
browser is going on. It also tells me that there is some funny
interaction going on between the two of them.
Also, does anyone know which kill signal to send the server to make it
properly shut down the replay system? My other admin is, for whatever
reason, sending a kill -9 to the screen process running the server,
which is clearly the wrong way to go about it. Does a normal SIGTERM
kill shut down replays correctly?
On 5/12/2011 8:56 PM, Jeff Sugar wrote:
I am still getting the issue where, in TF2, the *visible* max players
is one
less than what I set it to. Meaning, I set sv_visiblemaxplayers to
24, and
TF2 server browser shows it as 23. This wouldn't be so bad if the STEAM
server browser didn't then show it as what I set it to.
So, if I set it to 25 to account for the issue in TF2 showing one
less, then
the Steam server browser also shows 25. It's a no-win situation.
This long-standing issue is what caused us to avoid running SourceTV. It
mucked up our (reserve) slots in exactly this way.
On Thu, May 12, 2011 at 3:41 PM, Jon
Lippincott<j...@valvesoftware.com>wrote:
You can run with "-replay<config filename>" or just "-replay," which
will
default to "replay.cfg."
-Jon
-----Original Message-----
From: hlds_linux-boun...@list.valvesoftware.com [mailto:
hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Jon Lippincott
Sent: Thursday, May 12, 2011 12:39 PM
To: Half-Life dedicated Linux server mailing list; 'Half-Life dedicated
Win32 server mailing list'
Subject: [hlds_linux] Upate today
After today's update, you can remove +exec replay.cfg from your command
line. Instead, use "-replay" which will:
1. Automatically exec replay.cfg after valve.rc on startup.
2. Fix the max players bug.
-Jon
_______________________________________________
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
_______________________________________________
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
