PieceTrailCEGTag: Difference between revisions

From Spring
Jump to navigationJump to search
Koshi (talk | contribs)
fix category
Knorke (talk | contribs)
added link to http://springrts.com/phpbb/viewtopic.php?f=9&t=12879&start=20
Line 29: Line 29:
otherwise all possible <pieceTrailCEGRange> tags are
otherwise all possible <pieceTrailCEGRange> tags are
expected to be valid.
expected to be valid.
Thread about this: [http://springrts.com/phpbb/viewtopic.php?f=9&t=12879&start=20]
[[Category: CEG]]
[[Category: CEG]]

Revision as of 01:53, 30 April 2011

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.

Thread about this: [1]