Make HUD scene an autoload

[wjt]

scenes/ui_elements/hud/hud.tscn shows the threads that have been collected so far in this quest; how many threads are yet to be collected; and the townie helper (if any) that you may be able to call on at some point:

Right now it has to be manually added to every scene of every quest (plus Fray's End because it's the marker that you need to go back to the Loom at the end of a quest to complete the quest). I think it should be a global autoload, probably merged with input_hud.tscn. To do this it will need to be made to react to scene changes and show/hide itself when appropriate, but I don't think this is beyond the wit of man because we already do that for input_hud.

This would make it harder to accidentally omit it in a quest scene; and it would declutter the scene tree of every playable scene in the game.

XP Summary (total 500)

Subdomain	Skill	XP
Game Design: Game Feel & UX	Problem Solving	50
Game Design: Game Feel & UX	Creativity & Design Thinking	75
Game Design: Game Feel & UX	Technical Literacy	75
Engineering: Gameplay & Systems Programming	Problem Solving	75
Engineering: Gameplay & Systems Programming	Creativity & Design Thinking	75
Engineering: Gameplay & Systems Programming	Technical Literacy	150

[manuq]

Yes and, I wonder if we should merge the 2 HUDs we have in a single scene:

• res://scenes/ui_elements/hud/hud.tscn
• res://scenes/ui_elements/input_hints/input_hud.tscn

The latter is already an autoload. The difference they have is when to show/hide them. But that can be done by showing / hiding the inner nodes.

[justin-calleja]

What do you think of the approach here: https://github.com/justin-calleja/threadbare/commits/fix/2907/

The first commit is just removing HUD from all quest scenes.

In the second commit... couple of things.

hud_manager.gd

Is the new autoload (InputHud is removed from autoload and class_named). Manager preloads the other hud scenes and instantiates them so no new scene is needed for HudManager autoload.

It connects to scene changes. When scene changes (and first on ready) it tries to figure out whether or not it should show the hud (by hud i mean scenes\ui_elements\hud\components\hud.gd which is just showing the story_quest_progress).

I added a "scenes without hud" to exclude the hud from certain scenes like the splash screen / main menu.

FraysEnd needs some special treatment:

	if current_scene is FraysEnd:
		return GameState.quest.inventory.items.size() >= threads_to_collect

So that's "refresh_hud" - figures out if it needs to show or hide the hud. But it has an explicit "show_hud" because some dialogue was referencing the previous in quest scene hud and showing it. Now that dialogue does:

# scenes\quests\lore_quests\quest_000\2_stealth\components\tutorial_stealth.dialogue
do HudManager.show_hud()

story_quest_progress.gd

Before, each quest scene had its own hud so on _ready it did the slot creation and inventory filling. Now these are in refresh and called from HudManager on scene change.

---

Some other notes:

FraysEnd doesn't need to tell the hud to do anything anymore.

The TutorialRuinedVillage used to not have a Hud. Was that intentional? In this setup, it has it. But it can be excluded in e.g. adding to SCENES_WITHOUT_HUD.