Matchmaking Update

Discussion in 'Team Fortress 2 Talk' started by, Jul 22, 2016.

  1. L11: Posh Member

    Positive Ratings:
    Thanks for all of your feedback over the last couple weeks. In our previous post, we talked about a number of issues with the Meet Your Match update and what we were doing to address them. Here's a quick recap on what has happened since then:

    • We have been working hard to improve the matchmaking system, greatly reducing queue times and eliminating most causes of errors when attempting to play. On average, queue times are now below ninety seconds for most players. There are still some issues with lower population regions and game modes that we are looking into.
    • We have identified and corrected several issues where players weren't being sent to fill empty slots for in-progress matches. There should be far fewer matches where this happens, and we will continue making improvements here.

    • Casual Mode:
      • Players are now able to specify the maps they would like play on when using matchmaking. However, it is sometimes the case that players joining in-progress matches (aka "late join") end up on maps they did not select. This will be fixed in an upcoming update.
      • Abandon penalties have been removed, which means players can come and go as they please.
      • Vote-kicking has been added. Players that are kicked retain the experience they've earned to that point, in order to reduce the likelihood of players using the system to grief others.

    • Next, we would like to give you a quick overview of the things we are working on, and go over some of the issues you raise as needing more attention and work.

      Abandons in Competitive Mode:
      • We are going to make abandoning penalties much harsher. The current system increases matchmaking ban times based on the number of abandons over a period of time. We are making a change to more quickly move serial abandoners into really long ban times. We will also subtract the maximum number of rank points possible, per abandon. The amount lost will be far higher than what could normally be lost in a completed match.
      • In addition, we are investigating several options to offset the impact abandoners have on games that are in-progress. More on that when we have details to share.

    • Griefing in matchmaking:
      • We are working on systems that will give players with high numbers of in-game reports automated cooldowns from matchmaking, to discourage disruptive behavior.
      • As a side note, you can report players while in-game by clicking the "Report Player" button - located in the "Play" section on the main menu.

    • High ping and queue times:
      • There are still cases where players can wait longer than we'd like. This is more common in lower population regions and game modes in Casual Mode matchmaking, and the result is that players sometimes end up on a server where their ping is higher than normal.
      • One solution we are investigating is allowing matches to start with fewer than 24 players -- in cases where there are not enough available players to form a complete match, or when the players being considered are too far away. The system will instead prefer to start a smaller match more quickly, with a more appropriate ping, filling the remaining slots as more players become available.

    • Experience and incomplete matches in casual:
      • Right now, leaving a casual match results in no experience being earned. We are looking at changing this to avoid penalizing players for having to leave after investing significant amounts of time into a match, while still providing rewards for playing matches to completion.

    • We are monitoring the game around the clock, and we continue to read all your feedback and suggestions. Thanks again for taking the time to help improve TF.

    Read on the TF2 Blog...
    • Thanks Thanks x 2
  2. GroundCode_

    GroundCode_ L1: Registered

    Positive Ratings:
    I'm really into this transparency, but a majority of the TF2 community doesn't want casual to be improved... they want pubs back.

    Edit: Like a fourth of my friendslist, people who I know irl, have quit because they can't play "casually"
    • Agree Agree x 2
  3. Izotope

    aa Izotope Never releases maps

    Positive Ratings:
    While it sounds good, I am afraid some people will receive unjustified penalties for not doing anything wrong, but being reported for "fun" or other unreasonable reasons.
  4. Crowbar

    aa Crowbar perfektoberfest

    Positive Ratings:
    How high is the chance of meeting such "funny" people frequently enough to get banned because of this?
  5. Vel0city

    aa Vel0city func_fish

    Positive Ratings:
    Popular TF2 YouTuber siN made a Strawpoll. Kinda sums up people's experience with this update:

    Also: still waiting on the day they revert their Bison nerf and Quickybomb Launcher buff. Both were uncalled for, and the real troublesome weapons like Reserve Shooter, Airstrike, Beggar's Bazooka (the OP ones) and the Axtinguisher, Baby Face's Blaster, new Phlog (the UP ones) are left untouched, even though that's what people wanted the be changed the most.
  6. Pocket

    aa Pocket func_croc

    Positive Ratings:
    Yeah, giving users the power to punish other users without any oversight is a fucking terrible idea that will just lead to armies of trolls ganging up on people they don't like. Why the fuck has Valve not figured this out by now?
  7. CommodoreKong

    aa CommodoreKong

    Positive Ratings:
    B4nny was told by Valve that they were going to re-add the viewmodel FOV slider for comp matchmaking.

    I'm guessing we may finally be seeing Valve go in and fix the visual glitches you get when you set the viewmodel FOV to 70.
  8. Viperi

    aa Viperi Lord Procrastination

    Positive Ratings:
    Well now I feel threatened. Getting a cooldown for top scoring as Spy.
  9. CommodoreKong

    aa CommodoreKong

    Positive Ratings:
    If you watch the fully video they say they were told by Valve that the 54 viewmodel FOV lock was a temporary measure until they fixed the problems with the higher fov viewmodels. They think they'll fix the viewmodels up to FOV 70 but it doesn't sound like they know for sure.

    The talk about view models starts around 20 minutes in.
    • Thanks Thanks x 1