Action2 - Revision history

Jgr: Add road stops to feature table

2023-06-11T09:52:40Z

Add road stops to feature table

← Older revision		Revision as of 09:52, 11 June 2023
Line 85:		Line 85:
	\|-		\|-
	\|13\|\|[[Action2/Single_Set \| Tramtypes]]		\|13\|\|[[Action2/Single_Set \| Tramtypes]]
			\|-
			\|14\|\|[[Action2/Sprite_Layout \| Road Stops]] (special Sprite Layout format)
	\|}		\|}

Andrew350: /* Feature */ added roadtypes / tramtypes

2019-12-28T12:27:43Z

Feature: added roadtypes / tramtypes

← Older revision		Revision as of 12:27, 28 December 2019
Line 81:		Line 81:
	\|-		\|-
	\|11\|\|[[Action2/Sprite_Layout \| Airport Tiles]] (special Sprite Layout format)		\|11\|\|[[Action2/Sprite_Layout \| Airport Tiles]] (special Sprite Layout format)
			\|-
			\|12\|\|[[Action2/Single_Set \| Roadtypes]]
			\|-
			\|13\|\|[[Action2/Single_Set \| Tramtypes]]
	\|}		\|}

Frosch: move notes to the top and add some links

2011-06-21T21:41:24Z

move notes to the top and add some links

← Older revision		Revision as of 21:41, 21 June 2011
Line 3:		Line 3:
	Defining graphics set IDs.		Defining graphics set IDs.

	~~Action 2~~ is used to group sets of sprites from the previous [[Action1~~\|action 1~~]] together, and make them accessible by a variational or random ~~action2~~ (chain) or an ~~action3~~.		Action2 is used to group sets of sprites from the previous [[Action1]] together, and make them accessible by a [[VariationalAction2\|variational]] or [[RandomAction2\|random action 2]] (chain) or an [[Action3]].

		⚫	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 ==

	In general, the data looks as follows:		In general, the data looks as follows. Some features use a different syntax though (see table below).

	<Sprite-number> * <Length> 02 <feature> <set-id> <num-ent1> <num-ent2> <entries...>		<Sprite-number> * <Length> 02 <feature> <set-id> <num-ent1> <num-ent2> <entries...>
Line 94:		Line 96:

	This is the list of action 1 sets to use, first num-ent1 for the first range, then num-ent2 entries for the second range.		This is the list of action 1 sets to use, first num-ent1 for the first range, then num-ent2 entries for the second range.

	=== Notes ===

⚫	Do not skip an ~~action 2~~ using [[Action9~~\|action 9~~]] (unless it skips the whole file). ~~Action 2~~ must not be skipped by ~~action 9~~ or ~~the patch~~ will most likely crash. Skip or modify [[Action3~~\|action 3~~]] instead. Skipping an ~~action 2~~ with an [[Action7~~\|action 7~~]] has no effect.

	=== Feature specific formats ===

	Some features and/or num-ent1 values have a special format. These are detailed on their separate pages (see main menu)

	==Example==		==Example==

Frosch: update feature table

2011-06-21T21:32:17Z

