Image - Revision history

ATHSE: /* In {{ini|art}} */

2025-04-11T10:59:35Z

In {{ini|art}}

← Older revision		Revision as of 12:59, 11 April 2025
Line 31:		Line 31:
	When used in art(md).ini, this acts like a redirect. Image therefore instructs the game to use another object for the art, but it retains many or all of the traits of the first object with the <tt>Image=</tt> tag. Many [[BuildingTypes\|building]] animations, especially for damaged states, reuse the undamaged artwork this way, instructing the virtual damaged art object to use the real undamaged art.		When used in art(md).ini, this acts like a redirect. Image therefore instructs the game to use another object for the art, but it retains many or all of the traits of the first object with the <tt>Image=</tt> tag. Many [[BuildingTypes\|building]] animations, especially for damaged states, reuse the undamaged artwork this way, instructing the virtual damaged art object to use the real undamaged art.

	Image is also ignored when added to the various unit types. One example of this is the [CAML] infantry in YR has Image=JOSH, and yet it correctly displays CAML.SHP anyway. [[Projectile]] and [[~~Particle~~]] art is handled similarly, the art can only be selected from {{ini\|rules}}.		Image is also ignored when added to the various unit types. One example of this is the [CAML] infantry in YR has Image=JOSH, and yet it correctly displays CAML.SHP anyway. [[Projectile]] and [[Particles\|particle]] art is handled similarly, the art can only be selected from {{ini\|rules}}.

	==See Also==		==See Also==

ATHSE: linky

2025-04-11T10:54:10Z

linky

← Older revision		Revision as of 12:54, 11 April 2025
Line 31:		Line 31:
	When used in art(md).ini, this acts like a redirect. Image therefore instructs the game to use another object for the art, but it retains many or all of the traits of the first object with the <tt>Image=</tt> tag. Many [[BuildingTypes\|building]] animations, especially for damaged states, reuse the undamaged artwork this way, instructing the virtual damaged art object to use the real undamaged art.		When used in art(md).ini, this acts like a redirect. Image therefore instructs the game to use another object for the art, but it retains many or all of the traits of the first object with the <tt>Image=</tt> tag. Many [[BuildingTypes\|building]] animations, especially for damaged states, reuse the undamaged artwork this way, instructing the virtual damaged art object to use the real undamaged art.

	Image is also ignored when added to the various unit types. One example of this is the [CAML] infantry in YR has Image=JOSH, and yet it correctly displays CAML.SHP anyway. Projectile art is handled similarly, the art can only be selected from {{ini\|rules}}.		Image is also ignored when added to the various unit types. One example of this is the [CAML] infantry in YR has Image=JOSH, and yet it correctly displays CAML.SHP anyway. [[Projectile]] and [[Particle]] art is handled similarly, the art can only be selected from {{ini\|rules}}.

	==See Also==		==See Also==

ATHSE at 10:50, 11 April 2025

2025-04-11T10:50:06Z

← Older revision		Revision as of 12:50, 11 April 2025
Line 26:		Line 26:
	*[[AircraftTypes]] Image and [[Cameo]] will be displayed blank.		*[[AircraftTypes]] Image and [[Cameo]] will be displayed blank.

	*[[BuildingTypes]] [[Cameo]] will be displayed blank.		*[[BuildingTypes]] only the [[Cameo]] will be displayed blank.

	==In {{ini\|art}}==		==In {{ini\|art}}==

ATHSE at 10:49, 11 April 2025

2025-04-11T10:49:21Z

← Older revision		Revision as of 12:49, 11 April 2025
Line 22:		Line 22:

	In {{ra}}, setting <tt>Image=none</tt> for [[VehicleTypes]], [[AircraftTypes]], [[BuildingTypes]] will give the following results:		In {{ra}}, setting <tt>Image=none</tt> for [[VehicleTypes]], [[AircraftTypes]], [[BuildingTypes]] will give the following results:
	*[[VehicleTypes]] [[Image]] and [[Cameo]] will be displayed blank. When built, there will be a continuous <b>READY</b> message over its [[Cameo]] slot.		*[[VehicleTypes]] Image and [[Cameo]] will be displayed blank. When built, there will be a continuous <b>READY</b> message over its [[Cameo]] slot.

	*[[AircraftTypes]] [[Image]] and [[Cameo]] will be displayed blank.		*[[AircraftTypes]] Image and [[Cameo]] will be displayed blank.

	*[[BuildingTypes]] [[Cameo]] will be displayed blank.		*[[BuildingTypes]] [[Cameo]] will be displayed blank.

