where is the new contract stuff from tough break in rays hud?
nvm found it in hud animations

Can someone let me know how to change the numbers to smaller, closer and far up.

here is what i have

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

here is what i want it to look like

http://i.imgur.com/59acqIm.jpg

where do you move the numbers when you get a health pack or something like that?

talking about these.

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

i believe it's hudhealthaccount.res, the positioning is in hudlayout.res as CHealthAccountPanel

Did you find a fix for this?

Also, how can the green stat numbers in the scoreboard be fixed to not change color?

I was wondering where I could find the values to change to move the killstreak count away from the dominating image, and move the score directly under the score subtitle at the top, this is what it looks like now ~

http://imgur.com/SPZfxHG

Thanks!

Okay I'm back :D. How would you get these areas in the screenshot to any colour (e.g. black)?

This

Cheers! :)

Edit: Added the screenshot :D

In the Scoreboard.res 'LocalPlayerStatsPanel' you have to duplicate each non-Label:

// Default 'Kills' (goes with KillsLabel)											
		"Kills"
		{
			"ControlName"		"CExLabel"
			"fieldName"		"Kills"
			"font"			"ScoreboardVerySmall"
			"labelText"		"%kills%"
			"textAlignment"		"west"
			"xpos"			"180"
			"ypos"			"0"
			"zpos"			"3"
			"wide"			"35"
			"tall"			"20"
			"autoResize"	"0"
			"pinCorner"		"0"
			"visible"		"1"
			"enabled"		"1"
		}

You copy the first 3 lines and then add a 'visible 0' and a closing curly bracket and add 'Value' to the 'duplicated section where you define a FgColor (foreground color) to change the text color like so:

// 'Duplicate' the name, fieldName and then hide it (visible 0)
// Add 'Value' in the names on the new element and change color
		"Kills"
		{
			"ControlName"		"CExLabel"
			"fieldName"		"Kills"
 "visible" "0" // Hide the original value that turns green
}
		"KillsValue"
		{
			"ControlName"		"CExLabel"
			"fieldName"		"KillsValue" // Add 'Value' here and to the name
			"font"			"ScoreboardVerySmall"
			"labelText"		"%kills%"
  "FgColor" "TanLight" // Change color
			"textAlignment"		"west"
			"xpos"			"180"
			"ypos"			"0"
			"zpos"			"3"
			"wide"			"35"
			"tall"			"20"
			"autoResize"	"0"
			"pinCorner"		"0"
			"visible"		"1"
			"enabled"		"1"
		}

----------------------------------------

Add a 'killstreak_image_width' in the scores section in the top of your Scoreboard.res file

"scores"
{
		"killstreak_image_width" "15" // Default value
}

----------------------------------------

The file you need to open is 'Charinfopanel.res' and then the BackgroundHeader & BackgroundFooter sections.
- Remove the 'image' and add 'fillcolor_override" "Black"

Why would you duplicate them? You just change the name of the controlname and entity name from "kills" to "killsT" or something with a random letter at the end, Takes a lot less time.

wiethoofd uses the #base method for HUD editing, so replacing it would do no good. I think it's just a habit of coding, is all.

I duplicate them, just the actual name of the original value needs a visible 0 because it might be hidden by the new value you actually add to do the same job with a different color.

Having clear readable code makes it easier for someone else to maintain/modify, just good practice is all ;)

Yeah I know you duplicate them, that's why I asked why you do it lol. So it's literally just for legibility reasons, was curious if it was for some other reason. For the lazy, like me, it's nice and easy to only need to add a letter to get it working.

Would it be possible to use a #base file for it though, and have the original kills set to how you have it and then have a new definition in the #base file? I don't even know if there's a point in doing that, especially if I'm completely misunderstanding how #base files work.

is it possible to change the color of console text in sourcescheme

the text that's normally white that is (aka not errors)

base file just reads the original or whatever file you point it to, and then the one you edit overwrites it.

he has this weird system of using the tf2 base hud and recreating it to overwrite it instead of just overwriting it in the first place.

#base is really useful for modular concepts like health crosses/no crosses or crosshairs, but making the whole hud that way is a waste of time/effort imo

I used to think the same thing until I started digging deeper into using it. The fact that users can actually keep a HUD up to date with TF2 updates without having to wait for the HUD developer to release it. Because all the files *should* use #base, if they get updated, you just replace the file #base is reading it from using HLExtract or something similar.

It seems like more work, sure, but it can be quite handy. Just depends on if you want to bother with it, is all.

the average user isn't pulling the latest from HLExtract, they can barely check a github as is.

It doesn't come in handy at all for users trying to edit the hud, or add new things to it. It won't even prevent errors. When that witch hat bug happened, users still had to update the revised files, and when the scoreboard updated this tough break patch, the user would've also had to update the revised files or dealt with an ugly scoreboard.