update feature table

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

	=== ~~feature~~ ===		=== Feature ===

	This sets the type of feature that you wish to change. Set it to:		This sets the type of [[Features\|feature]] that you wish to change. Set it to:

	{\|		{\|- \|
	!Value!!Feature		!Value!![[Features\|Feature]]
	\|-		\|-
			\|00\|\|[[Action2/Vehicles \| Trains]]
	\|00 \|\| trains
	\|-		\|-
			\|01\|\|[[Action2/Vehicles \| Road Vehicles]]
	\|01 \|\| road vehicles
	\|-		\|-
			\|02\|\|[[Action2/Vehicles \| Ships]]
	\|02 \|\| ships
	\|-		\|-
			\|03\|\|[[Action2/Vehicles \| Aircraft]]
	\|03 \|\| planes
	\|-		\|-
			\|04\|\|[[Action2/Stations \| Stations]]
	\|04 \|\| stations
	\|-		\|-
			\|05\|\|[[Action2/Single_Set \| Canals/Rivers]]
	\|05 \|\| canals/rivers
	\|-		\|-
			\|07\|\|[[Action2/Sprite_Layout \| Houses]] (special Sprite Layout format)
	\|06 \|\| bridges
	\|-		\|-
			\|09\|\|[[Action2/Sprite_Layout \| Industry Tiles]] (special Sprite Layout format)
	\|07 \|\| houses
	\|-		\|-
			\|0A\|\|[[Action2/Industries \| Industries]] (special Production Callback format)
	\|09 \|\| industry tiles
	\|-		\|-
			\|0B\|\|[[Action2/Single_Set \| Cargos]]
	\|0A \|\| industries
	\|-		\|-
			\|0C\|\|[[Action2/Only_Callback_Failure \| Sound Effects]] (callback failure only)
	\|0B \|\| cargos
	\|-		\|-
			\|0D\|\|[[Action2/Single_Set \| Airports]]
	\|0D \|\| airports (OpenTTD r19204)
	\|-		\|-
			\|0E\|\|[[Action2/Only_Callback_Failure \| Signals]] (callback failure only)
	\|0F \|\| objects
	\|-		\|-
			\|0F\|\|[[Action2/Sprite_Layout \| Objects]] (special Sprite Layout format)
	\|10 \|\| rail types (OpenTTD r19056)
	\|-		\|-
			\|10\|\|[[Action2/Single_Set \| Railtypes]]
	\|11 \|\| airport tiles (OpenTTD r19204)
			\|-
			\|11\|\|[[Action2/Sprite_Layout \| Airport Tiles]] (special Sprite Layout format)
	\|}		\|}

Yexo: /* feature */ put all features in a table

2011-06-18T15:04:49Z

feature: put all features in a table

← Older revision		Revision as of 15:04, 18 June 2011
Line 45:		Line 45:
	This sets the type of feature that you wish to change. Set it to:		This sets the type of feature that you wish to change. Set it to:

			{\|
⚫	00 ~~for~~ trains
			!Value!!Feature

			\|-
⚫	01 ~~for~~ road vehicles
		⚫	\|00 \|\| trains

			\|-
⚫	02 ~~for~~ ships
		⚫	\|01 \|\| road vehicles

			\|-
⚫	03 ~~for~~ planes
		⚫	\|02 \|\| ships

			\|-
⚫	04 ~~for~~ stations
		⚫	\|03 \|\| planes

			\|-
⚫	05 ~~for~~ canals/rivers
		⚫	\|04 \|\| stations

			\|-
⚫	06 ~~for~~ bridges
		⚫	\|05 \|\| canals/rivers

			\|-
⚫	07 ~~for~~ houses
		⚫	\|06 \|\| bridges

			\|-
⚫	09 ~~for~~ industry tiles
		⚫	\|07 \|\| houses

			\|-
⚫	0A ~~for~~ industries
		⚫	\|09 \|\| industry tiles

			\|-
⚫	0B ~~for~~ cargos
		⚫	\|0A \|\| industries

			\|-
⚫	0F ~~for~~ objects
		⚫	\|0B \|\| cargos

			\|-
⚫	10 ~~for~~ rail types (~~since~~ OpenTTD r19056)
			\|0D \|\| airports (OpenTTD r19204)
			\|-
		⚫	\|0F \|\| objects
			\|-
		⚫	\|10 \|\| rail types (OpenTTD r19056)
			\|-
			\|11 \|\| airport tiles (OpenTTD r19204)
			\|}

	=== set-id ===		=== set-id ===

Pm-bot: Beautify wiki markup

2011-06-15T14:47:34Z

Beautify wiki markup

← Older revision		Revision as of 14:47, 15 June 2011
Line 5:		Line 5:
	Action 2 is used to group sets of sprites from the previous [[Action1\|action 1]] together, and make them accessible by a variational or random action2 (chain) or an action3.		Action 2 is used to group sets of sprites from the previous [[Action1\|action 1]] together, and make them accessible by a variational or random action2 (chain) or an action3.

	==Syntax==		== Syntax ==

	In general, the data looks as follows:		In general, the data looks as follows:
