Sniper Pyro Scout Soldier Engineer Medic Heavy Demoman Spy

TF Team

For general feedback about the game.

Steam Support

Visit the support site for any issues you may be having with the game or Steam.

I'm gonna be all over ya like shingles

May 5, 2009 - Eric Smith



Also, a quick note: The fine fellows at Gang Garrison have just released version 2.1 on their webpage. We played a bunch of 2.0, and can't wait to spend some time with the new update. There's a ton of new additions, from Control Point mode to Killcams to Manviches, so even if you've played it before, you should head over there and check it out!

You better hold onto your head, mate

May 5, 2009 - Robin Walker



The Sniper has been a tricky class to update. In particular, designing an alternative to the Sniper Rifle has been a challenge. To understand why, we need to go back, way back, into the mists of time, when dinosaurs roamed the earth, and we started working on TF2. If it helps, you can listen to the Doctor Who Theme while you read.

In our multiplayer FPS games, players tend to die a lot. Death is one of the great feedback mechanisms we have in the game, helping you evaluate your own skill versus that of your opponents, and the viability of the tactics being employed by each of you. Being hopeless optimists, we'd like your deaths to be positive experiences. When we started working on TF2, 22 years ago, we decided to examine the things that affected how players felt about their deaths in TFC. Our starting theory was that, for death to be a positive experience, players had to feel like they could have avoided dying if they'd done something different. We found two factors that seemed to be important in light of that theory:

  • The first was whether or not you understand what killed you. If you don't know what killed you, that death is failing in providing you the feedback it's supposed to, and you won't be able to figure out what you could have done differently. Unsurprisingly, we saw that these deaths were highly aggravating to players, and in sufficient number caused new players to stop playing entirely. Trying to reduce the number of these deaths in TF2 was done through a variety of changes. It was one of the reasons why we chose to remove the hand-held grenades that each class had in TFC, which were one of the primary causes of these deaths. It was one of several goals that led to the creation of the freezecam.
  • The second was whether you felt you were actually engaged with the person who killed you. Dying to someone you weren't engaged with, especially when you were already engaged with someone else, was aggravating. Even worse was dying to someone who you couldn't have engaged with, even if you chose to. In that case, you're very unlikely to believe you could have done anything differently to survive.

In particular, the second seemed to be the root cause of the hatred of Snipers. You're often killed by them while you're engaged with an enemy in the foreground, and most of the time the Sniper is so far away it feels like you couldn't have dealt with him even if you didn't have enemies nearby. In fact, the Sniper's goal is to create that relationship: he specifically wants to fight enemies outside their engagement range, because that's his primary advantage.

Which brings us back to the Sniper Rifle unlockable. In an effort to reduce some of the aggravation that other players feel towards the Sniper, we chose the goal of designing an unlockable that encouraged the Sniper to get a little closer to his target. We want him to give up some of his primary advantage in return for something else, so that enemies he kills feel like they were engaged with them, and feel like they could have survived if they'd just managed to fight a little better.

Wave goodbye to yer head, wanker

April 2, 2009 - Greg Cherlin

It's been a couple of weeks since we posted, so we thought it'd be good to do some housekeeping. The next class pack will focus on the Sniper. It's actually shaping up to be the largest TF2 update yet, with multiple new maps and a bunch of gameplay tweaks. In addition, we've got another update in the works that should be done before the Sniper, and that one will include some new content for all classes.

The XBox 360 update is still being worked on. If you're wondering what's taking so long, since the content is "done" on the PC already, it's mostly been around fitting it all onto the XBox. The original version of TF2 in the Orange Box was very close to the XBox's memory limit, and all the additional TF2 content we've produced has pushed well beyond it. We've found a couple of nifty ways to get back a bunch of that memory, but it's turned out to be a lot of work, and that's what most of our time is being spent on. In the meantime, we're going to get a code update out to address the server cheating that's going on.

Like many other folks online, the TF2 team has been loving the Top 10 TF2 Plays of the Week videos that Push Gaming has been doing. If you haven't seen them yet, you can catch week 1, and week 2. We're hoping for a third one soon, but we can't really complain. If we were doing them ourselves, you'd probably see the third one sometime next year. While waiting though, you can check out the exploits of some of the Sniper's countrymen in the second frag video of Aussie clan Mad Dogz.

A sneak preview of the next class update!

April 1, 2009 - Robin Walker


And that's what ye git fer toochin that!

March 12, 2009 - Robin Walker

One of the things we've been thinking about for a while now is how to improve the player experience around finding a server to play on. It's a tricky problem because our master servers need to ask a game server for its details, and that server can lie to us if it wants to. We decided we needed to find a way of scoring servers, with a goal of finding and delisting ones we considered "bad". The scoring system had to penalize lying without penalizing custom game rules, because some players like custom game rules. Best case, the system needed to work entirely from data that didn't come from the servers themselves, so they couldn't lie to us in any way to affect it.

After kicking around some proposals, we came up with a simple system built around the theory that player time on a server is a useful metric for how happy the player is with that server. It's game rules agnostic, and we can measure it on our steam backend entirely from steam client data, so servers can't interfere with it. We already had this data for all the TF2 servers in the world, allowing us to try several different scoring formulas out before settling on this simple one that successfully identified good & bad servers:

  • New servers start with a score of 0 points
  • Each time a player connects to a server, it loses 15 points
  • For each minute the player stays on the server, it earns 1 point (up to a max of 45 points per player)

In short, servers that have lots of players joining & leaving rapidly will score badly. Servers that consistently have players join and stay on for long periods of time will score well.

Here's a graph showing server scores for all the TF2 servers in the world as of last week. For the purpose of scoring, we ignored all password-protected servers, and all servers that had fewer than 200 connections a day. The blue line in the graph represents the scores for all the TF2 servers. The red line is the matching player connection count for each server.



As you can see, the bulk of servers in the world are doing a pretty good job of providing an experience that's expected by the people joining them. More importantly, it's really easy to see what servers are bad. Overlaying the number of players connecting to the servers illustrates how nasty an effect these bad servers are having on players. The very worst servers attract a large number of connections, mostly because they're lying in ways that make them look like a very attractive server at all times.

Our first step in improving this part of the player experience has been to delist all the really bad servers. The master server will simply stop giving these to you when you fire up the serverbrowser. After that, we're going to keep improving our ability to measure this kind of problem.