Press whatever key it's bound to and it will be brought to the foreground again (while in-game, not in the menu).

There should be an entry for it on Resource/UI/HUDDamageAccount.res, and you should probably clean up as well on Scripts/HUDAnimations_Custom (event DamagedPlayer and event Hitmarker).

Delete Resource/GameMenu and Resource/UI/MainMenuOverride.

I tried adding the class selection from QTCHUD to mine, but it's missing the black borders...

https://i.imgur.com/C15kYjh.png

... the original has:

https://i.imgur.com/Li4FtRH.png

It loads fine when the whole HUD is in there, but I'm not sure what's missing. Tried copying the classselection file and the whole vgui/replay/thumbnails/ folder, but it's not a missing texture.

-----

And another question: I changed my chat position with basechat.res' "HudChat" ypos/xpos, but it usually resets itself to the lower part, unless I do a hud_reloadscheme, which doesn't last for long.

Any helping hand?

My bet:

Oh, my apologies!

I didn't know this issue was shared by other HUDs, was just pointing out.

Oh boy, and here I was thinking I was being mentally challenged. Good to know.

Banana Bay does have some issues with the balcony at spawn giving snipers and sentries too much ground to cover, but even though the map layout can be overwhelming at first, it's quite fun to play. The best map to come out in the update imo.

Mercenary Park is all right for setting the theme of the update and all, but it's just another classic pub map with a lot of useless rooms and paths. Not sure how cramped it is because... pyros shooting fireballs everywhere.

Moss Rock up until the first point is a-okay, but contesting last is just a pain, and no route is better than the other, all very chokey. Who thought that recycling the "train blocks the defending team" feature from Freight was a good idea?

And as mentioned, 80% of Brazil is completely useless to the flow of the match, unlike maps such as Lakeside that the pool house offers some positioning.

bastHUD is missing the new entries on clientscheme as reported on huds.tf. By the way, do you know which line I need to edit in order to change the contracker's font?

And as I mentioned on the HUD edits thread, checking the notification on the main menu doesn't bring in any menus for us to click ok, such as new items.

I use bastHUD (updated by you) merged with a lot of other minor things. Since I touch on a few things, I was using the last updated version provided by you (prior to the jungle update), edited all my stuff in and have been using like that perfectly for a while. With this last update, I mainly updated lobbycontainerframe, lobbypanel, added the clientscheme entries for the contracker and deleted mainmenuoverride and gamemenu. I sticked to my old scoreboard file (which is not bast's, but was adjusted to work accordingly), hence me questioning why is that bugging out since there were no changes to it.

The pop-up bug I'd assume it's a menu issue that may be fixed when you get to it more thoroughly, but it's being a major annoyance.

Thanks for your attention! :)

My HUD's been fully functional so far, but since the jungle update hit, I updated the files provided by Hypnotize. But to no avail, the scoreboard has its class icons like this https://i.imgur.com/5f1RlK1.png and whenever I press 'ok' on a pop-up to see it, nothing comes up. I have to remove the HUD to be able to acknowledge the new items so it stops blinking and making the sound.

Those bugged icons happen both on the scoreboard and on that matchmaking panel that closes in. According to the repository, it seems that nothing was changed on the scoreboard.res file, but it was fine before and now it's like that.

Anyone happen to know a fix for these issues?

You're a wizard! Thanks!

Does anybody know which file I have to edit to fix this?

http://imgur.com/ZZRJaXG

Thanks in advance.

What more proof do you need that Valve has all the data they need, yet insist on doing things their own way? The very basics of 6's - being the core classes - Valve has decided to leave it as a "pick whatever you like, how many your team needs". They acknowledged there's a 6v6 format and a 9v9 format (you can see 9v9's going to become available in MM from the game files) yet they don't understand the gamemodes.

They've know for as long as comp TF2 exists the community thinks 1 demo and 1 medic are strong enough and yet they introduce MM with no class limits. And there you are thinking they'll hear complaints about weapons.

Besides that, I'm pretty sure they acknowledged how hard it is to introduce a new weapon to the game, despite the kids outcry for more. And yet - not sure if a moment of weakness or a hiatus of new content - they release them, some of which at their very core/context are unfixable. E.g.: The reserve shooter rewarding mini-crits for the enemy simply jumping was retarded, right? Wanting to deny what a scout is supposed to do... It was later changed, but how would you overhaul it? The weapon's idea is to deny jumpers. So unless you give it a serious cons on the side, it's unfixable. Valve has a lot on their hands with no idea of what to do with it.

So there we have it: a weapon system that, instead of being a list of situational, interesting and easy to understand choices, you have a f*ckfest of pros and cons, of which most new/casual players don't fathom or bother reading, and funny enough, even some veteran players may get caught out of the loop with the changes.

Following Slin's point on "let's use them all to show what's broken and why", I'd like to see some showmatches with no whitelist to showcase the banned weapons, followed perhaps with a post-game discussion to elaborate/explicit their flaws, rather than it being allowed in leagues. Especially if mid-season changes won't be allowed.

It's HUDItemEffectMeter_Heavy.res, shared with the heavy's rage meter.

I've seen "if_mvm" being used, but I didn't know which file controled that HUD element to even look it up, or if that would do the trick, hence me asking. I found that "TournamentConditionLabel" already has if_mvm visible set to 0, but it is visible - as shown in the screenshot -, so I don't know which snippet to look for.