Team Fortress 2 Update Released

Discussion in 'Team Fortress 2 Talk' started by tf2.com, Jun 7, 2018.

  1. tf2.com

    tf2.com L11: Posh Member

    Messages:
    843
    Positive Ratings:
    481
    An update to Team Fortress 2 has been released. The update will be applied automatically when you restart Team Fortress 2. The major changes include:
    • 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

    Read on the TF2 Blog...
     
    • Thanks Thanks x 1
    • Like Like x 1
  2. FishyUberMuffin

    FishyUberMuffin War Paints Everywhere

    Messages:
    943
    Positive Ratings:
    155
    I really like this update for 3 main reasons.

    R_Screenoverlay

    Achievement Restart

    Matchmaking ban

    First the R_screen. This should fix the problems with the overlays from overlapping one another and not letting people pick their gamemode for casual or missions for MvM.

    Achievement Restart. This is good if you are on an old account and you did all your achievements on a Achievement Sever when you first played TF2 and now you want to do it the proper way.

    The matchmaking bans. This is so great because of if a person is being not fun to play with now you can stop him or her from being unfun for the rest of the community for a short while. I wished that they would have told us on how long that they were banned for but oh well. I have said something towards this on Casperr's video on the Elo system. Now it's not 100% what I said but it's a start. However I wished that game would 100% do the ban and not rely somewhat on people reporting due to if it's a person with a group that is being unfun to play with then. That person's group could attack the people in the last known game that the person who was being unfun to play with. With my system nobody would be blame for reporting the non fun player and nobody would be attacked. But hey this is a good starting point.

    Casperr's Elo Video:
    View: https://youtu.be/_50sadMaN0g
     
    • Agree Agree x 1
    • Respectfully Disagree Respectfully Disagree x 1
  3. XEnderFaceX

    XEnderFaceX L3: Member

    Messages:
    149
    Positive Ratings:
    34
    Good Update!
     
    • Agree Agree x 1
  4. Da Spud Lord

    aa Da Spud Lord L0: Crappy Member

    Messages:
    703
    Positive Ratings:
    484
    I did not know that was a bug, thought they just nerfed the Sandman really hard.
     
  5. FishyUberMuffin

    FishyUberMuffin War Paints Everywhere

    Messages:
    943
    Positive Ratings:
    155
    I didn't know that was a problem at all. I never use the darn thing. XD
     
  6. Da Spud Lord

    aa Da Spud Lord L0: Crappy Member

    Messages:
    703
    Positive Ratings:
    484
    Did they decrease the allowed frequency of commands sent to the server? Because one of my scripts now causes me to get kicked from Casual servers for too many commands, when it definitely did not before.
     
  7. turtleboy666

    aa turtleboy666

    Messages:
    65
    Positive Ratings:
    37
    Yeah, I think they're doing that to combat lagbots
     
  8. Izotope

    aa Izotope Never releases maps

    Messages:
    613
    Positive Ratings:
    572
    What script is that?
     
  9. savvaisnotagirlolbbq

    savvaisnotagirlolbbq L2: Junior Member

    Messages:
    53
    Positive Ratings:
    36
    Thank god, I missed the memorable quotes like "I love my ball".
     
    • Agree Agree x 2
  10. Da Spud Lord

    aa Da Spud Lord L0: Crappy Member

    Messages:
    703
    Positive Ratings:
    484
    So I have a custom weapon switcher script. It allows me to scroll through my weapons 1-3 without PDAs or action slot items, as well as enable specific scripts for specific weapons. The easy way of doing this uses the "slot*" commands being constantly rebound on the mouse wheel every time I switch weapon. The problem is, the "slot*" commands are used by many community servers for menu navigation and voting, so sometimes I find myself accidentally voting or selecting a menu item when I really just want to switch weapons. To overcome this, instead of using the "slot*" commands for my scroll wheel, I used the "use" command (not to be confused with "+use"). The "use" command accepts a single argument, which is a weapon class (ex: "use tf_weapon_scattergun"), and will switch to that weapon if you have it equipped in your loadout. This requires a lot of commands though, as you have to add a separate "use" command for every single weapon that could possibly be in any slot 1-3.
     
  11. ics

    aa ics http://ics-base.net

    Messages:
    673
    Positive Ratings:
    416
    Yes, they did some changes to how commands are processed due to these lag and crash bots there have been in the last months. Now you cannot send too many commands at a certain timeframe. If your script gets you kicked, i think its time to refine it, as it might have increased network lag unintentionally before.
     
  12. [Rx.] Christian Troy

    [Rx.] Christian Troy L4: Comfortable Member

    Messages:
    172
    Positive Ratings:
    49
    Gee nothing could go wrong with this can it? Looks like we already got one person ready to abuse it.

    Aside from that, has any other server owners noticed that servers are sending and receiving more now after this update? Over the weekend I waited until all players logged off and noticed my servers are sending and receiving more idle traffic than normal. I haven't figured out yet what more is being sent out and received though. All I know for now is it being sent out and received from Valve at this time. I don't have any limits or caps myself from the ISP for the servers but other server owners do. This may or may not cause some problems in that area.