Gate enemies behind a detection range instead of instant omniscient pursuit (#69)
Chasers (EnemyPursuitComponent) and snipers (EnemyStandoffComponent) used to beeline/close in from anywhere on the map the instant they spawned - no matter how far the fleet was, which read as omniscient rather than alert. Both now sit idle until the fleet is within their own detection_range. Artillery's slow drift is gated the same way, but reuses its own existing fire_range rather than a new tunable - outside its firing envelope it has nothing to be drifting toward yet. The enemy mothership deliberately keeps the opposite behaviour: it is meant to read as a persistent, unavoidable stalking threat, not a local sentry, so it gets its own EnemyPursuitComponentMothership.tscn variant with an effectively unlimited detection_range - the same scene-variant pattern EnemySpawnerComponentChaser/Artillery already use for per-definition property overrides on a shared component script.
This commit is contained in:
parent
8d089d6f76
commit
1de66c6fb2
6 changed files with 161 additions and 7 deletions
|
|
@ -1,7 +1,7 @@
|
|||
[gd_resource type="Resource" script_class="EnemyDefinition" load_steps=6 format=3]
|
||||
|
||||
[ext_resource type="Script" path="res://EnemyDefinition.gd" id="1"]
|
||||
[ext_resource type="PackedScene" path="res://EnemyPursuitComponent.tscn" id="2"]
|
||||
[ext_resource type="PackedScene" path="res://EnemyPursuitComponentMothership.tscn" id="2"]
|
||||
[ext_resource type="PackedScene" path="res://EnemySpawnerComponentChaser.tscn" id="3"]
|
||||
[ext_resource type="PackedScene" path="res://EnemySpawnerComponentArtillery.tscn" id="4"]
|
||||
[ext_resource type="PackedScene" path="res://EnemyBigLaserComponent.tscn" id="5"]
|
||||
|
|
|
|||
Loading…
Reference in a new issue