Action1 - Revision history

Peter1138: /* Feature */

2025-12-03T08:24:14Z

Feature

2023-06-11T09:51:50Z

Add road stops to feature table

2019-12-28T12:33:27Z

Feature: added roadtypes / tramtypes

2012-07-22T09:40:47Z

update version requirement for ext a1 again

← Older revision		Revision as of 09:40, 22 July 2012
Line 28:		Line 28:

	=== Extended format ===		=== Extended format ===
	{{ottdp\|1.3\|no\|ottdrev=r24361}}		{{ottdp\|1.2.2\|no\|ottdrev=r24361}}
	<sprite-number> * <length> '''01''' <feature> '''00''' <first-set> <num-sets> <num-ent>		<sprite-number> * <length> '''01''' <feature> '''00''' <first-set> <num-sets> <num-ent>

2012-07-10T20:52:15Z

first-set: Document that spritesets are feature-specific

← Older revision		Revision as of 20:52, 10 July 2012
Line 102:		Line 102:
	This specifies the first set ID to define.		This specifies the first set ID to define.

	{{ottdp\|1.2\|no\|ottdrev=r22925}} Since OpenTTD r22925 spritesets stay valid across multiple Action1. That is, if one Action1 defines spritesets 0 to 4, and later a second Action1 redefines spriteset 0, spritesets 1 to 4 still refer to the first Action1. (Prior to OpenTTD r22925 and in TTDPatch only ~~spriteset~~ from a single Action1 are referencible from an Action2 at a time.)		{{ottdp\|1.2\|no\|ottdrev=r22925}} Since OpenTTD r22925 spritesets stay valid across multiple Action1. That is, if one Action1 defines spritesets 0 to 4, and later a second Action1 redefines spriteset 0, spritesets 1 to 4 still refer to the first Action1. Spritesets are feature-specific, each feature maintains its own mapping of ids to Action1 spritesets. (Prior to OpenTTD r22925 and in TTDPatch only spritesets from a single Action1 are referencible from an Action2 at a time. Referencing an Action1 with a different feature than the Action2 is an error.)

	This behaviour of Action1 applies to both the basic as well as the extended format.		This behaviour of Action1 applies to both the basic as well as the extended format.

2012-06-29T15:40:18Z

update version requirement for ext a1

← Older revision		Revision as of 15:40, 29 June 2012
Line 28:		Line 28:

	=== Extended format ===		=== Extended format ===
	{{ottdp\|1.2\|no\|ottdrev=~~r22926~~}}		{{ottdp\|1.3\|no\|ottdrev=r24361}}
	<sprite-number> * <length> '''01''' <feature> '''00''' <first-set> <num-sets> <num-ent>		<sprite-number> * <length> '''01''' <feature> '''00''' <first-set> <num-sets> <num-ent>

2011-09-11T16:06:40Z

mention meaning of 00 in basic format as well

← Older revision		Revision as of 16:06, 11 September 2011
Line 20:		Line 20:
	\|<feature>\|\|B\|\|The feature that following sprites should be used for (s.b.)		\|<feature>\|\|B\|\|The feature that following sprites should be used for (s.b.)
	\|-		\|-
	\|<num-sets>\|\|B\|\|The number of sprite sets you have (one sprite set is one vehicle/station/ship etc)		\|<num-sets>\|\|B\|\|The number of sprite sets you have (one sprite set is one vehicle/station/ship etc). Setting this to 00 makes it an extended format (see below).
	\|-		\|-
	\|<num-ent>\|\|B*\|\|The number of views the sprite has		\|<num-ent>\|\|B*\|\|The number of views the sprite has

2011-09-11T16:02:52Z

recolorsprites are valid in action1 as well for some time

← Older revision		Revision as of 16:02, 11 September 2011
Line 25:		Line 25:
	\|}		\|}

	The block of data that always follows after action 01 should consist of num-sets * num-ent RealSprites.		The block of data that always follows after action 01 should consist of num-sets * num-ent RealSprites or RecolorSprites.

	=== Extended format ===		=== Extended format ===
Line 51:		Line 51:
	\|}		\|}

	The block of data that always follows after action 01 should consist of num-sets * num-ent RealSprites.		The block of data that always follows after action 01 should consist of num-sets * num-ent RealSprites or RecolorSprites.

	== Description ==		== Description ==

2011-09-11T16:01:28Z

explain mixing spritesets from multiple action1

@@ Line 98: / Line 98: @@
 |11||Airport Tiles
 |}
 === num-sets ===

2011-09-11T15:46:39Z

extended format

@@ Line 5: / Line 5: @@
 == Syntax ==
  <sprite-number> * <length> '''01''' <feature> <num-sets> <num-ent>
@@ Line 21: / Line 21: @@
 |-
 |<num-sets>||B||The number of sprite sets you have (one sprite set is one vehicle/station/ship etc)
 |-
 |<num-ent>||B*||The number of views the sprite has