spaceship/enemies/EnemyRangedWeaponComponent.gd
Loïc Wisniewski 3debcd7edd #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

49 lines
1.7 KiB
GDScript

class_name EnemyRangedWeaponComponent
extends Node
# Same shape as VesselWeaponComponent, mirrored for an enemy: fires an
# EnemyProjectile at the nearest player ship's CURRENT position, not led,
# so a moving ship can dodge it.
var capability_id: String = "ranged_weapon"
@export var fire_range: float = 700.0
@export var fire_cooldown: float = 2.2
@export var projectile_speed: float = 260.0
@export var damage: int = 1
var fire_timer: float = 0.0
var projectile_scene: PackedScene = preload("res://enemies/EnemyProjectile.tscn")
func tick(delta: float) -> void:
fire_timer -= delta
if fire_timer > 0.0:
return
var enemy: Node2D = get_parent()
var target: Node2D = _nearest_ship_in_range(enemy)
if target == null:
fire_timer = 0.25
return
var projectile: Area2D = projectile_scene.instantiate()
# global_position: the projectile is reparented to root, a different
# node than the enemy's own (possibly nested) parent, so local
# position would be wrong the moment an enemy isn't a direct root
# child - exactly the case #44 introduced (planet-surface hosting).
projectile.position = enemy.global_position
projectile.damage = damage
projectile.speed = projectile_speed
enemy.get_tree().root.add_child(projectile)
projectile.launch(target.global_position - enemy.global_position)
fire_timer = fire_cooldown
# #101: shoots at whatever EnemyTargets says it is coming for, so a sniper
# shells a depot rather than sitting in range of one doing nothing.
func _nearest_ship_in_range(enemy: Node2D) -> Node2D:
var target: Node2D = EnemyTargets.nearest_target(self, enemy.global_position)
if target == null:
return null
if enemy.global_position.distance_to(target.global_position) > fire_range:
return null
return target