Line 31:		Line 31:
	\|}		\|}

	==Descriptions==		== Descriptions ==

	===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.

	===feature===		=== feature ===

	This sets the type of feature that you wish to change. Set it to:		This sets the type of feature that you wish to change. Set it to:
Line 71:		Line 71:
	10 for rail types (since OpenTTD r19056)		10 for rail types (since OpenTTD r19056)

	===set-id===		=== 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.		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.

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

	===num-ent1, num-ent2===		=== num-ent1, num-ent2 ===

	Each feature has two different graphics ranges, but their exact meaning differs from feature to feature. For example, for vehicles, the first set is used while moving, and the second while loading/unloading in a station.		Each feature has two different graphics ranges, but their exact meaning differs from feature to feature. For example, for vehicles, the first set is used while moving, and the second while loading/unloading in a station.

	===entries===		=== entries ===

	This is the list of action 1 sets to use, first num-ent1 for the first range, then num-ent2 entries for the second range.		This is the list of action 1 sets to use, first num-ent1 for the first range, then num-ent2 entries for the second range.

	===Notes===		=== Notes ===

	Do not skip an action 2 using [[Action9\|action 9]] (unless it skips the whole file). Action 2 must not be skipped by action 9 or the patch will most likely crash. Skip or modify [[Action3\|action 3]] instead. Skipping an action 2 with an [[Action7\|action 7]] has no effect.		Do not skip an action 2 using [[Action9\|action 9]] (unless it skips the whole file). Action 2 must not be skipped by action 9 or the patch will most likely crash. Skip or modify [[Action3\|action 3]] instead. Skipping an action 2 with an [[Action7\|action 7]] has no effect.

	===Feature specific formats===		=== Feature specific formats ===

	Some features and/or num-ent1 values have a special format. These are detailed on their separate pages (see main menu)		Some features and/or num-ent1 values have a special format. These are detailed on their separate pages (see main menu)

Planetmaker: finally... heading sizes

2011-06-14T22:36:12Z

finally... heading sizes

← Older revision		Revision as of 22:36, 14 June 2011
Line 31:		Line 31:
	\|}		\|}

			==Descriptions==
	==Filling in the terms==

	===Sprite-number===		===Sprite-number===
Line 71:		Line 71:
	10 for rail types (since OpenTTD r19056)		10 for rail types (since OpenTTD r19056)

	==set-id==		===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.		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.
Line 77:		Line 77:
	You can reuse action 2 IDs, and there's no restriction on the order in which they are defined.		You can reuse action 2 IDs, and there's no restriction on the order in which they are defined.

	==num-ent1, num-ent2==		===num-ent1, num-ent2===

	Each feature has two different graphics ranges, but their exact meaning differs from feature to feature. For example, for vehicles, the first set is used while moving, and the second while loading/unloading in a station.		Each feature has two different graphics ranges, but their exact meaning differs from feature to feature. For example, for vehicles, the first set is used while moving, and the second while loading/unloading in a station.

	==entries==		===entries===

	This is the list of action 1 sets to use, first num-ent1 for the first range, then num-ent2 entries for the second range.		This is the list of action 1 sets to use, first num-ent1 for the first range, then num-ent2 entries for the second range.

	==Notes==		===Notes===

	Do not skip an action 2 using [[Action9\|action 9]] (unless it skips the whole file). Action 2 must not be skipped by action 9 or the patch will most likely crash. Skip or modify [[Action3\|action 3]] instead. Skipping an action 2 with an [[Action7\|action 7]] has no effect.		Do not skip an action 2 using [[Action9\|action 9]] (unless it skips the whole file). Action 2 must not be skipped by action 9 or the patch will most likely crash. Skip or modify [[Action3\|action 3]] instead. Skipping an action 2 with an [[Action7\|action 7]] has no effect.

	==Feature specific formats==		===Feature specific formats===

	Some features and/or num-ent1 values have a special format. These are detailed on their separate pages (see main menu)		Some features and/or num-ent1 values have a special format. These are detailed on their separate pages (see main menu)

	===Example===		==Example==