ATHSE at 10:47, 11 April 2025

2025-04-11T10:47:08Z

← Older revision		Revision as of 12:47, 11 April 2025
Line 29:		Line 29:

	==In {{ini\|art}}==		==In {{ini\|art}}==
	When used in art(md).ini, this acts like a redirect. Image therefore instructs the game to use another object for the art, but it retains many or all of the traits of the first object with the <tt>Image=</tt> tag. Many [[BuildingTypes\|building]] animations, especially for damaged states, reuse to the undamaged artwork this way, ~~redirecting~~ the virtual damaged art object to use the real undamaged art.		When used in art(md).ini, this acts like a redirect. Image therefore instructs the game to use another object for the art, but it retains many or all of the traits of the first object with the <tt>Image=</tt> tag. Many [[BuildingTypes\|building]] animations, especially for damaged states, reuse the undamaged artwork this way, instructing the virtual damaged art object to use the real undamaged art.

	Image is also ignored when added to the various unit types. One example of this is the [CAML] infantry in YR has Image=JOSH, and yet it correctly displays CAML.SHP anyway. Projectile art is handled similarly, the art can only be selected from {{ini\|rules}}.		Image is also ignored when added to the various unit types. One example of this is the [CAML] infantry in YR has Image=JOSH, and yet it correctly displays CAML.SHP anyway. Projectile art is handled similarly, the art can only be selected from {{ini\|rules}}.

ATHSE at 10:45, 11 April 2025

2025-04-11T10:45:45Z

← Older revision		Revision as of 12:45, 11 April 2025
Line 14:		Line 14:
	\|yr=yes		\|yr=yes
	}}		}}
	Specifies the section from {{ini\|art}} which contains this object's graphical parameters such as cameos, firing offsets, attached animations, movement sequence, etc.		Specifies the section from {{ini\|art}} which contains this object's graphical parameters such as cameos, firing offsets, attached animations, movement sequence, etc. When not specified, the object art used is that of its own name, so having <tt>Image=CAWS01DM</tt> in [CAWS01DM] is redundant.

	The exception to this is Tiberium in TS (and Ore/Gems in RA2) which uses a lookup table of values. See [[Tiberiums]] for details.		The exception to this is Tiberium in TS (and Ore/Gems in RA2) which uses a lookup table of values. See [[Tiberiums]] for details.

	==In {{ini\|rules}}==		==In {{ini\|rules}}==
	~~For~~ [[~~AircraftTypes~~]]		The substitute art requested by <tt>Image=</tt> must have a valid {{ini\|art}} entry, and where appropriate, specifies what type of art, such as a voxel. This is especially important when specifying substitute voxel art, as the game assumes art is in [[Shape\|sprite]] format, unless specified in its art section, and without it bad things can happen. Therefore referencing voxel turret art directly in [[VoxelAnims]], requires first creating a section for it in {{ini\|art}} with {{f\|Voxel\|yes\|link}}.
	~~if we specify Image=any turret <b>(GTNKTUR~~,~~HTNKTUR~~,~~LTNKTUR)</b> We need to add tags~~. {{f\|Voxel\|yes\|~~Link~~}} ~~Go to section <b>GTNKTUR,HTNKTUR,LTNKTUR</b>~~

	~~within~~ [[~~Artmd.ini~~]] ~~even though~~ <b>~~GTNKTUR,HTNKTUR,LTNKTUR~~</b> ~~are~~ [[~~Voxel~~]] ~~files, If you don't do this you will get {{f\|Internal Error\|004145BD\|Link}}~~.		In {{ra}}, setting <tt>Image=none</tt> for [[VehicleTypes]], [[AircraftTypes]], [[BuildingTypes]] will give the following results:
			*[[VehicleTypes]] [[Image]] and [[Cameo]] will be displayed blank. When built, there will be a continuous <b>READY</b> message over its [[Cameo]] slot.

	~~For [[Red Alert]], setting <b><font style="color:red">Image=none</font></b> for [[VehicleTypes]], [[AircraftTypes]], [[BuildingTypes]] will give the following results.~~

	*[[VehicleTypes]] [[Image]] and [[Cameo]] will be displayed blank. And when it's completed, there will be a continuous <b>READY</b> message in the [[Cameo]] section.
	~~[[File:Image=noe for Ra1.png]]~~
	*[[AircraftTypes]] [[Image]] and [[Cameo]] will be displayed blank.		*[[AircraftTypes]] [[Image]] and [[Cameo]] will be displayed blank.

	*[[BuildingTypes]] [[Cameo]] will be displayed blank.~~<br>~~		*[[BuildingTypes]] [[Cameo]] will be displayed blank.
	~~If you have SHP file or Voxel file which matches the name [[TechnoTypes]] which is written in [[ rules(md).ini]] such as <b>YAPOWR</b><br>~~
	~~Even if you didn't specify <b>Image=YAPOWR</b> In-game images will be available automatically.~~


	==In {{ini\|art}}==		==In {{ini\|art}}==
	When used in art(md).ini, this acts like a redirect. Image therefore instructs the game to use another object for the art, but it retains many or all of the traits of the first object with the <tt>Image=</tt> tag. Many [[BuildingTypes\|building]] animations, especially for damaged states, reuse to the undamaged artwork this way, redirecting the virtual damaged art object to use the real undamaged art.		When used in art(md).ini, this acts like a redirect. Image therefore instructs the game to use another object for the art, but it retains many or all of the traits of the first object with the <tt>Image=</tt> tag. Many [[BuildingTypes\|building]] animations, especially for damaged states, reuse to the undamaged artwork this way, redirecting the virtual damaged art object to use the real undamaged art.

	The substitute art requested by <tt>Image=</tt> must have a valid {{ini\|art}} entry, and where appropriate, specifies what type of art, such as a voxel. This is especially important when specifying substitute voxel art, as the game assumes art is in [[Shape\|sprite]] format, unless specified in its art section, and without it bad things can happen. Therefore referencing voxel turret art directly in [[VoxelAnims]], requires first creating a section for it in {{ini\|art}} with {{f\|Voxel\|yes\|link}}.		Image is also ignored when added to the various unit types. One example of this is the [CAML] infantry in YR has Image=JOSH, and yet it correctly displays CAML.SHP anyway. Projectile art is handled similarly, the art can only be selected from {{ini\|rules}}.

	Image is also ignored when added to the various unit types. One example of this is the [CAML] infantry in YR has Image=JOSH, and yet it correctly displays CAML.SHP anyway. Projectile art is ~~also~~ handled similarly, the art can only be selected from {{ini\|rules}}.

	==See Also==		==See Also==