Also that assumes that everything new valve adds isnt recycled, and that it is placed correctly. For example if they add a new chargemeter tomorrow for a new pyro weapon, updating the base files is just going to give you an ugly charge meter randomly placed on your screen.

i honestly dont think theres any reason to do the whole hud in that fashion. he'll always have to update his shit regardless

I cannot figure out for the life of me where the width for the primary target id is located. It's driving me mad :P
Any pointers?

HLExtract is super easy. It creates a batch file, then you use that to replace the default files. Also, any dev using #base should include HLExtract anyway.

The point of it is that it can bypass crashes that the game may throw at you if the HUD updates. I'm not disputing that it isn't perfect, but it's an easier, temporary solution to game updates, rather than waiting for the HUD dev to fix crashes. For example: #base would have been perfect when the backpack buttons got added, because the game crashed if the buttons weren't set in the file (before they patched the crash).

#base used in the right way actually would have prevented the witch hat. It wouldn't be positioned correctly until a dev patch was released but at least there wouldn't be orange headwear on the screen.

#base is useful for more than just updates as well. It's real handy for files that are similar to one another; item effect meters, for example. The example you gave about an "ugly charge bar" would happen on any HUD, not just a #base coded one.

#base is just another way of working. You either like it or hate it. Don't shit on it because you don't like to use it; just do what you do and let others do what they do.

Agree to disagree, I suppose. I see where you're coming from because I thought the same way, but in using it, it's pretty fucking handy.

how do I make main menu buttons change color when I mouse over them?

You gotta mess with default, armed, and depressed values like these
https://github.com/MFSTATE/tf2basehud/blob/master/resource/ui/mainmenuoverride.res#L53-L62

Default is default, armed is mouse over, depressed is on click [I'm pretty sure, anyways]

edit - nvm figured out the issue. thanks!

Next time just PM me and i will fix it.

How do I add the contract score onto my hud (

http://imgur.com/CdG2qqM

) and on my HUD how to fix the contract progress when it is at the side of the screen whilst playing (the objectives are off the screen).

Thanks

Make sure the font QuestObjectiveTracker_Desc is defined in your clientscheme.res

@Flame you don't need to use #base at all, but for certain files it's easier to include the default one and just move things around, if you completely overhaul an element you can just provide your own .res file (or use that as the default for a #base include)

I decided to simply copy & paste it from the improved default hud, I copied everything in that clientscheme folder from "QuestObjectiveTracker_Desc" to "QuestLargeText_Merasmus", the last quest related thing in the file (just the "QuestObjectiveTracker_Desc" had no affect) and it didn't change (the bars at the bottom still had no text). This is the dl to the hud which I copied the clientscheme off - and if anyone knows how I could fix this it would be great.

how can I fix skinned weapons showing up as transparent in my backpack? example - http://imgur.com/I3aA6O6

@No1inPartiqlar That Clientscheme from idhud is up to date with the default hud and should make this work. If the font still doesn't show up, check if you have a custom "Resource/UI/quests/questitemtrackerpanel_base.res" and check the fonts/colors defined there (or just remove the file and use the actual default one)

Is it possible to have a main menu of one hud and the ingame gameplay of another?If so how can I do that?

How do I change the color of the damage numbers in broeselhud blue?
There are no numeric rgb values, just names.
Here are the contents of the hud:

"Resource/UI/HudDamageAccount.res"
{
"CDamageAccountPanel"
{
"fieldName" "CDamageAccountPanel"
"text_x" "0"
"text_y" "0"
"delta_item_end_y" "0"
"PositiveColor" "Last Damage done"
"NegativeColor" "Damage Numbers"
"delta_lifetime" "1.0"
"delta_item_font" "surface20outline"
"delta_item_font_big" "surface20outline"
}

"DamageAccountValue"
{
"ControlName" "CExLabel"
"fieldName" "DamageAccountValue"
"xpos" "c110"
"ypos" "r145"
"zpos" "2"
"wide" "100"
"tall" "26"
"visible" "1"
"enabled" "1"
"labelText" "%metal%"
"textAlignment" "center"
"fgcolor" "Last Damage done"
"font" "surface20"
}

"DamageAccountValueBG"
{
"ControlName" "CExLabel"
"fieldName" "DamageAccountValueBG"
"xpos" "c110"
"ypos" "r145"
"zpos" "1"
"wide" "101"
"tall" "27"
"visible" "1"
"enabled" "1"
"labelText" "%metal%"
"textAlignment" "center"
"fgcolor" "0 0 0 255"
"font" "surface20"
}
}

Just replace those aliases for RGBs, it wont kill anything.