spaceship/EnemySpawnerComponentChaser.tscn

[gd_scene load_steps=2 format=3]

[ext_resource type="Script" path="res://EnemySpawnerComponent.gd" id="1"]

[node name="EnemySpawnerComponentChaser" type="Node"]
script = ExtResource("1")
spawn_interval = 5.0
spawned_enemy_id = "chaser"
max_alive = 6
spawn_radius = 110.0
Enemy mothership (#53) A large, slow capital enemy that periodically launches chasers and artillery on their own intervals and fires a heavily telegraphed line beam capable of killing several player vessels at once. Spawning reuses #52's EnemySpawnerComponent as-is via two preset scenes (EnemySpawnerComponentChaser.tscn: 5s/chaser, EnemySpawnerComponentArtillery.tscn: 18s/max 2/artillery) rather than adding multi-type support to the component - two instances of a single-purpose component is the composition this codebase already uses everywhere ("enemy bomber" in the original request is read here as the existing artillery enemy's slow telegraphed AOE, not a new enemy type - flagged as a judgment call in the ticket). New EnemyBigLaserComponent.gd ("big_laser") fires a standalone EnemyBigLaserBeam on a long cooldown - the beam owns its whole charge/ fire/flash sequence once launched, so the mothership dying mid-charge doesn't cancel an already-telegraphed shot, same design as EnemyArtilleryComponent/ArtilleryShell. The aim direction is locked once in launch() and never re-read - nothing in the charging phase touches the fleet's position again, which is what makes it dodgeable. Damage is a line-segment check (projection + perpendicular distance) against every player_ships member; Ship.take_damage() already handles shield absorption per-ship. MothershipEnemyDefinition.tres: max_hp 60, speed 35 (slow), a ~96-unit hull, pursuit + two spawners + big_laser, no type switch anywhere - every stat from the definition, every behaviour from a component. Tests: new tests/test_enemy_mothership.gd, split into beam mechanics (tested directly, not through the component's own cooldown timing, which would make the geometry assertions timing-fragile) and the composed definition (tested through a real Enemy.tscn instance). Screenshot of the charge telegraph mid-countdown. Full suite: 80/80. Found and fixed a real bug along the way, in EnemySpawnerComponent.gd (#52): its `enemy_scene: PackedScene = preload("res://Enemy.tscn")` member-level preload could get permanently baked in as a broken, empty PackedScene when a definition's component_scenes chain led back to Enemy.tscn while it was still mid-load - confirmed empirically via ResourceLoader.has_cached() being true (a good copy existed) while the preloaded reference's own resource_path was empty. This only surfaces when a SINGLE definition composes two instances of a script carrying such a preload (the mothership's chaser/artillery spawner presets; #52's single-spawner turret never hit it). Fixed by resolving enemy_scene lazily via load() on first use instead of at compile time, and additionally made a fresh spawner count down from a full interval before its first spawn rather than firing on tick one, which also happens to keep two sibling spawners with different intervals from ever landing their first attempt on the same frame. 🤖 Generated with Claude Code Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> 2026-08-16 10:19:02 +02:00			`[gd_scene load_steps=2 format=3]`

			`[ext_resource type="Script" path="res://EnemySpawnerComponent.gd" id="1"]`

			`[node name="EnemySpawnerComponentChaser" type="Node"]`
			`script = ExtResource("1")`
			`spawn_interval = 5.0`
			`spawned_enemy_id = "chaser"`
			`max_alive = 6`
			`spawn_radius = 110.0`