I've just done more testing myself on one of my live servers and I'm
more sure this is meant to be a client convar as it's only showing when
the client is setting to 1.
When both client and server are at 0, returned value is generic d/c message.
When client is at 0 and server is at 1, returned value is generic d/c
message.
when client is at 1 and server is at 0, returned value is kick message
as specified by admin.
When client is at 1 and server is at 1, returned value is kick message
as specified by admin.
Keep in mind I'm going off of a server with SourceMod installed, where
the KickClient() function can pass a custom disconnect reason, and I'm
not 100% still, based on the rather vague description of "Show client
disconnect reason" as it's not clear if it's intended for use by a
server operator or client as there's no toggle in the settings menu (or
adv. settings) for it on the client's end.
----
5DE7 65CE F99A B8FB 62A3
6613 A792 D15F DA9E F531
-------- Original Message --------
From: Alex - osyu at pm.me (via hlds list)
[mailto:[email protected]]
Sent: Friday, June 24, 2022, 2:10 PM
To: [email protected], [email protected]
Subject: [hlds] Re: [hlds_announce] Mandatory Team Fortress 2 update
released
On Friday, June 24th, 2022 at 9:01 AM, Weasel [F&M]
<[email protected]> wrote:
So if I can correctly from the discussion so far in this thread, setting
net_disconnect_reason on server side, is basically just for the purpose
of having the reason show up in the server side logs?
Yes, also to show in chat to other players. It was never supposed to be a
client-side var according to its description (and to Joshua's replies in
here), it affecting the client was an oversight.
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/
