GRFSpecs - Recent changes [en-gb]

NML:IndustryTiles

Andythenorth — Sat, 15 Aug 2026 14:35:00 GMT

← Older revision		Revision as of 14:35, 15 August 2026
(2 intermediate revisions by the same user not shown)
Line 4:		Line 4:

	== Industry tile ID allocation ==		== Industry tile ID allocation ==
	Industry tile IDs are local to the NewGRF, you are free to choose any ID in the 0..255-range. You should start your item definition with the 'substitute'-property, which allocates a new industry tile. The value of this property should be the ID of a [[IndustryTileDefaultProps\|default industry tile]], which will be used instead of your item if it is not available for whatever reason (for example, missing NewGRF).		Industry tile IDs are local to the NewGRF, you are free to choose any ID in the 0..255-range.
			{{ottdp\|16}} OpenTTD 16 increased the tile range, choose any ID in the 0..511-range..

			You should start your item definition with the 'substitute'-property, which allocates a new industry tile. The value of this property should be the ID of a [[IndustryTileDefaultProps\|default industry tile]], which will be used instead of your item if it is not available for whatever reason (for example, missing NewGRF).

	Furthermore, you can set the 'override'-property, which will cause the existing industry tile to be replaced with your item. You should use this if you are for example defining a coal mine which changes production more dynamically. If your type is not a direct replacement of an existing item, don't set this property.		Furthermore, you can set the 'override'-property, which will cause the existing industry tile to be replaced with your item. You should use this if you are for example defining a coal mine which changes production more dynamically. If your type is not a direct replacement of an existing item, don't set this property.

Action0/Industry Tiles

Andythenorth — Sat, 15 Aug 2026 14:30:47 GMT

Introduction

← Older revision		Revision as of 14:30, 15 August 2026
Line 5:		Line 5:
	Defining industry tiles follows the same schema as houses do: to start using an ID, you first need to define it by setting property 8 for it. If you try to reference an ID (either via action0 or via action3) that isn't defined, your request is ignored, but not reported as an error, either. This means that if you want to conditionally define an ID, all you need to do is skipping the action0 that sets property8, and everything else gets skipped automatically.		Defining industry tiles follows the same schema as houses do: to start using an ID, you first need to define it by setting property 8 for it. If you try to reference an ID (either via action0 or via action3) that isn't defined, your request is ignored, but not reported as an error, either. This means that if you want to conditionally define an ID, all you need to do is skipping the action0 that sets property8, and everything else gets skipped automatically.

	Industry tile IDs are unique within each grf file~~. The per-GRF ID is specified as a byte, which means no GRF can define more than 256 tile IDs~~. You should use your industry tile IDs sparingly. [[VariationalAction2/Industry_Tiles#Relative_position_.2843.29\| Variational action 2 variable 43]] for industry tiles can help you limiting tile consumption to 2 or 3 per industry. Avoid using tile FFh, so the tileID can be turned into an extended byte (in Action 3) in the distant future without breaking your NewGRF.		Industry tile IDs are unique within each grf file. You should use your industry tile IDs sparingly. [[VariationalAction2/Industry_Tiles#Relative_position_.2843.29\| Variational action 2 variable 43]] for industry tiles can help you limiting tile consumption to 2 or 3 per industry. Avoid using tile FFh, so the tileID can be turned into an extended byte (in Action 3) in the distant future without breaking your NewGRF.

	{{ttdp\|}} In total, TTDPatch can have up to a total of 256 new industry tile IDs (i.e. old tile types don't count).		{{ttdp\|}} In total, TTDPatch can have up to a total of 256 new industry tile IDs (i.e. old tile types don't count).

VariationalAction2/Towns

Zephyris — Thu, 13 Aug 2026 12:46:05 GMT

Add 0x60, added in https://github.com/OpenTTD/OpenTTD/commit/ada7ffaa73b62d7ce3b73e787d9bb0ec59f0d2f2

← Older revision		Revision as of 12:46, 13 August 2026
Line 9:		Line 9:
	\|-		\|-
	\|41\|\|W (B)\|\|{{ottdp\| \|}}\|\|Town index<ref>In OpenTTD this variable is word-sized, in TTDPatch this variable is byte-sized.</ref>		\|41\|\|W (B)\|\|{{ottdp\| \|}}\|\|Town index<ref>In OpenTTD this variable is word-sized, in TTDPatch this variable is byte-sized.</ref>
			\|-
			\|60\|\|D\|\|{{ottdp\|16\|no\|}}\|\|Land info for nearby tiles.
	\|-		\|-
	\|82\|\|W\|\|{{ottdp\| \|}}\|\|Population		\|82\|\|W\|\|{{ottdp\| \|}}\|\|Population
Line 43:		Line 45:

	TTDPatch only: This variable has a value between 0 and 69 (inclusive).		TTDPatch only: This variable has a value between 0 and 69 (inclusive).

			=== Land info for nearby tiles (62) ===

			This variable works exactly like [[VarAction2IndustryTiles#Land info of nearby tiles (60)\|var. 60 for industry tiles]], except that bit 0 of the '''bb''' part is undefined.

	=== Population (82) ===		=== Population (82) ===

NML:Vehicles

Andythenorth — Thu, 30 Jul 2026 22:20:37 GMT

Undo revision 5278 by Andythenorth (talk)

← Older revision		Revision as of 22:20, 30 July 2026
Line 965:		Line 965:
	\| [0 <nowiki>\|</nowiki> 1]		\| [0 <nowiki>\|</nowiki> 1]
	\| No		\| No
	\| {{ottd\|16}} Value is 1 if the train is driving backwards (trains only)~~. Only valid for <code style="color:darkgreen">PARENT</code> scope.~~		\| {{ottd\|16}} Value is 1 if the train is driving backwards (trains only)
	\|-		\|-
	\| built_during_preview		\| built_during_preview

VariationalAction2/Vehicles

Andythenorth — Thu, 30 Jul 2026 22:20:09 GMT

Modflags (FE and FF): https://github.com/OpenTTD/OpenTTD/pull/15579 makes bit 11 accurate for all vehicles

← Older revision		Revision as of 22:20, 30 July 2026
Line 395:		Line 395:
	\|10\|\|{{ottdp\|0.6\|2.5\|ttdprev=r1334}}\|\|Vehicle was built during the exclusive preview		\|10\|\|{{ottdp\|0.6\|2.5\|ttdprev=r1334}}\|\|Vehicle was built during the exclusive preview
	\|-		\|-
	\|11 ~~<ref>This bit is only accurate for the first vehicle in the consist.</ref>~~\|\|{{ottd\|16}}\|\|The train is driving backwards (trains only)		\|11\|\|{{ottd\|16}}\|\|The train is driving backwards (trains only)
	\|}		\|}
	<references/>		<references/>

NML:Vehicles

Andythenorth — Thu, 30 Jul 2026 21:47:52 GMT

Variables without parameter: modflag 0xFE bit 11 only valid for parent scope (according to nfo spec page)

← Older revision		Revision as of 21:47, 30 July 2026
Line 965:		Line 965:
	\| [0 <nowiki>\|</nowiki> 1]		\| [0 <nowiki>\|</nowiki> 1]
	\| No		\| No
	\| {{ottd\|16}} Value is 1 if the train is driving backwards (trains only)		\| {{ottd\|16}} Value is 1 if the train is driving backwards (trains only). Only valid for <code style="color:darkgreen">PARENT</code> scope.
	\|-		\|-
	\| built_during_preview		\| built_during_preview