PieceTrailCEGTag: Difference between revisions

From Spring
Jump to navigationJump to search
Knorke (talk | contribs)
now its pieceExplosionGenerators
Flozi (talk | contribs)
update link, deprecate
Line 1: Line 1:
This is replaced by [[Units-UnitDefs#pieceExplosionGenerators]]
{{deprecated}}
This is replaced by [[Gamedev:UnitDefs#pieceExplosionGenerators]]


'''Old way does not to work anymore.'''
'''Old way does not to work anymore.'''

Revision as of 23:50, 28 October 2013

Warning! This page is outdated! The information displayed may no longer be valid, or has not been updated in a long time. Please refer to a different page for current information.


This is replaced by Gamedev:UnitDefs#pieceExplosionGenerators

Old way does not to work anymore.

Related thread with example and a way to easily convert from old to new system: http://springrts.com/phpbb/viewtopic.php?f=14&t=27554


original page below


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]