Re: [hlds] Mandatory Team Fortress 2 update released

2023-10-14 Thread Mahmoud Khalfallah
Hello
Anybody noticed that the teleporting spell doen't select.
Also bloodwater secondary objectives don't work.
Sinshine pumpkin bombs don't respawn.

On Sat, Oct 14, 2023, 00:10 Eric Smith - erics at valvesoftware.com (via
hlds list)  wrote:

> We've released a mandatory update for TF2. The new version number is
> 8416259. The notes for the update are here:
>
> https://www.teamfortress.com/post.php?id=210711
>
> 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/

Re: [hlds] Mandatory Team Fortress 2 update released

2023-10-09 Thread Josh Russell
The game didn't indicate that a restart was needed because an update
released.  Queuing would just stop.

On Mon, Oct 9, 2023 at 8:33 PM Eric Smith - erics at valvesoftware.com (via
hlds list)  wrote:

> We've released a mandatory update for TF2. The new version number is
> 8405242. The notes for the update are below.
>
> Thanks.
>
> -Eric
>
>
> --
>
> - Updated the Constructor's Cover to fix an issue with the materials
> - Updated zi_woods to fix missing Zombie Infection assets
> - Updated cp_degrootkeep_rats to fix an issue with the xylophone triggers
>
> ___
> 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

2022-12-05 Thread via hlds list
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: [hlds] Mandatory Team Fortress 2 update released

2022-12-05 Thread Naleksuh
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)  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/
___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

Re: [hlds] Mandatory Team Fortress 2 update released

2022-10-07 Thread Tohru Adachi
It's being discussed on the hlds_linux mailing list, Eric and co. are 
aware and are investigating.

  
5DE7 65CE F99A B8FB 62A3
6613 A792 D15F DA9E F531


 Original Message 
From: Jason Contreras [mailto:jasonl.contre...@gmail.com]
Sent: Saturday, October 8, 2022 at 2:06 AM
To: hlds@list.valvesoftware.com
Subject: [hlds] Mandatory Team Fortress 2 update released


Something fishy with this update. Stuck at 43MB. Confirmed for others as
well

On Fri, Oct 7, 2022 at 19:34 Eric Smith - erics at valvesoftware.com
<http://valvesoftware.com> (via hlds list) mailto:hlds@list.valvesoftware.com>> wrote:

We've released a mandatory update for TF2. The new version number is
7570091. The notes for the update can be found here:

https://www.teamfortress.com/post.php?id=144159
<https://www.teamfortress.com/post.php?id=144159>

Thanks.

-Eric

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/ <https://list.valvesoftware.com/>

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com <https://list.valvesoftware.com>/


___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

Re: [hlds] Mandatory Team Fortress 2 update released

2022-10-07 Thread Jason Contreras
Something fishy with this update. Stuck at 43MB. Confirmed for others as
well

On Fri, Oct 7, 2022 at 19:34 Eric Smith - erics at valvesoftware.com (via
hlds list)  wrote:

> We've released a mandatory update for TF2. The new version number is
> 7570091. The notes for the update can be found here:
>
> https://www.teamfortress.com/post.php?id=144159
>
> 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/

Re: [hlds] Mandatory Team Fortress 2 update released

2022-09-28 Thread Kami
Did you forget to continue the phrase?

Sent via t.me/gmailbot

2022-09-28 23:12 (GMT+00:00), "Eric Smith - erics at valvesoftware.com
(via hlds list)"  said:
> We've released a mandatory update for TF2. The new version number is 7542465.
> The notes for the update are below.
> Thanks.
> -Eric
> 
> - Reverted the +quickswitch bug fix while we evaluate
> ___
> 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

2022-09-26 Thread via hlds list
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: [hlds] Mandatory Team Fortress 2 update released

2022-09-26 Thread Naleksuh
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 
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)  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/

RE: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released

2022-07-08 Thread via hlds list
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/

Re: [hlds] Mandatory Team Fortress 2 update released

2022-07-08 Thread Josh Russell
Death Freeze is still happening, too, since the earlier update.

On Fri, Jul 8, 2022 at 5:45 AM R. D. D.  wrote:

> This issue still existed after the previous patch too.
>
> 2022-07-08, pn 07:33, Naleksuh  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?
>>
>>
>>
>>  On Thu, 07 Jul 2022 15:51:45 -0700 *Eric Smith - erics at
>> valvesoftware.com  (via hlds list)
>> >* wrote ---
>>
>> We've released a mandatory update for TF2. The new version number is
>> 7367266. The notes for the update can be found here:
>>
>> https://www.teamfortress.com/post.php?id=140004
>>
>> 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/
>
___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

Re: [hlds] Mandatory Team Fortress 2 update released

2022-07-08 Thread R. D. D.
This issue still existed after the previous patch too.

2022-07-08, pn 07:33, Naleksuh  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?
>
>
>
>  On Thu, 07 Jul 2022 15:51:45 -0700 *Eric Smith - erics at
> valvesoftware.com  (via hlds list)
> >* wrote ---
>
> We've released a mandatory update for TF2. The new version number is
> 7367266. The notes for the update can be found here:
>
> https://www.teamfortress.com/post.php?id=140004
>
> 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: [hlds] Mandatory Team Fortress 2 update released

2022-07-07 Thread Naleksuh
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?







 On Thu, 07 Jul 2022 15:51:45 -0700 Eric Smith - erics at valvesoftware.com 
(via hlds list)  wrote ---



We've released a mandatory update for TF2. The new version number is 7367266. 
The notes for the update can be found here: 
 
 https://www.teamfortress.com/post.php?id=140004 
 
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/

Re: [hlds] Mandatory Team Fortress 2 update released

2022-06-24 Thread Joshua Ashton




On 6/24/22 12:54, Tohru Adachi wrote:
It doesn't seem like it. The disconnect buffer being sent from server -> 
client was read then dropped/overridden on the client's end prior to 
this update. I was under the impression that this was a 
client-controlled var due to how the original update that changed this 
functionality was implemented.


I'd have expected this to be prefixed with sv_ if it were a 
server-controlled variable or a more verbal description appended to the 
convar, so it did throw me a bit.


Oh I agree, but given server hosts have probably set it already, would 
be kinda :/ to change it at this point.




(nice domain by the way, frogs are cool)


They are ribbiting! I like the .tf too :-)

- Joshie ✨



  -
5DE7 65CE F99A B8FB 62A3
6613 A792 D15F DA9E F531


 Original Message 
From: Joshua Ashton [mailto:jos...@froggi.es]
Sent: Friday, June 24, 2022, 1:45 PM
To: hlds@list.valvesoftware.com
Subject: [hlds] Mandatory Team Fortress 2 update released



On 6/24/22 12:41, Tohru Adachi wrote:
I was under the impression that the default value of 0 was to preserve
the behaviour from a previous update.

My previous question still stands, shouldn't this be a replicated var?
Valve servers keep it at 0 and retain the behaviour up to now,
community server ops can set it to 1 at their discretion and can have
kicks/bans/disconnects working as originally intended.

Replicated vars wouldn't work for this because a server could have this
set and reject a client well before replicating vars across and the
message would not get through.

The correct solution is to just have it do nothing on the client, which
is the intention all along.

- Joshie ✨


   -
5DE7 65CE F99A B8FB 62A3
6613 A792 D15F DA9E F531


 Original Message 
From: Joshua Ashton [mailto:jos...@froggi.es]
Sent: Friday, June 24, 2022, 1:22 PM
To: Alex; hlds@list.valvesoftware.com
Subject: [hlds] Mandatory Team Fortress 2 update released



On 6/24/22 12:13, Alex wrote:
On Friday, June 24th, 2022 at 6:05 AM, Joshua Ashton
 wrote:
The client does nothing with net_disconnect_reason.
It's an entirely server-sided convar.

A hah, I see. When I was attempting to repro, I was testing a client
sending it's disconnect message to a server, not a server forcefully
disconnecting a client and sending a disconnect message (which uses the
same message).

What ended up being fixed in the changelog was a different bug where
disconnect messages would sometimes not show in text chat due to a race
between player entity destruction and the player_disconnected event.

At least this misunderstanding led to fixing two bugs! :-)

This will be fixed in the next update, thanks!

- Joshie ✨


It looks like the ConVar is used in engine code which affects how both
the
client and server process all disconnect messages. When set to 0 on a
client,
it will always override the disconnect reason with "Client Disconnect"
on the
client's end, which is unintended behavior (it's also what was happening
before this ConVar existed).

Video demonstration of this:
https://www.youtube.com/watch?v=BiacrieODC8

Alex K.

___
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/

___
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: [hlds] Mandatory Team Fortress 2 update released

2022-06-24 Thread Tohru Adachi
It doesn't seem like it. The disconnect buffer being sent from server -> 
client was read then dropped/overridden on the client's end prior to 
this update. I was under the impression that this was a 
client-controlled var due to how the original update that changed this 
functionality was implemented.


I'd have expected this to be prefixed with sv_ if it were a 
server-controlled variable or a more verbal description appended to the 
convar, so it did throw me a bit.


(nice domain by the way, frogs are cool)

 -
5DE7 65CE F99A B8FB 62A3
6613 A792 D15F DA9E F531


 Original Message 
From: Joshua Ashton [mailto:jos...@froggi.es]
Sent: Friday, June 24, 2022, 1:45 PM
To: hlds@list.valvesoftware.com
Subject: [hlds] Mandatory Team Fortress 2 update released



On 6/24/22 12:41, Tohru Adachi wrote:
I was under the impression that the default value of 0 was to preserve
the behaviour from a previous update.

My previous question still stands, shouldn't this be a replicated var?
Valve servers keep it at 0 and retain the behaviour up to now,
community server ops can set it to 1 at their discretion and can have
kicks/bans/disconnects working as originally intended.

Replicated vars wouldn't work for this because a server could have this
set and reject a client well before replicating vars across and the
message would not get through.

The correct solution is to just have it do nothing on the client, which
is the intention all along.

- Joshie ✨


  -
5DE7 65CE F99A B8FB 62A3
6613 A792 D15F DA9E F531


 Original Message 
From: Joshua Ashton [mailto:jos...@froggi.es]
Sent: Friday, June 24, 2022, 1:22 PM
To: Alex; hlds@list.valvesoftware.com
Subject: [hlds] Mandatory Team Fortress 2 update released



On 6/24/22 12:13, Alex wrote:
On Friday, June 24th, 2022 at 6:05 AM, Joshua Ashton
 wrote:
The client does nothing with net_disconnect_reason.
It's an entirely server-sided convar.

A hah, I see. When I was attempting to repro, I was testing a client
sending it's disconnect message to a server, not a server forcefully
disconnecting a client and sending a disconnect message (which uses the
same message).

What ended up being fixed in the changelog was a different bug where
disconnect messages would sometimes not show in text chat due to a race
between player entity destruction and the player_disconnected event.

At least this misunderstanding led to fixing two bugs! :-)

This will be fixed in the next update, thanks!

- Joshie ✨


It looks like the ConVar is used in engine code which affects how both
the
client and server process all disconnect messages. When set to 0 on a
client,
it will always override the disconnect reason with "Client Disconnect"
on the
client's end, which is unintended behavior (it's also what was happening
before this ConVar existed).

