#166-#173: plainer words, a point to shoot at, and a catalog that says when it is broken

Eight tickets. The last one is the interesting one.

#166 - PLAINER DIALOG. Every spoken line rewritten: the nine prologue lines and
all twenty quest brief/done pairs. Mostly splitting em-dash subclauses into
sentences and dropping the literary register ("hulls" -> "ships", "That is our
hands back" -> "That frees us for other work"). Same meaning, same voice.

#167 - NOTHING ANNOUNCED TWICE. Quests carry an `important` flag; seven of the
twenty have it, and they are the search for the World Ship. A quest handed out
with its goal ALREADY met is now credited in silence unless it is one of those
- no brief, no answer, both signals still fired and the index still moved, so
it appears ticked in the objectives panel. The chain used to stop the game to
set a task the player had already done, then stop it again to congratulate
them on it.

#168 - THE KEYBOARD CAN ANSWER A DIALOG. The rule the ticket asks for (still
arriving, show it all; already whole, move on) was already the rule for a
click since #149, but a key press reached the banner and did nothing - and
this game is played with WASD and a mouse. Touch, click and key now go through
one door. Modifiers alone and auto-repeat echoes are not presses.

#169 - A LOADING SCREEN. A press raises a cover, and the load happens after it
has been on screen for a frame, so the wait is something the player is
watching. Deliberately still a blocking load: load_threaded_request() comes
back FAILED for these scenes, reporting text-parse errors that load() does not
produce, because the global class names and preloads they reach each other
through are not resolvable off the loading thread. A progress bar is not worth
a menu that sometimes refuses to start the game, and the web build ships with
thread support off anyway. Further presses while loading are ignored - on the
web a button fires on PRESS, so an impatient double tap costs nothing to make
and used to build the world twice.

