HunterSeekerEmergeSpeed
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Flag: | HunterSeekerEmergeSpeed |
File(s): | rules(md).ini |
Values: | ERROR – No value types set! Please edit this page and fix the Flag template! |
This entry was copied from DeeZire's Red Alert 2 and Yuris Revenge INI Editing Guide for the sake of completeness. As it is not our intention to rip off DeeZire's work, this article is subject to a re-write and update with the latest community knowledge. For further information, please read Inclusion of The Guide. |
The speed that a unit with HunterSeeker=yes set (which must also be defined with the GDIHunterSeeker= or NodHunterSeeker= statements) will ascend from the structure from which it is created as defined with the HSBuilding= statement in the [SpecialWeapons] section. Note that although a unit assigned as HunterSeeker=yes can have the AlternateSpeed= and AlternateFlightLevel= tags, those are only used if the unit is constructed rather than spawned thus are used only when it exits the factory from which it is built. It has not been established if this portion of the Hunter Seeker logic works in Red Alert 2.