Action7 - Revision history

Andythenorth: /* condition-type */ extend checks for roadtype, tramtype availability, also 'railtype' not 'rail type'

2020-02-18T20:26:01Z

condition-type: extend checks for roadtype, tramtype availability, also 'railtype' not 'rail type'

← Older revision		Revision as of 20:26, 18 February 2020
Line 161:		Line 161:
	\|0C\|\|\7C\|\|{{ottdp\|0.6\| \|ottdrev=r11358}}\|\|Cargo type is available (variable is ignored; value is the label)		\|0C\|\|\7C\|\|{{ottdp\|0.6\| \|ottdrev=r11358}}\|\|Cargo type is available (variable is ignored; value is the label)
	\|-		\|-
	\|0D\|\| \|\|{{ottdp\|0.7\|no\|ottdrev=r15418}}\|\|~~Rail type~~ label is not defined (variable is ignored; value is the label)		\|0D\|\| \|\|{{ottdp\|0.7\|no\|ottdrev=r15418}}\|\|Railtype label is not defined (variable is ignored; value is the label)
	\|-		\|-
	\|0E\|\| \|\|{{ottdp\|0.7\|no\|ottdrev=r15418}}\|\|~~Rail type~~ label is defined (variable is ignored; value is the label)		\|0E\|\| \|\|{{ottdp\|0.7\|no\|ottdrev=r15418}}\|\|Railtype label is defined (variable is ignored; value is the label)
			\|-
			\|0F\|\| \|\|{{ottdp\|1.10\|no\|}}\|\|Roadtype label is not defined (variable is ignored; value is the label)
			\|-
			\|10\|\| \|\|{{ottdp\|1.10\|no\|}}\|\|Roadtype label is defined (variable is ignored; value is the label)
			\|-
			\|11\|\| \|\|{{ottdp\|1.10\|no\|}}\|\|Tramtype label is not defined (variable is ignored; value is the label)
			\|-
			\|12\|\| \|\|{{ottdp\|1.10\|no\|}}\|\|Tramtype label is defined (variable is ignored; value is the label)
	\|}		\|}

Frosch: not about skipping unknown properties

2011-09-01T21:17:33Z

not about skipping unknown properties

← Older revision		Revision as of 21:17, 1 September 2011
Line 58:		Line 58:
	!Action to skip!!with 7!!with 9!!notes		!Action to skip!!with 7!!with 9!!notes
	\|-		\|-
	\|0 (new props)\|\|yes\|\|yes\|\|		\|0 (new props)\|\|yes\|\|yes\|\|To skip new properties unknown to old OpenTTD or TTDPatch you have to use Action 9.
	\|-		\|-
	\|1 (sprite blk)\|\|yes\|\|yes\|\|		\|1 (sprite blk)\|\|yes\|\|yes\|\|

Frosch: add summary table

2011-07-25T20:52:49Z

add summary table

← Older revision		Revision as of 20:52, 25 July 2011
Line 111:		Line 111:
	This sets the variable to base the decision on. It can be either one of the GRF parameters (see [[Action6\|action 6]]), or a built-in patch variable. If it's a GRF parameter that wasn't specified in the newgrf(w).cfg file, or variable 88 with a GRFID that doesn't exist, the action 7 or 9 is ignored and no sprites are skipped, the only exception being condition type 0A which will skip the sprites if the GRFID doesn't exist as well.		This sets the variable to base the decision on. It can be either one of the GRF parameters (see [[Action6\|action 6]]), or a built-in patch variable. If it's a GRF parameter that wasn't specified in the newgrf(w).cfg file, or variable 88 with a GRFID that doesn't exist, the action 7 or 9 is ignored and no sprites are skipped, the only exception being condition type 0A which will skip the sprites if the GRFID doesn't exist as well.

			{\| \|-
⚫	~~A comprehensive list of variables is found on the~~ [[GlobalVariables\| global variables page]]
			!Variables!!Description
			\|-
			\|00-7F\|\|GRF parameters, see [[Action6]].
			\|-
		⚫	\|80-BF\|\|See [[GlobalVariables\| global variables page]].
			\|-
			\|C0-FF\|\|Reserved. Do not use.
			\|}

	=== varsize ===		=== varsize ===

