2f161621c3
Everything lived in one flat directory, so a diff gave no clue what area it touched and finding the file you wanted meant knowing its exact name. Twelve folders now, grouped by what a thing IS rather than what type it is - a vessel's definition, its component scenes and its upgrade resources sit together, because that is the set you read when you change one of them. buildings core controllers enemies logistics planets resources shaders surface ui vessels vfx world 332 files moved and every res:// reference rewritten - 306 files touched, including the autoload and main-scene paths in project.godot. Nothing renamed: this is purely where files sit, so the diff is a pile of pure moves and no behaviour is buried in it. ui_theme.tres, icon.svg and web_shell.html stay at the root, where Godot and the export preset expect them. Verified three ways, because a suite alone would not have caught all of it: the full 117 pass, the web export builds clean, and the game renders. The export is why that matters. The FIRST export after the move failed with "Attempt to open script 'res://GameState.gd'" - the old path - while project.godot on disk plainly said res://core/GameState.gd. That is this project's documented Android FUSE mtime trap: Godot served a cached copy of a file whose content had changed. A `touch` fixed it. Nothing in the test suite would have found that, because the suite runs from a copy on a native filesystem - the one place the bug cannot happen. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
35 lines
1.9 KiB
GDScript
35 lines
1.9 KiB
GDScript
class_name EnemyDefinition
|
|
extends Resource
|
|
|
|
# Data-driven enemy stats and appearance, mirroring VesselDefinition's role
|
|
# for player ships. Enemy.gd instantiates component_scenes exactly like
|
|
# Ship.gd does, so behaviour (pursuit, ranged fire, ...) lives in capability
|
|
# components rather than in a type switch here.
|
|
|
|
@export var enemy_id: String = "chaser"
|
|
@export var display_name: String = "Chaser"
|
|
@export var max_hp: int = 3
|
|
@export var speed: float = 140.0
|
|
@export var acceleration: float = 260.0
|
|
@export var rotation_speed: float = 6.0
|
|
@export var hull_points: PackedVector2Array = PackedVector2Array([
|
|
Vector2(0, -16), Vector2(12, 0), Vector2(0, 16), Vector2(-12, 0),
|
|
])
|
|
@export var glow_color: Color = Color(1.0, 0.15, 0.2)
|
|
# Interior detail drawn on top of the hull, as consecutive PAIRS of points
|
|
# (a, b, c, d -> segments a-b and c-d). Every enemy used to be a single flat
|
|
# outline, which left the artillery and the turret spawner as the same
|
|
# octagon at two sizes - the silhouette carried no information about what a
|
|
# thing did. Kept as DATA rather than a per-type draw branch, for the same
|
|
# reason hull_points is: adding an enemy must not mean editing Enemy.gd.
|
|
@export var detail_lines: PackedVector2Array = PackedVector2Array()
|
|
# Rings, as triples of (centre x, centre y, radius). Sensor domes, muzzles
|
|
# and bay openings all read better as circles than as polygon chords.
|
|
@export var detail_rings: PackedVector2Array = PackedVector2Array()
|
|
# #82: this enemy is destroyed by the impact when it reaches a player vessel,
|
|
# rather than shrugging it off and lining up another pass. Data, not a type
|
|
# check: the chaser rams because ramming is its whole behaviour, while a
|
|
# sniper that happens to drift into a ship has not spent itself doing it.
|
|
@export var dies_on_contact: bool = false
|
|
@export var core_color: Color = Color(0.06, 0.02, 0.03)
|
|
@export var component_scenes: Array[PackedScene] = []
|