ATHSE at 10:39, 11 April 2025

2025-04-11T10:39:26Z

← Older revision		Revision as of 12:39, 11 April 2025
Line 36:		Line 36:

	==In {{ini\|art}}==		==In {{ini\|art}}==
	When used in art(md).ini, this acts like a redirect. Image therefore instructs the game to use another object for the art, but it retains many or all of the traits of the first object with the ~~{{Tt\|~~Image=~~=}}~~ tag. Many [[BuildingTypes\|building]] animations, especially for damaged states, reuse to the undamaged artwork this way, redirecting the virtual damaged art object to use the real undamaged art.		When used in art(md).ini, this acts like a redirect. Image therefore instructs the game to use another object for the art, but it retains many or all of the traits of the first object with the <tt>Image=</tt> tag. Many [[BuildingTypes\|building]] animations, especially for damaged states, reuse to the undamaged artwork this way, redirecting the virtual damaged art object to use the real undamaged art.

	The substitute art requested by ~~{{Tt\|~~Image=}} must have a valid {{ini\|art}} entry, and where appropriate, specifies what type of art, such as a voxel. This is especially important when specifying substitute voxel art, as the game assumes art is in [[Shape\|sprite]] format, unless specified in its art section, and without it bad things can happen. Therefore referencing voxel turret art directly in [[VoxelAnims]], requires first creating a section for it in {{ini\|art}} with {{f\|Voxel\|yes\|link}}.		The substitute art requested by <tt>Image=</tt> must have a valid {{ini\|art}} entry, and where appropriate, specifies what type of art, such as a voxel. This is especially important when specifying substitute voxel art, as the game assumes art is in [[Shape\|sprite]] format, unless specified in its art section, and without it bad things can happen. Therefore referencing voxel turret art directly in [[VoxelAnims]], requires first creating a section for it in {{ini\|art}} with {{f\|Voxel\|yes\|link}}.

	Image is also ignored when added to the various unit types. One example of this is the [CAML] infantry in YR has Image=JOSH, and yet it correctly displays CAML.SHP anyway. Projectile art is also handled similarly, the art can only be selected from {{ini\|rules}}.		Image is also ignored when added to the various unit types. One example of this is the [CAML] infantry in YR has Image=JOSH, and yet it correctly displays CAML.SHP anyway. Projectile art is also handled similarly, the art can only be selected from {{ini\|rules}}.