Video demonstration of this:
https://www.youtube.com/watch?v=BiacrieODC8

Alex K.

___
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/

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

Re: [hlds] Mandatory Team Fortress 2 update released

2022-06-24 Thread Joshua Ashton




On 6/24/22 12:41, Tohru Adachi wrote:
I was under the impression that the default value of 0 was to preserve 
the behaviour from a previous update.


My previous question still stands, shouldn't this be a replicated var? 
Valve servers keep it at 0 and retain the behaviour up to now, community 
server ops can set it to 1 at their discretion and can have 
kicks/bans/disconnects working as originally intended.


Replicated vars wouldn't work for this because a server could have this 
set and reject a client well before replicating vars across and the 
message would not get through.


The correct solution is to just have it do nothing on the client, which 
is the intention all along.


- Joshie ✨



  -
5DE7 65CE F99A B8FB 62A3
6613 A792 D15F DA9E F531


 Original Message 
From: Joshua Ashton [mailto:jos...@froggi.es]
Sent: Friday, June 24, 2022, 1:22 PM
To: Alex; hlds@list.valvesoftware.com
Subject: [hlds] Mandatory Team Fortress 2 update released



On 6/24/22 12:13, Alex wrote:
On Friday, June 24th, 2022 at 6:05 AM, Joshua Ashton
 wrote:
The client does nothing with net_disconnect_reason.
It's an entirely server-sided convar.

A hah, I see. When I was attempting to repro, I was testing a client
sending it's disconnect message to a server, not a server forcefully
disconnecting a client and sending a disconnect message (which uses the
same message).

What ended up being fixed in the changelog was a different bug where
disconnect messages would sometimes not show in text chat due to a race
between player entity destruction and the player_disconnected event.

At least this misunderstanding led to fixing two bugs! :-)

This will be fixed in the next update, thanks!

- Joshie ✨


It looks like the ConVar is used in engine code which affects how both
the
client and server process all disconnect messages. When set to 0 on a
client,
it will always override the disconnect reason with "Client Disconnect"
on the
client's end, which is unintended behavior (it's also what was happening
before this ConVar existed).

Video demonstration of this:
https://www.youtube.com/watch?v=BiacrieODC8

Alex K.

___
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: [hlds] Mandatory Team Fortress 2 update released

2022-06-24 Thread Tohru Adachi
I was under the impression that the default value of 0 was to preserve 
the behaviour from a previous update.


My previous question still stands, shouldn't this be a replicated var? 
Valve servers keep it at 0 and retain the behaviour up to now, community 
server ops can set it to 1 at their discretion and can have 
kicks/bans/disconnects working as originally intended.


 -
5DE7 65CE F99A B8FB 62A3
6613 A792 D15F DA9E F531


 Original Message 
From: Joshua Ashton [mailto:jos...@froggi.es]
Sent: Friday, June 24, 2022, 1:22 PM
To: Alex; hlds@list.valvesoftware.com
Subject: [hlds] Mandatory Team Fortress 2 update released



On 6/24/22 12:13, Alex wrote:
On Friday, June 24th, 2022 at 6:05 AM, Joshua Ashton
 wrote:
The client does nothing with net_disconnect_reason.
It's an entirely server-sided convar.

A hah, I see. When I was attempting to repro, I was testing a client
sending it's disconnect message to a server, not a server forcefully
disconnecting a client and sending a disconnect message (which uses the
same message).

What ended up being fixed in the changelog was a different bug where
disconnect messages would sometimes not show in text chat due to a race
between player entity destruction and the player_disconnected event.

At least this misunderstanding led to fixing two bugs! :-)

This will be fixed in the next update, thanks!

- Joshie ✨


It looks like the ConVar is used in engine code which affects how both
the
client and server process all disconnect messages. When set to 0 on a
client,
it will always override the disconnect reason with "Client Disconnect"
on the
client's end, which is unintended behavior (it's also what was happening
before this ConVar existed).

Video demonstration of this:
https://www.youtube.com/watch?v=BiacrieODC8

Alex K.

___
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: [hlds] Mandatory Team Fortress 2 update released

2022-06-24 Thread Joshua Ashton




On 6/24/22 12:13, Alex wrote:

On Friday, June 24th, 2022 at 6:05 AM, Joshua Ashton  wrote:

The client does nothing with net_disconnect_reason.
It's an entirely server-sided convar.


A hah, I see. When I was attempting to repro, I was testing a client 
sending it's disconnect message to a server, not a server forcefully 
disconnecting a client and sending a disconnect message (which uses the 
same message).


What ended up being fixed in the changelog was a different bug where 
disconnect messages would sometimes not show in text chat due to a race 
between player entity destruction and the player_disconnected event.


At least this misunderstanding led to fixing two bugs! :-)

This will be fixed in the next update, thanks!

- Joshie ✨



It looks like the ConVar is used in engine code which affects how both the
client and server process all disconnect messages. When set to 0 on a client,
it will always override the disconnect reason with "Client Disconnect" on the
client's end, which is unintended behavior (it's also what was happening
before this ConVar existed).

Video demonstration of this:
https://www.youtube.com/watch?v=BiacrieODC8

Alex K.


___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/


Re: [hlds] Mandatory Team Fortress 2 update released

2022-06-24 Thread Alex - osyu at pm.me (via hlds list)
On Friday, June 24th, 2022 at 6:05 AM, Joshua Ashton  wrote:
> The client does nothing with net_disconnect_reason.
> It's an entirely server-sided convar.

It looks like the ConVar is used in engine code which affects how both the
client and server process all disconnect messages. When set to 0 on a client,
it will always override the disconnect reason with "Client Disconnect" on the
client's end, which is unintended behavior (it's also what was happening
before this ConVar existed).

Video demonstration of this:
https://www.youtube.com/watch?v=BiacrieODC8

Alex K.
___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

Re: [hlds] Mandatory Team Fortress 2 update released

2022-06-24 Thread Joshua Ashton




On 6/22/22 02:40, Tohru Adachi wrote:
Didn't expect an update today, but it's a welcome thing to see. Just one 
thing though:


 > - Re-enabled ability for servers to send disconnect reasons to clients
 >    - Added ConVar net_disconnect_reason to use the disconnect reason 
sent from the client


Points for effort even if it's a bit late, except this defaults to 0, 
not 1 and is a non-replicated cvar. Honestly, this should either default 
to 1 for client or more ideally be a replicated variable which resets to 
the user's selection/default on client disconnect.


The client does nothing with net_disconnect_reason.
It's an entirely server-sided convar.

- Joshie ✨



Additionally, there doesn't seem to be a more accessible option to set 
this in any of the settings options. How is a less technically inclined 
user supposed to know to turn this on to know if a server operator has 
kicked/banned them or if a server has crashed/lost connection/kicked by 
slot reservation etc?

  -
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: Wednesday, June 22, 2022, 2:41 AM
To: hlds; 'hlds_annou...@list.valvesoftware.com'; 
'hlds_li...@list.valvesoftware.com'

Subject: [hlds]  Mandatory Team Fortress 2 update released

We've released a mandatory update for TF2. The new version number is 
7333517. The notes for the update are below.


Thanks.

-Eric



- Fixed an exploit related to clearing the in-game text chat
- Fixed an exploit where players could use sv_cheats on secure servers
- Fixed an exploit where players could teleport back to their own spawn 
by changing loadout/class while touching the other team's No Entry gate
- Fixed an exploit with the Huntsman in which a player could change 
loadout to negate the speed debuff when charged

- Fixed an exploit with the Ap-Sap where players could spam noises
- Fixed an exploit where dispensers could heal through glass on some maps
- Fixed an exploit where a Spy could disguise and create an invisible 
bullet blocking shield at their feet
- Fixed laggy animations on Halloween bosses, skeletons, ghosts and 
other ghoul-like beings
- Fixed the Spy using incorrect disguise weapons when disguising as 
Soldier, Pyro, Heavy or Engineer with no member of the same class on the 
opposing team

- Fixed projectiles sometimes colliding with teammates too early/late
- Fixed being able to change names during a matchmaking game
- Fixed some HUD images being blurry when using low texture settings
- Fixed the Spy's feigned deaths with the Dead Ringer not showing up in 
the matchmaking quick team status bar
- Fixed %killername% and other placeholder names sometimes showing up on 
the kill cam and stats screen

- Re-enabled ability for servers to send disconnect reasons to clients
 - Added ConVar net_disconnect_reason to use the disconnect reason 
sent from the client

- Removed Headgear option from the Mann Co. Catalog dropdown list
- Updated vote system
 - Both teams can have a kick vote running at the same time
 - Can have a global vote running at the same time as a kick vote
 - Fixed sometimes not being able to vote on maps at the end of the 
round

- Updated the El Fiestibrero to fix a problem with the model
- Updated/Added some tournament medals
- Updated the localization files





___
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: [hlds] Mandatory Team Fortress 2 update released

2022-06-21 Thread Tohru Adachi
Didn't expect an update today, but it's a welcome thing to see. Just one 
thing though:


> - Re-enabled ability for servers to send disconnect reasons to clients
>	- Added ConVar net_disconnect_reason to use the disconnect reason 
sent from the client


Points for effort even if it's a bit late, except this defaults to 0, 
not 1 and is a non-replicated cvar. Honestly, this should either default 
to 1 for client or more ideally be a replicated variable which resets to 
the user's selection/default on client disconnect.


Additionally, there doesn't seem to be a more accessible option to set 
this in any of the settings options. How is a less technically inclined 
user supposed to know to turn this on to know if a server operator has 
kicked/banned them or if a server has crashed/lost connection/kicked by 
slot reservation etc?

 -
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: Wednesday, June 22, 2022, 2:41 AM
To: hlds; 'hlds_annou...@list.valvesoftware.com'; 
'hlds_li...@list.valvesoftware.com'

Subject: [hlds]  Mandatory Team Fortress 2 update released

We've released a mandatory update for TF2. The new version number is 
7333517. The notes for the update are below.


Thanks.

-Eric



- Fixed an exploit related to clearing the in-game text chat
- Fixed an exploit where players could use sv_cheats on secure servers
- Fixed an exploit where players could teleport back to their own spawn 
by changing loadout/class while touching the other team's No Entry gate
- Fixed an exploit with the Huntsman in which a player could change 
loadout to negate the speed debuff when charged

- Fixed an exploit with the Ap-Sap where players could spam noises
- Fixed an exploit where dispensers could heal through glass on some maps
- Fixed an exploit where a Spy could disguise and create an invisible 
bullet blocking shield at their feet
- Fixed laggy animations on Halloween bosses, skeletons, ghosts and 
other ghoul-like beings
- Fixed the Spy using incorrect disguise weapons when disguising as 
Soldier, Pyro, Heavy or Engineer with no member of the same class on the 
opposing team

- Fixed projectiles sometimes colliding with teammates too early/late
- Fixed being able to change names during a matchmaking game
- Fixed some HUD images being blurry when using low texture settings
- Fixed the Spy's feigned deaths with the Dead Ringer not showing up in 
the matchmaking quick team status bar
- Fixed %killername% and other placeholder names sometimes showing up on 
the kill cam and stats screen

- Re-enabled ability for servers to send disconnect reasons to clients
	- Added ConVar net_disconnect_reason to use the disconnect reason sent 
