Great Ahruman, that solves several problems.Legacy script methods awardFuel: and setFuelLeak: now work on the current script target, not always the player.
Did you also alter the way 'fuel' is used by NPCs?
IIRC they currently refer to their shipdata-inherited-values only for determining how often they use injectors.
Do they even run out of fuel? e.g. Is the ship-object-atribute 'fuel' a variable or still a fixed value?
Could you incorporate a check for NPCs so that they cannot witchjump if out-of-fuel?
Also, on
stationLaunch: "set MaxFuel: 7.0"
when jumping: check if destination system is still in fuel-range. else: cancel jump after countdown and re-apply for a jump system. (no system available in range: set AI to goto sun(scoop?) or station(bounty<50?) for fuel.)
finally when entering-system: reduce ship-fuel in relation to travel distance.
(ships being generated at WP: ship-fuel acc. to possible jump-origins minus small random value.
ships followed through wormhole: carryover of previous ship-fuel-level minus jump distance)
Another thought: it may be prudent to bind injector usage to similar checks. It may be preferable to have this fuel-usage a factor seperate from actual fuel levels and to be alterable by script, as some AI's will have different fuel-priorities than others. (eg. save fuel to jump to profitable destination/ stay local goto station to trade/ use fuel solely for injectors/etc.) this fuel-economy-factor would then determine how much value the fuel has to the ship-entity.
I think the improved fuel-methods may produce strange NPC behaviour without these checks.
edit: but I'm just a fool...
