Jump to content

RandomRate: Difference between revisions

From ModEnc²
en>Crimsonum
Added flag section and a warning about random events
en>Starkku
Added information about a bug concerning parsing of RandomRate
Line 10: Line 10:
|yr=yes
|yr=yes
}}
}}
{{HorizontalBar|In Tiberian Sun, some random events such as RandomRate are not synchronized properly between players and cause Reconnection Errors. Use RandomRate with caution.|image=Warning.png}}


This tag holds two values. These specify the range at which a random Rate= will be generated. In debris animations, this makes the debris spin (because its animation is of the debris spinning) at a random speed each time the debris is generated.
This tag holds two values. These specify the range at which a random Rate= will be generated. In debris animations, this makes the debris spin (because its animation is of the debris spinning) at a random speed each time the debris is generated.


{{HorizontalBar|In Tiberian Sun, random events are known to cause Reconnection Errors. The game has trouble synchronizing random events between players. Use RandomRate with caution.|image=Warning.png}}
{{Bugs}}
*Due to an oversight this tag does not function correctly if values are listed in expected order of minimum & maximum. Swapping the order of the values allows it to function as expected.

Revision as of 14:34, 26 March 2022

Tiberian Dawn Red Alert Tiberian Sun Firestorm Red Alert 2 Yuri's Revenge
Flag: RandomRate
File(s): Art(md).ini
Values: Two Integers, separated by comma
Default: 0,0
Applicable to: Animations


In Tiberian Sun, some random events such as RandomRate are not synchronized properly between players and cause Reconnection Errors. Use RandomRate with caution.

This tag holds two values. These specify the range at which a random Rate= will be generated. In debris animations, this makes the debris spin (because its animation is of the debris spinning) at a random speed each time the debris is generated.

Bugs/Side-Effects/Unexpected Limitations

  • Due to an oversight this tag does not function correctly if values are listed in expected order of minimum & maximum. Swapping the order of the values allows it to function as expected.