#170 - THE PICTURE BEFORE THE CAPTION. The prologue's first line was up before
the scene had finished arriving, so the game opened STOPPED (#128) over a
convoy nobody had seen yet. It flies for three seconds first.

#171 - THE CONTROLS FOLLOW WHAT IS BEING HELD. is_touchscreen_available() asks
whether a touch COULD arrive, and in a browser that is yes on any laptop whose
panel reports touch support - so the web build put thumb sticks over a screen
being played with a mouse, and switched mouse aiming off on the machine it
exists for. The reading is now the last input actually used, it lives in
GameState so the sticks and the guns cannot disagree, and it is two-way:
nothing can strand a tablet, because the gesture that needs the controls is
the gesture that brings them back. A touch suppresses mouse evidence for a
second, so the click Godot manufactures out of a tap is not mistaken for a
mouse.

#172 - AIM AT A PLACE. Every gun was handed the same direction, so a fleet
firing at something threw a sheet of parallel bolts past either side of it and
only the middle hull could hit - worse the wider the formation. Guns now take
a POINT and each hull works out its own heading to it, so the fleet's fire
converges. The mouse already had a place and was flattening it into a bearing;
a pushed stick names the point at the guns' reach along it, so touch loses
nothing. The assist (#89) still bends a shot onto an enemy, now per hull and
around that hull's own heading. The aim guide stops at the point and marks it.

#173 - AND THE ONE THAT EXPLAINS ITSELF. "In the web export version the fleet
can not store any resources" is not a web bug. It is the third time the Godot
editor's .tres writer has quietly dropped a property it thought was
default-valued: InterceptorVesselDefinition losing `capabilities` leaves
cargo_capacity at 20 and takes away the "cargo" claim that
fleet_cargo_capacity() actually gates on, so the hold is zero and nothing can
be mined or carried. That is the symptom, word for word.

test_definitions_intact caught it in the suite. What it could not do is catch
it in a BUILD - an export is taken from the working tree at whatever moment
the editor last touched it, which is exactly when the damage is done and
exactly where nobody is running tests. The checks move to core/CatalogCheck.gd
and now run at startup in every build as well as in the test, from the same
function. On the web push_error lands in the on-page log web_shell.html
mirrors, which is the only error a phone can read.

The tree is intact today, so a fresh export should restore the hold. The point
of the change is that the next time it is not, the build says so.

Full suite green at 154/154.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0139MmxRAJSUe1j77kftAWv3

ui/MainMenu.gd

@@ -32,6 +32,25 @@ const STATUS_HEIGHT: float = 70.0
 @onready var dev_label: Label = $UI/DevModeLabel
 @onready var status_label: Label = $UI/StatusLabel
 
+# #169: what is being opened, and the cover that says so. Empty path means
+# nothing is loading, which is also what stops a second press starting a
+# second scene - on the web a button fires on PRESS (see IconButton), and an
+# impatient double tap on Play would otherwise build the world twice.
+const LOADING_SCREEN = preload("res://ui/LoadingScreen.gd")
+# How the player is told what they are waiting for. Keyed by scene path so a
+# new entry cannot go in without a name to put on the screen.
+const SCENE_NAMES: Dictionary = {
+	"res://world/Main.tscn": "Entering the convoy lane",
+	"res://surface/PlanetSetupEditor.tscn": "Opening the map editor",
+}
+# The load only starts once the cover has been up for a frame or two. One
+# would do; two is cheap and removes any argument about whether the first one
+# reached the screen.
+const COVER_FRAMES: int = 2
+
+var loading_path: String = ""
+var loading_screen: Control = null
+
 
 func _ready() -> void:
 	# #148: the theme starts here, at the first screen, and keeps playing
@@ -93,6 +112,11 @@ func _layout_stack() -> void:
 
 
 func _on_play_pressed() -> void:
+	# Checked here as well as in _start: this one has a side effect, and a
+	# second press while the first is still loading must not wipe the game
+	# that first press already set up (#169).
+	if loading_path != "":
+		return
 	GameState.reset_new_game()
 	_start("res://world/Main.tscn")
 
@@ -102,21 +126,71 @@ func _on_play_pressed() -> void:
 # there was no way to tell which part failed. Split out, each step can say so
 # - and a scene change that fails otherwise leaves the menu up, which looks
 # exactly like an unpressed button.
+#
+# #169: and now it does not look like anything else either. The press raises a
+# loading screen straight away and the load itself happens over the following
+# frames, driven from _process below, so the wait is something the player is
+# watching rather than a menu that has stopped responding.
 func _start(scene_path: String) -> void:
+	if loading_path != "":
+		return
+	loading_path = scene_path
+	status_label.text = ""
+	loading_screen = LOADING_SCREEN.new()
+	$UI.add_child(loading_screen)
+	loading_screen.begin(String(SCENE_NAMES.get(scene_path, scene_path.get_file())))
+
+
+# The load itself is still the ordinary blocking one, deliberately.
+#
+# ResourceLoader.load_threaded_request() was the obvious alternative and it
+# does not work here: asked for these scenes it comes back FAILED, with the
+# text-scene parser reporting errors ("Parse Error ... Rock.tscn:9", "Could
+# not resolve external class member PROFILES") that the same files do not
+# produce through load(). The project's scripts and scenes reach each other
+# through global class names and preloads, and that resolution is not
+# available off the loading thread. A progress bar is not worth a menu that
+# sometimes refuses to start the game - and the web build could not have used
+# the threaded path anyway, since it ships with thread support off.
+#
+# So what the cover buys is honest and worth having on its own: the press is
+# answered instantly, the player is told what is opening, and the frame that
+# blocks happens with something on the screen rather than behind a menu that
+# has stopped responding.
+func _process(_delta: float) -> void:
+	if loading_path == "":
+		return
+	# Nothing blocking until the cover is actually up - see LoadingScreen's
+	# own note. This is the whole reason the load waits for a frame at all.
+	if loading_screen == null or loading_screen.frames_shown < COVER_FRAMES:
+		return
+	var scene_path: String = loading_path
+	loading_path = ""
 	var packed: PackedScene = load(scene_path)
 	if packed == null:
-		status_label.text = "Could not load %s" % scene_path.get_file()
+		_abandon_loading("Could not load %s" % scene_path.get_file())
 		return
 	var scene: Node = packed.instantiate()
 	if scene == null:
-		status_label.text = "Could not build %s" % scene_path.get_file()
+		_abandon_loading("Could not build %s" % scene_path.get_file())
 		return
 	get_tree().root.add_child(scene)
 	get_tree().current_scene = scene
 	queue_free()
 
 
+# A failed load must leave a working menu behind, not a cover over a screen
+# with nothing coming.
+func _abandon_loading(message: String) -> void:
+	if loading_screen != null:
+		loading_screen.queue_free()
+		loading_screen = null
+	status_label.text = message
+
+
 func _on_dev_mode_pressed() -> void:
+	if loading_path != "":
+		return
 	# Guarded as well as hidden. Visibility is presentation; this is the rule.
 	if not is_developer_build():
 		status_label.text = "Dev mode only runs from Godot"