2026-08-15 14:43:29 +02:00
|
|
|
class_name EnemyPursuitComponent
|
|
|
|
|
extends Node
|
|
|
|
|
|
|
|
|
|
# Chases the nearest player ship. Moved out of Enemy.gd verbatim so the
|
|
|
|
|
# behaviour is opt-in per definition rather than hardcoded into every enemy.
|
|
|
|
|
|
|
|
|
|
var capability_id: String = "pursuit"
|
|
|
|
|
var velocity: Vector2 = Vector2.ZERO
|
|
|
|
|
|
2026-08-17 19:47:37 +02:00
|
|
|
# #69: used to beeline from anywhere on the map the instant it spawned,
|
|
|
|
|
# which read as omniscient rather than alert. Idle until the fleet actually
|
|
|
|
|
# comes within this radius. A persistent stalking threat wants the opposite
|
|
|
|
|
# of this - see EnemyPursuitComponentMothership.tscn, which overrides it to
|
|
|
|
|
# an effectively unlimited value for the mothership's own instance.
|
|
|
|
|
@export var detection_range: float = 850.0
|
|
|
|
|
|
2026-08-15 14:43:29 +02:00
|
|
|
|
|
|
|
|
func tick(delta: float) -> void:
|
|
|
|
|
var enemy: Node2D = get_parent()
|
#101 (#97c): waves attack buildings
Every enemy component used to ask the same question - which player SHIP is
nearest - so a structure was scenery they flew straight through. A Building
is also a plain Node2D, so there was nothing to collide with even if one had
tried.
EnemyTargets answers the question once, for pursuit, standoff, the lancer's
lunge and the ranged weapon together, so they cannot drift into disagreeing
about it. It keeps one thumb on the scale: a vessel inside 520px always
wins, even against a nearer building, or the fleet could not defend anything
by interposing itself and an enemy would fly past the ships shooting it.
Buildings get a hitbox - an Area2D in a group, the same shape as a Ship or
an asteroid, so EnemyProjectile needed one extra branch rather than a new
concept. It applies damage on a tick rather than on area_entered: entry
fires once, which is right for a rammer that dies on the first strike, but
would let a sniper that drifted inside sit there scratch-free for ever. On a
tick, an enemy parked on a structure is besieging it.
What one strike costs is data on the enemy definition, for the same reason
dies_on_contact is - a lancer arriving at 950px/s is not a sniper drifting
into a wall.
Also clears the asteroids in test_enemy_projectile_damage. set_process(false)
only stops NEW asteroids; the ones already placed keep drifting, and one
wandering into the shield vessel parked at (2000, 0) spent its single charge
so the projectile fired next killed it. That failed about one parallel suite
run in thirty and never in isolation. Clearing them is what the other combat
tests already do.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-23 13:53:17 +02:00
|
|
|
# #101: a structure is a target now, not scenery. EnemyTargets keeps a
|
|
|
|
|
# ship in the enemy's face ahead of a building further off.
|
|
|
|
|
var target: Node2D = EnemyTargets.nearest_target(self, enemy.global_position)
|
2026-08-23 21:38:09 +02:00
|
|
|
if target == null:
|
|
|
|
|
return
|
|
|
|
|
# #113: a wave enemy closes on what the player built from wherever it
|
|
|
|
|
# arrived. Everything else keeps the radius that stops it reading as
|
|
|
|
|
# omniscient (#69).
|
|
|
|
|
if not EnemyTargets.ignores_range(enemy) \
|
|
|
|
|
and enemy.global_position.distance_to(target.global_position) > detection_range:
|
2026-08-17 19:47:37 +02:00
|
|
|
return
|
#101 (#97c): waves attack buildings
Every enemy component used to ask the same question - which player SHIP is
nearest - so a structure was scenery they flew straight through. A Building
is also a plain Node2D, so there was nothing to collide with even if one had
tried.
EnemyTargets answers the question once, for pursuit, standoff, the lancer's
lunge and the ranged weapon together, so they cannot drift into disagreeing
about it. It keeps one thumb on the scale: a vessel inside 520px always
wins, even against a nearer building, or the fleet could not defend anything
by interposing itself and an enemy would fly past the ships shooting it.
Buildings get a hitbox - an Area2D in a group, the same shape as a Ship or
an asteroid, so EnemyProjectile needed one extra branch rather than a new
concept. It applies damage on a tick rather than on area_entered: entry
fires once, which is right for a rammer that dies on the first strike, but
would let a sniper that drifted inside sit there scratch-free for ever. On a
tick, an enemy parked on a structure is besieging it.
What one strike costs is data on the enemy definition, for the same reason
dies_on_contact is - a lancer arriving at 950px/s is not a sniper drifting
into a wall.
Also clears the asteroids in test_enemy_projectile_damage. set_process(false)
only stops NEW asteroids; the ones already placed keep drifting, and one
wandering into the shield vessel parked at (2000, 0) spent its single charge
so the projectile fired next killed it. That failed about one parallel suite
run in thirty and never in isolation. Clearing them is what the other combat
tests already do.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-23 13:53:17 +02:00
|
|
|
var to_target: Vector2 = target.global_position - enemy.global_position
|
2026-08-15 14:43:29 +02:00
|
|
|
|
|
|
|
|
if to_target.length() > 1.0:
|
|
|
|
|
var desired_velocity: Vector2 = to_target.normalized() * enemy.speed
|
|
|
|
|
velocity = velocity.move_toward(desired_velocity, enemy.acceleration * delta)
|
#101 (#97c): waves attack buildings
Every enemy component used to ask the same question - which player SHIP is
nearest - so a structure was scenery they flew straight through. A Building
is also a plain Node2D, so there was nothing to collide with even if one had
tried.
EnemyTargets answers the question once, for pursuit, standoff, the lancer's
lunge and the ranged weapon together, so they cannot drift into disagreeing
about it. It keeps one thumb on the scale: a vessel inside 520px always
wins, even against a nearer building, or the fleet could not defend anything
by interposing itself and an enemy would fly past the ships shooting it.
Buildings get a hitbox - an Area2D in a group, the same shape as a Ship or
an asteroid, so EnemyProjectile needed one extra branch rather than a new
concept. It applies damage on a tick rather than on area_entered: entry
fires once, which is right for a rammer that dies on the first strike, but
would let a sniper that drifted inside sit there scratch-free for ever. On a
tick, an enemy parked on a structure is besieging it.
What one strike costs is data on the enemy definition, for the same reason
dies_on_contact is - a lancer arriving at 950px/s is not a sniper drifting
into a wall.
Also clears the asteroids in test_enemy_projectile_damage. set_process(false)
only stops NEW asteroids; the ones already placed keep drifting, and one
wandering into the shield vessel parked at (2000, 0) spent its single charge
so the projectile fired next killed it. That failed about one parallel suite
run in thirty and never in isolation. Clearing them is what the other combat
tests already do.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-23 13:53:17 +02:00
|
|
|
enemy.global_position += velocity * delta
|
2026-08-15 14:43:29 +02:00
|
|
|
|
|
|
|
|
if velocity.length() > 5.0:
|
|
|
|
|
var target_angle: float = velocity.angle() + PI / 2.0
|
|
|
|
|
enemy.rotation = lerp_angle(enemy.rotation, target_angle, enemy.rotation_speed * delta)
|
|
|
|
|
|
|
|
|
|
|
2026-08-17 19:47:37 +02:00
|
|
|
func _nearest_ship(enemy: Node2D) -> Node2D:
|
#101 (#97c): waves attack buildings
Every enemy component used to ask the same question - which player SHIP is
nearest - so a structure was scenery they flew straight through. A Building
is also a plain Node2D, so there was nothing to collide with even if one had
tried.
EnemyTargets answers the question once, for pursuit, standoff, the lancer's
lunge and the ranged weapon together, so they cannot drift into disagreeing
about it. It keeps one thumb on the scale: a vessel inside 520px always
wins, even against a nearer building, or the fleet could not defend anything
by interposing itself and an enemy would fly past the ships shooting it.
Buildings get a hitbox - an Area2D in a group, the same shape as a Ship or
an asteroid, so EnemyProjectile needed one extra branch rather than a new
concept. It applies damage on a tick rather than on area_entered: entry
fires once, which is right for a rammer that dies on the first strike, but
would let a sniper that drifted inside sit there scratch-free for ever. On a
tick, an enemy parked on a structure is besieging it.
What one strike costs is data on the enemy definition, for the same reason
dies_on_contact is - a lancer arriving at 950px/s is not a sniper drifting
into a wall.
Also clears the asteroids in test_enemy_projectile_damage. set_process(false)
only stops NEW asteroids; the ones already placed keep drifting, and one
wandering into the shield vessel parked at (2000, 0) spent its single charge
so the projectile fired next killed it. That failed about one parallel suite
run in thirty and never in isolation. Clearing them is what the other combat
tests already do.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-23 13:53:17 +02:00
|
|
|
return EnemyTargets.nearest_ship(self, enemy.global_position)
|