from the client

- Removed Headgear option from the Mann Co. Catalog dropdown list
- Updated vote system
- Both teams can have a kick vote running at the same time
- Can have a global vote running at the same time as a kick vote
- Fixed sometimes not being able to vote on maps at the end of the round
- Updated the El Fiestibrero to fix a problem with the model
- Updated/Added some tournament medals
- Updated the localization files





___
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/

[hlds] Mandatory Team Fortress 2 update released

2021-12-02 Thread via hlds list
We've released a mandatory update for TF2. This is the Smissmas 2021 update. 
The new version number is 6928179. The notes for the update can be found here:

  https://www.teamfortress.com/post.php?id=101867

-Eric

___
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

2021-11-02 Thread via hlds_linux list
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

2021-10-28 Thread Tohru Adachi
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

2021-10-28 Thread via hlds list
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: [hlds] Mandatory Team Fortress 2 update released

2021-10-28 Thread Naleksuh
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)  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/

Re: [hlds] Mandatory Team Fortress 2 update released

2021-10-28 Thread vinyardat
fwiw, the disconnect server event still contains the reason.
 Original message From: sigsegv  Date: 
10/28/21  6:25 PM  (GMT-05:00) To: hlds@list.valvesoftware.com Subject: Re: 
[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 / sigsegvOn Thu, Oct 28, 2021 at 2:15 PM 
Naleksuh  wrote:I'm much more concerned about the SDR 
thing though. The help pages indicate it'll be available for community server 
operators and that they (possibly?) plan to route *all* traffic through it. I 
really do not want this as I prefer to have control over the networking for my 
servers and I also don't want it to literally become impossible to play the 
game when Steam servers are downYeah, I thought removing it from the chat 
message was enough, I don't think it should have been made impossible to send 
disconnect messages. It's absolutely essential for me as a community server 
operator for example, people who are using VPNs, people trying to join when the 
server is full (I have sv_visiblemaxplayers set below maxplayers so the built 
in message wont show), people banned or trying to use a specific feature, 
people who are sending too many commands (i.e. PASS time) and dozens more. Now 
people have no clue why they are getting disconnected. It made sense to remove 
it from the chat as clients were abusing it but it shouldn't just be completely 
impossible for servers to send disconnect reasons. And this was not just for 
matchmaking servers but all servers including community servers. Please bring 
it back. On Thu, 28 Oct 2021 14:04:56 -0700 Tohru Adachi  
wrote SDR is intended for Casual MM it seems - in the simplest terms it's 
like Cloudflare but for gameservers. Other games eg CS:GO already use the 
system for official MM.  While I'd be interested in seeing what they do with 
it, I don't think it's going to be rolled out to server operators. Can't say 
for sure because I'm not Eric or John (or whoever else still contributes to 
TF2).  As a sidenote, I'm a bit disappointed at the lack of chat over Valve 
removing disconnect reasons for clients (all disconnects are now "Client 
Disconnect" instead of whatever the server sends, regardless of Casual or 
non-casual server). Would very much like to see it back as it's useful for 
informing clients.   Original Message  From: Naleksuh 
[mailto:nalek...@naleksuh.com] Sent: Thursday, October 28, 2021, 9:57 PM To: 
hlds Subject: [hlds]  Mandatory Team Fortress 2 update released  So just to 
clarify. Using the SDR will remain optional right? I'd ideally like to not 
require a dependency on Steam servers to play the game as they are frequently 
down and some people might prefer connecting directly  
___ To unsubscribe, edit your list 
preferences, or view the list archives, please visit: 
https://list.valvesoftware.com/ 
___To unsubscribe, edit

Re: [hlds] Mandatory Team Fortress 2 update released

2021-10-28 Thread Tohru Adachi
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/


Re: [hlds] Mandatory Team Fortress 2 update released

2021-10-28 Thread sigsegv
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

On Thu, Oct 28, 2021 at 2:15 PM Naleksuh  wrote:

>
> I'm much more concerned about the SDR thing though. The help pages
> indicate it'll be available for community server operators and that they
> (possibly?) plan to route *all* traffic through it. I really do not want
> this as I prefer to have control over the networking for my servers and I
> also don't want it to literally become impossible to play the game when
> Steam servers are down
>
> Yeah, I thought removing it from the chat message was enough, I don't
> think it should have been made impossible to send disconnect messages. It's
> absolutely essential for me as a community server operator for example,
> people who are using VPNs, people trying to join when the server is full (I
> have sv_visiblemaxplayers set below maxplayers so the built in message wont
> show), people banned or trying to use a specific feature, people who are
> sending too many commands (i.e. PASS time) and dozens more. Now people have
> no clue why they are getting disconnected. It made sense to remove it from
> the chat as clients were abusing it but it shouldn't just be completely
> impossible for servers to send disconnect reasons. And this was not just
> for matchmaking servers but all servers including community servers. Please
> bring it back.
>
>
>
>
>
>  On Thu, 28 Oct 2021 14:04:56 -0700 *Tohru Adachi  >* wrote 
>
> SDR is intended for Casual MM it seems - in the simplest terms it's like
> Cloudflare but for gameservers. Other games eg CS:GO already use the
> system for official MM.
>
> While I'd be interested in seeing what they do with it, I don't think
> it's going to be rolled out to server operators. Can't say for sure
> because I'm not Eric or John (or whoever else still contributes to TF2).
>
> As a sidenote, I'm a bit disappointed at the lack of chat over Valve
> removing disconnect reasons for clients (all disconnects are now "Client
> Disconnect" instead of whatever the server sends, regardless of Casual
> or non-casual server). Would very much like to see it back as it's
> useful for informing clients.
>
>  Original Message ----
> From: Naleksuh [mailto:nalek...@naleksuh.com]
> Sent: Thursday, October 28, 2021, 9:57 PM
> To: hlds
> Subject: [hlds] Mandatory Team Fortress 2 update released
>
> So just to clarify. Using the SDR will remain optional right? I'd
> ideally like to not require a dependency on Steam servers to play the
> game as they are frequently down and some people might prefer connecting
> directly
>
> ___
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> https://list.valvesoftware.com/
>
>
>
> ___

Re: [hlds] Mandatory Team Fortress 2 update released

2021-10-28 Thread Tohru Adachi
I'm not too sure over Valve forcing operators to use SDR - this would 
require optimised routing pathing in almost every major hosting provider 
and owned/rented hardware there from Steam for users to route from 
within each AS for a lot of providers. I can see major providers who 
aren't yet on the list such as OVH next in line for SDR nodes as they'll 
likely be working on where to place nodes with good routing and peering 
for near-identical latency.


I don't see this being forced because it would be impossible to get 
sufficient coverage with latency at or around identical non-SDR 
pathings, especially in under-networked areas such as APAC/Aus/South 
America et cetera.

I could be completely wrong, though. I just hope I'm not, in this case.

 Original Message 
From: Naleksuh [mailto:nalek...@naleksuh.com]
Sent: Thursday, October 28, 2021, 10:14 PM
To: hlds
Subject: [hlds] Mandatory Team Fortress 2 update released


I'm much more concerned about the SDR thing though. The help pages
indicate it'll be available for community server operators and that they
(possibly?) plan to route *all* traffic through it. I really do not want
this as I prefer to have control over the networking for my servers and
I also don't want it to literally become impossible to play the game
when Steam servers are down

Yeah, I thought removing it from the chat message was enough, I don't
think it should have been made impossible to send disconnect messages.
It's absolutely essential for me as a community server operator for
example, people who are using VPNs, people trying to join when the
server is full (I have sv_visiblemaxplayers set below maxplayers so the
built in message wont show), people banned or trying to use a specific
feature, people who are sending too many commands (i.e. PASS time) and
dozens more. Now people have no clue why they are getting disconnected.
It made sense to remove it from the chat as clients were abusing it but
it shouldn't just be completely impossible for servers to send
disconnect reasons. And this was not just for matchmaking servers but
all servers including community servers. Please bring it back.

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/


Re: [hlds] Mandatory Team Fortress 2 update released

2021-10-28 Thread Naleksuh
I'm much more concerned about the SDR thing though. The help pages indicate 
it'll be available for community server operators and that they (possibly?) 
plan to route *all* traffic through it. I really do not want this as I prefer 
to have control over the networking for my servers and I also don't want it to 
literally become impossible to play the game when Steam servers are down




Yeah, I thought removing it from the chat message was enough, I don't think it 
should have been made impossible to send disconnect messages. It's absolutely 
essential for me as a community server operator for example, people who are 
using VPNs, people trying to join when the server is full (I have 
sv_visiblemaxplayers set below maxplayers so the built in message wont show), 
people banned or trying to use a specific feature, people who are sending too 
many commands (i.e. PASS time) and dozens more. Now people have no clue why 
they are getting disconnected. It made sense to remove it from the chat as 
clients were abusing it but it shouldn't just be completely impossible for 
servers to send disconnect reasons. And this was not just for matchmaking 
servers but all servers including community servers. Please bring it back.










 On Thu, 28 Oct 2021 14:04:56 -0700 Tohru Adachi  wrote 



SDR is intended for Casual MM it seems - in the simplest terms it's like 
Cloudflare but for gameservers. Other games eg CS:GO already use the 
system for official MM. 
 
While I'd be interested in seeing what they do with it, I don't think 
it's going to be rolled out to server operators. Can't say for sure 
because I'm not Eric or John (or whoever else still contributes to TF2). 
 
As a sidenote, I'm a bit disappointed at the lack of chat over Valve 
removing disconnect reasons for clients (all disconnects are now "Client 
Disconnect" instead of whatever the server sends, regardless of Casual 
or non-casual server). Would very much like to see it back as it's 
useful for informing clients. 
 
 Original Message  
From: Naleksuh [mailto:mailto:nalek...@naleksuh.com] 
Sent: Thursday, October 28, 2021, 9:57 PM 
To: hlds 
Subject: [hlds]  Mandatory Team Fortress 2 update released 
 
So just to clarify. Using the SDR will remain optional right? I'd 
ideally like to not require a dependency on Steam servers to play the 
game as they are frequently down and some people might prefer connecting 
directly 
 
___ 
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: [hlds] Mandatory Team Fortress 2 update released

2021-10-28 Thread Tohru Adachi
SDR is intended for Casual MM it seems - in the simplest terms it's like 
Cloudflare but for gameservers. Other games eg CS:GO already use the 
system for official MM.


While I'd be interested in seeing what they do with it, I don't think 
it's going to be rolled out to server operators. Can't say for sure 
because I'm not Eric or John (or whoever else still contributes to TF2).


As a sidenote, I'm a bit disappointed at the lack of chat over Valve 
removing disconnect reasons for clients (all disconnects are now "Client 
Disconnect" instead of whatever the server sends, regardless of Casual 
or non-casual server). Would very much like to see it back as it's 
useful for informing clients.


 Original Message 
From: Naleksuh [mailto:nalek...@naleksuh.com]
Sent: Thursday, October 28, 2021, 9:57 PM
To: hlds
Subject: [hlds]  Mandatory Team Fortress 2 update released

So just to clarify. Using the SDR will remain optional right? I'd
ideally like to not require a dependency on Steam servers to play the
game as they are frequently down and some people might prefer connecting
directly

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/


