Action0/Objects - Revision history

Peter1138: /* Number of views (17) */

2025-06-06T11:14:38Z

Number of views (17)

← Older revision		Revision as of 11:14, 6 June 2025
Line 194:		Line 194:
	=== Number of views (17) ===		=== Number of views (17) ===

	Objects may have "views", i.e. different graphical representations, e.g. used to show rotated views of an object. Number of views may be 1, 2, or 4. Default value is 1. Views should be used for rotations or minor variations, not for objects of different types as those should just be different object types which provides a better experience for players.		Objects may have "views", i.e. different graphical representations, e.g. used to show rotated views of an object. Number of views may be 1, 2, or 4. Default value is 1. Views should be used for rotations or minor variations, not for objects of different types as those should just be different object types which provides a better experience for players. Using separate objects is better for discoverability, naming, filtering, used state, favourite state, and badges.

	For non-square objects, x and y sizes are swapped for odd views. I.e., giving an object size of 12 (x = 1, y = 2), it will be displayed as 12 for num = <nowiki>[</nowiki>0,2] (x-direction) but as 2*1 for num = <nowiki>[</nowiki>1,3] (y-direction).		For non-square objects, x and y sizes are swapped for odd views. I.e., giving an object size of 12 (x = 1, y = 2), it will be displayed as 12 for num = <nowiki>[</nowiki>0,2] (x-direction) but as 2*1 for num = <nowiki>[</nowiki>1,3] (y-direction).

Peter1138: /* Number of views (17) */

2025-06-06T09:25:43Z

Number of views (17)

← Older revision		Revision as of 09:25, 6 June 2025
Line 194:		Line 194:
	=== Number of views (17) ===		=== Number of views (17) ===

	Objects may have "views", i.e. different graphical representations, e.g. used to show rotated views of an object. Number of views may be 1, 2, or 4. Default value is 1.		Objects may have "views", i.e. different graphical representations, e.g. used to show rotated views of an object. Number of views may be 1, 2, or 4. Default value is 1. Views should be used for rotations or minor variations, not for objects of different types as those should just be different object types which provides a better experience for players.

	For non-square objects, x and y sizes are swapped for odd views. I.e., giving an object size of 12 (x = 1, y = 2), it will be displayed as 12 for num = <nowiki>[</nowiki>0,2] (x-direction) but as 2*1 for num = <nowiki>[</nowiki>1,3] (y-direction).		For non-square objects, x and y sizes are swapped for odd views. I.e., giving an object size of 12 (x = 1, y = 2), it will be displayed as 12 for num = <nowiki>[</nowiki>0,2] (x-direction) but as 2*1 for num = <nowiki>[</nowiki>1,3] (y-direction).

	Use object varaction2 var48 to access particular views of an object.		Use object varaction2 var48 to access particular views of an object.

	==Examples==		==Examples==

Frosch: /* Animation triggers (13) */

2025-04-24T18:45:09Z

Animation triggers (13)

← Older revision		Revision as of 18:45, 24 April 2025
Line 150:		Line 150:

	{\|		{\|
	!~~Bit~~!!~~Value~~!!Meaning!!Happens on!!Var 18		!Property bit, var18 byte 0!!Property value!!Meaning!!Happens on!!Var 18 byte 1
	\|-		\|-
	\|0\|\|1\|\|Object is built\|\|all tiles\|\|		\|0\|\|1\|\|Object is built\|\|all tiles\|\|
Line 158:		Line 158:
	\|2\|\|4\|\|Synchronised periodic tile loop\|\|all tiles\|\|		\|2\|\|4\|\|Synchronised periodic tile loop\|\|all tiles\|\|
	\|}		\|}
	Currently no trigger provides additional information in var 18.		Currently no trigger provides additional information in var 18 byte 1.

	The synchronised periodic tile loop is called directly after the (unsynchronised) periodic tile loop of the northern tile.		The synchronised periodic tile loop is called directly after the (unsynchronised) periodic tile loop of the northern tile.

Peter1138: /* Properties */

2025-02-17T14:55:49Z

Properties

← Older revision		Revision as of 14:55, 17 February 2025
Line 49:		Line 49:
	\|-		\|-
	\|18\|\|B\|\|{{ottdp\|1.4\|no\|ottdrev=r25879}}\|\|Measure for number of objects placed upon map creation		\|18\|\|B\|\|{{ottdp\|1.4\|no\|ottdrev=r25879}}\|\|Measure for number of objects placed upon map creation
			\|-
			\|19\|\|W n*W\|\|{{ottdp\|15}}\|\|List of badges
	\|}		\|}

Peter1138: Add badge for 14.0 feature

2023-05-05T07:29:10Z

Add badge for 14.0 feature

← Older revision		Revision as of 07:29, 5 May 2023
Line 8:		Line 8:
	OpenTTD supports 64000 object types per game, and 255 object IDs per grf file.		OpenTTD supports 64000 object types per game, and 255 object IDs per grf file.

	64000 object IDs per grf file are supported since OpenTTD 14.0.		{{ottdp\|14.0\|no}} 64000 object IDs per grf file are supported since OpenTTD 14.0.

	The property you '''must''' set for each object ID is 08 (in addition to defining an action 3 for it). Also, all object IDs must get their classes in the right order, starting from ID 00 onwards.		The property you '''must''' set for each object ID is 08 (in addition to defining an action 3 for it). Also, all object IDs must get their classes in the right order, starting from ID 00 onwards.