Planetmaker: /* value */ clearify version info

2011-07-24T12:44:50Z

value: clearify version info

← Older revision		Revision as of 12:44, 24 July 2011
Line 192:		Line 192:
	For conditions 0B, 0C, 0D and 0E the value specifies directly the cargo/railtype label; it is no index into a translation table.		For conditions 0B, 0C, 0D and 0E the value specifies directly the cargo/railtype label; it is no index into a translation table.

	For conditions 0B and ~~(since TTDPatch~~ 2.~~0.1~~ alpha 72) 0C, the variable given is ignored (but must be a valid variable nonetheless), the varsize must be 4 and the value must be the cargo label to check for. If no cargo with this label is defined in case of condition 0B, the given number of sprites are skipped. For condition 0C, the sprites are skipped if the cargo label has been defined. Both tests work irrespective of the order of .grf files in newgrf(w).cfg; the cargo is considered to be available even if it is defined by a later grf file. For this to work correctly, you ''must not'' skip a cargo definition with conditions 0B or 0C.		For conditions 0B and {{ottdp\| \|2.5\|ttdprev=alpha 72}} 0C, the variable given is ignored (but must be a valid variable nonetheless), the varsize must be 4 and the value must be the cargo label to check for. If no cargo with this label is defined in case of condition 0B, the given number of sprites are skipped. For condition 0C, the sprites are skipped if the cargo label has been defined. Both tests work irrespective of the order of .grf files in newgrf(w).cfg; the cargo is considered to be available even if it is defined by a later grf file. For this to work correctly, you ''must not'' skip a cargo definition with conditions 0B or 0C.

	The same holds for conditions 0D and 0E wrt. railtypes and their reservation.		The same holds for conditions 0D and 0E wrt. railtypes and their reservation.

	Since r1384, setting varsize to 8, changes value slightly, the first 4 bytes are the value (generalised GRFID), and the next 4 bytes are a bit mask for the GRFIDs to check. Please note you should make sure any masked bits are also not in the GRFID to check, as value to check against is not currently masked.		Since {{ottdp\| \|2.5\|ttdprev=r1384}}, setting varsize to 8, changes value slightly, the first 4 bytes are the value (generalised GRFID), and the next 4 bytes are a bit mask for the GRFIDs to check. Please note you should make sure any masked bits are also not in the GRFID to check, as value to check against is not currently masked.

	=== num-sprites ===		=== num-sprites ===

Planetmaker: /* condition-type */ add version info

2011-07-24T12:42:18Z

condition-type: add version info