Re: [hlds] Mandatory Team Fortress 2 update released

2021-10-28 Thread Naleksuh
So just to clarify. Using the SDR will remain optional right? I'd ideally like 
to not require a dependency on Steam servers to play the game as they are 
frequently down and some people might prefer connecting directly






 On Wed, 27 Oct 2021 16:59:58 -0700 Eric Smith - erics at valvesoftware.com 
(via hlds list)  wrote 


We've released a mandatory update for TF2. The new version number is 6858943. 
The notes for the update are below. 
 
Thanks. 
 
-Eric 
 
 
-- 
 
- Bug fixes to Steam Datagram Relay (SDR) support. This is currently in limited 
testing. We will have more info about this when it rolls our more broadly. 
 
___ 
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

2021-10-22 Thread via hlds list
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

2021-10-22 Thread Naleksuh
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

2021-10-22 Thread via hlds list
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: [hlds] Mandatory Team Fortress 2 update released

2021-10-22 Thread Naleksuh
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?






 On Fri, 22 Oct 2021 15:46:32 -0700 Eric Smith - erics at valvesoftware.com 
(via hlds list)  wrote 


We've released a mandatory update for TF2. The new version number is 6848227. 
The notes for the update can be found here: 
 
https://www.teamfortress.com/post.php?id=90380 
 
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/

Re: [hlds] Mandatory Team Fortress 2 update released

2021-09-26 Thread Arron Vinyard
Yeah, I definitely would like to see the disconnect reason
reverted/restored. Not sure if it was a lazy fix to an issue or what, but
it removes valuable information that the client should be aware of.

On Sun, Sep 26, 2021, 8:07 PM Tohru Adachi  wrote:

> Bottom Line Up Front: Recent changes to how the client handles
> disconnections breaks server-side plugins' kick/ban reason functionality.
> --
>
> I'd like to bring up an issue I think has been slightly overshadowed due
> to the recent server connection issues. This is in regards to a client
> change as of version 6770799.
>
> The following change has caused reduced functionality in some basic
> functions in SourceMod:
>  > - Removed the disconnect reason when a player leaves the server
>
> The string "Disconnect: Client Disconnect" is always shown to the client
> whenever the server terminates the connection between client. What has
> changed though, is that the client overwrites the sent string with
> "Client Disconnect" regardless of the cause of the disconnect eg.
> SourceMod's kick function.
>
> In short: Kick/ban message reason functionality does not work as of
> 6770799. The change affects the game client, not the server binaries, so
> there's no workaround.
>
> While it's logical to see the reasoning behind not showing disconnection
> messages to other clients by default due to abuse within Valve servers,
> I personally believe this could have been implemented better e.g. to
> allow moderators of community servers to show a kick or ban reason to
> the target client only, as currently almost all disconnects from a
> community server to the disconnected client will all show as "Client
> Disconnect", which can be misleading and confusing depending on the
> circumstances.
>
> In practice, there can be multiple reasons for disconnects, such as
> server shutdown (quit), removed by administrator or vote kick (both via
> SourceMod functionality, I cannot comment on the stock vote menu),
> prohibited by whitelist, prohibited by account status or statistics, and
> so on.
>
> If possible, can this functionality be changed to only send a static
> message if the server is registered in the Valve Matchmaking pool? This
> would mitigate abuse by malicious actors in Valve servers, while still
> allowing community server operators to use the disconnect function for
> the purpose of showing disconnect reasons to users (kick/ban/et cetera).
>
> Thank you.
> --
>
> 
> // PGP key fingerprint:   //
> // 5DE7 65CE F99A B8FB 62A3   //
> // 6613 A792 D15F DA9E F531   //
> // For sensitive communications, please send your public key. //
> 
>
> ___
> 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: [hlds] Mandatory Team Fortress 2 update released

2021-09-26 Thread Tohru Adachi
Bottom Line Up Front: Recent changes to how the client handles 
disconnections breaks server-side plugins' kick/ban reason functionality.

--

I'd like to bring up an issue I think has been slightly overshadowed due 
to the recent server connection issues. This is in regards to a client 
change as of version 6770799.


The following change has caused reduced functionality in some basic 
functions in SourceMod:

> - Removed the disconnect reason when a player leaves the server

The string "Disconnect: Client Disconnect" is always shown to the client 
whenever the server terminates the connection between client. What has 
changed though, is that the client overwrites the sent string with 
"Client Disconnect" regardless of the cause of the disconnect eg. 
SourceMod's kick function.


In short: Kick/ban message reason functionality does not work as of 
6770799. The change affects the game client, not the server binaries, so 
there's no workaround.


While it's logical to see the reasoning behind not showing disconnection 
messages to other clients by default due to abuse within Valve servers, 
I personally believe this could have been implemented better e.g. to 
allow moderators of community servers to show a kick or ban reason to 
the target client only, as currently almost all disconnects from a 
community server to the disconnected client will all show as "Client 
Disconnect", which can be misleading and confusing depending on the 
circumstances.


In practice, there can be multiple reasons for disconnects, such as 
server shutdown (quit), removed by administrator or vote kick (both via 
SourceMod functionality, I cannot comment on the stock vote menu), 
prohibited by whitelist, prohibited by account status or statistics, and 
so on.


If possible, can this functionality be changed to only send a static 
message if the server is registered in the Valve Matchmaking pool? This 
would mitigate abuse by malicious actors in Valve servers, while still 
allowing community server operators to use the disconnect function for 
the purpose of showing disconnect reasons to users (kick/ban/et cetera).


Thank you.
--


// PGP key fingerprint:   //
// 5DE7 65CE F99A B8FB 62A3   //
// 6613 A792 D15F DA9E F531   //
// For sensitive communications, please send your public key. //


___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/


[hlds] Mandatory Team Fortress 2 update released

2021-09-24 Thread via hlds list
We've released a mandatory update for TF2. The new version number is 6788809. 
The notes for the update are below.

Thanks.

-Eric



- Fixed a bug where some methods of connecting to Steam would not honor the -ip 
command line parameter

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2021-09-17 Thread via hlds list
We've released another mandatory update for TF2. The new version number is 
6774624. The notes for the update are below.

Thanks.

-Eric



- Added ConVar "sdr_spew_level" for clients and servers to control 
SteamNetworkingSockets console spew. Default is 4 (warning).
- Fixed official TF2 bots displaying avatars in the scoreboard during modes 
like Offline Practice
- Updated the War Paint inspection panel to support all seed values
- Updated custom player sprays and other temp files to only be deleted on 
shutdown

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2021-06-22 Thread via hlds list
We've released another mandatory update for TF2. The new version number is 
6623512. The notes for the update are below.

Thanks.

-Eric



- Fixed players not being able to download large custom maps from servers
- Added check to prevent players without admin access using the dump_all_caches 
server command

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

Re: [hlds] Mandatory Team Fortress 2 update released

2021-06-22 Thread Bakugo
And this is why I tell people to stop asking for TF2 updates.
Modern Valve can't be trusted to update the game without ruining things
that have been working fine for literal decades.

On Tue, Jun 22, 2021 at 11:51 PM Tohru Adachi  wrote:

> I've heard reports that custom downloads have been hardcoded to no more
> than 64MB. I went ahead and tested this with some custom maps - anything
> over the aforementioned limit would not download. Worse still, it seems
> this is a hardcoded limit and is NOT changeable via convar.
>
> Why is this a thing? Old code? Lazy fix for a security vulnerability? Or
> are you actually trying to kill off community servers outright, Valve?
>
> I'm genuinely not impressed here - anyone who wants to run a custom map
> with maybe a few more custom assets than usual that just about puts them
> over this cap is out of luck, as the file will just fail to download as
> if it doesn't exist on the server or FastDL location, eventually
> disconnecting the client with a missing map error if the file in
> question is a mapfile.
>
> TL;DR: TF2 now seems to just fail to download any custom content over
> 64MB - this breaks a lot of larger custom content (think custom maps).
> and is not good news in the long run.
> ___
> 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: [hlds] Mandatory Team Fortress 2 update released

2021-06-22 Thread Tohru Adachi
I've heard reports that custom downloads have been hardcoded to no more 
than 64MB. I went ahead and tested this with some custom maps - anything 
over the aforementioned limit would not download. Worse still, it seems 
this is a hardcoded limit and is NOT changeable via convar.


Why is this a thing? Old code? Lazy fix for a security vulnerability? Or 
are you actually trying to kill off community servers outright, Valve?


I'm genuinely not impressed here - anyone who wants to run a custom map 
with maybe a few more custom assets than usual that just about puts them 
over this cap is out of luck, as the file will just fail to download as 
if it doesn't exist on the server or FastDL location, eventually 
disconnecting the client with a missing map error if the file in 
question is a mapfile.


TL;DR: TF2 now seems to just fail to download any custom content over 
64MB - this breaks a lot of larger custom content (think custom maps). 
and is not good news in the long run.

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/


[hlds] Mandatory Team Fortress 2 update released

2021-06-22 Thread via hlds list
We've released a mandatory update for TF2. The new version number is 6616932. 
The notes for the update are below.

Thanks.

-Eric



- Added the Summer 2021 Cosmetic Case
- Contains 18 new community-contributed items
- Adds 6 new community-created Unusual effects
- Numerous security and stability improvements
- Added a cooldown before a player can create a vote when they join a match 
already in-progress
- sv_vote_late_join_time controls the grace period after the match 
starts before the cooldown is applied: default 90 secs
- sv_vote_late_join_cooldown controls the length of the cooldown: 
default 5 min
- Kick votes will end early and automatically pass if the vote target leaves 
the match during the vote
- Added a ConVar to control players changing their name during a match
- tf_allow_player_name_change: default is 1
- Matchmaking servers will set this to 0
- Updated the player list in the vote-kick dialog to show the time each player 
has been connected to the server
- Removed the disconnect reason from the message when players leave the server
- Updated the Mann vs. Machine "inspect" command to only work for players in 
your party or in your Friends list
- Moved materials for the community particle effects into the Effects/workshop 
sub-folder to distinguish them from Valve materials
- Updated/Added some tournament medals
- Updated the localization files
- Updated cp_snakewater_final1
- Fixed clipping throughout map
- Fixed explosion splash being caught by objects throughout map
- Made movement smoother throughout map
- Reworked some problematic areas like the kitchen
- Minor visual enhancements throughout the map
- Updated cp_process
- Fixed incorrect skin for the Red radio tower

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2021-03-02 Thread via hlds list
We've released a mandatory update for TF2. The new version number is 6394067. 
The notes for the update are below.

Thanks.

-Eric



- Added a round timer to cp_powerhouse
- Updated/Added some tournament medals
- Updated the localization files

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2021-01-08 Thread via hlds list
We've released a mandatory update for TF2. The new version number is 6300758. 
The notes for the update are below.

Thanks.

-Eric



- Updated pl_pier
- Added additional exits to forward spawns
- Added windows to RED final spawn
- Added small platform to the first beach
- Improved general clipping
- Players can no longer build on the tables in RED spawn

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2020-12-16 Thread via hlds list
We've released a mandatory update for TF2. The new version number is 6269048. 
The notes for the update are below.

Thanks.

