Sharpen fleet handling, widen the laser, and fix the map editor's file identity
The fleet had a second of inertia in it: every vessel's acceleration sat at
roughly its own top speed, so flipping the stick while cruising took 0.58s to
take effect and let go coasted 222 units, while the formation anchor the ships
chase turns instantly. Acceleration is now ~3x top speed, chosen by measuring
rather than taste - past 3x the reversal time stops improving because
max_speed becomes the limit. Measured after: 0.18s and 23 units.
test_fleet_agility guards all three numbers and proves the bounds discriminate
by re-running the same measurement at the old value.
The laser reaches 1450 instead of 950 and strikes 38 units either side instead
of 22. Its drawn width is now derived from the hit width: the two were
independent numbers that had drifted, so the beam killed things it visibly
missed. LaserController's aim range also stopped hardcoding a second copy of
950. Tapping the laser button without dragging used to do nothing at all - the
press was claimed, the aim begun, then thrown away on release. It now fires at
the nearest enemy in range; dragging still aims precisely. That lives in the
shared aimed-ability controller, so the gas bomb gains it too.
Planets sat one per ~29 chunks - some 35,000 units of nothing between them.
Now one per ~12, measured over 14,641 chunks. The two thresholds moved by
different amounts deliberately: every SPACE-biome planet is a gas giant, so
lowering both equally would have tripled the gas-giant share as well. This
changes how often you find a planet, not what you find. Extractors produce
half as fast to match, so expanding is what grows the economy.
The research screen gave its tree 386px of 1280 and the text below it 520.
The text is now at the bottom, the tree has 550, and the resource table has
room and legible type - and its LOCAL column is no longer hidden behind the
close button.
Two map-editor bugs turned out to be one cause: a setup's id and its FILENAME
are not the same thing, and both save and delete rebuilt the path from the id.
ResearchLabSetup.tres holds setup_id "research_lab_1", so deleting it looked
for a file that does not exist and silently refused - which read as "the first
item in the list cannot be deleted" - while saving it wrote a second file
under the derived name and left the original behind, so the pool served the
stale twin. A third bug hid behind those: rescan() re-read through Godot's
resource cache and handed back pre-save values even when the file on disk was
correct. All three present to a player as "my change was not saved".
Research labs no longer grant a point of their own; what conquering one is
worth comes entirely from its authored map, as asked. The shipped lab map
carries 1 so the balance is unchanged - only where it is configured moved.
Suite 109/109. Four tests changed because the behaviour they pinned changed:
the joystick coast is now derived from cruise_speed^2/(2*acceleration) rather
than a constant tuned to one acceleration; the extractor wait derives from
EXTRACTOR_RATE; the research-point test asserts the delegation; and the black
hole test no longer assumes nobody will ever author a void-profile map.
test_planet_setups and test_planet_map_assignment stopped depending on which
maps happen to be in the content folder, which was making them fail when maps
were added or deleted elsewhere.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-20 09:55:11 +02:00
|
|
|
extends SceneTree
|
|
|
|
|
|
|
|
|
|
# Headless gameplay test: run with
|
|
|
|
|
# godot --headless -s res://tests/test_laser_auto_aim.gd
|
|
|
|
|
# Tapping the laser button without dragging used to do nothing whatsoever:
|
|
|
|
|
# the press was claimed and the aim begun, then releasing inside the aim
|
|
|
|
|
# deadzone threw the whole thing away. It reads as a dead button. A tap now
|
|
|
|
|
# fires at the nearest enemy in range; dragging is still how a shot is placed
|
|
|
|
|
# precisely.
|
|
|
|
|
#
|
|
|
|
|
# Covers:
|
|
|
|
|
# A. a tap picks the NEAREST enemy, not merely any enemy, and fires
|
|
|
|
|
# B. it fires at all - the shot lands and the target takes the hit
|
|
|
|
|
# C. a tap with nothing in range does not fire, says so, and leaves the
|
|
|
|
|
# shot unspent rather than wasting it on empty space
|
|
|
|
|
# D. a tap does not consume the drag-aim path: dragging past the deadzone
|
|
|
|
|
# still aims where it was dragged, not at the nearest enemy
|
|
|
|
|
|
|
|
|
|
var game_state: Node
|
|
|
|
|
var main: Node
|
|
|
|
|
var fleet: Node
|
|
|
|
|
var skill: Node
|
|
|
|
|
var shooter: Node2D
|
|
|
|
|
var near_enemy: Node
|
|
|
|
|
var far_enemy: Node
|
|
|
|
|
var near_position: Vector2 = Vector2.ZERO
|
|
|
|
|
var far_position: Vector2 = Vector2.ZERO
|
|
|
|
|
var stage: int = 0
|
|
|
|
|
var elapsed: float = 0.0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
func _initialize() -> void:
|
|
|
|
|
game_state = root.get_node("GameState")
|
|
|
|
|
game_state.buildings.clear()
|
|
|
|
|
game_state.extractors.clear()
|
|
|
|
|
game_state.stored_vessels.clear()
|
|
|
|
|
game_state.reset_progression()
|
|
|
|
|
game_state.vessel_levels["unlock_laser"] = 1
|
|
|
|
|
game_state.deposit_fleet_resource(GameState.RESOURCE_ENERGY, 500)
|
#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
|
|
|
main = load("res://world/Main.tscn").instantiate()
|
Sharpen fleet handling, widen the laser, and fix the map editor's file identity
The fleet had a second of inertia in it: every vessel's acceleration sat at
roughly its own top speed, so flipping the stick while cruising took 0.58s to
take effect and let go coasted 222 units, while the formation anchor the ships
chase turns instantly. Acceleration is now ~3x top speed, chosen by measuring
rather than taste - past 3x the reversal time stops improving because
max_speed becomes the limit. Measured after: 0.18s and 23 units.
test_fleet_agility guards all three numbers and proves the bounds discriminate
by re-running the same measurement at the old value.
The laser reaches 1450 instead of 950 and strikes 38 units either side instead
of 22. Its drawn width is now derived from the hit width: the two were
independent numbers that had drifted, so the beam killed things it visibly
missed. LaserController's aim range also stopped hardcoding a second copy of
950. Tapping the laser button without dragging used to do nothing at all - the
press was claimed, the aim begun, then thrown away on release. It now fires at
the nearest enemy in range; dragging still aims precisely. That lives in the
shared aimed-ability controller, so the gas bomb gains it too.
Planets sat one per ~29 chunks - some 35,000 units of nothing between them.
Now one per ~12, measured over 14,641 chunks. The two thresholds moved by
different amounts deliberately: every SPACE-biome planet is a gas giant, so
lowering both equally would have tripled the gas-giant share as well. This
changes how often you find a planet, not what you find. Extractors produce
half as fast to match, so expanding is what grows the economy.
The research screen gave its tree 386px of 1280 and the text below it 520.
The text is now at the bottom, the tree has 550, and the resource table has
room and legible type - and its LOCAL column is no longer hidden behind the
close button.
Two map-editor bugs turned out to be one cause: a setup's id and its FILENAME
are not the same thing, and both save and delete rebuilt the path from the id.
ResearchLabSetup.tres holds setup_id "research_lab_1", so deleting it looked
for a file that does not exist and silently refused - which read as "the first
item in the list cannot be deleted" - while saving it wrote a second file
under the derived name and left the original behind, so the pool served the
stale twin. A third bug hid behind those: rescan() re-read through Godot's
resource cache and handed back pre-save values even when the file on disk was
correct. All three present to a player as "my change was not saved".
Research labs no longer grant a point of their own; what conquering one is
worth comes entirely from its authored map, as asked. The shipped lab map
carries 1 so the balance is unchanged - only where it is configured moved.
Suite 109/109. Four tests changed because the behaviour they pinned changed:
the joystick coast is now derived from cruise_speed^2/(2*acceleration) rather
than a constant tuned to one acceleration; the extractor wait derives from
EXTRACTOR_RATE; the research-point test asserts the delegation; and the black
hole test no longer assumes nobody will ever author a void-profile map.
test_planet_setups and test_planet_map_assignment stopped depending on which
maps happen to be in the content folder, which was making them fail when maps
were added or deleted elsewhere.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-20 09:55:11 +02:00
|
|
|
root.add_child(main)
|
|
|
|
|
current_scene = main
|
|
|
|
|
fleet = main.get_node("Fleet")
|
|
|
|
|
skill = main.get_node("LaserController")
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
func _tap() -> void:
|
|
|
|
|
# Press and release at the same point - inside AIM_DEADZONE, so this is a
|
|
|
|
|
# tap and not a drag.
|
|
|
|
|
var button: Control = main.get_node("UI/LaserButton")
|
|
|
|
|
var at: Vector2 = button.global_position + button.size * 0.5
|
|
|
|
|
for pressed in [true, false]:
|
|
|
|
|
var event := InputEventScreenTouch.new()
|
|
|
|
|
event.index = 7
|
|
|
|
|
event.position = at
|
|
|
|
|
event.pressed = pressed
|
|
|
|
|
main._handle_touch(event)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
func _process(delta: float) -> bool:
|
|
|
|
|
elapsed += delta
|
|
|
|
|
match stage:
|
|
|
|
|
0:
|
|
|
|
|
if elapsed < 0.2:
|
|
|
|
|
return false
|
|
|
|
|
main.get_node("EnemySpawner").set_process(false)
|
|
|
|
|
main.get_node("AsteroidField").set_process(false)
|
|
|
|
|
# Whatever the world spawned would be a second, unintended target.
|
|
|
|
|
for hazard in get_nodes_in_group("asteroids") + get_nodes_in_group("enemies"):
|
|
|
|
|
if is_instance_valid(hazard):
|
|
|
|
|
hazard.queue_free()
|
|
|
|
|
|
|
|
|
|
fleet.spawn_ships(1, Vector2.ZERO, PackedStringArray([GameState.VESSEL_LASER]))
|
|
|
|
|
skill._process(0.0)
|
|
|
|
|
if not main.get_node("UI/LaserButton").visible:
|
|
|
|
|
return _fail("a laser ship in the fleet did not reveal the laser control")
|
|
|
|
|
shooter = skill._next_ready_laser_ship()
|
|
|
|
|
if shooter == null:
|
|
|
|
|
return _fail("no laser ship was ready right after spawning")
|
|
|
|
|
stage = 1
|
|
|
|
|
elapsed = 0.0
|
|
|
|
|
return false
|
|
|
|
|
1:
|
|
|
|
|
if elapsed < 0.1:
|
|
|
|
|
return false
|
|
|
|
|
|
|
|
|
|
# --- C. nothing in range: no shot, and it says why ---------------
|
|
|
|
|
_tap()
|
|
|
|
|
if not skill.beams.is_empty():
|
|
|
|
|
return _fail("tapping with no enemy in range fired anyway")
|
|
|
|
|
if skill.aiming:
|
|
|
|
|
return _fail("tapping with no target left the control stuck in aiming")
|
|
|
|
|
if main.get_node("UI/LaserStatus").text == "":
|
|
|
|
|
return _fail("tapping with no target fired nothing and said nothing")
|
|
|
|
|
print("no target in range: no shot fired, status explains why")
|
|
|
|
|
|
|
|
|
|
# --- A/B. two targets, the nearer one is picked ------------------
|
|
|
|
|
# Deliberately placed in DIFFERENT directions, so hitting the near
|
|
|
|
|
# one cannot be explained by the beam happening to pass through
|
|
|
|
|
# both. Both are well inside range.
|
|
|
|
|
far_enemy = _spawn_enemy(Vector2(0.0, -900.0))
|
|
|
|
|
near_enemy = _spawn_enemy(Vector2(400.0, 0.0))
|
|
|
|
|
far_position = far_enemy.global_position
|
|
|
|
|
near_position = near_enemy.global_position
|
|
|
|
|
stage = 2
|
|
|
|
|
elapsed = 0.0
|
|
|
|
|
return false
|
|
|
|
|
2:
|
|
|
|
|
if elapsed < 0.1:
|
|
|
|
|
return false
|
|
|
|
|
_tap()
|
|
|
|
|
if skill.beams.is_empty():
|
|
|
|
|
return _fail("tapping with an enemy in range did not fire")
|
|
|
|
|
if skill.last_hit_count < 1:
|
|
|
|
|
return _fail("the auto-aimed shot hit nothing")
|
|
|
|
|
# Asserted on where it AIMED, not on a body count. Enemies have
|
|
|
|
|
# hit points and a beam damages rather than always destroys, so
|
|
|
|
|
# "did it die" would be measuring the damage numbers instead of
|
|
|
|
|
# the targeting this test is about.
|
|
|
|
|
if skill.aim_target.distance_to(near_position) > 1.0:
|
|
|
|
|
return _fail("the tap aimed at %s, but the nearest enemy is at %s" \
|
|
|
|
|
% [skill.aim_target, near_position])
|
|
|
|
|
print("tap aimed at the nearest enemy (%.0f away), not the one %.0f away in another direction" \
|
|
|
|
|
% [shooter.global_position.distance_to(near_position),
|
|
|
|
|
shooter.global_position.distance_to(far_position)])
|
|
|
|
|
|
|
|
|
|
# --- D. dragging still aims where it is dragged ------------------
|
|
|
|
|
stage = 3
|
|
|
|
|
elapsed = 0.0
|
|
|
|
|
return false
|
|
|
|
|
3:
|
|
|
|
|
# Wait out the per-ship cooldown so the next shot is available.
|
|
|
|
|
if elapsed < 6.0:
|
|
|
|
|
return false
|
|
|
|
|
if skill._next_ready_laser_ship() == null:
|
|
|
|
|
return _fail("the laser ship never came off cooldown")
|
|
|
|
|
var button: Control = main.get_node("UI/LaserButton")
|
|
|
|
|
var at: Vector2 = button.global_position + button.size * 0.5
|
|
|
|
|
var press := InputEventScreenTouch.new()
|
|
|
|
|
press.index = 8
|
|
|
|
|
press.position = at
|
|
|
|
|
press.pressed = true
|
|
|
|
|
main._handle_touch(press)
|
|
|
|
|
# Dragged straight UP, towards the far enemy and away from where
|
|
|
|
|
# auto-aim would have pointed.
|
|
|
|
|
var drag := InputEventScreenDrag.new()
|
|
|
|
|
drag.index = 8
|
|
|
|
|
drag.position = at + Vector2(0.0, -300.0)
|
|
|
|
|
main._handle_drag(drag)
|
|
|
|
|
var release := InputEventScreenTouch.new()
|
|
|
|
|
release.index = 8
|
|
|
|
|
release.position = drag.position
|
|
|
|
|
release.pressed = false
|
|
|
|
|
main._handle_touch(release)
|
|
|
|
|
|
|
|
|
|
# Dragged up, so the shot must go UP - not to the nearest enemy,
|
|
|
|
|
# which lies to the right. Checked as a direction because the
|
|
|
|
|
# laser always extends to its full range along the aimed heading.
|
|
|
|
|
var heading: Vector2 = (skill.aim_target - shooter.global_position).normalized()
|
|
|
|
|
if heading.y > -0.9:
|
|
|
|
|
return _fail("dragging upward aimed along %s - auto-aim overrode a deliberate aim" % heading)
|
|
|
|
|
print("dragging still aims where it is dragged (heading %s), not at the nearest enemy" % heading)
|
|
|
|
|
|
|
|
|
|
print("TEST_LASER_AUTO_AIM: PASS")
|
|
|
|
|
quit(0)
|
|
|
|
|
return true
|
|
|
|
|
return false
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
func _spawn_enemy(offset: Vector2) -> Node:
|
#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
|
|
|
var enemy: Node = load("res://enemies/Enemy.tscn").instantiate()
|
Sharpen fleet handling, widen the laser, and fix the map editor's file identity
The fleet had a second of inertia in it: every vessel's acceleration sat at
roughly its own top speed, so flipping the stick while cruising took 0.58s to
take effect and let go coasted 222 units, while the formation anchor the ships
chase turns instantly. Acceleration is now ~3x top speed, chosen by measuring
rather than taste - past 3x the reversal time stops improving because
max_speed becomes the limit. Measured after: 0.18s and 23 units.
test_fleet_agility guards all three numbers and proves the bounds discriminate
by re-running the same measurement at the old value.
The laser reaches 1450 instead of 950 and strikes 38 units either side instead
of 22. Its drawn width is now derived from the hit width: the two were
independent numbers that had drifted, so the beam killed things it visibly
missed. LaserController's aim range also stopped hardcoding a second copy of
950. Tapping the laser button without dragging used to do nothing at all - the
press was claimed, the aim begun, then thrown away on release. It now fires at
the nearest enemy in range; dragging still aims precisely. That lives in the
shared aimed-ability controller, so the gas bomb gains it too.
Planets sat one per ~29 chunks - some 35,000 units of nothing between them.
Now one per ~12, measured over 14,641 chunks. The two thresholds moved by
different amounts deliberately: every SPACE-biome planet is a gas giant, so
lowering both equally would have tripled the gas-giant share as well. This
changes how often you find a planet, not what you find. Extractors produce
half as fast to match, so expanding is what grows the economy.
The research screen gave its tree 386px of 1280 and the text below it 520.
The text is now at the bottom, the tree has 550, and the resource table has
room and legible type - and its LOCAL column is no longer hidden behind the
close button.
Two map-editor bugs turned out to be one cause: a setup's id and its FILENAME
are not the same thing, and both save and delete rebuilt the path from the id.
ResearchLabSetup.tres holds setup_id "research_lab_1", so deleting it looked
for a file that does not exist and silently refused - which read as "the first
item in the list cannot be deleted" - while saving it wrote a second file
under the derived name and left the original behind, so the pool served the
stale twin. A third bug hid behind those: rescan() re-read through Godot's
resource cache and handed back pre-save values even when the file on disk was
correct. All three present to a player as "my change was not saved".
Research labs no longer grant a point of their own; what conquering one is
worth comes entirely from its authored map, as asked. The shipped lab map
carries 1 so the balance is unchanged - only where it is configured moved.
Suite 109/109. Four tests changed because the behaviour they pinned changed:
the joystick coast is now derived from cruise_speed^2/(2*acceleration) rather
than a constant tuned to one acceleration; the extractor wait derives from
EXTRACTOR_RATE; the research-point test asserts the delegation; and the black
hole test no longer assumes nobody will ever author a void-profile map.
test_planet_setups and test_planet_map_assignment stopped depending on which
maps happen to be in the content folder, which was making them fail when maps
were added or deleted elsewhere.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-20 09:55:11 +02:00
|
|
|
enemy.position = shooter.global_position + offset
|
|
|
|
|
main.add_child(enemy)
|
|
|
|
|
enemy.speed = 0.0
|
|
|
|
|
return enemy
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
func _fail(message: String) -> bool:
|
|
|
|
|
print("TEST_LASER_AUTO_AIM: FAIL (%s)" % message)
|
|
|
|
|
quit(1)
|
|
|
|
|
return true
|