Report - Revision history

Rain-Islet: [bot] Batch update {{Bugs}} templates.

2025-07-02T15:47:23Z

[bot] Batch update {{Bugs}} templates.

← Older revision		Revision as of 17:47, 2 July 2025
Line 27:		Line 27:
	*Since the '''Report''' tag does not use electricity to operate, even if the building animation does not play due to the lack of electricity, [but] the continuous (loop) sound specified in the '''Report''' section for the building animation will continue to play until the building is destroyed/sold or no longer exists.		*Since the '''Report''' tag does not use electricity to operate, even if the building animation does not play due to the lack of electricity, [but] the continuous (loop) sound specified in the '''Report''' section for the building animation will continue to play until the building is destroyed/sold or no longer exists.
	*If you use the [[StartSound]] and [[Report]] tags in the animation [[Report]] tags are ignored.		*If you use the [[StartSound]] and [[Report]] tags in the animation [[Report]] tags are ignored.
	{{Bugs}}		=={{Bugs}}==
	'''Report''' that comes from weapons If we define it like this:<br>		'''Report''' that comes from weapons If we define it like this:<br>
	'''[M60]'''<br>		'''[M60]'''<br>

MarkJFox: 12 revisions imported

2025-03-31T20:03:23Z

12 revisions imported

← Older revision	Revision as of 22:03, 31 March 2025
(No difference)

en>Testid123 at 13:25, 16 January 2025

2025-01-16T13:25:05Z

← Older revision		Revision as of 15:25, 16 January 2025
Line 32:		Line 32:
	'''Report=GIAttack,InitiateAttack'''<br>		'''Report=GIAttack,InitiateAttack'''<br>
	Even though they are [[TechnoTypes]] of the same type, sometimes attacks from [[TechnoTypes]] of the same type but being the 2nd, 3rd, or 4th unit will play different attack sounds.<br>		Even though they are [[TechnoTypes]] of the same type, sometimes attacks from [[TechnoTypes]] of the same type but being the 2nd, 3rd, or 4th unit will play different attack sounds.<br>
			*If the [[Report]] tag is used on building animations The sound produced by this tag Will be played along with the first building placement (equivalent to tag [[BuildingSlam]]).<br>

en>Testid123 at 15:34, 6 January 2025

2025-01-06T15:34:01Z

← Older revision		Revision as of 17:34, 6 January 2025
Line 26:		Line 26:
	==Note==		==Note==
	*Since the '''Report''' tag does not use electricity to operate, even if the building animation does not play due to the lack of electricity, [but] the continuous (loop) sound specified in the '''Report''' section for the building animation will continue to play until the building is destroyed/sold or no longer exists.		*Since the '''Report''' tag does not use electricity to operate, even if the building animation does not play due to the lack of electricity, [but] the continuous (loop) sound specified in the '''Report''' section for the building animation will continue to play until the building is destroyed/sold or no longer exists.
			*If you use the [[StartSound]] and [[Report]] tags in the animation [[Report]] tags are ignored.
	{{Bugs}}		{{Bugs}}
	'''Report''' that comes from weapons If we define it like this:<br>		'''Report''' that comes from weapons If we define it like this:<br>

en>Testid123 at 10:27, 4 January 2025

2025-01-04T10:27:18Z

← Older revision		Revision as of 12:27, 4 January 2025
Line 26:		Line 26:
	==Note==		==Note==
	*Since the '''Report''' tag does not use electricity to operate, even if the building animation does not play due to the lack of electricity, [but] the continuous (loop) sound specified in the '''Report''' section for the building animation will continue to play until the building is destroyed/sold or no longer exists.		*Since the '''Report''' tag does not use electricity to operate, even if the building animation does not play due to the lack of electricity, [but] the continuous (loop) sound specified in the '''Report''' section for the building animation will continue to play until the building is destroyed/sold or no longer exists.
			{{Bugs}}
			'''Report''' that comes from weapons If we define it like this:<br>
			'''[M60]'''<br>
			'''Report=GIAttack,InitiateAttack'''<br>
			Even though they are [[TechnoTypes]] of the same type, sometimes attacks from [[TechnoTypes]] of the same type but being the 2nd, 3rd, or 4th unit will play different attack sounds.<br>

en>Testid123 at 06:08, 11 November 2024

2024-11-11T06:08:39Z

← Older revision		Revision as of 08:08, 11 November 2024
Line 16:		Line 16:
	\|rp=yes		\|rp=yes
	}}		}}

	Specifies a sound (from {{f\|sound(md).ini\|link}} [{{f\|SoundList\|link}}]) to be played when this weapon fires.		Specifies a sound (from {{f\|sound(md).ini\|link}} [{{f\|SoundList\|link}}]) to be played when this weapon fires.

Line 24:		Line 23:

	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.

			==Note==
			*Since the '''Report''' tag does not use electricity to operate, even if the building animation does not play due to the lack of electricity, [but] the continuous (loop) sound specified in the '''Report''' section for the building animation will continue to play until the building is destroyed/sold or no longer exists.

en>Testid123 at 15:48, 21 July 2024

2024-07-21T15:48:57Z

← Older revision		Revision as of 17:48, 21 July 2024
Line 4:		Line 4:
	\|values=strings (names of [[Sound]]s)		\|values=strings (names of [[Sound]]s)
	\|default=none		\|default=none
	\|types={{Categ\|Weapon\|Weapons}}		\|types={{Categ\|Weapon\|Weapons}}, {{Categ\|Animations}}
	\|games=[[RA]], [[TS]], [[RA2]], [[YR]]		\|games=[[RA]], [[TS]], [[RA2]], [[YR]]
	\|ra=yes		\|ra=yes

en>EvilRenegade: Replacing Template:TTL with Template:F.

2009-11-27T08:30:32Z

Replacing Template:TTL with Template:F.

← Older revision		Revision as of 10:30, 27 November 2009
Line 17:		Line 17:
	}}		}}

	Specifies a sound (from {{~~TTL~~\|sound(md).ini}} [{{~~TTL~~\|SoundList}}]) to be played when this weapon fires.		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 {{~~TTL~~\|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 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.

en>Nighthawk200: Special removed

2007-04-02T09:56:14Z

Special removed

← Older revision		Revision as of 11:56, 2 April 2007
Line 3:		Line 3:
	\|files={{Categ\|Rules(md).ini}}		\|files={{Categ\|Rules(md).ini}}
	\|values=strings (names of [[Sound]]s)		\|values=strings (names of [[Sound]]s)
	~~\|special=none~~
	\|default=none		\|default=none
	\|types={{Categ\|Weapon\|Weapons}}		\|types={{Categ\|Weapon\|Weapons}}

72.73.241.227: grammar editing mostly, sorry

2007-02-09T06:04:00Z

grammar editing mostly, sorry

← Older revision		Revision as of 08:04, 9 February 2007
Line 22:		Line 22:
	The oddity here, though, as opposed to most other sound listings (like for example {{TTL\|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 oddity here, though, as opposed to most other sound listings (like for example {{TTL\|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 ~~definedin~~ 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 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.