Peter1138: /* Introduction */

2023-05-05T07:27:07Z

Introduction

← Older revision		Revision as of 07:27, 5 May 2023
Line 7:		Line 7:

	OpenTTD supports 64000 object types per game, and 255 object IDs per grf file.		OpenTTD supports 64000 object types per game, and 255 object IDs per grf file.

			64000 object IDs per grf file are supported since OpenTTD 14.0.

	The property you '''must''' set for each object ID is 08 (in addition to defining an action 3 for it). Also, all object IDs must get their classes in the right order, starting from ID 00 onwards.		The property you '''must''' set for each object ID is 08 (in addition to defining an action 3 for it). Also, all object IDs must get their classes in the right order, starting from ID 00 onwards.

Andythenorth: Max number of objects was quite significantly wrong for OpenTTD case.

2022-01-24T10:03:04Z

Max number of objects was quite significantly wrong for OpenTTD case.

← Older revision		Revision as of 10:03, 24 January 2022
Line 4:		Line 4:
	Unlike vehicles or new stations, most new objects have no real equivalent in TTD.		Unlike vehicles or new stations, most new objects have no real equivalent in TTD.

	The IDs are therefore free to be chosen and will in fact be allocated automatically by the patch. In action 0, you only specify IDs relative to the set, i.e. the ID of the first object type is 00, the second object type is 01 and so on. ~~In total, each game can only have 255 object IDs for all active grf files.~~		The IDs are therefore free to be chosen and will in fact be allocated automatically by the patch. In action 0, you only specify IDs relative to the set, i.e. the ID of the first object type is 00, the second object type is 01 and so on.

			OpenTTD supports 64000 object types per game, and 255 object IDs per grf file.

	The property you '''must''' set for each object ID is 08 (in addition to defining an action 3 for it). Also, all object IDs must get their classes in the right order, starting from ID 00 onwards.		The property you '''must''' set for each object ID is 08 (in addition to defining an action 3 for it). Also, all object IDs must get their classes in the right order, starting from ID 00 onwards.

Frosch: water amount != length of coastline

2013-10-18T17:51:31Z

water amount != length of coastline

← Older revision		Revision as of 17:51, 18 October 2013
Line 124:		Line 124:
	\|12\|\|4096\|\|{{ottdp\|1.1\|2.6\|ottdrev=r21455\|ttdprev=r2360}}\|\|Random bits in the "next animation frame" callback		\|12\|\|4096\|\|{{ottdp\|1.1\|2.6\|ottdrev=r21455\|ttdprev=r2360}}\|\|Random bits in the "next animation frame" callback
	\|-		\|-
	\|13\|\|8192\|\|{{ottdp\|1.4\|no\|ottdrev=r25878}}\|\|Scale amount of objects placed on map generation roughly by ~~water~~ ~~content~~ of ~~map~~		\|13\|\|8192\|\|{{ottdp\|1.4\|no\|ottdrev=r25878}}\|\|Scale amount of objects placed on map generation not by map area, but roughly by the length of the coastline
	\|}		\|}

Planetmaker: /* Properties */ 0x18: Number of objects placed upon map creation

2013-10-17T21:53:31Z

Properties: 0x18: Number of objects placed upon map creation

← Older revision		Revision as of 21:53, 17 October 2013
Line 43:		Line 43:
	\|-		\|-
	\|17\|\|B\|\|{{ottdp\|1.1\|2.6\|ottdrev=r20670\|ttdprev=r2340}}\|\|Number of object views		\|17\|\|B\|\|{{ottdp\|1.1\|2.6\|ottdrev=r20670\|ttdprev=r2340}}\|\|Number of object views
			\|-
			\|18\|\|B\|\|{{ottdp\|1.4\|no\|ottdrev=r25879}}\|\|Measure for number of objects placed upon map creation
	\|}		\|}

Planetmaker: /* Object flags (10) */ missing ttdp indication

2013-10-17T21:51:03Z

Object flags (10): missing ttdp indication

← Older revision		Revision as of 21:51, 17 October 2013
Line 122:		Line 122:
	\|12\|\|4096\|\|{{ottdp\|1.1\|2.6\|ottdrev=r21455\|ttdprev=r2360}}\|\|Random bits in the "next animation frame" callback		\|12\|\|4096\|\|{{ottdp\|1.1\|2.6\|ottdrev=r21455\|ttdprev=r2360}}\|\|Random bits in the "next animation frame" callback
	\|-		\|-
	\|13\|\|8192\|\|{{~~ottd~~\|1.4\|ottdrev=r25878}}\|\|Scale amount of objects placed on map generation roughly by water content of map		\|13\|\|8192\|\|{{ottdp\|1.4\|no\|ottdrev=r25878}}\|\|Scale amount of objects placed on map generation roughly by water content of map
	\|}		\|}