ATHSE: first pass

2025-04-11T10:37:02Z

first pass

@@ Line 1: / Line 1: @@
 {{Flag
 |name={{PAGENAME}}
@@ Line 15: / Line 13: @@
 |ra2=yes
 |yr=yes
 }}
-Specifies the section from {{Tt|[[Art|art(md).ini]]}} which contains this object's graphical representation parameters such as cameos, firing offsets, and the like.
+Specifies the section from {{ini|art}} which contains this object's graphical parameters such as cameos, firing offsets, attached animations, movement sequence, etc.
 For [[AircraftTypes]]
 if we specify Image=any turret <b>(GTNKTUR,HTNKTUR,LTNKTUR)</b> We need to add tags. {{f|Voxel|yes|Link}} Go to section <b>GTNKTUR,HTNKTUR,LTNKTUR</b>
@@ Line 35: / Line 34: @@
 Even if you didn't specify <b>Image=YAPOWR</b> In-game images will be available automatically.
-See [[Tiberiums#Note|Tiberiums]] for details.
+==In {{ini|art}}==
-== On Animations and other objects in art(md).ini ==
+The substitute art requested by {{Tt|Image=}} must have a valid {{ini|art}} entry, and where appropriate, specifies what type of art, such as a voxel. This is especially important when specifying substitute voxel art, as the game assumes art is in [[Shape|sprite]] format, unless specified in its art section, and without it bad things can happen. Therefore referencing voxel turret art directly in [[VoxelAnims]], requires first creating a section for it in {{ini|art}} with {{f|Voxel|yes|link}}.
-{{Flag
+Image is also ignored when added to the various unit types. One example of this is the [CAML] infantry in YR has Image=JOSH, and yet it correctly displays CAML.SHP anyway. Projectile art is also handled similarly, the art can only be selected from {{ini|rules}}.
-When used in art(md).ini, this flag also refers to an art(md).ini section as well, but it only uses the referred section to derive a filename of the SHP file to use.
+==See Also==
-This flag does '''not''' work on InfantryTypes, VehicleTypes and AircraftTypes in art(md).ini sections. This is evident by looking at the following code snippets from unmodded artmd.ini:
+[[AlternateArcticArt]]
-'''[120MM]'''<br>
+[[NoSpawnAlt]]
-*It's funny for <b>Image</b> located in the section [[Projectiles]] if it's a SHP file, it can have shadows + play animations + remap colors but can't set it to rotate in 32 directions.<br>
+[[How The Engine Uses Files]]

ZivDero: /* On {{f|Tiberiums|link}} */

2025-04-10T12:09:22Z

On {{f|Tiberiums|link}}

← Older revision		Revision as of 14:09, 10 April 2025
Line 40:		Line 40:
	\|files={{Categ\|ini=rules}}		\|files={{Categ\|ini=rules}}
	\|values={{values\|unsigned integers}}		\|values={{values\|unsigned integers}}
	\|default=?		\|default=-1
	\|types={{Categ\|Tiberiums}}		\|types={{Categ\|Tiberiums}}
	\|ts=yes		\|ts=yes

ZivDero: /* On {{f|Tiberiums|link}} */

2025-04-10T12:08:55Z

On {{f|Tiberiums|link}}

← Older revision		Revision as of 14:08, 10 April 2025
Line 44:		Line 44:
	\|ts=yes		\|ts=yes
	\|fs=yes		\|fs=yes
	~~\|ets=yes~~
	\|ra2=yes		\|ra2=yes
	\|yr=yes		\|yr=yes
	~~\|rp=yes~~
	}}		}}

	~~{{NeedsTesting}}~~		See [[Tiberiums#Note\|Tiberiums]] for details.

	~~Depending on the value given (0 to 4), the game will use a certain index in the OverlayTypes array, plus the following 11 entries.~~

	~~=== in TS ===~~
	* Image=0 and Image=1 will use OverlayType index #~~102.~~
	* Image=2 will use OverlayType index #28 and will only use that one entry, it is hardcoded to use only one entry.
	* Image=3 will use OverlayType index #127.
	* Image=4 will use OverlayType index #150.

	~~=== In YR ===~~

	* Image=2 will use OverlayType index #27 and will only use that one entry, it is hardcoded to use only one entry.
	* Image=3 will use OverlayType index #127.
	* Image=4 will use OverlayType index #147.
	* All other values will use OverlayType index #102.

	== On Animations and other objects in art(md).ini ==		== On Animations and other objects in art(md).ini ==