订阅以下载
[WOTC] Cost-Based Ability Colors

This is an updated version of Cost-Based Ability Colors for WOTC. All credit for the original mod and concept goes to infectedm and you should go rate it if you haven't already.

Overrides UITacticalHUD_Ability and is incompatible with any other mod doing the same (unsubscribe from the original).

To use with LWOTC, change "USE_ACTION_ICON_COLORS" to false in XComLW_Overhaul.ini, then inside the game, after loading a save, open the Options > Abilities menue and check the "Use Base-Game Tactical Ability HUD" box.



For the most part, the original Cost-Based Ability Colors works fine in WOTC, but there were a few situations where it needed an update, especially with regards to improving support for mod-added abilities. Here are the big changes from the original version:

• Updated Free Reload Handling: The handling of Free Reloads has been updated to take bonus charges into account and has been set to an ini toggle so that it may be disabled entirely by users when using other mods that handle free reloads (like [WOTC] Free Reload Anytime , for example).
  
• Better Override Support: The mod has been re-written to provide more robust, conditional color overrides for mod authors. The cost category can be changed or a completely custom color can be assigned to an ability and it can be conditional to the presence of an another ability or an activated effect on the unit.
  
• Updated Cost Check Logic: The cost-checking logic has been updated, primarily to support action point altering effects from mods utilizing XModBase. The mod will now recognize actions with a cost of 0 as free (was previously only considering the bFreeCost variable). A check for valid action point types has also been added and when a unit does not have a valid action point type for an ability (for example, when a unit only has Movement-only action points, etc.) the Unavailable color will be used.

If you have an ability that needs an override entry to display correctly, you can include a copy of XComWOTC_CostBasedAbilityColors.ini with your mod that contains the following:


Some examples of when you might want to use an override include abilities that only return actions via PostAbilityCostPaid(), abilities that are bFreeCost = true, but will remove action points through further processing, or when you want an ability to use a different border color than any of the preset categories under certain conditions.

The overrides are entered using a struct and the members and their usage are detailed below. Only include the OPTIONAL members that you need. See the ini file included in this mod for more information and examples:

• AbilityName (string)
  REQUIRED - The name of the ability being modified
  
  
• ModifyingAbilityName (string)
  OPTIONAL - The name of the ability that the unit must have to validate the modify
  
  
• ModifyingEffectName (string)
  OPTIONAL - The name of the effect that the unit must have to validate the modify
  
  
• ModifyingActionName (string)
  OPTIONAL - The name of the actionpoint type that the unit must have to validate the modify
  
  
• OverrideColor (string)
  OPTIONAL - If a color string is entered, the ability being modified will use that color instead
  
  
• bIsFreeAction (bool)
  OPTIONAL - If true, the ability being modified will be considered a free action
  
  
• bIsTurnEnding (bool)
  OPTIONAL - If true, the ability being modified will be considered a turn ending action
  
  
• bNotTurnEnding (bool)
  OPTIONAL - If true, the ability being modified will be considered a non-turn ending action
  
  
• NOTES:
  More than one entry for a single ability can be entered when there are more than one ModifyingAbilityName or ModifyingEffectName that may modify that ability. When multiple Modifying conditions are present in the same AbilityCostColorOverride entry, they will be treated as an AND statement. Use multiple Override entries for OR statements.
  
  The OverrideColor, if defined, will take first priority - use this to give an ability a border color outside the preset categories. The bIsFreeAction bool will be evaluated next and, if true, will use the FreeAction border color. If neither an OverrideColor or the bIsFreeAction bool are defined, then the TurnEnding bools will be evaluated for their preset colors.
  
  bIsFreeAction and bIsTurnEnding are immediate overrides - when either one is found in an override, their preset color is used and no other override entries are evaluated. bNotTurnEnding, however, is not immediate - the value is stored and continues evaluating other override entries, primarily to allow any potential bIsFreeAction overrides to supercede it.

Some Examples:


(See Change Notes for full history)

1.2.2:
• Updated color selection logic for certain turn-ending abilities to let them reflect actual costs instead of exiting early to 1-point turn ending color (sniper rifle overwatch, etc.) - Thanks to Zelfana for fix!
1.2.1:
• Updated default config to remove override for Whiplash ability (no longer needed) for compatibility support.
1.2.0:
• Added additional override variable to conditionalize color changes based on the presence of an actionpoint type.
  
• Reworked override struct handling so multiple conditions in the same override entry function as an AND statement.
  
• Changed ModifyingEffectName to look at effects applied to the unit vs effects the unit has applied.