Action2/Single Set - Revision history

Andrew350: /* Introduction */ added roadtypes and tramtypes

2019-12-28T12:31:51Z

Introduction: added roadtypes and tramtypes

← Older revision		Revision as of 12:31, 28 December 2019
Line 10:		Line 10:
	\|-		\|-
	\|Railtypes \|\| {{ottdp\|1.0\|no\|ottdrev=r19056}} \|\| Depends on [[Action3/Railtypes#cargo-type\| Action3 'cargo' type]]		\|Railtypes \|\| {{ottdp\|1.0\|no\|ottdrev=r19056}} \|\| Depends on [[Action3/Railtypes#cargo-type\| Action3 'cargo' type]]
			\|-
			\|Roadtypes \|\| {{ottdp\|1.10}} \|\| Depends on [[Action3/Roadtypes#cargo-type\| Action3 'cargo' type]]
			\|-
			\|Tramtypes \|\| {{ottdp\|1.10}} \|\| Depends on [[Action3/Tramtypes#cargo-type\| Action3 'cargo' type]]
	\|}		\|}

Line 16:		Line 20:
	The only graphics associated to cargoes is their icon that is shown in the station window.		The only graphics associated to cargoes is their icon that is shown in the station window.

	The graphics associated with railtypes are somewhat more complicated, but all their logic is in variational action2s and the action3; the standard action2 is again not complicated.		The graphics associated with railtypes, roadtypes, and tramtypes are somewhat more complicated, but all their logic is in variational action2s and the action3; the standard action2 is again not complicated.

	The only graphics associated with airports is their preview sprite. The default size for the preview sprite is 230x140. The airport build GUI will automatically scale if you have a smaller or larger image, but it will probably look best if you make sure it is no larger than the default size.		The only graphics associated with airports is their preview sprite. The default size for the preview sprite is 230x140. The airport build GUI will automatically scale if you have a smaller or larger image, but it will probably look best if you make sure it is no larger than the default size.

PikkaBird: /* Introduction */ point the railtype action 3 link straight to the railtype action 3 page instead of the general action 3 page.

2012-04-06T04:19:50Z

Introduction: point the railtype action 3 link straight to the railtype action 3 page instead of the general action 3 page.

← Older revision		Revision as of 04:19, 6 April 2012
Line 9:		Line 9:
	\|Airports \|\| {{ottdp\|1.1\|no}} \|\| Single preview image		\|Airports \|\| {{ottdp\|1.1\|no}} \|\| Single preview image
	\|-		\|-
	\|Railtypes \|\| {{ottdp\|1.0\|no\|ottdrev=r19056}} \|\| Depends on [[Action3#cargo-type \| Action3 'cargo' type]]		\|Railtypes \|\| {{ottdp\|1.0\|no\|ottdrev=r19056}} \|\| Depends on [[Action3/Railtypes#cargo-type\| Action3 'cargo' type]]
	\|}		\|}

Frosch: version tags

2011-08-15T14:51:57Z

version tags

← Older revision		Revision as of 14:51, 15 August 2011
Line 3:		Line 3:
	!Feature !! Version !! Associated graphics		!Feature !! Version !! Associated graphics
	\|-		\|-
	\|Canals \|\| {{ottdp\|0.6\| }} \|\| Depends on [[Action3#ids \| Action3 ID]]; see [[Action0/Canals \| Action0]]		\|Canals \|\| {{ottdp\|0.6\|2.5}} \|\| Depends on [[Action3#ids \| Action3 ID]]; see [[Action0/Canals \| Action0]]
	\|-		\|-
	\|Cargos \|\| {{ottdp\|0.6\| }} \|\| Single icon sprite		\|Cargos \|\| {{ottdp\|0.6\|2.5}} \|\| Single icon sprite
	\|-		\|-
	\|Airports \|\| {{ottdp\|1.1\|no}} \|\| Single preview image		\|Airports \|\| {{ottdp\|1.1\|no}} \|\| Single preview image

Planetmaker: /* Introduction */ add versions

2011-07-23T13:19:34Z

Introduction: add versions

← Older revision		Revision as of 13:19, 23 July 2011
Line 1:		Line 1:
	== Introduction ==		== Introduction ==
	{\| \|-		{\| \|-
	!Feature !! ~~TTDPatch !! OpenTTD~~ !! Associated graphics		!Feature !! Version !! Associated graphics
	\|-		\|-
	\|Canals \|\| ? \|\| 0.6 \|\| Depends on [[Action3#ids \| Action3 ID]]; see [[Action0/Canals \| Action0]]		\|Canals \|\| {{ottdp\|0.6\| }} \|\| Depends on [[Action3#ids \| Action3 ID]]; see [[Action0/Canals \| Action0]]
	\|-		\|-
	\|Cargos \|\| ? \|\| 0.6 \|\| Single icon sprite		\|Cargos \|\| {{ottdp\|0.6\| }} \|\| Single icon sprite
	\|-		\|-
	\|Airports \|\| ~~not supported~~ \|\| 1.1.0 \|\| Single preview image		\|Airports \|\| {{ottdp\|1.1\|no}} \|\| Single preview image
	\|-		\|-
	\|Railtypes \|\| ~~not supported~~ \|\| 1.0~~.0 (~~r19056) \|\| Depends on [[Action3#cargo-type \| Action3 'cargo' type]]		\|Railtypes \|\| {{ottdp\|1.0\|no\|ottdrev=r19056}} \|\| Depends on [[Action3#cargo-type \| Action3 'cargo' type]]
	\|}		\|}

Frosch: move notes to the top and add some links

2011-06-21T21:47:59Z

move notes to the top and add some links

← Older revision		Revision as of 21:47, 21 June 2011
Line 19:		Line 19:

	The only graphics associated with airports is their preview sprite. The default size for the preview sprite is 230x140. The airport build GUI will automatically scale if you have a smaller or larger image, but it will probably look best if you make sure it is no larger than the default size.		The only graphics associated with airports is their preview sprite. The default size for the preview sprite is 230x140. The airport build GUI will automatically scale if you have a smaller or larger image, but it will probably look best if you make sure it is no larger than the default size.

		⚫	Do not skip an Action2 using [[Action9]] (unless it skips the whole file). Action2 must not be skipped by Action9 or TTDPatch will most likely crash. Skip or modify [[Action3]] instead. Skipping an Action2 with an [[Action7]] has no effect.

	== Syntax ==		== Syntax ==
Line 66:		Line 68:
	The sprite set to use for displaying. Entry is a WORD value in little endian format, and refers to the most recent action1 set. For example, action1 set 3 would be encoded as 03 00. Note the additional 00 which is needed because it must be a word value here.		The sprite set to use for displaying. Entry is a WORD value in little endian format, and refers to the most recent action1 set. For example, action1 set 3 would be encoded as 03 00. Note the additional 00 which is needed because it must be a word value here.
	(Don't forget that sprite set numbering starts from zero)		(Don't forget that sprite set numbering starts from zero)

	=== Notes ===

⚫	Do not skip an ~~action2~~ using ~~action9~~ (unless it skips the whole file). Action2 must not be skipped by ~~action9~~ or TTDPatch will most likely crash. Skip or modify ~~action3~~ instead. Skipping an ~~action2~~ with an ~~action7~~ has no effect.

Frosch: do not put some random feature into the syntax

2011-06-20T20:20:51Z

do not put some random feature into the syntax

← Older revision		Revision as of 20:20, 20 June 2011
Line 22:		Line 22:
	== Syntax ==		== Syntax ==

	<Sprite-number> * <Length> 02 ~~0B/10~~ <set-id> 01 00 <set>		<Sprite-number> * <Length> 02 <feature> <set-id> 01 00 <set>

	{\|		{\|
Line 33:		Line 33:
	\|02\|\|B\|\|Defines action2		\|02\|\|B\|\|Defines action2
	\|-		\|-
			\|<feature>\|\|B\|\|[[Features \| Feature]] being defined
	\|0B/10\|\|B\|\|Sprites are used for feature 0B - cargoes, or feature 10 - rail types
	\|-		\|-
	\|<set-id>\|\|B\|\|What set-ID this action2 defines		\|<set-id>\|\|B\|\|What set-ID this action2 defines

Frosch: moved Action2Cargos to Action2/Single Set: use subpages

2011-06-17T21:13:31Z

moved Action2Cargos to Action2/Single Set: use subpages

← Older revision	Revision as of 21:13, 17 June 2011
(No difference)

Frosch: merge canals page

2011-06-17T21:03:31Z

merge canals page

← Older revision		Revision as of 21:03, 17 June 2011
Line 56:		Line 56:
	Count the number of bytes in this action.		Count the number of bytes in this action.

	=== ~~Set~~ ===		=== set-id ===

			This defines the ID of the current action 2. This ID will later be referred to by [[Action3\|action 3]], or a variational/random action 2.
⚫	~~A '''WORD''' value, the number of the sprite set to be used.~~ (Don't forget that sprite set numbering starts from zero)

			You can reuse action 2 IDs, and there's no restriction on the order in which they are defined.

			=== set ===

			The sprite set to use for displaying. Entry is a WORD value in little endian format, and refers to the most recent action1 set. For example, action1 set 3 would be encoded as 03 00. Note the additional 00 which is needed because it must be a word value here.
		⚫	(Don't forget that sprite set numbering starts from zero)

			=== Notes ===

			Do not skip an action2 using action9 (unless it skips the whole file). Action2 must not be skipped by action9 or TTDPatch will most likely crash. Skip or modify action3 instead. Skipping an action2 with an action7 has no effect.

Frosch: merge pages on cargos, canals, airports and railtypes

2011-06-17T20:56:07Z

merge pages on cargos, canals, airports and railtypes

← Older revision		Revision as of 20:56, 17 June 2011
Line 1:		Line 1:
	== Introduction ==		== Introduction ==
			{\| \|-
			!Feature !! TTDPatch !! OpenTTD !! Associated graphics
			\|-
			\|Canals \|\| ? \|\| 0.6 \|\| Depends on [[Action3#ids \| Action3 ID]]; see [[Action0/Canals \| Action0]]
			\|-
			\|Cargos \|\| ? \|\| 0.6 \|\| Single icon sprite
			\|-
			\|Airports \|\| not supported \|\| 1.1.0 \|\| Single preview image
			\|-
			\|Railtypes \|\| not supported \|\| 1.0.0 (r19056) \|\| Depends on [[Action3#cargo-type \| Action3 'cargo' type]]
			\|}

			The Action2 for these features defines only a single spriteset, therefore the action2 you need isn't too complicated.
	Defining set-IDs for cargoes, railtypes and airports.

	The only graphics associated to cargoes is their icon that is shown in the station window~~, therefore the action2 you need isn't too complicated~~.		The only graphics associated to cargoes is their icon that is shown in the station window.

	The graphics associated with railtypes are somewhat more complicated, but all their logic is in variational action2s and the action3; the standard action2 is again not complicated.		The graphics associated with railtypes are somewhat more complicated, but all their logic is in variational action2s and the action3; the standard action2 is again not complicated.

Pm-bot: Beautify wiki markup

2011-06-15T14:47:44Z

Beautify wiki markup

← Older revision		Revision as of 14:47, 15 June 2011
Line 1:		Line 1:

	== Introduction ==		== Introduction ==

Line 10:		Line 9:
	The only graphics associated with airports is their preview sprite. The default size for the preview sprite is 230x140. The airport build GUI will automatically scale if you have a smaller or larger image, but it will probably look best if you make sure it is no larger than the default size.		The only graphics associated with airports is their preview sprite. The default size for the preview sprite is 230x140. The airport build GUI will automatically scale if you have a smaller or larger image, but it will probably look best if you make sure it is no larger than the default size.

	==Syntax==		== Syntax ==

	<Sprite-number> * <Length> 02 0B/10 <set-id> 01 00 <set>		<Sprite-number> * <Length> 02 0B/10 <set-id> 01 00 <set>
Line 36:		Line 35:
	You may note that this is the same as the action2 entry for vehicles, but with num_loadtypes=1 and num_loadingtypes=0, and only one set number.		You may note that this is the same as the action2 entry for vehicles, but with num_loadtypes=1 and num_loadingtypes=0, and only one set number.

	==Description==		== Description ==

	===Sprite-number===		=== Sprite-number ===

	This is just the number you are at.		This is just the number you are at.

	===Length===		=== Length ===

	Count the number of bytes in this action.		Count the number of bytes in this action.

	===Set===		=== Set ===

	A '''WORD''' value, the number of the sprite set to be used. (Don't forget that sprite set numbering starts from zero)		A '''WORD''' value, the number of the sprite set to be used. (Don't forget that sprite set numbering starts from zero)