#116: the Spacial Workshop, and the drones that mend what waves break
Modelled on the transport hub, deliberately and closely: drones belong to a
workshop rather than to the player, are provisioned when it is built, are
never a production order, and are upgraded at a ship lab like any other
vessel. Anything that already knows how hub transporters behave knows how
these do, and Drone Bays raises the count at workshops already standing -
the same shape as Freight Yards and Garrison Bays.
What a repair COSTS is the one new idea. It is a share of the building's own
price, in proportion to how much of its health is gone: levelling a crafter
and rebuilding it costs its full price, and patching one up after a wave
costs a fraction, the fraction being the damage. The ore is spent when a
drone LEAVES, so two drones cannot be sent to the same wall and spend twice
for one load of repair, and a building demolished in transit sends its load
home rather than swallowing it.
"Required resources are sent to the spacial workshop": the workshop asks hub
logistics for the ore its outstanding repairs will need, exactly as a gas
burner asks for gas, because building_logistics_deficit now takes the larger
of the definition's static buffer and what the world actually demands. There
is a ceiling on that, so one badly-mauled base cannot pull the whole bank
into a single workshop and starve everything else.
Worst first: the structure closest to coming down is the one a repair is
worth most on.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-23 21:59:51 +02:00
|
|
|
extends Node2D
|
|
|
|
|
|
|
|
|
|
# #116: purely visual - a repair drone on its way out to a damaged structure
|
|
|
|
|
# or back to its workshop. Carries no state of its own; GameState owns the
|
|
|
|
|
# simulation and RepairDroneField creates, positions and frees this to match.
|
|
|
|
|
|
2026-09-05 21:57:53 +02:00
|
|
|
const VESSEL_DEFINITIONS = preload("res://vessels/VesselDefinitions.gd")
|
#116: the Spacial Workshop, and the drones that mend what waves break
Modelled on the transport hub, deliberately and closely: drones belong to a
workshop rather than to the player, are provisioned when it is built, are
never a production order, and are upgraded at a ship lab like any other
vessel. Anything that already knows how hub transporters behave knows how
these do, and Drone Bays raises the count at workshops already standing -
the same shape as Freight Yards and Garrison Bays.
What a repair COSTS is the one new idea. It is a share of the building's own
price, in proportion to how much of its health is gone: levelling a crafter
and rebuilding it costs its full price, and patching one up after a wave
costs a fraction, the fraction being the damage. The ore is spent when a
drone LEAVES, so two drones cannot be sent to the same wall and spend twice
for one load of repair, and a building demolished in transit sends its load
home rather than swallowing it.
"Required resources are sent to the spacial workshop": the workshop asks hub
logistics for the ore its outstanding repairs will need, exactly as a gas
burner asks for gas, because building_logistics_deficit now takes the larger
of the definition's static buffer and what the world actually demands. There
is a ceiling on that, so one badly-mauled base cannot pull the whole bank
into a single workshop and starve everything else.
Worst first: the structure closest to coming down is the one a repair is
worth most on.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-23 21:59:51 +02:00
|
|
|
const HULL_COLOR: Color = Color(0.5, 0.95, 0.8)
|
|
|
|
|
|
|
|
|
|
var laden: bool = false
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
func _ready() -> void:
|
|
|
|
|
add_to_group("repair_drones")
|
|
|
|
|
# #91: behind the fleet, like every other piece of ground furniture.
|
|
|
|
|
z_index = -1
|
|
|
|
|
queue_redraw()
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
func set_laden(value: bool) -> void:
|
|
|
|
|
if laden == value:
|
|
|
|
|
return
|
|
|
|
|
laden = value
|
|
|
|
|
queue_redraw()
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
func _draw() -> void:
|
|
|
|
|
# Small and blunt, with a tool arm out front, in the workshop's own
|
|
|
|
|
# green-teal: it should read as a tender belonging to a building rather
|
|
|
|
|
# than as a fleet vessel or a hub's magenta hauler.
|
2026-09-05 21:57:53 +02:00
|
|
|
# From the DEFINITION, for the reason Transporter.gd records: #216 made
|
|
|
|
|
# these fly out as ordinary deliveries, and a delivery draws the
|
|
|
|
|
# definition's hull. Two copies meant two shapes for one vessel.
|
|
|
|
|
NeonDraw.draw_glowing_polygon(self, _hull(), HULL_COLOR, 1.0)
|
#116: the Spacial Workshop, and the drones that mend what waves break
Modelled on the transport hub, deliberately and closely: drones belong to a
workshop rather than to the player, are provisioned when it is built, are
never a production order, and are upgraded at a ship lab like any other
vessel. Anything that already knows how hub transporters behave knows how
these do, and Drone Bays raises the count at workshops already standing -
the same shape as Freight Yards and Garrison Bays.
What a repair COSTS is the one new idea. It is a share of the building's own
price, in proportion to how much of its health is gone: levelling a crafter
and rebuilding it costs its full price, and patching one up after a wave
costs a fraction, the fraction being the damage. The ore is spent when a
drone LEAVES, so two drones cannot be sent to the same wall and spend twice
for one load of repair, and a building demolished in transit sends its load
home rather than swallowing it.
"Required resources are sent to the spacial workshop": the workshop asks hub
logistics for the ore its outstanding repairs will need, exactly as a gas
burner asks for gas, because building_logistics_deficit now takes the larger
of the definition's static buffer and what the world actually demands. There
is a ceiling on that, so one badly-mauled base cannot pull the whole bank
into a single workshop and starve everything else.
Worst first: the structure closest to coming down is the one a repair is
worth most on.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-23 21:59:51 +02:00
|
|
|
NeonDraw.draw_glowing_line(self, Vector2(0, -11), Vector2(0, -18), HULL_COLOR, 0.9, 0.35)
|
|
|
|
|
NeonDraw.draw_glowing_line(self, Vector2(-5, -18), Vector2(5, -18), HULL_COLOR, 0.9, 0.35)
|
|
|
|
|
if laden:
|
|
|
|
|
# The load it is carrying out, in ore's own colour so it reads as
|
|
|
|
|
# material rather than as a light on the hull.
|
|
|
|
|
NeonDraw.draw_glowing_circle(self, Vector2(0, 3), 5.0,
|
|
|
|
|
GameState.resource_color(GameState.RESOURCE_ORE), 1.0)
|
2026-09-05 21:57:53 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
func _hull() -> PackedVector2Array:
|
|
|
|
|
var definition: Resource = VESSEL_DEFINITIONS.get_definition(GameState.REPAIR_DRONE)
|
|
|
|
|
return PackedVector2Array() if definition == null else definition.hull_points
|