Table of Contents

HexLibVar-based oil use

This is a new addition that allows a hexLibVar to specify from which regimeslot the oil is taken.

Rulevar(949) can be set to number >0 to activate this rule. When number for example is '1' then the engine will try to find the HexLibVar named “oil1”. When it is set to '123' it will try to find the HexLibVar 'oil123'.

The only change caused by this rulevar is that the oil will be taken from an alternate regimeslot than specified in the unitSFType.

No for the values read from HexLibVar in question. When '0' is read the original SFType regime var slot is going to be used. if '>0' is read the regimeslot specified is returned. This means you cannot make the HexLibVar cause the unit to take the fuel from regimeslot '0'. A small disability to the engine.

This rule is actually interacting with a hell of a lot of engine functions and needs to be properly tested to be sure it works as intended.

Details

Used in own power transfer (interface support not present in DC). HQ location providing transfer points determines hex.

Used in hq leveraged transfer (interface support not present in DC). HQ location providing transfer points overrules rulevar 852,854 or 856. 852,854,856 must be >0 to allow fuel regimeslot to be overruled.

Used in hq leveraged strategic transfer (interface support not present in DC). HQ location providing transfer points overrules rulevar 852,854,856. 852,854,856 must be >0 to allow fuel regimeslot to be overruled.

Used in move. Original hex move orginated from determines hex.

Used in combat. Original hex unit is defending or attacking from.

Used in anti-supply. Original hex the unit is located in.

Used in CheckMaxFuelUsed. Current hex of the unit is used.

If a unit is somehow loaded on board another the coordinates of its holder are used.

 
hexlibvaroiluse.txt · Last modified: 2016/02/26 18:24 (external edit)
 
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki