Scanner fix batch: consumable hosts decay on the same tick; hostility, pilot-path, consumable and wire-key-51 tests
ConsumableItemEffect.Update now runs Execute before the always-updated pass, as EquippedItem.Update does, so a consumable-hosted scanner decays on the tick the scan breaks. Tests: AScanReadsNoHostility (hostile/friendly, honest/lying), AScanTakesTheSamePathForAnyPilot (AI-agent ship and agentless ship), AConsumableScannerDecaysOnTheSameTick, ScannerDataRoundTripsAsUnionKey51. Not yet verified at this commit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
b026ea6eb6
commit
26d0e66ff5
4 changed files with 133 additions and 6 deletions
|
|
@ -81,7 +81,8 @@ public class Scanner : Behavior, IAlwaysUpdatedBehavior, IProgressBehavior
|
|||
return true;
|
||||
}
|
||||
|
||||
// Every tick, after Execute: a scan not held this tick (out of range, untracked, or the item inactive so Execute did
|
||||
// Every tick, after Execute on either host (EquippedItem.Update and ConsumableItemEffect.Update both run Execute first):
|
||||
// a scan not held this tick (out of range, untracked, or the item inactive so Execute did
|
||||
// not run) decays over ScanTime (ruling scan-held-beam). The one decay site.
|
||||
public void Update(float delta)
|
||||
{
|
||||
|
|
|
|||
Loading…
Reference in a new issue