Planetmaker: further small fixes

2011-06-14T22:34:55Z

further small fixes

← Older revision		Revision as of 22:34, 14 June 2011
Line 1:		Line 1:

	== Introduction ==		== Introduction ==

	=Action 2=

	Defining graphics set IDs.		Defining graphics set IDs.

	==Introduction==

	Action 2 is used to group sets of sprites from the previous [[Action1\|action 1]] together, and make them accessible by a variational or random action2 (chain) or an action3.		Action 2 is used to group sets of sprites from the previous [[Action1\|action 1]] together, and make them accessible by a variational or random action2 (chain) or an action3.

	==~~Format~~==		==Syntax==

	In general, the data looks as follows:		In general, the data looks as follows:
Line 98:		Line 93:
	Some features and/or num-ent1 values have a special format. These are detailed on their separate pages (see main menu)		Some features and/or num-ent1 values have a special format. These are detailed on their separate pages (see main menu)

	==Example==		===Example===

	<span style='color:#808080'>Something to go here</span>

Planetmaker: /* Feature specific formats */ toc for action2 not there. Refer to main menu

2011-06-14T22:33:36Z

Feature specific formats: toc for action2 not there. Refer to main menu

← Older revision		Revision as of 22:33, 14 June 2011
Line 96:		Line 96:
	==Feature specific formats==		==Feature specific formats==

	Some features and/or num-ent1 values have a special format. These are detailed on ~~the~~ pages ~~listed~~ ~~below.~~		Some features and/or num-ent1 values have a special format. These are detailed on their separate pages (see main menu)

	{toc}

	==Example==		==Example==

Planetmaker: /* Format */ fix style further and bot mistakes

2011-06-14T22:32:19Z

Format: fix style further and bot mistakes

← Older revision		Revision as of 22:32, 14 June 2011
Line 14:		Line 14:
	In general, the data looks as follows:		In general, the data looks as follows:

	~~<pre> -+~~<Sprite-number> * <Length> 02 <feature> <set-id> <num-ent1> <num-ent2> <entries...~~>+-</pre~~>		<Sprite-number> * <Length> 02 <feature> <set-id> <num-ent1> <num-ent2> <entries...>

	{\|		{\|
	!~~'''~~Element~~'''~~!![[GRFActionsDetailed~~!!'''~~Size~~'''~~]]!!~~'''~~Description~~'''~~		!Element!![[GRFActionsDetailed\|Size]]!!Description

	\|-		\|-
	\|<Sprite-number>\|\|dec\|\|A sequential sprite number		\|<Sprite-number>\|\|dec\|\|A sequential sprite number

	\|-		\|-
	\|<length>\|\|dec\|\|The total number of bytes used in this action		\|<length>\|\|dec\|\|The total number of bytes used in this action

	\|-		\|-
	\|02\|\|B\|\|Defines action 02		\|02\|\|B\|\|Defines action 02

	\|-		\|-
	\|<feature>\|\|B\|\|For what type of feature should the following sprites be used?		\|<feature>\|\|B\|\|For what type of feature should the following sprites be used?

	\|-		\|-
	\|<set-id>\|\|B\|\|What set-ID this action 2 defines		\|<set-id>\|\|B\|\|What set-ID this action 2 defines

	\|-		\|-
	\|<num-ent1>\|\|B\|\|First number of entries, depends on feature		\|<num-ent1>\|\|B\|\|First number of entries, depends on feature

	\|-		\|-
	\|<num-ent2>\|\|B\|\|Second number of entries, depends on feature		\|<num-ent2>\|\|B\|\|Second number of entries, depends on feature

	\|-		\|-
	\|<entries...>\|\|W\|\|Entry numbers, depends on the feature		\|<entries...>\|\|W\|\|Entry numbers, depends on the feature