Skip to content
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

Create @ MOVE THIS WHOLE FOLDER INTO _ENABLED NOT JUST THE FILES.txt #516

Merged
merged 1 commit into from
Jul 28, 2024

Conversation

PeanutKarver
Copy link
Contributor

@PeanutKarver PeanutKarver commented Jul 28, 2024

Unlike the other #customization bh_ folders, bh_player_boxes didn't have this file even though BudHud calls for the whole folder, as seen here:

bh_player_ammobox.res
https://github.com/rbjaxter/budhud/blob/master/resource/ui/hudammoweapons.res

bh_player_healthbox.res
https://github.com/rbjaxter/budhud/blob/master/resource/ui/hudplayerhealth.res

bh_player_uberbox.res
https://github.com/rbjaxter/budhud/blob/master/resource/ui/hudmediccharge.res

Latest commit archive for future reference (Contains all files):
6fadfa9

Side note, I noticed bh_player_uberbox.res's file name is HudPlayerHealth.res even though it's called for under hudmediccharge.res. It's bh_UberBG element is also from _budhud/resource/ui/hudmediccharge.res. It works as intended, even if you change its file name info from HudPlayerHealth.res to HudMedicCharge.res. I just thought I'd point that out.

Added this file to match with the other #customization bh_ folders
@rbjaxter
Copy link
Owner

Yeah, interestingly enough the name at the top of the file doesn't actually matter at all; all TF2 cares about is that it's there. You can notice them in some random default hud files too that reference the wrong file at the top (honestly not sure why it behaves that way).

Seems like a reasonable addition though, wouldn't want people getting confused about the folders. Thanks :)

@rbjaxter rbjaxter merged commit 964e0ea into rbjaxter:master Jul 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants