Team Fortress 2 Patched, Spy Side-stabs Return
Gameplay alterations include adding a duck timer, re-enabling spy side-stabs, and a primary weapon default for disguises. Other various bug fixes round out the list. Take a gander at the full patch notes below:
Gameplay changes
- Added a duck timer that prevents duck spamming while running around on-ground
- In-air, players are only allowed to duck once before they touch ground again
- Fixed several bounding box issues with jumping, falling, and rocket jump air-walking. Bounding box should be much more accurate there now
- Increased backstab check so that Spies can side-stab again
- When disguising, Spies now always start showing the primary weapon in their disguise, and can then switch it with the last-disguise key
- Fixed flamethrower loophole that resulted in the flame effect being stuck on while the flamethrower wasn't really firing
- Fixed exploit that allowed players to circumvent the force-fire timeout on the pipebomb launcher
- Fixed a bug that caused Natasha's slow on hit effect to be inverted from 75% to 25%
- Restored sawmill_logs.mdl file, fixing some user maps that used it
- Fixed some localization issues with Scout achievement strings
- Removed the "Final" phrasing in the map loading screen
- Fixed a server crash on startup under Linux
- Fixed a buffer overflow issue related to network string tables
- Gamestats uploading is now done asynchronously. This fixes the client timeout issues on map changes
- Fixed an exploit where engineers could build a teleporter exit in an invalid area
- Fixed a few bad overlay assignments and other minor issues
-
redfive
replyOh good, side stab is back.
-
-
-
-
Yeah I think it has to do with lag. Kind of like how if say a heavy is shooting at you and you think you've avoided them by running around a corner, but you still die. Due to the lag your killer was still seeing you before you rounded the corner. Similar with the face-stab, you were already stabbed. Face-stabs may have been broken further than that though, not sure.
-
It has nothing to do with lag. It's an issue with the hitbox code in TF2. Valve has stated this before and they keep trying to hammer-down the bug in it.
The patch before this one made the hitbox "smaller" from behind for other classes when playing as Spy. So you had to be a bit more accurate when hitting with the knife.-
-
It has to do with how the character model moves in terms of speed and the hit registering precisely at that very second. They keep chipping away at it.
Eventually I think they will get it right...eventually :P
-
-
-
There's three ways to handle latency for cases like this (and I'm using a sniper rifle as an example):
* Attacker-side: If you were in my sights when I pulled the trigger, you were hit.
* Server-side: If you were still where I aimed when the server received the command to fire, you were hit.
* Victim-side: If you were behind cover when the server tells you I fired, you were not hit, even if I saw you in my sights.
Someone's paying the price for latency. In the first case, the victim pays for both the attacker's and the victim's latency (ducking behind cover only to get hit later). In the latter case, the attacker pays for the victim's and the attacker's latency (a clear shot misses and sparks the ground). In the server model, you only pay for your own latency (plus the server has the final say in who's standing where.)
Any clear answer on how backstabs are resolved?
-
Everything is already server side and the advantage goes to LATENCY, period. It can and does change on a whim and in two battles between the same players, it can be in the favor of each of them one time.
I love all you people complaining about lag NOW. Where were you 9 years ago when there was a chance to have actually fixed the hitboxes, hit detection / registration and netcode when it popped up in Counter-Strike?? Or at least really made Valve aware that it was an issue back then, not only now because finally more people fracking see it? :(
Valve can't fix the problem unless they revamp their netcode from the "high pings don't matter" mentality that has carried on since those days. Back when people didn't play Quake and UT because their high pings got them beat down by players with lower pings. Valve took a stance and said pings shouldn't matter.
Well, here we are today. Pings don't matter. You can have a 110 ping and be up against someone with a 30 ping, and the person with the lower ping can experience latency because of the crappy netcode.
Back stabs are resolved like everything else. Server registers the hit, checks where both players were on their end at time of attack, netcode factors in pings and the hit is registered. Even if you never even saw the attacker because there was so much latency their model wasn't drawn. And it can go both ways......you figure it out.
-
-
-
-
-
Of course, you're talking about gimping the Spy in the same update that added a ton of disguise buffs, which was preceded by allowing him to recharge cloak from any ammo lying around and then actually removing the telltale dispenser trail so he could just camp a dispenser, waiting for (and thus not helping the team in the meantime) one miserable Engineer to be alone so they could feel less than pathetic.
He's had a hefty net buff recently.-
We have, and we're still a solid 9th place. But don't worry. Or look behind you.
-
-
-
-
