Off the top of my head

you could make it work by creating individual buffs for each effect and then putting them into the AbilityIonBlast or more likely the BuffIonBlast as bufftypes under an "InstantActionTriggerType" of "OnChance"....

Basically you would just need to fill the BuffIonBlast with varrations on....

buffInstantActionType "ApplyBuffToSelf"
instantActionTriggerType "OnChance"
buffApplyChance
Level:0 0.0100000
Level:1 0.0100000
Level:2 0.0100000
buffType "BuffCaptureNeutralEntity"
effectInfo
effectAttachInfo
attachType "Invalid"
smallEffectName ""
largeEffectName ""
soundID ""

NOTE: thats just an example i took from a planet assaulting troop ship im testing out. but thats the general idea

So I looked in the entity file for the Vasari Carrier's fighter phasing ability for the OnChance syntax to double check and the suggested EMPBlast files to see how buffs call over buffs, tried to mimic the Ion Blast to do the same, and Sins doesn't want to launch As soon as I remove the 'trigger' entity file for the buff, it starts up fine.

Here's what I got (relevant lines only):

AbilityIonBlast.entity:

buffInstantActionType "ApplyBuffToTargetWithTravel"
instantActionTriggerType "AlwaysPerform"
buffType "BuffIonBlastTrigger"
targetFilter
numOwnerships 1
ownership "Friendly"
numObjects 3
object "CapitalShip"
object "Frigate"
object "PlanetModule"
numConstraints 0
range
Level:0 7000.000000
Level:1 7000.000000
Level:2 7000.000000

BuffIonBlastTrigger.entity:

numInstantActions 1
instantAction
buffInstantActionType "ApplyBuffToTarget"
instantActionTriggerType "OnChance"
buffApplyChance
Level:0 0.330000
Level:1 0.330000
Level:2 0.330000
bufftype "BuffIonBlastEngines"
targetFilter
numOwnerships 1
ownership "Friendly"
numObjects 3
object "CapitalShip"
object "Frigate"
object "PlanetModule"
numConstraints 0
range
Level:0 7000.000000
Level:1 7000.000000
Level:2 7000.000000
effectInfo
effectAttachInfo
attachType "Invalid"
smallEffectName ""
largeEffectName ""
soundID ""
numPeriodicActions 0
numOverTimeActions 0
numEntityModifiers 0
numEntityBoolModifiers 0
numFinishConditions 1
finishCondition
finishConditionType "TimeElapsed"
time
Level:0 3.000000
Level:1 5.000000
Level:2 7.000000

BuffIonBlastEngines.entity:

numInstantActions 2
instantAction
buffInstantActionType "PlayPersistantAttachedEffect"
instantActionTriggerType "OnDelay"
delayTime 0.000000
effectInfo
effectAttachInfo
attachType "Above"
smallEffectName "CapitalBuff_IonDisableSmall"
largeEffectName "CapitalBuff_IonDisableLarge"
soundID ""
instantAction
buffInstantActionType "DoInterrupt"
instantActionTriggerType "OnDelay"
delayTime 0.000000
numPeriodicActions 0
numOverTimeActions 0
numEntityModifiers 0
numEntityBoolModifiers 2
entityBoolModifier "DisableLinearEngines"
entityBoolModifier "DisableAngularEngines"
numFinishConditions 0

Nothing jumps out as being way off The Ability file calls on the trigget buff (I set it to friendly targets for easier testing), the trigger tells the buff to apply to the target, and 33% of the time to cast the IonBlastEngines buff (syntax borrowed from how EMPBlastSpawn calls sub-buff) and to expire in 3/5/7 seconds. The IonBlastEngines buff calls for the effect to be placed on target, interrupt target's actions, and disable actions.

The trigger file is what's causing the game to crash on launch - I tried setting the chance to 1.000000, tried doing it OnDelay 0, using the same effects as the actual ion blast, nada..

I'm stumped.

Well, Craig says it's certainly possible, so gotta figure out why it doesn't like my trigger file so much

Well the weird thing is, at one point I removed OnChance entirely and set it to OnDelay of 0, and it still gave a runtime error on game start

PeriodicActions seems like it only works for passives, it basically sounds like for a constantly applied buff, every one in a while it does another buff. So I could make a passive "EMP field" projection that would have a chance to disable something every so often, but that's not quite the same

I realized that after I posted I might be able to use it as a workaround, will have to try it when I get home.



I had it with the same finish condition as the default BuffIonBlast at one point, and that didn't do anything. I'll try it again later just to be sure. My logic was that the "trigger" is the main buff that ends in 3/5/7 seconds for the appropriate level, and it just calls a sub-buff to apply the actual effect, but when the trigger expires so does the sub-buff.

Like Foogsie said on IRC last night, it'd be nice to be able to debug a bit to see where it goes wrong I don't mind the trial and error approach, but guessing as to what's wrong can be a little frustrating