ModEnc is currently in Maintenance Mode: Changes could occur at any given moment, without advance warning.
Difference between revisions of "Report"
From ModEnc
Nighthawk200 (talk | contribs) m (Special removed) |
EvilRenegade (talk | contribs) m (Replacing Template:TTL with Template:F.) |
||
Line 17: | Line 17: | ||
}} | }} | ||
− | Specifies a sound (from {{ | + | Specifies a sound (from {{f|sound(md).ini|link}} [{{f|SoundList|link}}]) to be played when this weapon fires. |
− | The oddity here, though, as opposed to most other sound listings (like for example {{ | + | The oddity here, though, as opposed to most other sound listings (like for example {{f|VoiceDeploy|link}}) is that while the listing is chosen randomly, it's only chosen once at the creation of the individual unit instead of at each use. Meaning each built unit of that type will only play one listing, and consistantly play it when that unit fires instead of using all options on Report= list. |
The downside is that if one wishes to use the sounds of two sound(md).ini entries, they would have to make ''one'' listing for all desired sounds, even if everything is already defined in other entries to that ini. | The downside is that if one wishes to use the sounds of two sound(md).ini entries, they would have to make ''one'' listing for all desired sounds, even if everything is already defined in other entries to that ini. | ||
The only positive of this quirk is that vehicles can be a bit more individualized by exploiting multiple listings. Such as junky-looking technicals could utilize differing machine gun tones, or a weaponized propaganda truck could have 'unique' public adress system voices for seperate trucks. | The only positive of this quirk is that vehicles can be a bit more individualized by exploiting multiple listings. Such as junky-looking technicals could utilize differing machine gun tones, or a weaponized propaganda truck could have 'unique' public adress system voices for seperate trucks. |
Revision as of 09:30, 27 November 2009
Flag: | Report |
File(s): | Rules(md).ini |
Values: | strings (names of Sounds) |
Default: | none |
Applicable to: | Weapons |
Specifies a sound (from sound(md).ini [SoundList]) to be played when this weapon fires.
The oddity here, though, as opposed to most other sound listings (like for example VoiceDeploy) is that while the listing is chosen randomly, it's only chosen once at the creation of the individual unit instead of at each use. Meaning each built unit of that type will only play one listing, and consistantly play it when that unit fires instead of using all options on Report= list.
The downside is that if one wishes to use the sounds of two sound(md).ini entries, they would have to make one listing for all desired sounds, even if everything is already defined in other entries to that ini.
The only positive of this quirk is that vehicles can be a bit more individualized by exploiting multiple listings. Such as junky-looking technicals could utilize differing machine gun tones, or a weaponized propaganda truck could have 'unique' public adress system voices for seperate trucks.