In order to implement range limitations in TeleportBehavior public methods RemainingFuel and FuelCostToTravel were added to Building_TeleportConsole and TeleportBehavior has uses statements like originator is Building_TeleportConsole console in order to utilize these methods.
This isn't ideal...
TeleportBehavior shouldn't need knowledge of Building_TeleportConsole; it should get the CompUsesConsumables associated with the originator and use it directly to generalize long-range global teleport fuel range limits.
[x] fuel range limitations should depend on CompUsesConsumablesrefuelableComp being available, otherwise gracefully ignore fuel range limits
-[] make TeleportBehavior access the ~~CompUsesConsumablesrefuelableComp of originator~~
-[] rename TeleportBehavior variables referencing "fuel" to "consumables" or something
[x] onSuccess should still be responsible for fuel consumption
In order to implement range limitations in
TeleportBehavior
public methodsRemainingFuel
andFuelCostToTravel
were added toBuilding_TeleportConsole
andTeleportBehavior
has uses statements likeoriginator is Building_TeleportConsole console
in order to utilize these methods.This isn't ideal...
TeleportBehavior
shouldn't need knowledge ofBuilding_TeleportConsole
; it should get theCompUsesConsumables
associated with theoriginator
and use it directly to generalize long-range global teleport fuel range limits.CompUsesConsumables
refuelableComp
being available, otherwise gracefully ignore fuel range limits-[]
makeTeleportBehavior
access the ~~CompUsesConsumables
refuelableComp
oforiginator
~~ -[]renameTeleportBehavior
variables referencing "fuel" to "consumables" or somethingonSuccess
should still be responsible for fuel consumption