Team Fortress 2
talvikarhu May 18, 2014 @ 3:16am
Weird %killername% bug.
I started playing TF2 again couple weeks ago and I've started noticing that sometimes, when I get killed, the name shows up as %killername% and above it it says %NEMESISNAME%

http://steamcommunity.com/sharedfiles/filedetails/?id=259814982
http://steamcommunity.com/sharedfiles/filedetails/?id=259241454
http://steamcommunity.com/sharedfiles/filedetails/?id=261084265

I've figured an inconsistent pattern, where this happens when I first get killed after launching TF2. Now, this doesn't happen every time, thus inconsistent, but it's the only pattern I've noticed. I hope this is the right place to report this, since the whole site feels so obfuscated.
< >
Showing 1-12 of 12 comments
sad but in a cool way (Banned) May 18, 2014 @ 3:28am 
Verify your files or reintall TF2
Sebenza May 18, 2014 @ 3:45am 
You're most likely using an outdated custom HUD. Update your HUD and things should be fine. If not, verify your files.
Aperture May 18, 2014 @ 5:44am 
Merasmus?

Maybe not.

COWER MORTAL FOOLS, MERASMUS HAS ARRIVED!!!!!

Whoa, I lost control of my body and WHAT IS THAT COMMENT?!?!?

RUN GUYS, HE HAS ZOMBIES!!!!!!
Rubik May 29, 2016 @ 9:41am 
I am also seeing this bug. I tried re-installing the game, but that doesn't help. For me, the bug is more likely to occur in MvM games, but it sometimes happens in standard games too. I am using the standard HUD.
fish Dec 26, 2017 @ 12:36pm 
Same, it happens in both MVM and Casual for me, and I've verified and reinstalled, and I am using a standard HUD as well
bga Dec 26, 2017 @ 12:40pm 
Originally posted by Lord Somnus:
Same, it happens in both MVM and Casual for me, and I've verified and reinstalled, and I am using a standard HUD as well
check the date my dude
Bazooks Dec 26, 2017 @ 12:41pm 
It is likely to occur in mvm, especially from deaths from getting crushed by tanks.
Crazy Gunman Dec 26, 2017 @ 3:25pm 
Check your config. The anti-aliasing and dx commands caused these strings to appear. Basically every command that can lag your gáme for several seconds might cause this bug.
Originally posted by Crazy Gunman:
Check your config. The anti-aliasing and dx commands caused these strings to appear. Basically every command that can lag your gáme for several seconds might cause this bug.
Check...the bloody....date....
Crazy Gunman Dec 26, 2017 @ 3:27pm 
Originally posted by Dimm Nogal:
Check...the bloody....date....

Why tho? People are still experiencing these problems. Spamming 'necro' or 'check the date' in every thread isn't helpful at all.
Mr. Venom Nov 11, 2020 @ 9:04pm 
Has this been fixed yet?
Ding Nov 11, 2020 @ 9:22pm 
Originally posted by Mr. Venom:
Has this been fixed yet?
No and likely wont
< >
Showing 1-12 of 12 comments
Per page: 1530 50

Date Posted: May 18, 2014 @ 3:16am
Posts: 12