0810c99f08
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>
11 lines
385 B
Text
11 lines
385 B
Text
[gd_scene load_steps=3 format=3]
|
|
|
|
[ext_resource type="Script" path="res://buildings/WorkshopBuildingVisual.gd" id="1"]
|
|
[ext_resource type="Script" path="res://buildings/BuildingActionProvider.gd" id="2"]
|
|
|
|
[node name="Visual" type="Node2D"]
|
|
script = ExtResource("1")
|
|
|
|
[node name="ActionProvider" type="Node" parent="."]
|
|
script = ExtResource("2")
|
|
actions = PackedStringArray("transfer")
|