-Eric



- Fixed a client crash related to inspecting the same item twice
- Fixed the Strange Count Transfer Tool not being able to transfer stats 
between Mad Milk and Mutated Milk
- Fixed the equip_region for Pebbles the Penguin
- Fixed not being able to use Taunt: The Table Tantrum Unusualifier on Taunt: 
The Boiling Point
- Updated Taunt: The Pooped Deck to fix some sounds
- Updated the localization files
- Updated ctf_snowfall_final
- Fixed an issue some players were having with candy cane textures
- Updated the lighting
- Updated pl_wutville_event
- The Smissmas trees are now properly colliding with mercs and ordinance
- The larger first BLU spawn has been re-zoned for proper class changes 
and no more Engineer shenanigans
- Wooden crates and furniture from the 2Fort division has had the 
minimum DirectX levels restored and should now be visible to mercs
- Clipping of ledges and outcroppings around the Control Points has 
been installed to keep the merc's boots on the ground
- The train tunnels will no longer allow for early escape

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2020-12-11 Thread via hlds list
We've released a mandatory update for TF2. The new version number is 6258167. 
The notes for the update are below.

Thanks.

-Eric



- Fixed the Spy's arms not cloaking
- Updated Taunt: Spin-to-Win to fix an animation timing issue
- Updated Taunt: The Pooped Deck with missing animations and sounds
- Updated the equip_region for The Cammy Jammies
- Updated the localization files

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2020-12-09 Thread via hlds list
We've released a mandatory update for TF2. The new version number is 6252422. 
The notes for the update are below.

Thanks.

-Eric



- Fixed Strange war paint weapons not including the Strange attribute in their 
name
- Fixed an issue with the Select Style and Adjust Unusual dialogs not 
displaying properly in the loadout panel at some resolutions
- Added jingle sound to the Elf Care Provider
- Added Taunt: The Table Tantrum to the list of items for the Unusualifier
- Updated the Anodized Aloha war paint to fix an issue with the Back Scratcher
- Updated Taunt: The Fist Bump to add a particle effect on success
- Updated Taunt: The Boston Boarder to fix moving forward too early
- Updated Taunt: Spin-to-Win to have the sign stay longer at the end of the 
taunt
- Updated web page with community fixes from Liam Stone (boba)
- Updated Spy invis materials with community fixes from Liam Stone (boba)
- Updated/Added some tournament medals
- Updated the localization files
- Updated pd_snowville_event
- Fixed ground texture incompatibility with mat_specular 0
- Fixed clipping issues
- Rewrote HUD file to not conflict with custom HUDs
- Festivized the middle pine tree
- Updated pl_pier
- Expanded hallways to BLU spawn exits
- Players can no longer build inside RED spawn
- Fixed rock occasionally missing a texture
- Fixed clipping not covering some roof overhangs

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2020-12-03 Thread via hlds list
We've released a mandatory update for TF2. This is the Smissmas update. The new 
version number is 6239334. The notes for the update can be found here:

https://www.teamfortress.com/post.php?id=78083

Thanks.

-Eric

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2020-11-05 Thread via hlds list
We've released a mandatory update for TF2. The new version number is 6186971. 
The notes for the update can be found here:

https://www.teamfortress.com/post.php?id=77492

Thanks.

-Eric

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2020-10-29 Thread via hlds list
We've released a mandatory update for TF2. The new version number is 6173888. 
The notes for the update can be found here:

https://www.teamfortress.com/post.php?id=77157

Thanks.

-Eric

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2020-10-15 Thread via hlds list
We've released a mandatory update for TF2. The new version number is 6145689. 
The notes for the update can be found here:

https://www.teamfortress.com/post.php?id=76577

Thanks.

-Eric

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2020-10-09 Thread Eric Smith - erics at valvesoftware.com (via hlds list)
We've released a mandatory update for TF2. The new version number is 6131739. 
The notes for the update can be found here:

https://www.teamfortress.com/post.php?id=76348

Thanks.

-Eric

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2020-10-08 Thread Eric Smith - erics at valvesoftware.com (via hlds list)
We've released a mandatory update for TF2. The new version number is 6131739. 
The notes for the update can be found here:

https://www.teamfortress.com/post.php?id=76303

Thanks.

-Eric

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2020-10-02 Thread Eric Smith - erics at valvesoftware.com (via hlds list)
We've released a mandatory update for TF2 to fix an issue with the Handsome 
Devil. The new version number is 6121893. 

Thanks.

-Eric

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2020-10-02 Thread Eric Smith - erics at valvesoftware.com (via hlds list)
We've released a mandatory update for TF2. The new version number is 6121705. 
The notes for the update can be found here:

https://www.teamfortress.com/post.php?id=76161

Thanks.

-Eric

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2020-10-01 Thread Eric Smith - erics at valvesoftware.com (via hlds list)
We've released a mandatory update for TF2. This is the Scream Fortress update. 
The new version number is 6118528. The notes for the update can be found here:

https://www.teamfortress.com/post.php?id=76112

Thanks.

-Eric

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2020-07-03 Thread via hlds list
We've released a mandatory update for TF2. The notes for the update are below. 
The new version number is 5970214.

-Eric


--

- Accounts that are unable to chat in matchmaking are now also restricted from 
sending voice chat
- Fixed a bug where cosmetic items in the second and third equip slots would be 
un-equipped
- Fixed matchmaking badges not displaying the correct tier in the scoreboard 
and other dialogs
- Added matchmaking badge and time connected to the Report Player dialog
- Updated the vote kick process to automatically vote Yes for anyone who hasn't 
already voted if the target for the vote leaves the server
- Updated the Mute Player dialog to have the same information as the Report 
Player dialog
- Updated item schema with community fixes from Andrés S. (rabscootle)
- Updated/Added some tournament medals
- Updated the localization files

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2020-06-24 Thread via hlds list
We've released a mandatory update for TF2. The notes for the update are below. 
The new version number is 5948754.

-Eric


--

- Added rate limit checks for in-game text chat
- Accounts that are unable to chat in matchmaking can no longer update their 
in-game name while connected to the server
- Fixed being able to update team name while in matchmaking games
- Fixed seeing the RED team skin for the TF2VRH while on the BLU team
- Updated/Added some tournament medals
- Updated the localization files

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2020-06-16 Thread via hlds list
We've released a mandatory update for TF2. The notes for the update are below. 
The new version number is 5932704.

-Eric


--

- Restricted certain new accounts from using chat in official matchmaking modes
- Work is ongoing to mitigate the use of new and free accounts for 
abusive purposes
- Added "Enable text chat" and "Enable voice chat" options to the top of the 
Advanced Options dialog to disable in-game text and voice chat
- Updated the Report Player dialog to include more details so players can make 
informed decisions about who they're reporting
- Fixed getting the "Incoming message..." quest HUD notification when you've 
already completed all available quests
- Fixed the OnDestroyed output not getting fired when an object is destroyed by 
the Red-Tape Recorder
- Updated The Telefragger Toque to fix swapped materials
- Updated The TF2VRH headset to include on/off styles
- Updated the PASS Time Federation medals to fix issues with them not drawing 
correctly
- Updated/Added some tournament medals
- Updated the localization files

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2020-05-01 Thread via hlds list
We've released a mandatory update for TF2. The update notes are below. The new 
version number is 5840528.

-Eric

-

-Added a tribute to Rick May, voice of the Soldier
-Fixed a client crash related to malformed custom spray files
-Fixed an exploit where sentry guns could fire through thin walls
-Fixed confirm dialog showing the error model for some items when using paint 
cans
-Updated the Aim Assistant and Telefragger Toque to fix jigglebones issues 
-Updated the ConTracker font to fix missing characters in some languages
-Updated/Added some tournament medals
-Updated the localization files

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2020-04-27 Thread via hlds list
We've released a mandatory update for TF2. The update notes are below. The new 
version number is 5830736.

-Eric

-

- Fixed Heavy exploit related to infinite overheal
- Updated localization files




___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2020-04-07 Thread via hlds list
We've released a mandatory update for Team Fortress 2. The notes for the
update are below. The new version is 5799494.

- John



- Fixed a server crash exploit
- Updated localization files

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2020-01-18 Thread Eric Smith
We've release a mandatory update for TF2. The new version number is 5615298. 
The notes for the update are here:

http://www.teamfortress.com/post.php?id=57794

Thanks.

-Eric

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

Re: [hlds] Mandatory Team Fortress 2 update released

2019-11-20 Thread Stealth Mode
Hello Mr. Smith,

Long time no see/hear. Been inactive for a minute. Please pass along to
Lord Gaben that Stealthmode requests respectfully that the Half-Life 3 be
pursued on a newer engine. Mayhaps Vulkan?

Sorry for the OT, however, just doing my part. Have a good day. And good to
see that you are still busy at vALVE. Miss testing Condition Zero, and all
that fun jazz back in 2002/2003 (Still the best bot AI ever imho).

Christopher "StealthMode" Larkins

On Thu, Oct 24, 2019 at 2:03 PM Eric Smith  wrote:

> We've released a mandatory update for TF2. The new version number is
> 5440607. The notes for the update can be found here:
>
> http://www.teamfortress.com/post.php?id=55444
>
> 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/

Re: [hlds] Mandatory Team Fortress 2 update released

2019-10-10 Thread sigsegv
While playing on Valve casual servers today, I also encountered some
interesting server crashes:

1. One on koth_harvest_event, which I believe occurred the very moment
before one team was going to win by running down the timer while owning the
point. (I am slightly less certain about this one than the other one.)
2. One on cp_manor_event, which definitely occurred the precise moment
(possibly the very last tick) before blue team captured the last point.
Contract progress for the round was not recorded.

These seem to corroborate the general “something is sporadically going
wrong at round end in some cases” hypothesis.

(Oh yeah, and when I attempted to MM into another Valve casual server right
after the second server crash disconnection, I experienced a client crash
as well. It happened exactly 3 seconds after the "sigsegv connected" line
showed up in my client-side console.log; the last line logged was
"Redownloading all lightmaps". Interestingly, the Windows event log entry
for the crash shows that it was an access violation in
filesystem_stdio.dll. So that's interesting, and suggestive that some of
the recent changes to the filesystem code are likely still causing issues
of some sort. I believe I do have a dump file for that crash, so I'll
probably figure out the stack trace and then send that info over in a
little while.)

Server crash #1: 162.254.194.163:27039 [A:1:3374034954:13436] @ 12:35:35 PDT
Server crash #2: 162.254.194.152:27039 [A:1:379075:13436] @ 14:21:57 PDT

Client crash: just after connecting to 208.78.165.72:27018
[A:1:3302946821:13436]
@ 14:24:38 PDT

Justin (sigsegv)

On Thu, Oct 10, 2019 at 4:04 PM stephanie  wrote:

> 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 
> 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/

RE: [External Mail] Re: [hlds] Mandatory Team Fortress 2 update released

2019-10-10 Thread Eric Smith
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/

Re: [hlds] Mandatory Team Fortress 2 update released

2019-10-10 Thread stephanie
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  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/

Re: [hlds] Mandatory Team Fortress 2 update released

2019-05-01 Thread ics
This has to be something on your end since mine are working fine. That, 
or windows version has something wrong. Running linux myself.


