Info HUD y offset doesn't account for labels above the HUD

[joel4848]

Labels (# active randomat events, disguiser, radar etc.) are cut off if the info HUD is moved too close to the top of the screen. I'm creating this issue to ask for a decision on which potential solution to go for:

1. Do nothing, let clients move the HUD down a bit if they notice the labels are cut off
   • Easiest, but laziest and unsatisfying
2. Move the HUD down when labels are added if they would be cut off
   • Probably the best solution, but may look visually weird because the HUD will jump down/up when e.g. the disguiser is enabled/disabled
3. Make labels draw beneath the HUD if it's positioned within a certain distance of the top of the screen
   • Probably the 'cleanest' solution, but probably not worth the time/effort/other things I'd no doubt inadvertently break in rewriting the label code to do that, compared to option 2

[Malivil]

I prefer 1 or 3. 3 wouldn't be that bad because it's just changing the render y position

[NoxxFlame]

I agree with Mal. The position of the HUD should be constant. Moving it around to make room for other elements feels back-to-front.

[Malivil]

After looking into this implementation, we currently cannot implement the 3rd option (moving the labels when they are too close to the top of the screen) because we don't know how many labels there are in advance since the implementers of the hook do the rendering. This is important because the labels are rendered bottom-up and we would not be able to calculate the starting position (bottom of the stack) correctly without knowing the number of labels in advance.

We'll keep this issue around for when we do a breaking HUD rewrite and can reimplement this functionality in a way that makes this more doable.