Configuration

Configuration

All parameters are loaded from the {game}/x64/scripts/config/TheInsurgentsChainBenefitsConfig.lua file when opening the game.

This configuration file can be modified via any text editor. The following configuration is the default and equivalent to how chain benefits work in the vanilla game:

Default Configuration
local function config(targetTypes, benefitTypes, particleEffects, statusEffects, augments)
  local benefits = {
    --{{targetType0, benefitType0, benefitParameter0, particleEffect0, chance0}, {...}, {targetTypeX, benefitTypeX, benefitParameterX, particleEffectX, chanceX}}
    {--Chain Level 0

    },
    {--Chain Level 1
      {targetTypes.party, benefitTypes.hp, 10, particleEffects.chainBenefit, 10.00},
      {targetTypes.party, benefitTypes.mp, 10, particleEffects.chainBenefit, 10.00},
    },
    {--Chain Level 2
      {targetTypes.party, benefitTypes.hp, 10, particleEffects.chainBenefit, 20.00},
      {targetTypes.party, benefitTypes.mp, 10, particleEffects.chainBenefit, 20.00},
      {targetTypes.leader, benefitTypes.statusEffect, statusEffects.protect, particleEffects.chainBenefit, 5.00},
      {targetTypes.leader, benefitTypes.statusEffect, statusEffects.shell, particleEffects.chainBenefit, 5.00},
    },
    {--Chain Level 3
      {targetTypes.party, benefitTypes.hp, 10, particleEffects.chainBenefit, 25.00},
      {targetTypes.party, benefitTypes.mp, 10, particleEffects.chainBenefit, 25.00},
      {targetTypes.party, benefitTypes.statusEffect, statusEffects.protect, particleEffects.chainBenefit, 5.00},
      {targetTypes.party, benefitTypes.statusEffect, statusEffects.shell, particleEffects.chainBenefit, 5.00}
    }
  }

  return benefits
end

return config

Below is a list of all configurable options and what they are used for:

Target Type

The type of the targets the benefit is applied to.

Benefit Type

The type of the benefit that is applied.

Benefit Parameter

The effect or efficiency of the benefit (0 -> 255).

For example: A benefit type of 4 and a benefit parameter of 3 would result in all nearby foes levelling up by 3 levels.

Particle Effect

The particle effect that will be played when the benefit is applied.

Chance

The chance of the benefit to apply.

Notes

Parameters are processed top to bottom and anything past the sum of 100 of all benefit chances is ignored. For example:

  • If there are 3 benefits with the following chances: 80%, 21%, 10%. The chance of the second one is actually 20%, not 21% and the third one is ignored.

  • If there are 2 benefits with the following chances: 50%, 20%. There is a 30% chance that no benefit will be granted.

The order of the benefit list determines to which chain level the benefits are tied. So even if some chain level have no benefits, there should still be an empty entry ({}) like in the default configuration.

  • You cannot give a status effect to a target with KO, Stone or X-Zone.

  • Status effects and augments are always temporarily applied. The default duration is defined in Battlepack -> Section 15 for status effects and Battlepack -> Section 58 for augments. If a status effect or augment has no timer, they will not be applied.

  • A status effect is only applied to a target if they lack the status effects that conflict with the former. For example, a target cannot get Berserk if they have Confuse. This behaviour is defined in Battlepack -> Section 15 -> Absent Status Effects.

  • Applying the augments Physical-Immunity, Magick-Immunity, or Status-Immunity to a target will display a combat log message. Once the timer runs out, another message will be displayed.

  • A level up is not possible for a party member if weak-mode is enabled.

  • A level up pop-up is only displayed for party members.

For a list of status effect and augment identifiers, you can view this spreadsheet.

For a list of all particle effects, you can view this spreadsheet. Be mindful as some of them last indefinitely until changing the location.

Since this script also allows modifying existing chain benefits, the ones configured under Battlepack -> Section 6 will be ignored to prevent having to maintain 2 differently structured configuration files.

Last updated