-ics

vinyardat wrote:

Hello,

Unsure if this is the proper channel for contact. Last tf2 update 
causes all of my servers to crash on any map change. Last console 
message is always "Unable to load manifest file 
'scripts/soundscapes_manifest.txt'"


 Original message 
From: John Schoenick 
Date: 4/30/19 8:08 PM (GMT-05:00)
To: hlds_annou...@list.valvesoftware.com, hlds@list.valvesoftware.com, 
Half-Life dedicated Linux server mailing list 


Subject: [hlds]  Mandatory Team Fortress 2 update released

We've released a mandatory update for Team Fortress 2. The notes for the
update are below. The new version is 5063830.

- John



- Fixed the datacenter display in matchmaking settings occasionally
being blank
- Fixed several client crashes
- Updated/Added some tournament medals
- Updated the localization files

___
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: [hlds] Mandatory Team Fortress 2 update released

2019-04-30 Thread vinyardat
Hello,Unsure if this is the proper channel for contact. Last tf2 update causes 
all of my servers to crash on any map change. Last console message is always 
"Unable to load manifest file 'scripts/soundscapes_manifest.txt'"
 Original message From: John Schoenick 
 Date: 4/30/19  8:08 PM  (GMT-05:00) To: 
hlds_annou...@list.valvesoftware.com, hlds@list.valvesoftware.com, Half-Life 
dedicated Linux server mailing list  
Subject: [hlds]  Mandatory Team Fortress 2 update released We've released a 
mandatory update for Team Fortress 2. The notes for theupdate are below. The 
new version is 5063830.- 
John- Fixed the 
datacenter display in matchmaking settings occasionallybeing blank- Fixed 
several client crashes- Updated/Added some tournament medals- Updated the 
localization files___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/

[hlds] Mandatory Team Fortress 2 update released

2019-04-30 Thread John Schoenick
We've released a mandatory update for Team Fortress 2. The notes for the
update are below. The new version is 5063830.

- John



- Fixed the datacenter display in matchmaking settings occasionally
being blank
- Fixed several client crashes
- Updated/Added some tournament medals
- Updated the localization files

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2019-03-28 Thread John Schoenick
We've released a mandatory update for Team Fortress 2. The notes for the
update are below. The new version is 5018191.

- John



- Improved how vote kicks work in matchmaking to reduce potential for abuse
- Fixed a case where vote-kicked players could rejoin a match
- Added Asian BBall Cup tournament medals
- Updated model/materials for the Rasslabyxa Cup Helper medal
- Updated RETF2 Retrospective finalist medals to be paintable

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2018-12-20 Thread Eric Smith
We've released a mandatory update for Team Fortress 2. The notes for the update 
are below. The new version number is 4883963.  

Thanks.

-Eric



- Updated cp_gullywash_final1 to fix func_rotating entities not working in the 
skybox
- Updated some of the cosmetic items from the Winter 2018 Cosmetics Collection 
to fix missing styles

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2018-12-19 Thread Eric Smith
We've released a mandatory update for Team Fortress 2. The notes for the update 
are here:

http://www.teamfortress.com/post.php?id=46984

The new version number is 4881676.  Thanks.

-Eric

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2018-10-30 Thread Eric Smith
We've released a mandatory update for Team Fortress 2. The notes for the update 
are below. The new version number is 4783668.

Thanks.

-Eric

==

- Fixed XP-earned text being truncated for some clients
- Fixed some missing particles when running in DirectX8
- Fixed the Athenian Attire not being paintable
- Added server ConVar "sv_downloadlist_include_navfile" to control downloading 
.nav files to clients (disabled by default)
- Added ESEA 6s Invite Season 29 and Season 30 tournament medals
- Added Brazil Fortress 6v6 Season 1 and Season 2 tournament medals
- Updated the LODs for the TFNew tournament medals
- Updated the Roaring Rockets unusual taunt particle effect
- Updated pl_rumble_event
- Fixed bumper car head start not being awarded correctly to the 
winning team of the normal world
- Fixed Merasmus announcing winner of the bumper car race twice
- Fixed players sometimes getting stuck on closing doors
- Added spawn locations for the collectable soul gargoyle in the normal 
world
- Increased sound distance for the flying sawblades so they can be 
heard from farther away
- Improved clipping in the underworld race area
- Updated pl_millstone_event
- Fixed an issue where players were able to trap Headless Horseman 
above the death pit
- Updated pd_cursed_cove_event
- Fixed missing materials
- Updated koth_slasher
- Fixed an inconsistent set of func_nobuilds at mid
- Fixed a spot where Engineers could hide buildings in trees
- Fixed players being able to build on top of the spawn rooms
- Updated koth_bagel_event
- Entering the underworld now puts players back to full health
- Players will no longer fall off the platform if they enter the 
underworld while moving backwards or sideways
- Added a couple pumpkin spawn locations in the underworld
- Minor visual update to underworld exit

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2018-10-25 Thread Eric Smith
We've released a mandatory update for Team Fortress 2. The notes for the update 
can be found at the link below. The new version number is 4777091.

http://www.teamfortress.com/post.php?id=45236

Thanks.

-Eric

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2018-10-22 Thread John Schoenick
We've released a mandatory update for Team Fortress 2. The notes for the
update are below. The new version is 4771545.

- John



- Fixed a common crash related to the Panzer Pants taunt
- Fixed competitive match history failing to load
- Fixed an issue preventing some players from being able to activate
Halloween Contracts

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2018-10-19 Thread Eric Smith
We've released a mandatory Team Fortress 2 update for Scream Fortress X. The 
notes for the update can be found at the link below. The new version number is 
4767377.

http://www.teamfortress.com/post.php?id=45049

Thanks.

-Eric


___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2018-09-21 Thread John Schoenick
We've released a mandatory update for Team Fortress 2. The notes for the
update are below. The new version is 4725564.

- John



- Added LBTF2 6v6 Season 15 tournament medals
- Added NewbieDuo Cup Summer 2018 tournament medals
- Added Ultimate Ultiduo Season 2 tournament medals
- Added Fresh Meat Prolander Cup Summer 2018 and Autumn 2018 tournament
medals
- Added ETF2L Highlander Season 15, 6v6 Season 30, and Highlander Season
16 tournament medals
- Added Newbie Highlander Season 4 tournament medals
- Added RGL.gg Season 4, Season 5, and One Day Prolander Cup tournament
medals
- Added PASS Time Federation Season 1 tournament medals
- Added Chapelaria Highlander Season 1 tournament medals
- Added Respawn League Highlander Season 1 tournament medals
- Added Moscow LAN Summer 2018 tournament medals
- Community request: player_hurt events are now visible to SourceTV clients
- Updated the localization files

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2018-08-02 Thread John Schoenick
We've released a mandatory update for Team Fortress 2. The notes for the
update are below. The new version is 4647498.

- John



- Added UGC Highlander Season 24, Highlander Season 25, 6v6 Season 26,
6v6 Season 27, 4v4 Season 13, and 4v4 Season 14 tournament medals
- Added TFCL 6v6 Season 4, Ultiduo Season 5, and Highlander Season 2
tournament medals
- Added TF2Maps 72hr TF2Jam Summer Participant 2018 community medal
- Added Insomnia 63 tournament medals
- Added Essentials.TF monthly tournament medals
- Updated the localization files

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[hlds] Mandatory Team Fortress 2 update released

2018-06-26 Thread John Schoenick
We've released a mandatory update for Team Fortress 2. The notes for the
update are below. The new version is 4586063.

- John



- Added tournament/community medals for HLMixes, Hydro.tf, Ready Steady
Pan Season 4, and Blapature
- Tweaked Competitive Mode MMR calculations
  - MMR mobility increased somewhat across the board
  - Players who have high game counts relative to the rest of the player
base should see fewer adjustments of 1 or 0 MMR
- Updated pl_enclosure_final to fix a displacement hole in stage two
- Updated Test Run items such that the discount is not valid if the item
is already on sale in the Mann Co. Store
- Updated the models for The Frontier Djustice, The Rotation Sensation,
and the Elf Esteem to fix display problems with unusual effects
- Fixed some currencies not properly calculating the Test Run discount,
which prevented being able to purchase the item
- Updated the localization files

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/

[HLDS] Mandatory Team Fortress 2 update released

2018-06-07 Thread Eric Smith
We've released a mandatory update for Team Fortress 2. The notes for the update 
are below. The new version number is 4549959.



Thanks.



-Eric



==



- Several fixes to address exploits and stability issues

- Fixed server crash related to the CTriggerAddTFPlayerCondition map entity

- Fixed client crash when playing Mann vs. Machine

- Fixed client crash on exit

- Fixed Scouts not being able to pick-up the Sandman's baseball

- Fixed broken Unusual effects for the Exquisite Rack, the Stainless Pot, and 
the Universal Translator

- Fixed broken Strange Filter store images for Brimstone, Maple Ridge Event, 
and Pit of Death

- Updated r_screenoverlay command to accept '0' as well as 'off' to disable 
overlays. This fixes some community mods that were incorrectly expecting 0 to 
disable the overlay, resulting in unexpected behavior.

- Added "Reset All Achievements" button to the Achievements dialog

- A small number of achievements are based on player stats and 
will be awarded again when Team Fortress 2 is restarted unless the player stats 
are also reset

- Resetting achievements will not allow you to receive 
achievement-based items multiple times

- Players who consistently demonstrate a pattern of negative behavior in-game 
(based upon excessive reports from other players and several other factors) 
will now receive a temporary matchmaking ban

- Added RGL.gg tournament medals

- Added Copenhagen Games tournament medals

- Added PURE League tournament medals

- Added Beginnings 5 tournament medals

- Added ozfortress Season 22 tournament medals

To unsubscribe from this list please go to 
http://www.simplelists.com/confirm.php?u=bafqsjIGAvbk6UHJGmU3sMrmlZiVHgsC

Re: [hlds] Mandatory Team Fortress 2 update released

2018-04-26 Thread Eric Smith
It didn’t, but it does now. Thanks for the email.

-Eric


From: hlds <hlds-boun...@list.valvesoftware.com> On Behalf Of Fear
Sent: Thursday, April 26, 2018 3:05 PM
To: Half-Life dedicated Win32 server mailing list <hlds@list.valvesoftware.com>
Subject: Re: [hlds] Mandatory Team Fortress 2 update released

- Added the new Pyro weapons to the list of weapons that can be found via 
random drops

Does this include the Heavy Banana?

On Thu, Apr 26, 2018 at 4:40 PM, Eric Smith 
<er...@valvesoftware.com<mailto:er...@valvesoftware.com>> wrote:
We're released a mandatory update for Team Fortress 2. The notes for the update 
are below. The new version number is 4478108.

-Eric

-

- Fixed players not being able to push the payload cart on some maps
- Fixed a client crash related to the main menu
- Fixed a client crash when exiting the game
- Fixed not being able to pickup item_bonuspack entities that have not been 
assigned to a specific team
- Added self-damage when using the Short Circuit's orb to attack an enemy at 
close range
- Added the new Pyro weapons to the list of weapons that can be found via 
random drops
- Added The Heartfelt Hero medal for the Hugs.tf 2018 community event
- Updated ctf_foundry
- Organized powerup locations to be more consistent with other maps
- Removed the crit powerup in the center of the map
- Fixed the return times for dropped flags

