2026-08-14 22:12:57 +02:00
|
|
|
[gd_resource type="Resource" script_class="VesselDefinition" load_steps=6 format=3]
|
#84: move 215 root files into a folder hierarchy
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>
2026-08-21 19:44:14 +02:00
|
|
|
[ext_resource type="Script" path="res://vessels/VesselDefinition.gd" id="1"]
|
|
|
|
|
[ext_resource type="PackedScene" path="res://vessels/VesselCargoComponent.tscn" id="2"]
|
|
|
|
|
[ext_resource type="PackedScene" path="res://vessels/VesselTransportComponent.tscn" id="3"]
|
|
|
|
|
[ext_resource type="Resource" path="res://vessels/TransportCapacityUpgrade.tres" id="4"]
|
|
|
|
|
[ext_resource type="Resource" path="res://vessels/TransportSpeedUpgrade.tres" id="5"]
|
2026-08-14 22:12:57 +02:00
|
|
|
[resource]
|
|
|
|
|
script = ExtResource("1")
|
|
|
|
|
definition_id = "transporter"
|
|
|
|
|
display_name = "Transporter"
|
2026-08-15 00:09:10 +02:00
|
|
|
description = "Hub-owned logistics vessel that moves resources automatically."
|
|
|
|
|
build_cost = 0
|
|
|
|
|
build_time = 0.0
|
2026-08-14 22:12:57 +02:00
|
|
|
icon = 12
|
|
|
|
|
glow_color = Color(0.95, 0.55, 0.85, 1)
|
|
|
|
|
capabilities = PackedStringArray("cargo", "transport")
|
|
|
|
|
component_scenes = Array[PackedScene]([ExtResource("2"), ExtResource("3")])
|
Implement #85, #86, #87 and #88
#85 - on a computer the sticks and the pivot pair are dead weight: WASD
steers, the mouse aims, Q/E pivot. All four go together the first time a
keyboard or a mouse is used, and only where there is no touchscreen. A touch
device with a keyboard attached keeps everything, because a finger is still a
way to play it.
#86 - the default gun shoots faster (500 -> 850) and further (320 -> 620).
The interesting half is that a bolt now STOPS where the gun's range ends.
Projectile lifetime is derived from fire_range at launch rather than set
independently, so the distance a shot covers and the distance the aim guide
draws are one number. They were two, and they disagreed: the guide promised
320 while a bolt actually flew speed * lifetime = 750, so shots landed on
things well past the line saying where they would stop.
#87 - the ship that fires throws sparks, so a shot is visibly attached to the
vessel it came from; with a whole fleet shooting there was nothing tying the
two together, which started mattering once the player had to aim. Enemy deaths
gained a shockwave ring and roughly double the debris - a kill used to read as
a small red puff that was easy to miss in a fight.
#88 - everything moves 1.5x faster: fleet cruise, every vessel's max_speed and
acceleration, and every enemy's. Scaling the enemies too keeps it a change of
TEMPO rather than a difficulty cut, and scaling acceleration alongside speed
keeps the handling from #77's tuning intact.
Three tests carried assertions that were really about one balance pass:
test_enemy_mothership pinned a literal 35.0 and now compares against the
chaser, which is what "never reaches ramming speed" actually means;
test_planet_atmosphere_transition flew far enough at the new speed to reach
the landed garrison, and now clears it, since that test is about the handoff
and not about a fight it never meant to pick.
Also repaired real data loss, caught only because test_gas_burner failed:
Godot had silently re-serialised GasBurnerBuildingDefinition.tres and dropped
collected_outputs, capabilities, map_radius and map_phase, and had recreated a
stale copy of it at the pre-#84 root path. Without collected_outputs no
transporter ever collects a burner's energy. Both files restored from git.
It had also resurrected pre-#84 SNAPSHOTS of Main.tscn, Planet.tscn and
lunar_surface.gdshader at their old root paths - the root Main.tscn still
carried 27 references to the flat layout. They are dead weight the engine
never loads, since project.godot and every preload point into the folders, but
they are exactly the kind of thing that wastes an hour later when someone
edits the wrong copy. Deleted, and the root is now down to ui_theme.tres,
icon.svg, web_shell.html and the two config files.
Suite 119/119.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-22 02:19:14 +02:00
|
|
|
base_stats = {"max_speed": 690.0, "acceleration": 2025.0, "cargo_capacity": 20.0, "transport_speed": 150.0, "delivery_speed": 180.0}
|
2026-08-14 22:12:57 +02:00
|
|
|
upgrades = Array[Resource]([ExtResource("4"), ExtResource("5")])
|