I've noticed some small bugs & issues after release as well, caught up on some sleep and will fix those asap and post an update.

The Ranked Bar thing I didn't even realize was broken because I didn't actually play the game besides some MM without having those elements modified :P And the entire end of round panel needs to be the same as what I initially had for the MM beta, which looks way prettier!

With a grand total of 6 hours of sleep combined in the past 3 days all the Matchmaking and Meat your Match stuff has been added, customized and tweaked to be consistent with the rest of WietHUD.

(Purple & Blue theme active in Clientscheme.res | Default Theme in the download is Black/Gray!)

https://pbs.twimg.com/media/CnMv8jzXEAAAOq4.jpg:large

http://i.imgur.com/EVOE3Pe.jpg

https://pbs.twimg.com/media/CnMwUdTW8AIIeAY.jpg:large

Changelog
Download

Looks nice! Without me having played any Overwatch I don't see the need to use this, but props for the effort you put in!

I would recommend setting up the hudanimations_manifest so this hud is less likely to crash on future updates (in addition to #base)

lobbycontainerframe and lobbypanel have been split up into _comp, _casual and _mvm #base versions, check if those add checkboxes

#based update :D

The main menu consists of 2 files:

/resource/ui/mainmenuoverride.res // Where things are positioned, what things look like
/resource/gamemenu.res // Defines actions for the buttons defined in the aforementioned file

Update/remove an old GameMenu.res and there should be no/less crashes.

Working on an update, removing a lot of stuff from the main menu that Valve removed, tweaking the (un)ranked Lobby screens and fixing some MM stuff and the newly added panels.

A temporary fix to get things to work again* is adding a info.vdf to the WietHUD root folder with the following contents:

WietHUD
{
	"ui_version"	"1"
}

* Main Menu might/will be broken, still requires extract_base_hudfiles.bat to be run for other files to update the hud.

@ Tambo Update your HudPlayerHealth.res file (the PlayerStatus_RuneWarlock got renamed to something different)

@ Degu have them use the same border that is used for the player panels (TFFatLineBorderRedBG & TFFatLineBorderBlueBG)
And I see you found the icons I made for the different mediguns

Unusual Weapon prices in donations are completely wrong, as seems to be the case with almost all (strange) skins.

For the /donations overview times when the donation was submitted might be nice to see if it's your page and logged in.

resource/ui/mainmenuoverride.res and the color in clientscheme.res if it's not hard set rgba values

I'll mention sv_cheats 1; vgui_drawtree 1 and ticking Highlight Selected once more for figuring out which elements are which to possibly help pinpoint which files and elements are responsible for what you see on screen to be able to answer simple questions which have been answered before anyway.

Use pin_to_sibling for the letters in front/after the labels and just have the shortkeys hidden off screen, using auto_wide_tocontents for the actual text label with a bgcolor together with the pinning will work regardless of language and look good if used properly.

@ kane: HudMatchStatus.res has the ObjectiveStatusTimePanel with a TimePanelValue which is the timer on top (and also used for the king of the hill timers)

@ Medico, could you specify the shortcuts to certain buttons? I guarantee you that in 99% of those cases adding an offscreen hud element with a command with an ampersand letter combo (&d) will work fine to have shortkeys in those hud files (and allows it to work regardless of language!)

You pin the class images in the file to each other (spy to sniper, sniper to medic, medic to engineer, engineer to heavy etc.) and then you pin the scout to the list of items on the left.

Using positive xpos values will offset them from each other when using "pin_corner_to_sibling PIN_TOPLEFT" and "pin_to_corner_sibling PIN_TOPRIGHT"

Clientscheme.res (compare the default file and check which ones you're missing)

If you really want to stay up to date a #base setup with the default clientscheme and applying your changes to fonts/borders/colors would make things a lot easier to maintain.

This issue with the overlapping class images in the charinfoloadoutsubpanel can all be fixed with pin_to_sibling and then works regardless of resolution and aspect ratio.