___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds

___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


Re: [hlds] Mandatory Team Fortress 2 update released

2018-04-26 Thread Fear
 - Added the new Pyro weapons to the list of weapons that can be found via
random drops

Does this include the Heavy Banana?

On Thu, Apr 26, 2018 at 4:40 PM, Eric Smith  wrote:

> We're released a mandatory update for Team Fortress 2. The notes for the
> update are below. The new version number is 4478108.
>
> -Eric
>
> -
>
> - Fixed players not being able to push the payload cart on some maps
> - Fixed a client crash related to the main menu
> - Fixed a client crash when exiting the game
> - Fixed not being able to pickup item_bonuspack entities that have not
> been assigned to a specific team
> - Added self-damage when using the Short Circuit's orb to attack an enemy
> at close range
> - Added the new Pyro weapons to the list of weapons that can be found via
> random drops
> - Added The Heartfelt Hero medal for the Hugs.tf 2018 community event
> - Updated ctf_foundry
> - Organized powerup locations to be more consistent with other maps
> - Removed the crit powerup in the center of the map
> - Fixed the return times for dropped flags
>
> ___
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
>
___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


[hlds] Mandatory Team Fortress 2 update released

2018-04-26 Thread Eric Smith
We're released a mandatory update for Team Fortress 2. The notes for the update 
are below. The new version number is 4478108.

-Eric

-

- Fixed players not being able to push the payload cart on some maps
- Fixed a client crash related to the main menu
- Fixed a client crash when exiting the game
- Fixed not being able to pickup item_bonuspack entities that have not been 
assigned to a specific team
- Added self-damage when using the Short Circuit's orb to attack an enemy at 
close range
- Added the new Pyro weapons to the list of weapons that can be found via 
random drops
- Added The Heartfelt Hero medal for the Hugs.tf 2018 community event
- Updated ctf_foundry
- Organized powerup locations to be more consistent with other maps
- Removed the crit powerup in the center of the map
- Fixed the return times for dropped flags

___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


Re: [hlds] Mandatory Team Fortress 2 update released

2018-04-12 Thread Josh Russell
Also, the last stages in the multi-stage Payload Race maps are broken.

On Thu, Apr 12, 2018 at 8:36 PM, Alex Kowald  wrote:

> Heads up, you left your debug prints in when a player is healed. It can
> produce quite some spam in the server console.
>
> On Thu, Apr 12, 2018 at 7:42 PM, Eric Smith 
> wrote:
>
>> We’re released a mandatory update for Team Fortress 2. The notes for the
>> update are below. The new version number is 4462894.
>>
>>
>>
>> -Eric
>>
>>
>>
>> -
>>
>>
>>
>> Matchmaking Changes
>>
>> - The initial load time into a match no longer counts against a player's
>> abandon timer
>>
>> - Changed the timeout before a missing player is marked as having
>> abandoned a competitive match to be three minutes from the first time a
>> player disconnects from the server, rather than from the moment the match
>> is formed
>>
>> - Queue times should now be significantly faster when dealing with large
>> numbers of placement and recently-placed players in queue
>>
>> - Moved the Competitive MMR change notification so it no longer overlaps
>> your rank
>>
>> - Fixed continuing to receive the prompt to rejoin a match after you have
>> been dropped from said match
>>
>> - Fixed a case where players would receive a rank change in matches that
>> dissolved due to abandon
>>
>>
>>
>> General
>>
>> - Added a stomp animation to Pyro that plays when coming down after
>> blasting off from the Thermal Thruster
>>
>> - Added HLPugs.tf tournament medals
>>
>> - Added Gette it Onne! tournament medals
>>
>> - Added TFCL tournament medals
>>
>> - Added Copenhagen Games tournament medals
>>
>> - Fixed Medics having an accelerated Übercharge build-rate when healing
>> full-health Snipers who are using The Razorback
>>
>> - Fixed being able to capture control points during setup time
>>
>> - Fixed the Golden Wrench not having an offset when using minimized
>> viewmodels
>>
>> - Fixed the Private Maggot Muncher hiding the Soldier's hat when equipped
>>
>> - Fixed the Medic's auto-call feature not including enemy Spies disguised
>> as the Medic's team
>>
>> - Fixed The Lugermorph not displaying when inspected in the backpack
>>
>> - Fixed unusual effects on the Brass Bucket rendering in the wrong spot
>>
>> - Fixed Mann vs. Machine late-join failing for parties of two or more
>>
>> - Fixed the Short Circuit orb not changing particle color after being
>> deflected
>>
>> - Fixed the Short Circuit orb not being able to destroy rockets/grenades
>> during the first 0.25 seconds of their lifetime
>>
>> - Updated models and materials for the Private Maggot Muncher
>>
>> - Updated the localization files
>>
>>
>>
>> ___
>> To unsubscribe, edit your list preferences, or view the list archives,
>> please visit:
>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
>>
>>
>
> ___
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
>
>
___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


Re: [hlds] Mandatory Team Fortress 2 update released

2018-04-12 Thread Alex Kowald
Heads up, you left your debug prints in when a player is healed. It can
produce quite some spam in the server console.

On Thu, Apr 12, 2018 at 7:42 PM, Eric Smith  wrote:

> We’re released a mandatory update for Team Fortress 2. The notes for the
> update are below. The new version number is 4462894.
>
>
>
> -Eric
>
>
>
> -
>
>
>
> Matchmaking Changes
>
> - The initial load time into a match no longer counts against a player's
> abandon timer
>
> - Changed the timeout before a missing player is marked as having
> abandoned a competitive match to be three minutes from the first time a
> player disconnects from the server, rather than from the moment the match
> is formed
>
> - Queue times should now be significantly faster when dealing with large
> numbers of placement and recently-placed players in queue
>
> - Moved the Competitive MMR change notification so it no longer overlaps
> your rank
>
> - Fixed continuing to receive the prompt to rejoin a match after you have
> been dropped from said match
>
> - Fixed a case where players would receive a rank change in matches that
> dissolved due to abandon
>
>
>
> General
>
> - Added a stomp animation to Pyro that plays when coming down after
> blasting off from the Thermal Thruster
>
> - Added HLPugs.tf tournament medals
>
> - Added Gette it Onne! tournament medals
>
> - Added TFCL tournament medals
>
> - Added Copenhagen Games tournament medals
>
> - Fixed Medics having an accelerated Übercharge build-rate when healing
> full-health Snipers who are using The Razorback
>
> - Fixed being able to capture control points during setup time
>
> - Fixed the Golden Wrench not having an offset when using minimized
> viewmodels
>
> - Fixed the Private Maggot Muncher hiding the Soldier's hat when equipped
>
> - Fixed the Medic's auto-call feature not including enemy Spies disguised
> as the Medic's team
>
> - Fixed The Lugermorph not displaying when inspected in the backpack
>
> - Fixed unusual effects on the Brass Bucket rendering in the wrong spot
>
> - Fixed Mann vs. Machine late-join failing for parties of two or more
>
> - Fixed the Short Circuit orb not changing particle color after being
> deflected
>
> - Fixed the Short Circuit orb not being able to destroy rockets/grenades
> during the first 0.25 seconds of their lifetime
>
> - Updated models and materials for the Private Maggot Muncher
>
> - Updated the localization files
>
>
>
> ___
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
>
>
___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


[hlds] Mandatory Team Fortress 2 update released

2018-04-12 Thread Eric Smith
We're released a mandatory update for Team Fortress 2. The notes for the update 
are below. The new version number is 4462894.



-Eric



-



Matchmaking Changes

- The initial load time into a match no longer counts against a player's 
abandon timer

- Changed the timeout before a missing player is marked as having abandoned a 
competitive match to be three minutes from the first time a player disconnects 
from the server, rather than from the moment the match is formed

- Queue times should now be significantly faster when dealing with large 
numbers of placement and recently-placed players in queue

- Moved the Competitive MMR change notification so it no longer overlaps your 
rank

- Fixed continuing to receive the prompt to rejoin a match after you have been 
dropped from said match

- Fixed a case where players would receive a rank change in matches that 
dissolved due to abandon



General

- Added a stomp animation to Pyro that plays when coming down after blasting 
off from the Thermal Thruster

- Added HLPugs.tf tournament medals

- Added Gette it Onne! tournament medals

- Added TFCL tournament medals

- Added Copenhagen Games tournament medals

- Fixed Medics having an accelerated Übercharge build-rate when healing 
full-health Snipers who are using The Razorback

- Fixed being able to capture control points during setup time

- Fixed the Golden Wrench not having an offset when using minimized viewmodels

- Fixed the Private Maggot Muncher hiding the Soldier's hat when equipped

- Fixed the Medic's auto-call feature not including enemy Spies disguised as 
the Medic's team

- Fixed The Lugermorph not displaying when inspected in the backpack

- Fixed unusual effects on the Brass Bucket rendering in the wrong spot

- Fixed Mann vs. Machine late-join failing for parties of two or more

- Fixed the Short Circuit orb not changing particle color after being deflected

- Fixed the Short Circuit orb not being able to destroy rockets/grenades during 
the first 0.25 seconds of their lifetime

- Updated models and materials for the Private Maggot Muncher

- Updated the localization files

___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


Re: [hlds] Mandatory Team Fortress 2 update released

2018-03-30 Thread Josh Russell
The Sandman baseball is impossible to pick up now and alien bombs weren't
rendering in a 2Fort_invasion match I was just in.

On Thu, Mar 29, 2018 at 8:40 PM, John Schoenick 
wrote:

>  We've released a mandatory update for Team Fortress 2. The notes for
> the update are below. The new version is 4442762.
>
> - John
>
> 
>
> - Added smoke to the Punk's Pomp
> - Made the Sky High Fly Guy and The Hot Case paintable
> - Fixed the Short Circuit still performing its old area-of-effect attack
> when firing
> - Fixed Scouts taking to the skies
> - Fixed thumbnail for ctf_foundry
>
>
> ___
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
>
___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


[hlds] Mandatory Team Fortress 2 update released

2018-03-30 Thread John Schoenick
We've released a mandatory update for Team Fortress 2. The notes for
the update are below. The new version is 4445080.

- John



- Updated model/materials for the Starboard Crusader and added a second
style
- Added AsiaFortress Season 13 medals
- Updated the localization files
- Fixed Mann vs. Machine matches with open slots not receiving late-joiners
- Fixed a server crash related to the Sniper Rifle
- Fixed the "View promotional codes" button not showing for those users
with promotional codes


Notes missed from Competitive Revamp update
- The UI version has been bumped to 3.  Any UI mods will need to be
updated to work with the new UI changes.


___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


[hlds] Mandatory Team Fortress 2 update released

2018-03-29 Thread John Schoenick
 We've released a mandatory update for Team Fortress 2. The notes for
the update are below. The new version is 4442762.

- John



- Added smoke to the Punk's Pomp
- Made the Sky High Fly Guy and The Hot Case paintable
- Fixed the Short Circuit still performing its old area-of-effect attack
when firing
- Fixed Scouts taking to the skies
- Fixed thumbnail for ctf_foundry


___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


[hlds] Mandatory Team Fortress 2 update released

