ModEnc is currently in Maintenance Mode: Changes could occur at any given moment, without advance warning.
Difference between revisions of "Priority"
From ModEnc
(Split and moved the flag section under the subheaders) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
==For Sound== | ==For Sound== | ||
| + | {{flag|name=Priority|files={{Categ|ini=eva}}, {{Categ|ini=sound}}|values=<dl><dt>{{ra2}}/{{yr}}<dd><dl><dt>Eva(md).ini: (case-insensitive, ''default'')<dd>LOW, ''NORMAL'', IMPORTANT, CRITICAL<dt>Sound(md).ini: (case-insensitive, ''default'')<dd>LOWEST, LOW, ''NORMAL'', HIGH, CRITICAL</dl><dt>{{ts}}/{{fs}}<dd>{{Values|unsigned integer|0–100}}</dl>|default=NORMAL (RA2), 10 (TS))|types={{Categ|DialogList|VoxTypes}}, {{Categ|SoundList|VocTypes}}|ts=yes|fs=yes|ets=yes|ra2=yes|yr=yes|rp=yes}} | ||
| − | + | {{f|Priority}} is used in {{ini|eva}} and {{ini|sound}} 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=== | ===eva(md).ini=== | ||
#LOW | #LOW | ||
| Line 21: | Line 21: | ||
'''On a closer look''', it is undeniable that three of four used values in eva(md) are also used in sound(md); given that both files use the same flag, and both files are dealing with sound overlay, one cannot deny the chance that it's the same function for both files. This would suggest that the values are interchangeable, meaning that IMPORTANT is also valid in sound(md), while LOWEST and HIGH can also be used in eva(md). This is, however, purely theoretical and has not been tested. // DC: flag template update should clear this up, but leaving in just in case --> | '''On a closer look''', it is undeniable that three of four used values in eva(md) are also used in sound(md); given that both files use the same flag, and both files are dealing with sound overlay, one cannot deny the chance that it's the same function for both files. This would suggest that the values are interchangeable, meaning that IMPORTANT is also valid in sound(md), while LOWEST and HIGH can also be used in eva(md). This is, however, purely theoretical and has not been tested. // DC: flag template update should clear this up, but leaving in just in case --> | ||
| − | + | ====In Tiberian Sun==== | |
| − | In | + | In {{ts}} and {{fs}}, the usage of {{f|Priority}} is the same, with the exceptions that |
| − | #TS/FS does not have an eva | + | #TS/FS does not have an {{ini|eva}}, and |
| − | #The priorities are measured by an integer value, with 100 being the highest | + | #The priorities are measured by an integer value, with 100 being the highest. |
==In [[TeamTypes]]== | ==In [[TeamTypes]]== | ||
| + | {{Flag | ||
| + | |name={{PAGENAME}} | ||
| + | |files={{Categ|ini=ai}}, {{Categ|maps}} | ||
| + | |values={{Values|unsigned integer}} | ||
| + | |types={{Categ|TeamTypes}} | ||
| + | |ts=yes | ||
| + | |fs=yes | ||
| + | |hp=yes | ||
| + | |ra2=yes | ||
| + | |yr=yes | ||
| + | |ares=yes | ||
| + | }} | ||
| − | + | A [[TeamTypes|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 [[ScriptTypes|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 {{ini|ai}} 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 {{f|AreTeamMembersRecruitable|yes|link}}. When {{f|Recruiter|no|link}}, then their [[Group|group IDs]] should match. Check {{f|Group|link}} for the exception case of ID with value -2. When {{f|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. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 00:21, 6 September 2020
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.
