-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TF2] MvM bots missing names in the kill feed #3958
Comments
Always wondered why this happened. This makes a lot more sense now. |
Should be fixed in the next update, thanks! |
@kisak-valve Just to confirm, would the above comment constitute a 'Reviewed' tag for this issue? |
Hello, per "Fixed bots not displaying the correct names" in the 2022-07-07 Team Fortress 2 update, please retest this issue. |
I think it fixes the issue that made it infinitely more consistent (casual name change limits), but I do recall TFBots appearing in the killfeed being a longstanding issue, just much more uncommon. |
Possibly, this was my 2nd game after the update, I have not had time to play since. |
In the day of the update the names were fixed for me but yesterday when I played MvM they were back to TFBot |
Regarding the lag, that is being experienced every time a large squad of robots spawn in their spawn area, is it possible that the recent updates for MvM have made the lag worse? The bots' missing names have so far been partially fixed, since it has been both observed (#number)TFBot and their intended names. I am wondering if the fix makes the gameservers struggle, if the lag is indeed worse. |
How's this been going for others btw? I've noticed that since the summer updates this is still happening but much, MUCH less frequently than before! (down from about every other bot to 1 in 5-10 I'd say) |
Bug has reverted to pre 6/21/22 behavior. Names still occasionally break as per behavior since 6/24/20 patch (mainly affects Valve dedicated servers). |
Some MvM bots are missing their names. Their names show up for example as (20)TFbot in the kill feed.
The text was updated successfully, but these errors were encountered: