5 réponses à ce sujet

[M. Rieder]

What is the last argument, string sEffectTag, for?  Is it so you can create a blueprint of a trigger which will specify the size of the AOE?   If not, how do you specify the size of the AOE?

Modifié par M. Rieder, 04 février 2012 - 01:25 .

[painofdungeoneternal]

It makes the AOE have a given tag, which can be used to refer to it later, or prevent duplicate AOE's ( see blade barrier ).

Size of the AOE is determined by the 2da referred to as the first argument ( vfx_persistent.2da ), the 3 middle parameters if not "" will let you set custom scripts for it. Lookup that 2da and you will see how to set the size of it.

[M. Rieder]

Thanks pain.

[Dann-J]

Does anyone happen to know what the default size of a custom-defined AOE is? I've used them many times, but have no idea how far the radius extends.

[MasterChanger]

DannJ wrote...

Does anyone happen to know what the default size of a custom-defined AOE is? I've used them many times, but have no idea how far the radius extends.

As far as I know, that is defined by the row the first parameter is linked to. The scripts that are listed in the other parameters can override the OnEnter, OnHB, and OnExit columns for that AOE, but not the other columns.

The size would be set by a combination of the first four columns after the label: Shape, Radius, Width, and Length.

Unfortunately, this means that each time you want a VFX of different size, you need to create a new row. I suppose the alternative would be to have a shape that's bigger than you need and then determine within the scripts whether the object is within the polygon that you want using trig functions.

[Dann-J]

Thanks for the info. I'll look up the constant value for the custom option and check what 2DA line it defaults to.

I usually define the search radius in the custom scripts, but the default radius in the 2DA would still determine when the OnEnter and OnExit scripts fire.