RE: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released
If you open the Mann Co. Store in-game, there should be a * SALE * tab. -Eric From: hlds@list.valvesoftware.com On Behalf Of Naleksuh Sent: Monday, December 5, 2022 6:19 PM To: hlds Subject: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released The patch notes mention a winter sale, but I do not see one. All items seem to be the normal price. Is this change live yet or am I missing something? On Mon, 05 Dec 2022 17:30:09 -0800 Eric Smith - erics at valvesoftware.com (via hlds list) mailto:hlds@list.valvesoftware.com>> wrote --- We've released a mandatory update for TF2. This is the Smissmas update. The new version number is 7701286. The notes for the update can be found here: https://www.teamfortress.com/post.php?id=166625 Thanks. -Eric ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/
RE: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released
Yes, there was a second update. Apologies for the missing email. Going to send one now. -Eric From: hlds@list.valvesoftware.com On Behalf Of Naleksuh Sent: Monday, September 26, 2022 8:03 PM To: hlds Subject: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released Hey, I noticed a second update was posted on the blog but didn't send around any email for that one. Was that an item schema only update and there was only one game update? (Confused as there has been "fake" updates before like this one<https://www.teamfortress.com/post.php?id=89760>) On Mon, 26 Sep 2022 12:39:03 -0700 Eric Smith - erics at valvesoftware.com (via hlds list) mailto:hlds@list.valvesoftware.com>> wrote --- We've released a mandatory update for TF2. The new version number is 7532489. The notes for the update can be found here: https://www.teamfortress.com/post.php?id=143572 Thanks. -Eric ___ 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/ ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/
RE: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released
I’ve forwarded the information for both of these issues. Thanks. -Eric From: hlds@list.valvesoftware.com On Behalf Of Josh Russell Sent: Friday, July 8, 2022 8:40 AM To: Half-Life dedicated Win32 server mailing list Subject: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released Death Freeze is still happening, too, since the earlier update. On Fri, Jul 8, 2022 at 5:45 AM R. D. D. mailto:supergro...@gmail.com>> wrote: This issue still existed after the previous patch too. 2022-07-08, pn 07:33, Naleksuh mailto:nalek...@naleksuh.com>> rašė: Hi Eric, in a previous update one of the patchnotes stated that you fixed players sometimes being unable to vote for next map-- but I just got this issue. Either this patch put it back or the issue wasn't really fixed. Can you investigate more? ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/
[hlds_linux] RE: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released
We intend to it possible for community server operators to opt into SDR if they want. Hopefully we'll have some more information on that soon. There are no plans to *require* SDR. There's really no upside for us to eliminate ordinary direct UDP access. -Original Message- From: hlds@list.valvesoftware.com On Behalf Of Tohru Adachi Sent: Thursday, October 28, 2021 3:40 PM To: hlds@list.valvesoftware.com Subject: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released From my own findings re. disconnect messages, the client still accepts the buffer from the server on net_disconnect, it just overrides the reason regardless. It's a bit of a hack job considering that there's non-user disconnect behaviour that uses that function (eg srcds quit) to display a different disconnect reason. I'm not sure why there isn't a convar check in there to see if the server is part of the MM pool - I'm fairly sure there's similar checks for some client behaviour such as activating contracts on the client. It is true that most SrcDS games are, to a degree, somewhat dependent on Steam servers eg. master server for server browser, GC/items and so forth. On the flipside, those can be mitigated to an extent by serverside mods and some convar changes, although you could also argue that with virtually all gameserver traffic directed at Valve through the use of Casual MM, it doesn't really matter much either way in regards to the current atmosphere and image of community-run game servers. That's a whole other topic though, so I won't delve into that... - 5DE7 65CE F99A B8FB 62A3 6613 A792 D15F DA9E F531 - Original Message From: sigsegv [mailto:sigs...@sigpipe.info] Sent: Thursday, October 28, 2021, 11:24 PM To: hlds@list.valvesoftware.com Subject: [hlds] Mandatory Team Fortress 2 update released A quick devil’s advocate argument (more of a food for thought thing, than an attempt to push any particular position really): One could perhaps reasonably argue that you’re already reliant on Steam’s servers being up anyway, even as an independent TF2 community server: if the TF2 GC is down, items don’t function properly; and since the scope of items covers not just cosmetics but large swaths of weapons, it has a pretty significantly deleterious impact on gameplay. So—arguably—you’re sorta already in the dependent-on-Steam-servers situation you’re saying you don’t want to be in; and it wouldn’t necessarily be a substantially different situation in the event that all community servers were required to use SDR. (It’s true though that the GC being up, and the SDR servers being up, aren’t exactly equivalent in impact: items not loading is less impactful than possibly being unable to connect to, or stay connected to, a server. And since these servers are distinct from the GC servers, it’s in reality an additional point of failure / degree of freedom that expands the potential outage “shadow” so to speak, rather than lining up perfectly such that there’s no difference.) Anyway… I just figured that was worth bringing up. Of course, all of this is moot if SDR does not in fact end up being mandatory. I believe CS:GO has been quite a bit ahead of TF2 in adopting SDR; so perhaps surveying the community server situation over there (such as it is) might be a useful exercise. (Incidentally: Now I want to look into the server disconnect reason thing more thoroughly. There’s no doubt the chat messages were being abused; but I’m wondering now if maybe there’s a legitimate reason for removing the rest of it too. (Not giving a convar to revert to the old behavior does seem ill-advised; maybe there were also client-side changes which made that infeasible…? Maybe not, dunno.) Anyhow… time to go dumpster diving into publicly available cheat source code and dig thru all the game-disconnect-related crap…) Justin / sigsegv ___ 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/
Re: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released
Thank you very much for taking the time to reply back regarding this - it's very much appreciated. - 5DE7 65CE F99A B8FB 62A3 6613 A792 D15F DA9E F531 Original Message From: Eric Smith - erics at valvesoftware.com (via hlds list) [mailto:hlds@list.valvesoftware.com] Sent: Friday, October 29, 2021, 1:04 AM To: hlds Subject: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released We don’t have the details yet, but we’re going to look into how we can continue supporting them. -Eric ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/
RE: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released
We don’t have the details yet, but we’re going to look into how we can continue supporting them. -Eric From: hlds@list.valvesoftware.com On Behalf Of Naleksuh Sent: Thursday, October 28, 2021 4:23 PM To: hlds Subject: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released Hey, thanks. I'm glad you were listening to the previous thread and are willing to consider bringing them back. Will we as server operators have to do anything different with disconnect reasons in the future? Or will they just start working again like they did before? On Thu, 28 Oct 2021 16:05:42 -0700 Eric Smith - erics at valvesoftware.com (via hlds list) mailto:hlds@list.valvesoftware.com>> wrote We’ve released a mandatory update for TF2. The new version number is 6862056. The notes for the update can be found here: https://www.teamfortress.com/post.php?id=100603 We’ll look into ways we can support the client disconnect reason for one of the coming updates. Thanks. -Eric ___ 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/ ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/
RE: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released
The game treats bots like it would normal players and kicks them for being idle. If you’re running this on your own server, does setting “mp_idledealmethod 0” fix the problem you’re having? The ConVar mp_idlemaxtime sets how long players are allowed to be idle. The default is 3 minutes. -Eric From: hlds@list.valvesoftware.com On Behalf Of Naleksuh Sent: Friday, October 22, 2021 4:52 PM To: hlds Subject: RE: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released 1) Have 1 or more bots on the server 2) Have them not move for 3 minutes (or whatever mp_idlemaxtime is set to) 3) They will be kicked (as long as idle kicking is enabled) Video version available at : https://www.youtube.com/watch?v=kDDc2WSDoYM This seems to only happen with bots created directly in the engine and not through end user commands. This specific case is niche but seems to be part of a wider problem of not recognizing bots. Started with the Sep 16 patch, the same one that caused bots to show avatars before being special cased there with just the avatars. I would appreciate a fix for this issue whether bots being treated as humans in general or a specific exemption for bots being kicked. On Fri, 22 Oct 2021 15:59:31 -0700 Eric Smith - erics at valvesoftware.com (via hlds list) mailto:hlds@list.valvesoftware.com>> wrote If you have step by step instructions on how to reproduce the problem, it will help. Thanks. -Eric From: hlds@list.valvesoftware.com<mailto:hlds@list.valvesoftware.com> mailto:hlds@list.valvesoftware.com>> On Behalf Of Naleksuh Sent: Friday, October 22, 2021 3:49 PM To: hlds mailto:hlds@list.valvesoftware.com>> Subject: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released Hey Eric, ever since the patch on September 16th bots are getting kicked for being idle if they don't move. The cause might be similar to the bug that was causing bots to have avatars. Can a check be made to prevent bots from being kicked for being idle or other stuff like that? ___ 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/ ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/
RE: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released
1) Have 1 or more bots on the server 2) Have them not move for 3 minutes (or whatever mp_idlemaxtime is set to) 3) They will be kicked (as long as idle kicking is enabled) Video version available at : https://www.youtube.com/watch?v=kDDc2WSDoYM This seems to only happen with bots created directly in the engine and not through end user commands. This specific case is niche but seems to be part of a wider problem of not recognizing bots. Started with the Sep 16 patch, the same one that caused bots to show avatars before being special cased there with just the avatars. I would appreciate a fix for this issue whether bots being treated as humans in general or a specific exemption for bots being kicked. On Fri, 22 Oct 2021 15:59:31 -0700 Eric Smith - erics at valvesoftware.com (via hlds list) wrote If you have step by step instructions on how to reproduce the problem, it will help. Thanks. -Eric From: mailto:hlds@list.valvesoftware.com <mailto:hlds@list.valvesoftware.com> On Behalf Of Naleksuh Sent: Friday, October 22, 2021 3:49 PM To: hlds <mailto:hlds@list.valvesoftware.com> Subject: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released Hey Eric, ever since the patch on September 16th bots are getting kicked for being idle if they don't move. The cause might be similar to the bug that was causing bots to have avatars. Can a check be made to prevent bots from being kicked for being idle or other stuff like that? ___ 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/
RE: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released
If you have step by step instructions on how to reproduce the problem, it will help. Thanks. -Eric From: hlds@list.valvesoftware.com On Behalf Of Naleksuh Sent: Friday, October 22, 2021 3:49 PM To: hlds Subject: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released Hey Eric, ever since the patch on September 16th bots are getting kicked for being idle if they don't move. The cause might be similar to the bug that was causing bots to have avatars. Can a check be made to prevent bots from being kicked for being idle or other stuff like that? ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/
RE: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released
We’re looking into it. Thanks. -Eric From: hlds@list.valvesoftware.com On Behalf Of stephanie Sent: Thursday, October 10, 2019 4:04 PM To: Half-Life dedicated Win32 server mailing list Subject: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released Not sure if you folks are aware; there seems to be several reports of random server crashes at the end of both pl_precipice_event_final and koth_slaughter_event. It appears to be related to a round-end event, but I'm not too sure, as I've only seen it happen on Casual servers. https://i.imgur.com/o8kQLKm.jpg On Thu, Oct 10, 2019 at 2:52 PM Eric Smith mailto:er...@valvesoftware.com>> wrote: We've released a mandatory update for TF2. This is the Scream Fortress XI update. The new version number is 5407238. The notes for the update can be found here: http://www.teamfortress.com/post.php?id=54757 Thanks. -Eric ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/ -- stephanie ___ 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/