Priority
For Sound
Flag: | Priority |
File(s): | eva(md).ini, sound(md).ini |
Values: |
|
Default: | NORMAL (RA2), 10 (TS)) |
Applicable to: | VoxTypes, VocTypes |
Priority is used in eva(md).ini and sound(md).ini to set how important a sound overlay is compared to other currently playing sounds, in order to decide when/how to play it. The available values are a ranking, from lowest importance to highest, with higher priorities overruling the lower ones (obviously).
eva(md).ini
- LOW
- NORMAL
- IMPORTANT
- CRITICAL
sound(md).ini
- LOWEST
- LOW
- NORMAL
- HIGH
- CRITICAL
In Tiberian Sun
In Tiberian Sun and Firestorm, the usage of Priority is the same, with the exceptions that
- TS/FS does not have an eva(md).ini, and
- The priorities are measured by an integer value, with 100 being the highest.
In TeamTypes
Flag: | Priority |
File(s): | ai(md).ini, maps |
Values: | Unsigned integers: All non-negative whole numbers from 0 to either 32767, 2147483647 or 4294967295. |
Applicable to: | TeamTypes |
A TeamType with higher Priority value can recruit team members from a TeamType with lower Priority value, even if the lower Priority value team hasn't yet completed its script actions. TeamTypes with equal Priority values cannot recruit from one another. Also a lower Priority TeamType cannot recruit from a TeamType with higher Priority value.
Used values range from 0 to 50. Unmodified ai(md).ini files use values in multiples of 4 (TS) or 5 or 7 (RA2/YR). Other numbers are used in single player maps which gives granular control of the priority status.
Recruitment needs the following conditions to be met: The TeamType should allow recruitment of its members with AreTeamMembersRecruitable=yes. When Recruiter=no, then their group IDs should match. Check Group for the exception case of ID with value -2. When Recruiter=yes, inter-group recruitment is allowed.
When the team members finish their script actions, they lose their Priority value and can be recruited into teams with any Priority value.