Anomaly Synchronizer fixes (#21883)
- Show if an anomaly is attached when examining - Add verb for attaching anomaly - Add popup messages for when you try to attach when machine isn't powered, or when no anomaly is in range. - Use anomaly threshold values from anomaly comp, instead of hardcoded **and incorrect** values - Use Entity<T> - Formatting fixes and other misc code cleanup
This commit is contained in:
@@ -27,6 +27,11 @@ anomaly-scanner-pulse-timer = Time until next pulse: [color=gray]{$time}[/color]
|
||||
|
||||
anomaly-sync-connected = Anomaly successfully attached
|
||||
anomaly-sync-disconnected = The connection to the anomaly has been lost!
|
||||
anomaly-sync-no-anomaly = No anomaly in range.
|
||||
anomaly-sync-examine-connected = It is [color=darkgreen]attached[/color] to an anomaly.
|
||||
anomaly-sync-examine-not-connected = It is [color=darkred]not attached[/color] to an anomaly.
|
||||
anomaly-sync-connect-verb-text = Attach anomaly
|
||||
anomaly-sync-connect-verb-message = Attach a nearby anomaly to {THE($machine)}.
|
||||
|
||||
anomaly-generator-ui-title = Anomaly Generator
|
||||
anomaly-generator-fuel-display = Fuel:
|
||||
|
||||
Reference in New Issue
Block a user