spaceship/TurretSpawnerEnemyDefinition.tres

[gd_resource type="Resource" script_class="EnemyDefinition" load_steps=3 format=3]

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

[resource]
script = ExtResource("1")
enemy_id = "turret_spawner"
display_name = "Turret Spawner"
max_hp = 20
speed = 0.0
acceleration = 0.0
rotation_speed = 0.0
hull_points = PackedVector2Array(0, -32, 22.6, -22.6, 32, 0, 22.6, 22.6, 0, 32, -22.6, 22.6, -32, 0, -22.6, -22.6)
glow_color = Color(0.68, 0.92, 0.18, 1)
component_scenes = Array[PackedScene]([ExtResource("2")])
Turret vessel spawner enemy (#52) New EnemySpawnerComponent.gd (capability_id "spawner"): continuously instantiates another enemy type beside its host at a fixed interval, capped at max_alive concurrently, refilling as spawns die. Spawned enemies are parented under the SPAWNER'S OWN PARENT rather than the spawner itself, so they are siblings, not descendants - killing the spawner can't free them, and a surface-hosted spawner (under PlanetSetupHost) keeps its spawns under the same host instead of leaking them to a hardcoded path, the same hazard #44 already closed for pursuit/standoff/ranged-weapon components. TurretSpawnerEnemyDefinition.tres: stationary (speed 0, no pursuit or standoff component), max_hp 20 (~7x a chaser), a bulky octagon hull, and its own acid-green glow distinct from chaser/sniper/artillery. Registered in EnemyDefinitions.ORDER/DEFINITIONS - the map editor palette (#48) picks it up with no editor code change. Tests: new tests/test_turret_spawner_enemy.gd covers registration and real definition defaults, no spawns without a fleet, spawning capped at max_alive, a dead spawn's slot refilling, never moving, surviving 19 damage and dying on the 20th, and its spawns surviving its death with their pursuit component intact. Screenshot beside a chaser confirms the two read as visually distinct enemies. Full suite: 79/79. Repo notes for the next agent, confirmed empirically this session: - A node's set_process(false) call made before it has fully finished entering the tree doesn't reliably stick (already documented in tests/test_planet_atmosphere_transition.gd, and it bit this test too): BuildController._check_fleet_wipe() kept rebuilding a ship during an intended "empty fleet" test window even after disabling it in _initialize(). Do it in _process()'s first real tick instead, once _ready() cascades are confirmed complete. - Overriding an @export interval (like spawn_interval) on an already-running component does NOT reset its own in-progress countdown timer - only changes what it resets TO on its next expiry. If the countdown already started at the OLD value before your override lands, reset the timer variable itself too, or the first real interval after the override silently uses the stale value. - A capped spawner's freed-slot refill can land within a couple of frames once its interval is short - don't assert on an intermediate "just dropped by one" count that a fast interval can blow straight through before your next check runs. Assert the net effect instead (the specific killed instance is gone AND a replacement filled the slot) rather than an exact mid-transition snapshot. 🤖 Generated with Claude Code Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> 2026-08-16 09:43:44 +02:00			`[gd_resource type="Resource" script_class="EnemyDefinition" load_steps=3 format=3]`

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

			`[resource]`
			`script = ExtResource("1")`
			`enemy_id = "turret_spawner"`
			`display_name = "Turret Spawner"`
			`max_hp = 20`
			`speed = 0.0`
			`acceleration = 0.0`
			`rotation_speed = 0.0`
			`hull_points = PackedVector2Array(0, -32, 22.6, -22.6, 32, 0, 22.6, 22.6, 0, 32, -22.6, 22.6, -32, 0, -22.6, -22.6)`
			`glow_color = Color(0.68, 0.92, 0.18, 1)`
			`component_scenes = Array[PackedScene]([ExtResource("2")])`