#80 - desktop combat. The mouse aims, the left button fires, and the number keys pick the weapon: 1 the fleet's guns, 2 and up the abilities. The twin sticks are built for thumbs; on a desktop they mean dragging a virtual stick with a pointer that could simply BE the crosshair. The pointer path hands its heading to FireStickController rather than driving weapons itself, so exactly one thing in the scene aims a gun, and a held stick wins - a finger on it is a deliberate act, a mouse resting somewhere is not. Abilities gained fire_at(), which aims and fires in one call instead of pretending to be a press-drag-release touch. It is gated on the absence of a touchscreen, because Godot emulates a mouse button from every touch and without that a tap on a phone would fire the guns. The gate has an explicit override, and not for tidiness: headless reports a touchscreen, so with the automatic answer alone the aiming could never be exercised by a test and the only covered behaviour would be the guard. #81 - the bottom-left control hint is gone, from both scenes and from GameController. #82 - a chaser is destroyed by the impact when it reaches a vessel. It used to pass through the wreck untouched and line up another pass, which made a ramming enemy strictly better than any other. Data-driven per enemy (dies_on_contact), because a sniper that happens to drift into a ship has not spent itself doing it - and routed through take_damage, so it dies exactly as it dies to gunfire. The enemy is told about the impact BEFORE the ship resolves its own damage, since resolving it can free the ship. #83 - the research tree's buy button is gone; tapping a node twice buys it. Deliberately "the same node twice" rather than a timed double-tap: no window to miss on a slow phone, no accidental purchase while browsing, and the first tap always does something visible, so the second is never a blind commitment. The status line now says "Tap again to research" - with the button gone it is the only thing distinguishing an affordable node from an unaffordable one. test_enemy_collision asserted the exact behaviour #82 reversed, and now checks the ram costs both. Suite 117/117. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
82 lines
2.4 KiB
GDScript
82 lines
2.4 KiB
GDScript
extends Area2D
|
|
|
|
signal destroyed
|
|
|
|
const ENEMY_DEFINITIONS = preload("res://EnemyDefinitions.gd")
|
|
|
|
@export var enemy_id: String = "chaser"
|
|
|
|
var definition: Resource
|
|
var hp: int
|
|
|
|
# Mirrors Ship.gd's own max_speed/acceleration: copied from the definition
|
|
# once, then mutable, so a test/preview can pin an enemy in place (e.g.
|
|
# `enemy.speed = 0.0`) without needing to know about definitions at all.
|
|
var speed: float
|
|
var acceleration: float
|
|
var rotation_speed: float
|
|
var max_hp: int
|
|
|
|
|
|
func _ready() -> void:
|
|
add_to_group("enemies")
|
|
definition = ENEMY_DEFINITIONS.get_definition(enemy_id)
|
|
speed = definition.speed
|
|
acceleration = definition.acceleration
|
|
rotation_speed = definition.rotation_speed
|
|
max_hp = definition.max_hp
|
|
hp = max_hp
|
|
for component_scene in definition.component_scenes:
|
|
var component: Node = component_scene.instantiate()
|
|
add_child(component)
|
|
if component.has_method("setup"):
|
|
component.setup()
|
|
queue_redraw()
|
|
|
|
|
|
func get_component(capability: String) -> Node:
|
|
for child in get_children():
|
|
if child.get("capability_id") == capability:
|
|
return child
|
|
return null
|
|
|
|
|
|
func has_capability(capability: String) -> bool:
|
|
return get_component(capability) != null
|
|
|
|
|
|
func _physics_process(delta: float) -> void:
|
|
for child in get_children():
|
|
if child.has_method("tick"):
|
|
child.tick(delta)
|
|
|
|
|
|
# Called by a player vessel this has just collided with. Whether the impact
|
|
# destroys it is the definition's call - see EnemyDefinition.dies_on_contact.
|
|
# Routed through take_damage so it dies exactly as it dies to gunfire: same
|
|
# explosion, same `destroyed` signal, same bookkeeping for whatever is
|
|
# listening.
|
|
func collide_with_player_vessel() -> void:
|
|
if definition != null and bool(definition.dies_on_contact):
|
|
take_damage(hp)
|
|
|
|
|
|
func take_damage(amount: int) -> void:
|
|
hp -= amount
|
|
if hp <= 0:
|
|
EnemyExplosionVFX.spawn(get_tree().root, position)
|
|
destroyed.emit()
|
|
queue_free()
|
|
|
|
|
|
func _draw() -> void:
|
|
# Drawn through EnemyDefinitions.draw_definition, the same routine the
|
|
# map editor's markers and palette use, so a definition cannot end up
|
|
# looking one way where it is placed and another where it is fought.
|
|
if definition == null:
|
|
NeonDraw.draw_glowing_polygon(self, PackedVector2Array([
|
|
Vector2(0, -16), Vector2(12, 0), Vector2(0, 16), Vector2(-12, 0),
|
|
]), Color(1.0, 0.15, 0.2), 1.0)
|
|
return
|
|
# Constant glow - see Ship.gd. Nothing animates, so no per-frame redraw.
|
|
ENEMY_DEFINITIONS.draw_definition(self, definition, definition.glow_color)
|