PieceTrailCEGTag: Difference between revisions
From Spring
Jump to navigationJump to search
New page: From Kloot: In case you missed the changelog entry, this can now be done using the new unit FBI tags pieceTrailCEGTag and pieceTrailCEGRange (where Tag is a string and Range is an integer... |
No edit summary |
||
| Line 13: | Line 13: | ||
// CEG definitions | // CEG definitions | ||
[Fire0] | [Fire0] | ||
... | |||
[Fire1] | [Fire1] | ||
... | |||
[Fire2] | [Fire2] | ||
... | |||
[Fire3] | [Fire3] | ||
... | |||
</code> | </code> | ||
Revision as of 19:54, 16 April 2009
From Kloot:
In case you missed the changelog entry, this can now be done using the new unit FBI tags pieceTrailCEGTag and pieceTrailCEGRange (where Tag is a string and Range is an integer). If Tag is given, each piece of an exploding unit randomly loads one of <pieceTrailCEGRange> CEG's whose tag starts with the prefix <pieceTrailCEGTag> and ends with a number in the range [0, pieceTrailCEGRange - 1]:
Code:
// CEG definitions
[Fire0]
...
[Fire1]
...
[Fire2]
...
[Fire3]
...
Code:
// unit FBI
pieceTrailCEGTag = "Fire";
pieceTrailCEGRange = 4;
If range is 1 (default) then you only need Fire0 defined, otherwise all possible <pieceTrailCEGRange> tags are expected to be valid.