← Older revision		Revision as of 12:42, 24 July 2011
Line 125:		Line 125:
	There are several conditions you can choose from to test against. This has an escape sequence for each valid value. See [[GRFActionsDetailed#Byte order\|the discussion of escape sequences]] for further information on escape sequences in general. For your convenience they are summed up in yet another table:		There are several conditions you can choose from to test against. This has an escape sequence for each valid value. See [[GRFActionsDetailed#Byte order\|the discussion of escape sequences]] for further information on escape sequences in general. For your convenience they are summed up in yet another table:
	{\|		{\|
	!Condition type!!Escape!!Description		!Condition type!!Escape!!Version!!Description
	\|-		\|-
	\|00\|\|\71\|\|Test for bit given by value being set		\|00\|\|\71\|\|{{ottdp\|0.6\| }}\|\|Test for bit given by value being set
	\|-		\|-
	\|01\|\|\70\|\|Test for bit given by value being clear		\|01\|\|\70\|\|{{ottdp\|0.6\| }}\|\|Test for bit given by value being clear
	\|-		\|-
	\|02\|\|\7=\|\|Parameter is equal to value		\|02\|\|\7=\|\|{{ottdp\|0.6\| }}\|\|Parameter is equal to value
	\|-		\|-
	\|03\|\|\7!\|\|Parameter is not equal to value		\|03\|\|\7!\|\|{{ottdp\|0.6\| }}\|\|Parameter is not equal to value
	\|-		\|-
	\|04\|\|\7<\|\|Parameter is less than value		\|04\|\|\7<\|\|{{ottdp\|0.6\| }}\|\|Parameter is less than value
	\|-		\|-
	\|05\|\|\7>\|\|Parameter is greater than value		\|05\|\|\7>\|\|{{ottdp\|0.6\| }}\|\|Parameter is greater than value
	\|-		\|-
	\|06\|\|\7G\|\|GRFID (see [[Action8\|action 8]]) is active (for variable 88 only)		\|06\|\|\7G\|\|{{ottdp\|0.6\| }}\|\|GRFID (see [[Action8\|action 8]]) is active (for variable 88 only)
	\|-		\|-
	\|07\|\|\7g\|\|GRFID is not active (for variable 88 only)		\|07\|\|\7g\|\|{{ottdp\|0.6\| }}\|\|GRFID is not active (for variable 88 only)
	\|-		\|-
	\|08\|\|\7gG\|\|GRFID is not active yet but will be activated (variable 88 only)		\|08\|\|\7gG\|\|{{ottdp\|0.6\| }}\|\|GRFID is not active yet but will be activated (variable 88 only)
	\|-		\|-
	\|09\|\|\7GG\|\|GRFID is or will be active (variable 88 only)		\|09\|\|\7GG\|\|{{ottdp\|0.6\| }}\|\|GRFID is or will be active (variable 88 only)
	\|-		\|-
	\|0A\|\|\7gg\|\|GRFID is not nor will it be active (variable 88 only)		\|0A\|\|\7gg\|\|{{ottdp\|0.6\| \|ottdrev=r11358}}\|\|GRFID is not nor will it be active (variable 88 only)
	\|-		\|-
	\|0B\|\|\7c\|\|Cargo type is not available (variable is ignored; value is the label)*		\|0B\|\|\7c\|\|{{ottdp\|0.6\| \|ottdrev=r11358}}\|\|Cargo type is not available (variable is ignored; value is the label)
	\|-		\|-
	\|0C\|\|\7C\|\|Cargo type is available (variable is ignored; value is the label)*		\|0C\|\|\7C\|\|{{ottdp\|0.6\| \|ottdrev=r11358}}\|\|Cargo type is available (variable is ignored; value is the label)
	\|-		\|-
	\|0D\|\| \|\|Rail type label is not defined (variable is ignored; value is the label)**		\|0D\|\| \|\|{{ottdp\|0.7\|no\|ottdrev=r15418}}\|\|Rail type label is not defined (variable is ignored; value is the label)
	\|-		\|-
	\|0E\|\| \|\|Rail type label is defined (variable is ignored; value is the label)**		\|0E\|\| \|\|{{ottdp\|0.7\|no\|ottdrev=r15418}}\|\|Rail type label is defined (variable is ignored; value is the label)
	\|}		\|}

	Note that for the characters, a capital letter means available, and a lowercase character means not available. For the two character GRFID sequences, the first character is its current state, and the second is its future state.		Note that for the characters, a capital letter means available, and a lowercase character means not available. For the two character GRFID sequences, the first character is its current state, and the second is its future state.

	(*) Prior to r11358, OpenTTD will skip these checks with variable 88.

	(**) Only in OpenTTD since r15418.

	The tests for variable 88 depend on the current [[GrfLoadingStages\|GRF Loading Stage]], the order GRFs are loaded, and of course whether they are present or were disabled (by themself or by other GRFs). Consider two GRFs A and B (loaded in that order):		The tests for variable 88 depend on the current [[GrfLoadingStages\|GRF Loading Stage]], the order GRFs are loaded, and of course whether they are present or were disabled (by themself or by other GRFs). Consider two GRFs A and B (loaded in that order):

Planetmaker: /* variable */ move variable descriptions to global variable page

2011-07-24T12:36:24Z

variable: move variable descriptions to global variable page

← Older revision		Revision as of 12:36, 24 July 2011
Line 110:		Line 110:

	This sets the variable to base the decision on. It can be either one of the GRF parameters (see [[Action6\|action 6]]), or a built-in patch variable. If it's a GRF parameter that wasn't specified in the newgrf(w).cfg file, or variable 88 with a GRFID that doesn't exist, the action 7 or 9 is ignored and no sprites are skipped, the only exception being condition type 0A which will skip the sprites if the GRFID doesn't exist as well.		This sets the variable to base the decision on. It can be either one of the GRF parameters (see [[Action6\|action 6]]), or a built-in patch variable. If it's a GRF parameter that wasn't specified in the newgrf(w).cfg file, or variable 88 with a GRFID that doesn't exist, the action 7 or 9 is ignored and no sprites are skipped, the only exception being condition type 0A which will skip the sprites if the GRFID doesn't exist as well.
	{\|
	!'''Variable'''!![[GRFActionsDetailed\|'''Size''']]!!'''Description'''
	\|-
	\|81\|\|B\|\|current year (count from 1920, max. 2175 even with eternalgame)
	\|-
	\|83\|\|B\|\|Current climate: 00 = temp, 01 = arctic, 02 = trop, 03 = toyland
	\|-
	\|84\|\|D\|\|[[GrfLoadingStages\|GRF loading stage]], see below
	\|-
	\|85\|\|B\|\|[[TTDPatchFlags\|TTDPatch flags]]: only for bit tests
	\|-
	\|86\|\|B\|\|Road traffic side: bit 4 clear=left, set=right
	\|-
	\|88\|\|4*B\|\|Checks specified GRFID (see condition-types below)
	\|-
	\|8B\|\|D\|\|TTDPatch version, see below
	\|-
	\|8D\|\|B\|\|TTD version, 0=DOS, 1=Windows
	\|-
	\|8E\|\|B\|\|Y-Offset for train sprites
	\|-
	\|8F\|\|4*B\|\|Rail track type cost factors
	\|-
	\|92\|\|B\|\|Game mode, 0 in title screen, 1 in game and 2 in editor
	\|-
	\|93\|\|D\|\|Tile refresh offset to left
	\|-
	\|94\|\|D\|\|Tile refresh offset to right
	\|-
	\|95\|\|D\|\|Tile refresh offset upwards
	\|-
	\|96\|\|D\|\|Tile refresh offset downwards
	\|-
	\|9A\|\|D\|\|Has always all bits set; you can use this to make unconditional jumps
	\|-
	\|9D\|\|D\|\|TTD Platform, 0=TTDPatch, 1=OpenTTD
	\|-
	\|A1\|\|D\|\|OpenTTD version, see below.
	\|-
	\|A2\|\|D\|\|Difficulty level: 00= easy, 01=medium, 02=hard, 03=custom, since r12449 for OpenTTD and r1857 for TTDPatch
	\|-
	\|A3\|\|D\|\|Current date(4); long format, since r13376 in OpenTTD and r2048 in TTDPatch
	\|-
	\|A4\|\|D\|\|Current year(4); long format, year zero based since r13376 in OpenTTD and r2048 in TTDPatch
	\|}

			A comprehensive list of variables is found on the [[GlobalVariables\| global variables page]]
	Note 1: All other parameter values greater than 80 (hexadecimal) are reserved and must not be used in action 7 or 9.

	Note 2: The value of variable 88 can only be tested with the GRFID tests.

	Note 3: The tile refresh offsets are available from TTDPatch 2.0.1 alpha 39. See [[ActionD#Tile+refresh+offsets\|Action D]] for more details on their use.

	Note 4: OpenTTD doesn't report the current date and year but the date and year the game was loaded. The reason lies in the fact that it was seen that use of this variable leads to desyncs in network games.

	Variable 84 is a BYTE variable up to TTDPatch 2.5r1220. Its lower byte (bits 0..7) are 0 for the post-load and GRF initialization stages and 01 for all other stages. The remaining bits are a bitmask, and including the lower byte have the following meaning:
	{\|
	!Bit!!Meaning
	\|-
	\|0\|\|Set after the "Initialization" stage completes
	\|-
	\|1..7\|\|Always clear
	\|-
	\|8\|\|Set during the "Reserve" stage only
	\|-
	\|9\|\|Set during the "Activate" stage only
	\|-
	\|10\|\|Set during the "Test" stage only
	\|}

	Variable 8B has the following format: MMmrbbbb (though encoded in little endian as bb bb mr MM)
	{\|
	!Element!!Meaning!!Value
	\|-
	\|MM\|\|major\|\|First number of the TTDPatch version
	\|-
	\|m\|\|minor\|\|Second number of the TTDPatch version
	\|-
	\|r\|\|revision\|\|Third number of the TTDPatch version*
	\|-
	\|bbbb\|\|build\|\|Alpha/beta version number times ten (up to an including TTDPatch 2.5 beta 5), SVN revision (from TTDPatch 2.5 beta 5 r418 on)
	\|}

	Examples
	{\|
	!Version!!Variable 8B!!Elements
	\|-
	\|1.9.1 alpha 50\|\|019101F4\|\| MM=01, m=9, r=1, bbbb=50*10=01F4
	\|-
	\|2.0 beta 4\|\|02040028\|\|MM=02, m=0, r=4, bbbb=410=0028
	\|-
	\|2.0 final\|\|02070046\|\|MM=02, m=0, r=7*, bbbb=70=0046
	\|-
	\|2.0 rev 1\|\|02070050\|\|MM=02, m=0, r=7*, bbbb=80=0050
	\|-
	\|2.0.1 alpha 3\|\|020A001E\|\|MM=02, m=0, r=10, bbbb=310=001E
	\|-
	\|2.5 beta 2\|\|02500014\|\|MM=02, m=5, r=0, bbbb=2*10=0014
	\|-
	\|2.5 rev631\|\|02500631\|\|MM=02, m=5, r=0, bbbb=631=0631
	\|}

	(*) For TTDPatch 2.0, r=7 and for TTDPatch 2.0.1 series, r=10 due to an oversight which used r=1..4 for TTDPatch 2.0 beta 1..4.

	To detect versions from TTDPatch 2.5 rev419 and up correctly, check that var. 8B is 02500419 or higher, or replace 0419 with the actual required revision (using the revision number as hex digits). Because SVN revisions are shared with other patch branches, it is important to check the actual patch version as well as the SVN revision.

	Variable A1 has the following format: Mmrbbbbb (though encoded in little endian as bb bb rb Mm). This variable has only a usefull meaning when variable 9D is 1 (OpenTTD). This variable can be used since OpenTTD r11330.
	{\|
	!Element!!Meaning!!Value
	\|-
	\|M\|\|major\|\|First number of the OpenTTD version
	\|-
	\|m\|\|minor\|\|Second number of the OpenTTD version
	\|-
	\|r\|\|revision\|\|Third number of the OpenTTD version
	\|-
	\|bbbbb\|\|build\|\|Subversion revision of a build leading towards a release. When a final release is done 80000h is set.
	\|}

	The presence of 80000h (bit 19 set) means that a release always has a higher version number than any builds leading to that release.

	Examples
	{\|
	!Version!!Variable A1!!Elements
	\|-
	\|0.6.0 r11330\|\|06002C42\|\|M=0, m=6, r=0, bbbbb=11330=2C42
	\|-
	\|0.6.0 (release)\|\|06080000\|\|M=0, m=6, r=0, bbbbb=0=80000 (due to release)
	\|}

	=== varsize ===		=== varsize ===

Frosch: fix conversion

2011-06-18T19:19:16Z

fix conversion

← Older revision		Revision as of 19:19, 18 June 2011
Line 373:		Line 373:
	Due to action 7 being skipped during initalization, and action B severity bit 7 not working before TTDPatch 2.0.1 alpha 66, the best way to check for the required patch version is the following sequence:		Due to action 7 being skipped during initalization, and action B severity bit 7 not working before TTDPatch 2.0.1 alpha 66, the best way to check for the required patch version is the following sequence:

	// Check for TTDPatch 2.0.1 alpha 57, skip action B if present		// Check for TTDPatch 2.0.1 alpha 57, skip action B if present
	1 * 9 09 8B 04 05 39 02 0A 02 01		1 * 9 09 8B 04 05 39 02 0A 02 01
	// Abort with fatal action B if not (during its first activation)		// Abort with fatal action B if not (during its first activation)
Line 381:		Line 381:
	// Skip rest of file if not TTDPatch 2.0.1 alpha 57,		// Skip rest of file if not TTDPatch 2.0.1 alpha 57,
	// to prevent meaningless "invalid sprite" errors		// to prevent meaningless "invalid sprite" errors
	4 * 9 09 8B 04 04 3A 02 0A 02 00~~~/pp~</pre>~~		4 * 9 09 8B 04 04 3A 02 0A 02 00

	This way the GRF Status entry shows the proper error message as well as the correct name and description because the action 8 is still being processed during initialization, and all unknown sprites are skipped so that the "invalid sprites" error message is not shown first (or else it would become the permanent message shown in the GRF Status Window).		This way the GRF Status entry shows the proper error message as well as the correct name and description because the action 8 is still being processed during initialization, and all unknown sprites are skipped so that the "invalid sprites" error message is not shown first (or else it would become the permanent message shown in the GRF Status Window).

Frosch: fix conversion

2011-06-18T19:16:55Z

fix conversion

← Older revision		Revision as of 19:16, 18 June 2011
Line 211:		Line 211:
	\|}		\|}

	* For TTDPatch 2.0, r=7 and for TTDPatch 2.0.1 series, r=10 due to an oversight which used r=1..4 for TTDPatch 2.0 beta 1..4.		(*) For TTDPatch 2.0, r=7 and for TTDPatch 2.0.1 series, r=10 due to an oversight which used r=1..4 for TTDPatch 2.0 beta 1..4.

	To detect versions from TTDPatch 2.5 rev419 and up correctly, check that var. 8B is 02500419 or higher, or replace 0419 with the actual required revision (using the revision number as hex digits). Because SVN revisions are shared with other patch branches, it is important to check the actual patch version as well as the SVN revision.		To detect versions from TTDPatch 2.5 rev419 and up correctly, check that var. 8B is 02500419 or higher, or replace 0419 with the actual required revision (using the revision number as hex digits). Because SVN revisions are shared with other patch branches, it is important to check the actual patch version as well as the SVN revision.
Line 286:		Line 286:
	Note that for the characters, a capital letter means available, and a lowercase character means not available. For the two character GRFID sequences, the first character is its current state, and the second is its future state.		Note that for the characters, a capital letter means available, and a lowercase character means not available. For the two character GRFID sequences, the first character is its current state, and the second is its future state.

	* Prior to r11358, OpenTTD will skip these checks with variable 88.		(*) Prior to r11358, OpenTTD will skip these checks with variable 88.

	** Only in OpenTTD since r15418.		(**) Only in OpenTTD since r15418.

	The tests for variable 88 depend on the current [[GrfLoadingStages\|GRF Loading Stage]], the order GRFs are loaded, and of course whether they are present or were disabled (by themself or by other GRFs). Consider two GRFs A and B (loaded in that order):		The tests for variable 88 depend on the current [[GrfLoadingStages\|GRF Loading Stage]], the order GRFs are loaded, and of course whether they are present or were disabled (by themself or by other GRFs). Consider two GRFs A and B (loaded in that order):
Line 346:		Line 346:
	47 * 6 07 83 01 03 00 00		47 * 6 07 83 01 03 00 00

	What does this Action 7 tells the ~~programme~~ to do with the fictional .grf file?		What does this Action 7 tells the program to do with the fictional .grf file?
	{\|		{\|
	!Byte!!Meaning		!Byte!!Meaning
Line 389:		Line 389:
	Var 9A always has all bits set, so to make an unconditional jump you can use a bit test:		Var 9A always has all bits set, so to make an unconditional jump you can use a bit test:

	~1 * 7 07 9A 01 00 00 01 resp.		1 * 7 07 9A 01 00 00 01 resp.
	~1 * 7 07 9A 01 \\71 00 01		1 * 7 07 9A 01 \71 00 01

	What this does is that it checks if bit 0 from the first byte of variable 9A is set (which it always is), so the sprite which you put after this action 7 is always skipped.		What this does is that it checks if bit 0 from the first byte of variable 9A is set (which it always is), so the sprite which you put after this action 7 is always skipped.

Frosch: use a real table, this is not tikiwki

2011-06-16T19:07:32Z

use a real table, this is not tikiwki

← Older revision		Revision as of 19:07, 16 June 2011
Line 292:		Line 292:
	The tests for variable 88 depend on the current [[GrfLoadingStages\|GRF Loading Stage]], the order GRFs are loaded, and of course whether they are present or were disabled (by themself or by other GRFs). Consider two GRFs A and B (loaded in that order):		The tests for variable 88 depend on the current [[GrfLoadingStages\|GRF Loading Stage]], the order GRFs are loaded, and of course whether they are present or were disabled (by themself or by other GRFs). Consider two GRFs A and B (loaded in that order):

			{\| \|-
	<pre>
			!rowspan="2"\| Condition
	\| Condition \|\| Initialisation \|\| Reservation/Activation \|\| Tested GRF \|\|
			!colspan="2"\| Initialisation
⚫	\|
			!colspan="2"\| Reservation/Activation
⚫	~~\| \|\|~~ A testing for B \|\| B testing for A \|\| A testing for B \|\| B testing for A ~~\|\| not present \|\|~~
			!rowspan="2"\| Tested GRF not present
⚫	\|
		⚫	\|-
	\| ----------+-----------------------+------------------------+------------------------+------------------------\|\|--------------\|\|
		⚫	! A testing for B !! B testing for A !! A testing for B !! B testing for A
⚫	\|
		⚫	\|-
	\|06 \\7G \|\| always false \|\| always false \|\| always false \|\| A not disabled? \|\| always false \|\|
	\|		\|-
	\|07 \~~\7g~~ \|\| always ~~true~~ \|\| always ~~true~~ \|\| always ~~true~~ \|\| A disabled? \|\| always false \|\|		\|06 \7G \|\| always false \|\| always false \|\| always false \|\| A not disabled? \|\| always false
	\|		\|-
	\|08 \~~\7gG~~ \|\| always ~~false~~ \|\| A ~~not~~ ~~(yet)~~ ~~disabled?~~ \|\| B ~~not~~ ~~(yet)~~ ~~disabled?~~ \|\| always ~~false~~ \|\| ~~always~~ ~~false~~ \|\|		\|07 \7g \|\| always true \|\| always true \|\| always true \|\| A disabled? \|\| always false
	\|		\|-
	\|09 \~~\7GG~~ \|\| always false \|\| A not (yet) disabled? \|\| B not (yet) disabled? \|\| A ~~not~~ ~~disabled?~~ \|\| always false \|\|		\|08 \7gG \|\| always false \|\| A not (yet) disabled? \|\| B not (yet) disabled? \|\| always false \|\| always false
	\|		\|-
	\|0A \~~\7gg~~ \|\| B ~~(already)~~ ~~disabled?~~ \|\| A (~~already~~) disabled? \|\| B (~~already~~) disabled? \|\| A disabled? \|\| always ~~true \|\|~~		\|09 \7GG \|\| always false \|\| A not (yet) disabled? \|\| B not (yet) disabled? \|\| A not disabled? \|\| always false
		⚫	\|-
	</pre>
			\|0A \7gg \|\| B (already) disabled? \|\| A (already) disabled? \|\| B (already) disabled? \|\| A disabled? \|\| always true
			\|}

	If the tested GRF is not present, conditions 06 to 09 always evaluate to "false". For condition 0A "disabled" and "not present" are the same, i.e. it always evaluates to "true".		If the tested GRF is not present, conditions 06 to 09 always evaluate to "false". For condition 0A "disabled" and "not present" are the same, i.e. it always evaluates to "true".

Pm-bot: Bot: Automated text replacement (-OTTD +OpenTTD)

2011-06-15T17:34:31Z

Bot: Automated text replacement (-OTTD +OpenTTD)

← Older revision		Revision as of 17:34, 15 June 2011
Line 286:		Line 286:
	Note that for the characters, a capital letter means available, and a lowercase character means not available. For the two character GRFID sequences, the first character is its current state, and the second is its future state.		Note that for the characters, a capital letter means available, and a lowercase character means not available. For the two character GRFID sequences, the first character is its current state, and the second is its future state.

	* Prior to r11358, ~~OTTD~~ will skip these checks with variable 88.		* Prior to r11358, OpenTTD will skip these checks with variable 88.

	** Only in OpenTTD since r15418.		** Only in OpenTTD since r15418.