2018-03-28 Thread Eric Smith
We've released a mandatory update for Team Fortress 2. The update notes can be 
found using the link below. The new version number is 4439428.

http://www.teamfortress.com/post.php?id=38643

Thanks.

-Eric


___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


[hlds] Mandatory Team Fortress 2 update released

2017-12-21 Thread Eric Smith
We've released another mandatory update for Team Fortress 2. The new version 
number is 4294355. The notes for the update are below.

Thanks.

-Eric

-

- Fixed missing sounds for the new taunts
- Fixed a bug that prevented already-Festivized weapons from drawing their 
lights
- Updated materials/model for the Blast Blocker
- Updated the Heals for Reals medals so they can be painted

___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


[hlds] Mandatory Team Fortress 2 update released

2017-12-21 Thread Eric Smith
We've released a mandatory update for Team Fortress 2. The new version number 
is 4293828. The notes for the update are below.

Thanks.

-Eric

-

Happy Smissmas 2017!

- All players who play TF2 during the event will receive a Stuffed Stocking as 
a gift! Stockings contain goodies for good little Mercenaries.
- Event runs through January 10th, 2018
- Added the Winter 2017 War Paint Case
- Contains 15 new community-contributed War Paints
- Randomly dropped for players who have activated a Jungle Inferno 
Campaign Pass 
- Added the Winter 2017 Cosmetic Case
- Contains 20 new community-contributed items
- The Festivizer can be found as a bonus drop when opening the case
- Added 6 new community-contributed taunts to the Mann Co. Store
- Taunt: The Skating Scorcher
- Taunt: The Bunnyhopper
- Taunt: Runner's Rhythm
- Taunt: Luxury Lounge
- Taunt: Surgeon's Squeezebox
- Taunt: The Trackman's Touchdown
- Expanded the list of weapons that can be Festivized!
- Ubersaw, Dragon's Fury, Amputator, Air Strike, Back Scratcher, 
Scotsman's Skullcutter, Bazaar Bargain, Black Box, Claidheamh Mòr, Crusader's 
Crossbow, Degreaser, Loose Cannon, Persian Persuader, Detonator, Brass Beast, 
Holy Mackerel, Loch-n-Load, Powerjack, Iron Bomber, Reserve Shooter, 
Disciplinary Action, Family Business, Shahanshah, Scorch Shot, Shortstop, Soda 
Popper, Rescue Ranger, Tomislav, Panic Attack, Winger
- Mann Co. Store winter sale!

General

- War Paints can now be used for Mann Co. Trade-Ups
- Fixed a rendering issue with the Misty Skull unusual effect
- Fixed a case where it was possible to use the Thermal Thruster twice in one 
launch
- Fixed the inspect animation for the Shortstop
- Fixed the Festive Sandvich not showing the bite mark when eaten
- Increased the maximum number of backpack slots to 3000 (from 2500)
- Added the UGC Highlander Season 21, Highlander Season 22, Highlander Season 
23, 6v6 Season 23, 6v6 Season 24, 6v6 Season 25, 4v4 Season 10, 4v4 Season 11, 
and 4v4 Season 12 tournament medals
- Added Ready Steady Pan Season 3 tournament medals
- Updated cp_mercenarypark
- Added a forward spawn for BLU when attacking the final control point
- Added a connecting stairwell to the mid-structure of the final 
control point
- Fixed area portal rendering issues between the first and second 
control points
- Updated pd_watergate
- Respawn times of the teams will change dynamically based on the 
difference in scores. This should help balance any extreme differences in the 
team skills/scores.
- <50% difference in scores: 8s for leading team, 4s for 
trailing 
- >50% difference in scores: 12s for leading team, 0s for 
trailing 
- Equal scores: 6s for each team
- Relocated the player beer pickup counter on the HUD to the lower 
left, but made it slightly larger
- Updated the soundscape to have more alien-y sounds in the main areas
- Adjusted detail in the center and spawn rooms
- Adjusted clipping around the map



___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


Re: [hlds] Mandatory Team Fortress 2 update released

2017-12-13 Thread Tyler Bramfield
https://steamcommunity.com/app/440/discussions/0/2906376154311411808/

On Wed, Dec 13, 2017 at 6:56 PM, Eric Smith  wrote:

> We've released a mandatory update for Team Fortress 2. The new version
> number is 4280740. The notes for the update are below.
>
> Thanks.
>
> -Eric
>
> -
>
> - Fixed a client crash related to viewing notifications
> - Fixed being able to interrupt taunts using the ConTracker commands
> - Fixed a bug with the Medi Gun not staying attached to players
> - Fixed a bug with the Backburner using its owner's angle to determine
> whether the attack is behind the victim
> - Fixed a rendering issue with the Spectral Swirl unusual effect
> - Fixed not being able to fire the Dragon's Fury in some areas (e.g. the
> control point on Nucleus)
> - Fixed not being able to light Huntsman arrows with the Dragon's Fury
> - Fixed Dragon's Fury projectiles not fizzling when hitting water
> - Fixed not being able to detonate stickybombs when switching to melee
> with secondary attack held down
> - Fixed the charge sound for the Stickybomb Launcher not stopping if the
> player switches weapons while charging
> - Fixed Quick-Fix Medics not properly following/mirroring the Pyro after
> launching with the Thermal Thruster
> - Fixed being able to shoot flares through objects like setup gates
> - Fixed the Pretty Boy's Pocket Pistol always giving 7hp per-hit
> - Fixed the Winger not counting towards the Scout achievement "Gun Down"
> - Fixed the Festive Sandvich not counting towards the Heavy achievement
> "Konspicuous Konsumption"
> - Fixed the Rescue Ranger not counting towards the Engineer achievement
> "Texas Two-Step"
> - Fixed the Genuine version of the Flying Guillotine having no taunt
> - Updated the Vita-Saw so victims spawn random internal organs on hit
> - Updated the Atomizer damage penalty vs players to -15% (from -25%)
> - Updated the party system so invites are shown to all party members
> - Updated the Thermal Thruster stomp damage on other players to be 3x the
> base fall damage - not the reduced fall damage of the owner
> - Updated the "With Friends Like these..." achievement to check for five
> friends instead of seven
> - Added the Heals for Reals 2017 community medals
> - Added the "Philanthropist's Indulgence" community medal for Random Acts
> of TF2
> - Added the "Spectral Snowflake" community medal for the Nightmare Before
> Smissmas 2017 community showcase
>
>
> ___
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
>
___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


[hlds] Mandatory Team Fortress 2 update released

2017-12-13 Thread Eric Smith
We've released a mandatory update for Team Fortress 2. The new version number 
is 4280740. The notes for the update are below.

Thanks.

-Eric

-

- Fixed a client crash related to viewing notifications
- Fixed being able to interrupt taunts using the ConTracker commands
- Fixed a bug with the Medi Gun not staying attached to players
- Fixed a bug with the Backburner using its owner's angle to determine whether 
the attack is behind the victim
- Fixed a rendering issue with the Spectral Swirl unusual effect
- Fixed not being able to fire the Dragon's Fury in some areas (e.g. the 
control point on Nucleus)
- Fixed not being able to light Huntsman arrows with the Dragon's Fury
- Fixed Dragon's Fury projectiles not fizzling when hitting water
- Fixed not being able to detonate stickybombs when switching to melee with 
secondary attack held down
- Fixed the charge sound for the Stickybomb Launcher not stopping if the player 
switches weapons while charging
- Fixed Quick-Fix Medics not properly following/mirroring the Pyro after 
launching with the Thermal Thruster
- Fixed being able to shoot flares through objects like setup gates 
- Fixed the Pretty Boy's Pocket Pistol always giving 7hp per-hit
- Fixed the Winger not counting towards the Scout achievement "Gun Down"
- Fixed the Festive Sandvich not counting towards the Heavy achievement 
"Konspicuous Konsumption"
- Fixed the Rescue Ranger not counting towards the Engineer achievement "Texas 
Two-Step"
- Fixed the Genuine version of the Flying Guillotine having no taunt
- Updated the Vita-Saw so victims spawn random internal organs on hit
- Updated the Atomizer damage penalty vs players to -15% (from -25%)
- Updated the party system so invites are shown to all party members
- Updated the Thermal Thruster stomp damage on other players to be 3x the base 
fall damage - not the reduced fall damage of the owner
- Updated the "With Friends Like these..." achievement to check for five 
friends instead of seven
- Added the Heals for Reals 2017 community medals
- Added the "Philanthropist's Indulgence" community medal for Random Acts of TF2
- Added the "Spectral Snowflake" community medal for the Nightmare Before 
Smissmas 2017 community showcase


___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


[hlds] Mandatory Team Fortress 2 update released

2017-12-01 Thread Eric Smith
We've released a mandatory update for Team Fortress 2. The new version number 
is 4264764. The notes for the update are below.

Thanks.

-Eric

-

- Added the Chapelaria 6v6 Season 3 tournament medals
- Contract loaner items no longer have an expiration date
- Players viewing their ConTracker can no longer move or attack
- Fixed the main menu not updating its layout after a resolution change
- Fixed the Engineer's ConTracker animation
- Fixed the Medic, Sniper, and Engineer not un-hiding their weapons at the end 
of the ConTracker animation
- Fixed item collections sometimes incorrectly marking items as owned
- Fixed rendering issues with the Infernal Flames, Infernal Smoke, Cloudy Moon, 
It's A Secret To Everybody, Ancient Eldritch, Eldritch Flame, and Death by 
Disco unusual effects
- Updated the materials for Mandrew's Munificent Mug

___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


[hlds] Mandatory Team Fortress 2 update released

2017-11-17 Thread Eric Smith
We've released a mandatory update for Team Fortress 2. The new version number 
is 4246944. The notes for the update are below.

Thanks.

-Eric

-

- Fixed the scoreboard not displaying the proper images for Jungle Inferno 
Campaign Pass owners
- Fixed a Pyro animation bug related to jumping
- Fixed the Spy-cicle not giving the Spy fire immunity
- Fixed the animation for The Second Banana plate
- Fixed a Scout bug where mini-crits were granted to weapons other than The 
Atomizer while jumping
- Added the Titanium Tank Participant Medal
- Updated the Mann Co. Store to support the new foreign currencies added to 
Steam
- Updated the localization files
- Updated pl_enclosure_final
- Fixed a buildable area in BLU spawn for stage 1
- Updated materials for foliage props
- Updated plr_bananabay
- The train will now pass at its maximum frequency after both payloads 
make it up the large hill
- Fixed players getting pushed into the underwater tunnel and ceiling 
over right spawn exit
- Fixed spawn gates trapping enemy players
- Amplified train engine sound
- Reworked left spawn exit
- Added small barrier near final cap
- Improved performance in some areas
- Reduced push force near outer rocks
- Updated cp_mossrock
- Fixed small area where Engineers could build in initial BLU spawn
- Fixed area where you could fall in the pit and not die
- Fixed cases where you could block the train without dying
- The train now doesn't kill you if your toe touches it
- Optimized FPS around the last point. Should be significantly better.
- Brightened the underside of last point slightly
- Improved clipping around the ramp to last point
- Fixed a case where your view would glitch out on the sign near cap A


___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds


  1   2   3   4   5   6   7   >