Help:Values - Revision history

MarkJFox: 18 revisions imported

2025-03-31T19:27:05Z

18 revisions imported

← Older revision	Revision as of 21:27, 31 March 2025
(No difference)

en>TAK02: As requested: the link to BobingAbout's and pd's RGB2HSB converter. On a side-note: we might want a PPM/ModDB link made too just in case.

2017-11-23T19:42:41Z

As requested: the link to BobingAbout's and pd's RGB2HSB converter. On a side-note: we might want a PPM/ModDB link made too just in case.

← Older revision		Revision as of 21:42, 23 November 2017
Line 87:		Line 87:
	'''H'''ue, '''s'''aturation, and '''b'''rightness, is used much less frequently than RGB[[{{PAGENAME}}#RGB\|{{sup\|{{arr\|u}}}}]]. Similarly, each byte[[{{PAGENAME}}#Bytes\|{{sup\|{{arr\|u}}}}]] represents the amount of each factor. However it is {{co\|'''important'''\|red}} to note that the {{ts}} and {{ra2}} [[engine]]s use a unique '''HSB''' color model that is not the same as the one used by most PC programs, like MS Paint.		'''H'''ue, '''s'''aturation, and '''b'''rightness, is used much less frequently than RGB[[{{PAGENAME}}#RGB\|{{sup\|{{arr\|u}}}}]]. Similarly, each byte[[{{PAGENAME}}#Bytes\|{{sup\|{{arr\|u}}}}]] represents the amount of each factor. However it is {{co\|'''important'''\|red}} to note that the {{ts}} and {{ra2}} [[engine]]s use a unique '''HSB''' color model that is not the same as the one used by most PC programs, like MS Paint.

	~~{{HorizontalBar\|Attention ModEnc editors! If a link~~ to ~~[[User:BobingAbout\|BobingAbout]]'s~~ HSB ~~conversion tool can be located, please insert~~ it here~~!}}~~		Bobingabout made an RGB-to-HSB color converter. Get it here: http://bobingabout.gamemod.net/Files/rgb2hsb.exe.

	This unique color model is used with flags in the {{sl\|Colors}} section.		This unique color model is used with flags in the {{sl\|Colors}} section.

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

2009-11-27T08:06:40Z

Replacing Template:TTL with Template:F.

← Older revision		Revision as of 10:06, 27 November 2009
Line 6:		Line 6:
	Data types representing the real line are '''signed''' if they represent a subset of real numbers, negative and non-negative. Likewise, they are '''unsigned''' if only representing non-negative numbers—those above and including 0.		Data types representing the real line are '''signed''' if they represent a subset of real numbers, negative and non-negative. Likewise, they are '''unsigned''' if only representing non-negative numbers—those above and including 0.

	In the [[INI]]s, negative numbers are written by prefixing them with a hyphen (-). For example, {{~~TTL~~\|InitialAmmo}} accepts '''signed''' integers[[{{PAGENAME}}#Integers\|{{sup\|{{arr\|d}}}}]]. Thus, <code>InitialAmmo=-2</code> sets the value to −2.		In the [[INI]]s, negative numbers are written by prefixing them with a hyphen (-). For example, {{f\|InitialAmmo\|link}} accepts '''signed''' integers[[{{PAGENAME}}#Integers\|{{sup\|{{arr\|d}}}}]]. Thus, <code>InitialAmmo=-2</code> sets the value to −2.

	==Value types==		==Value types==
Line 27:		Line 27:
	\|}		\|}

	Most [[:Category:INI_Flags\|INI flag]] that take '''integers''' accept ''signed long integers''<!--, according to pd-->. One notable exception is {{~~TTL~~\|ExtraLight}}, which accepts ''short signed integers''.		Most [[:Category:INI_Flags\|INI flag]] that take '''integers''' accept ''signed long integers''<!--, according to pd-->. One notable exception is {{f\|ExtraLight\|link}}, which accepts ''short signed integers''.

	Flag values should be without commas and negative numbers should be prefixed with a hyphen: −5,387 should be entered as <code>-5387</code>.		Flag values should be without commas and negative numbers should be prefixed with a hyphen: −5,387 should be entered as <code>-5387</code>.
Line 36:		Line 36:
	This value type is used for certain [[:Category:INI_Flags\|INI flags]] in the {{ts}} and {{ra2}} [[engine]]s to represent a single coordinate in pseudo-3D space, which is measured in [[lepton]]s. Each integer represents distance in leptons along the X, Y, and Z axes, respectively.		This value type is used for certain [[:Category:INI_Flags\|INI flags]] in the {{ts}} and {{ra2}} [[engine]]s to represent a single coordinate in pseudo-3D space, which is measured in [[lepton]]s. Each integer represents distance in leptons along the X, Y, and Z axes, respectively.

	An example of a flag that accepts '''XYZ''' is {{~~TTL~~\|ExitCoord}}.		An example of a flag that accepts '''XYZ''' is {{f\|ExitCoord\|link}}.

	===Floating Points===		===Floating Points===
Line 55:		Line 55:
	Flag values should be without commas and negative numbers should be prefixed with a hyphen: −5,387.036 should be entered as <code>-5387.036</code>. It should also be noted that the leading 0, for values between −1 and 1, is optional; −0.25 can be entered as <code>-0.25</code> or simply <code>-.25</code>.		Flag values should be without commas and negative numbers should be prefixed with a hyphen: −5,387.036 should be entered as <code>-5387.036</code>. It should also be noted that the leading 0, for values between −1 and 1, is optional; −0.25 can be entered as <code>-0.25</code> or simply <code>-.25</code>.

	An example of a flag that accepts '''floats''' is {{~~TTL~~\|RechargeTime}}.		An example of a flag that accepts '''floats''' is {{f\|RechargeTime\|link}}.

	===Bytes===		===Bytes===
Line 72:		Line 72:
	Negative flag values should be prefixed with a hyphen; −30 should be entered as <code>-30</code>.		Negative flag values should be prefixed with a hyphen; −30 should be entered as <code>-30</code>.

	In very rare cases, the {{ts}} and {{ra2}} [[engine]]s have flags that only accept '''bytes''' as opposed to integers. One example is {{~~TTL~~\|CloakRadiusInCells}}.		In very rare cases, the {{ts}} and {{ra2}} [[engine]]s have flags that only accept '''bytes''' as opposed to integers. One example is {{f\|CloakRadiusInCells\|link}}.

	====Colors====		====Colors====
Line 82:		Line 82:
	'''R'''ed, '''g'''reen, and '''b'''lue, is the most common way colors are represented. Each byte[[{{PAGENAME}}#Bytes\|{{sup\|{{arr\|u}}}}]] represents the amount of each color respectively, with 0 as the minimum and 255 as the maximum.		'''R'''ed, '''g'''reen, and '''b'''lue, is the most common way colors are represented. Each byte[[{{PAGENAME}}#Bytes\|{{sup\|{{arr\|u}}}}]] represents the amount of each color respectively, with 0 as the minimum and 255 as the maximum.

	This color model is used with {{~~TTL~~\|RadColor}}, for instance.		This color model is used with {{f\|RadColor\|link}}, for instance.

	=====HSB=====		=====HSB=====
Line 94:		Line 94:
	A '''boolean''' is a truth value that is either ''true'' or ''false''. In computing, this can be stored in one bit as a 1 or a 0, representing ''true'' and ''false'' respectively.		A '''boolean''' is a truth value that is either ''true'' or ''false''. In computing, this can be stored in one bit as a 1 or a 0, representing ''true'' and ''false'' respectively.

	In the [[INI]]s, a '''boolean''' value of ''true'' can be represented by the literals {{tt\|yes}}, {{tt\|true}}, or {{tt\|1}}; while {{tt\|no}}, {{tt\|false}}, and {{tt\|0}} convert to ''false''. Even if one were to set {{~~TTL~~\|Capturable\|no way!}}, it would still be considered ''false''.		In the [[INI]]s, a '''boolean''' value of ''true'' can be represented by the literals {{tt\|yes}}, {{tt\|true}}, or {{tt\|1}}; while {{tt\|no}}, {{tt\|false}}, and {{tt\|0}} convert to ''false''. Even if one were to set {{f\|Capturable\|no way!\|link}}, it would still be considered ''false''.

	Examples of flags that take '''booleans''' are {{~~TTL~~\|Radar}}, {{~~TTL~~\|Armory}}, and {{~~TTL~~\|Insignificant}}.		Examples of flags that take '''booleans''' are {{f\|Radar\|link}}, {{f\|Armory\|link}}, and {{f\|Insignificant\|link}}.

	===Strings===		===Strings===
Line 103:		Line 103:
	The accepted character set includes upper and lower-case letters a to z and A to Z, numerals 0 to 9, as well as hyphens (-) and underscores (_). Whitespace (tabs and spaces) and most other punctuation marks and characters are not allowed.		The accepted character set includes upper and lower-case letters a to z and A to Z, numerals 0 to 9, as well as hyphens (-) and underscores (_). Whitespace (tabs and spaces) and most other punctuation marks and characters are not allowed.

	In most cases, '''string''' values are intended to point to an ID of a certain object class. For example, {{~~TTL~~\|HoldsWhat}} can only take an ID of an existing [[Particle]] class object.		In most cases, '''string''' values are intended to point to an ID of a certain object class. For example, {{f\|HoldsWhat\|link}} can only take an ID of an existing [[Particle]] class object.

	A few flags take '''string''' values that must be formatted in a certain way. These values are referred to as being [[hardcoded]] because they are only accepted if they match the predefined format. One example is {{~~TTL~~\|Armor}}, which accepts different '''strings''' depending on the game [[engine]].		A few flags take '''string''' values that must be formatted in a certain way. These values are referred to as being [[hardcoded]] because they are only accepted if they match the predefined format. One example is {{f\|Armor\|link}}, which accepts different '''strings''' depending on the game [[engine]].

	Furthermore, some flags take a list of '''strings''', separated by whitespace and possibly a distinct, separator character. {{~~TTL~~\|Explosion}} takes a comma-separated (with optional whitespace) list of [[Animations]], while {{~~TTL~~\|Sounds}} takes a whitespace-separated list of [[VocTypes]].		Furthermore, some flags take a list of '''strings''', separated by whitespace and possibly a distinct, separator character. {{f\|Explosion\|link}} takes a comma-separated (with optional whitespace) list of [[Animations]], while {{f\|Sounds\|link}} takes a whitespace-separated list of [[VocTypes]].

	===CLSID===		===CLSID===

en>Vinifera7: Small revisions to Floats

2008-05-28T17:22:36Z

Small revisions to Floats

← Older revision		Revision as of 19:22, 28 May 2008
Line 41:		Line 41:
	Also called '''floats''' for short, '''floating points''' are real numbers written in decimal notation without a fixed position for the decimal point. They can represent numbers such as 51.025, −0.8, and 3.67829.		Also called '''floats''' for short, '''floating points''' are real numbers written in decimal notation without a fixed position for the decimal point. They can represent numbers such as 51.025, −0.8, and 3.67829.

	~~'''Floats''' are a unique data type because they can represent a number of ranges depending on where the decimal point is located. The range is also limited by how many bits are used to store the data~~. ~~A single precision '''float''' occupies a total of 32 bits (~~4 ~~bytes), with 24 bits allocated to the significand~~ (~~the significant~~ digits ~~of the number~~). ~~It can take about~~ 7 ~~decimal digits. A double precision '''float''', often called a ''double'', occupies 64 bits (8 bytes), with 52 bits allocated to the significand~~&~~mdash~~;~~about 16 decimal~~ digits.		{\|class="table_descrow" style="float:right; margin-left:10px; text-align:center;" cellpadding="5"
			!float
			!double
			\|-
			\|3.4{{sup\|±38}}<br />(7 digits)
			\|1.7{{sup\|±308}}<br />(15 digits)
			\|}

	Most [[:Category:INI_Flags\|INI flags]] that take '''floats''' accept ''doubles''<!--, according to DCoder-->, though this will rarely make a difference, as extraneous precision will simply be ~~omitted~~ if it will not fit into the allocated space.		'''Floats''' are a unique data type because they can represent a number of ranges depending on where the decimal point is located. The range is also limited by how many bits are used to store the data. A single precision '''float''' occupies a total of 32 bits (4 bytes), with 24 bits allocated to the significand (the significant digits of the number). The actual range can be written in exponent notation as 3.4{{sup\|±38}}, which allows about 7 digits, one of which is assumed to be the decimal point. A double precision '''float''', often called a ''double'', occupies 64 bits (8 bytes), with 52 bits allocated to the significand—1.7{{sup\|±308}}, or about 15 decimal digits.

			Most [[:Category:INI_Flags\|INI flags]] that take '''floats''' accept ''doubles''<!--, according to DCoder-->, though this will rarely make a difference, as extraneous precision will simply be rounded if it will not fit into the allocated space. For example, a single precision '''float''' with a value of <code>890001.35</code> will simply round up to 890001. Similarly, <code>734.967623</code> rounds to 734.968.

	Flag values should be without commas and negative numbers should be prefixed with a hyphen: −5,387.036 should be entered as <code>-5387.036</code>. It should also be noted that the leading 0, for values between −1 and 1, is optional; −0.25 can be entered as <code>-0.25</code> or simply <code>-.25</code>.		Flag values should be without commas and negative numbers should be prefixed with a hyphen: −5,387.036 should be entered as <code>-5387.036</code>. It should also be noted that the leading 0, for values between −1 and 1, is optional; −0.25 can be entered as <code>-0.25</code> or simply <code>-.25</code>.

en>Vinifera7: ...

2008-05-28T01:26:17Z

...

← Older revision		Revision as of 03:26, 28 May 2008
Line 107:		Line 107:
	: {4A582742-9839-11d1-B709-00A024DDAFD1}		: {4A582742-9839-11d1-B709-00A024DDAFD1}

	These are used in {{ini\|rules}} primarily for [[~~Locomotor~~]]s, but also for [[AI generals]].		These are used in {{ini\|rules}} primarily for [[locomotor]]s, but also for [[AI_Generals\|AI generals]].

	==References==		==References==

en>Vinifera7: Major freaking overhaul! I can now mark this off of my to-do list.

2008-05-28T01:22:03Z

Major freaking overhaul! I can now mark this off of my to-do list.

Show changes

en>Renegade: Reverted edits by CnCVK (Talk); changed back to last version by Renegade

2007-03-06T14:08:51Z

Reverted edits by CnCVK (Talk); changed back to last version by Renegade

← Older revision		Revision as of 16:08, 6 March 2007
Line 65:		Line 65:

	==[http://en.wikipedia.org/wiki/CLSID CLSIDs/Locomotors]==		==[http://en.wikipedia.org/wiki/CLSID CLSIDs/Locomotors]==
	Commonly seen as [[Locomotor]]s. They are in registry format.		Commonly seen as [[Locomotor]]s, CLSIDs are also used for [[AI Generals]], for example. They are in registry format.

	An example would be the ship locomotor, {2BEA74E1-7CCA-11d3-BE14-00104B62A16C}.		An example would be the ship locomotor, {2BEA74E1-7CCA-11d3-BE14-00104B62A16C}.

en>CnCVK: /* [http://en.wikipedia.org/wiki/CLSID CLSIDs/Locomotors] */

2007-03-05T21:05:17Z

[http://en.wikipedia.org/wiki/CLSID CLSIDs/Locomotors]

← Older revision		Revision as of 23:05, 5 March 2007
Line 65:		Line 65:

	==[http://en.wikipedia.org/wiki/CLSID CLSIDs/Locomotors]==		==[http://en.wikipedia.org/wiki/CLSID CLSIDs/Locomotors]==
	Commonly seen as [[Locomotor]]s~~, CLSIDs are also used for [[AI Generals]], for example~~. They are in registry format.		Commonly seen as [[Locomotor]]s. They are in registry format.

	An example would be the ship locomotor, {2BEA74E1-7CCA-11d3-BE14-00104B62A16C}.		An example would be the ship locomotor, {2BEA74E1-7CCA-11d3-BE14-00104B62A16C}.

en>Renegade: god damnit - thing reverted too far.

2006-08-15T22:53:19Z

god damnit - thing reverted too far.

← Older revision		Revision as of 00:53, 16 August 2006
Line 70:		Line 70:

	==POINT3D==		==POINT3D==
	Coordinates.		Coordinates in [[leptons]](1/256th of a cell).<br>
	The 3 ~~bytes~~ represent '''X''', '''Y''' and '''Z'''.<br>		The 3 signed integers represent '''X''', '''Y''' and '''Z'''.<br>
	An example for a POINT3D INI tag is the [[ExitCoord]] tag.		An example for a POINT3D INI tag is the [[ExitCoord]] tag.

	[[Category:INI Flags]]		[[Category:INI Flags]]
	[[Category:General Editing Information]]		[[Category:General Editing Information]]

en>Renegade: Reverted edits by CnCVK (Talk); changed back to last version by Renegade

2006-08-15T22:51:31Z

Reverted edits by CnCVK (Talk); changed back to last version by Renegade

← Older revision		Revision as of 00:51, 16 August 2006
Line 64:		Line 64:
	This unique HSB format is used in the [<tt>[[Colors]]</tt>] section.		This unique HSB format is used in the [<tt>[[Colors]]</tt>] section.

	==[http://en.wikipedia.org/wiki/CLSID ~~CLSID~~]==		==[http://en.wikipedia.org/wiki/CLSID CLSIDs/Locomotors]==
	Commonly seen as [[Locomotor]]s, CLSIDs are also used for [[AI Generals]], for example. They are in registry format.		Commonly seen as [[Locomotor]]s, CLSIDs are also used for [[AI Generals]], for example. They are in registry format.

Line 70:		Line 70:

	==POINT3D==		==POINT3D==
	Coordinates ~~in [[leptons]](1/256th of a cell)~~.~~<br>~~		Coordinates.
	The 3 ~~signed integers~~ represent '''X''', '''Y''' and '''Z'''.<br>		The 3 bytes represent '''X''', '''Y''' and '''Z'''.<br>
	An example for a POINT3D INI tag is the [[ExitCoord]] tag.		An example for a POINT3D INI tag is the [[ExitCoord]] tag.

	[[Category:INI Flags]]		[[Category:INI Flags]]
	[[Category:General Editing Information]]		[[Category:General Editing Information]]