I would start by actually updating your resource/econ/backpackpanel.res from the default one and actually add in the page numbers, they allow for the hovering over the number while dragging an item to change to that page.

The Hitmarker is a hud animation thing utilizing the DamagedPlayer event, making elements appear and/or change color.

There has to be if you made that screenshot, if it's not there, same trick still applies if you modify the default file or one from a different hud.

Looks good!
I can however see one issue: The disposable mini sentry form MvM will overlap with the build/destroy menu

ClassLoadoutPanel.res > modelpanels_kv
change text_ypos to a value so it is outside of the panel or change tall to 0 for namepanel

MainMenuOverride.res is the file you're looking for

1. Set the following launch option and start TF2

   • -default

2. When in the main menu: host_writeconfig to generate a new config.cfg with default settings
   
3. Quit game, sync config to cloud
   
4. Remove the -default launch options and replace with

   • -autoconfig -dxlevel 95

5. Relaunch game to set up your video and audio settings
   
6. Quit again, sync config to cloud & remove every launch option set previously, replace them with:

   • -novid -high

@chostarman Check the tall and ypos values for CMainTargetID (looking at someone/buidling), CSecondaryTargetID (when being healed) & CSpectatorTargetID (when dead and spectating and tf_spectator_target_location is set to 0) and also the position values inside targetid.res

Don't use the high quality item images or at least don't mess with the size of the model ones, I've found out from experience (valve messed this up at Christmas when they introduced more festive weapons)

I think my implementation in WietHUD is quite clean, based on Mannterface. The files you're looking for: SpectatorTournamentGUIHealth.res & SpectatorTournament.res (the full width HealthIcon in playerpanels_kv)

@JarateKing I explained a little and linked your example image in the last post on the previous page

It's a shame my hud (shameless plug for WietHUD) is being put together with the 'looks like default' most of the time.

True, it does look like it, but code wise it has found a lot of groundbreaking stuff you see used in huds used these days (#base, hudanimations_manifest, high quality item images) and made a lot of optimizations to the horrible code Valve has managed to churn out over the years. Visually the same != code wise the same.

chat_english is very cool to use, thanks for finding that one out! It has been used for every casting hud I've made and maintain (tftv, blackouttv, tflivetv)

Very hyped to do production for this, can't wait to show off the new ingame score overlay!

Nicell, center the PlayerStatusHealthBonusImage in the health element (spectatortournamentguihealth), which should be taking up the full width of the playerpanel_kv

To lower from the outside pin an element to the side of the bonus image (pin_to_sibling) so it 'covers' up the background, darkening it and making it look like an actual healthbar.

If you have the correct offset (centered bonus image) you can move 1 half of the player panel off screen for each side so you get only on side visible.

More here in Jarateking's post about the health bars.

For the ThinBorder: ClientScheme.res?

A link to the plugin thread or download might help ;)

EventPromo is the element your looking for

Wrong thread, try here

There are some times I love doing TF2 camerawork:
https://clips.twitch.tv/SincereTacitPepperTBCheesePull
https://clips.twitch.tv/IronicLivelySpiderTinyFace

hud_reloadscheme doesn't work for main menu, change mat_antialias from 1 to 2 and back to reload it.

Also you should edit your previous post instead of having 5 with the same/similar question

For EU viewers, this is 12:00 CEST!

It looks like I removed a line from HudPlayerClass.res possibly enabling those.

I'm updating some files with more documentation and also referring to the Easy TF2 Crosshairs created by omni for more flexibility, as I do not provide (m)any but do support custom crosshairs with WietHUD; because that repo for all the crosshairs already exists and shouldn't be too hard to add.