I imagine they'd just change mp_tournament_stopwatch 1 to
mp_tournament_stopwatch 0 rather than changing how Stopwatch works.
You're on the server mailing list, there's an unwritten assumption that
you'd know about things like this.
On 7/15/2016 12:14 AM, Bartek S wrote:
If they change
If they change stopwatch mode code-wise without adding a cvar that defaults
to old behavior and is used with a different value for casual, all
stopwatch based games will be affected.
___
To unsubscribe, edit your list preferences, or view the list
You guys know this only affects Casual mode and not Competitive, right?
On 7/14/2016 11:08 PM, Bartek S wrote:
Original stopwatch mode is alright. The backlash you received for it
working as it does is from people who are not used to this. Comp
players, myself included, play stopwatch games
Original stopwatch mode is alright. The backlash you received for it
working as it does is from people who are not used to this. Comp players,
myself included, play stopwatch games DAILY and have no issues with the
games ending on stopwatch timeout. Also, if the attacking team goes over
the time
Making people play through the entirety of a game they've already lost
sounds like a really bad idea.
On Thu, Jul 14, 2016 at 6:34 PM, Jordan Olling
wrote:
> I rarely reply to these things, but I actually wasn't liking how entire
> areas of maps weren't seeing any action
We've released a fix for this. Your client should pick it up automatically.
-Eric
-Original Message-
From: hlds_linux-boun...@list.valvesoftware.com
[mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Ross Bemrose
Sent: Thursday, July 14, 2016 7:17 PM
To: Half-Life
I saw on Twitter that deleting casualcriteria.vdf fixes this problem.
You know, in case someone from Valve wants to fix that tonight.
On 7/14/2016 10:15 PM, HD wrote:
Yes I agree - TF2 is now Broken! lol
*From:*hlds-boun...@list.valvesoftware.com
Yes I agree - TF2 is now Broken! lol
From: hlds-boun...@list.valvesoftware.com
[mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of Thomas Deisinger
Sent: Thursday, July 14, 2016 10:08 PM
To: Half-Life dedicated Win32 server mailing list
Subject: Re: [hlds] Mandatory Team Fortress 2
So apparently after you turn the game off after the update you cannot turn
the game on again, crashes to desktop. Happening to anyone who restarts the
game.
On Thu, Jul 14, 2016 at 7:39 PM, Eric Smith wrote:
> We're working on a mandatory update for Team Fortress 2. The
I rarely reply to these things, but I actually wasn't liking how entire
areas of maps weren't seeing any action whatsoever because of the timer. I
like playing the full map, so I think I'll like this change. Let's try it
for a few days.
On Jul 14, 2016 6:08 PM, "Guess Who"
"Maps previously using the stopwatch timer will now play to completion,
regardless of the first team's time"
Please revert this. I know there's been some backlash to stopwatch mode for
casual matchmaking, but it's a purely reactionary thing from people who
aren't used to it. It's the only
We've released a mandatory update for Team Fortress 2. The notes for the update
are below. The new version is 3537953.
-Eric
- Updated Casual Mode
- Fixed a problem where in-progress games with open slots would not
receive
We're working on a mandatory update for Team Fortress 2. The notes for the
update are below. We should have it ready soon.
-Eric
- Updated Casual Mode
- Fixed a problem where in-progress games with open slots would not
13 matches
Mail list logo