NML:IndustryTiles - Revision history

Rito12: /* Industry tile variables */ rail type -> industry tile

2026-01-04T14:39:05Z

Industry tile variables: rail type -> industry tile

← Older revision		Revision as of 14:39, 4 January 2026
Line 155:		Line 155:
	\| Label from the [[NML:Badgetable\|badgetable]].		\| Label from the [[NML:Badgetable\|badgetable]].
	\| [0 <nowiki>\|</nowiki> 1]		\| [0 <nowiki>\|</nowiki> 1]
	\| {{ottd\|15.0}} Check if the ~~rail~~ ~~type~~ has that specific badge attached.		\| {{ottd\|15.0}} Check if the industry tile has that specific badge attached.
	\|}		\|}

Rito12: /* Industry tile variables */

2026-01-04T14:38:28Z

Industry tile variables

← Older revision		Revision as of 14:38, 4 January 2026
Line 141:		Line 141:
	Industry tiles have access to the [[#Common variables\|common variables]] described above. Additionally, they have access to the following:		Industry tiles have access to the [[#Common variables\|common variables]] described above. Additionally, they have access to the following:

	{\| class="t"		{\| class="wikitable sortable"
	! name		! name
	! arguments		! arguments
			! value range
	! comment		! comment
	\|-		\|-
	\| nearby_tile_is_same_industry		\| nearby_tile_is_same_industry
	\| x, y		\| x, y
			\| [0 <nowiki>\|</nowiki> 1]
	\| Parameters indicate a signed tile offset relative to the current tile. Returns 1 if the tile is part of the same industry, 0 otherwise		\| Parameters indicate a signed tile offset relative to the current tile. Returns 1 if the tile is part of the same industry, 0 otherwise
			\|-
			\| has_badge
			\| Label from the [[NML:Badgetable\|badgetable]].
			\| [0 <nowiki>\|</nowiki> 1]
			\| {{ottd\|15.0}} Check if the rail type has that specific badge attached.
	\|}		\|}

Rito12: /* Industry tile properties */ Move badges property

2026-01-03T21:28:44Z

Industry tile properties: Move badges property

← Older revision		Revision as of 21:28, 3 January 2026
Line 66:		Line 66:
	* This property adds 8/8 acceptance for the matching cargotypes. You can list negative acceptances (-8/8) in property 13 to exclude specific cargos.		* This property adds 8/8 acceptance for the matching cargotypes. You can list negative acceptances (-8/8) in property 13 to exclude specific cargos.
	* Tile callback cargo_type_accept overrides all acceptances including those added by this flag.		* Tile callback cargo_type_accept overrides all acceptances including those added by this flag.
		⚫	\|-
		⚫	\| badges
		⚫	\| Array of badge labels from the [[NML:Badgetable\|badgetable]].
		⚫	\| Since {{ottd\|15.0}}
	\|}		\|}

Line 91:		Line 95:
	\| LSF_ALLOW_ON_WATER		\| LSF_ALLOW_ON_WATER
	\| The land/water check is disabled for this tile so it can be built on water. If you need more control over this use callback "tile_check".		\| The land/water check is disabled for this tile so it can be built on water. If you need more control over this use callback "tile_check".
⚫	\|-
⚫	\| badges
⚫	\| Array of badge labels from the [[NML:Badgetable\|badgetable]].
⚫	\| Since {{ottd\|15.0}}
	\|}		\|}

Rito12: /* Industry tile properties */ badges property

2026-01-03T21:28:05Z

Industry tile properties: badges property

← Older revision		Revision as of 21:28, 3 January 2026
Line 91:		Line 91:
	\| LSF_ALLOW_ON_WATER		\| LSF_ALLOW_ON_WATER
	\| The land/water check is disabled for this tile so it can be built on water. If you need more control over this use callback "tile_check".		\| The land/water check is disabled for this tile so it can be built on water. If you need more control over this use callback "tile_check".
			\|-
			\| badges
			\| Array of badge labels from the [[NML:Badgetable\|badgetable]].
			\| Since {{ottd\|15.0}}
	\|}		\|}

Peter1138: /* Industry tile callbacks */

2024-08-02T13:18:20Z

Industry tile callbacks

← Older revision		Revision as of 13:18, 2 August 2024
Line 168:		Line 168:
	* <code style="color:darkgreen">extra_callback_info1</code>: 32 random bits, if enabled in the <code style="color:darkgreen">special_flags</code> property.		* <code style="color:darkgreen">extra_callback_info1</code>: 32 random bits, if enabled in the <code style="color:darkgreen">special_flags</code> property.
	Returning a sound effect in the high byte will cause that sound effect to be played.		Returning a sound effect in the high byte will cause that sound effect to be played.
			Note: Every time the animation frame is changed the map tile will be refreshed, even if the selected graphics stay the same. Therefore using the animation frame as a timer should be avoided, and animation triggers should be preferred instead.
	\|-		\|-
	\| anim_control		\| anim_control
Line 175:		Line 176:
	* <code style="color:darkgreen">extra_callback_info1</code>: 32 random bits, if enabled in the <code style="color:darkgreen">special_flags</code> property.		* <code style="color:darkgreen">extra_callback_info1</code>: 32 random bits, if enabled in the <code style="color:darkgreen">special_flags</code> property.
	* <code style="color:darkgreen">getbits(extra_callback_info2, 0, 8)</code>: Reason for the callback trigger, see the [[#Animation triggers\|table]] below. Note that you need to enable the wanted triggers in the <code style="color:darkgreen">animation_triggers</code> property.		* <code style="color:darkgreen">getbits(extra_callback_info2, 0, 8)</code>: Reason for the callback trigger, see the [[#Animation triggers\|table]] below. Note that you need to enable the wanted triggers in the <code style="color:darkgreen">animation_triggers</code> property.
			Note: Every time the animation frame is changed the map tile will be refreshed, even if the selected graphics stay the same. Therefore using the animation frame as a timer should be avoided, and animation triggers should be preferred instead.
	\|-		\|-
	\| anim_speed		\| anim_speed

Heresy: Changed the appropriate tables from t to sortable.

2022-08-30T21:15:45Z

Changed the appropriate tables from t to sortable.

← Older revision		Revision as of 21:15, 30 August 2022
Line 10:		Line 10:
	==Industry tile properties==		==Industry tile properties==

	{\| class="t"		{\| class="wikitable sortable"
	! property		! property
	! value range		! value range
Line 70:		Line 70:
	===Land shape flags===		===Land shape flags===

	{\| class="t"		{\| class="wikitable sortable"
	! Flag		! Flag
	! Meaning		! Meaning
Line 97:		Line 97:
	==Industry tile variables==		==Industry tile variables==

	{\| class="t"		{\| class="wikitable sortable"
	! name		! name
	! value range		! value range
Line 149:		Line 149:
	==Industry tile callbacks==		==Industry tile callbacks==

	{\| class="t"		{\| class="wikitable sortable"
	! callback		! callback
	! return value		! return value
Line 210:		Line 210:
	===Animation triggers===		===Animation triggers===

	{\| class="t"		{\| class="wikitable sortable"
	! Trigger		! Trigger
	! Meaning		! Meaning

Andythenorth: /* Industry tile properties */ Note that accepted_cargos is increased to 16 with nml 0.5 / OpenTTD 1.9

2020-02-18T21:45:20Z

Industry tile properties: Note that accepted_cargos is increased to 16 with nml 0.5 / OpenTTD 1.9

← Older revision		Revision as of 21:45, 18 February 2020
Line 27:		Line 27:
	\| accepted_cargos		\| accepted_cargos
	\| Array with up to 3 [cargo_id, amount]-pairs.		\| Array with up to 3 [cargo_id, amount]-pairs.
			{{nml\|0.5}} {{ottdp\|1.9\|no}}Array with up to 16 [cargo_id, amount]-pairs.
	\| The cargos that are accepted by this tile. CargoID is a cargo type from your cargo translation table, amount is the acceptance of the given cargo in 1/8 units.<br /> Example: to make a tile accept both COAL and IORE you could use this: <code style="color:darkgreen"><nowiki>accepted_cargos: [[COAL, 8], [IORE, 8]];</nowiki></code><br /> Example: for a tile that doesn't any cargos at all you'd use: <code style="color:darkgreen">accepted_cargos: [];</code>		\| The cargos that are accepted by this tile. CargoID is a cargo type from your cargo translation table, amount is the acceptance of the given cargo in 1/8 units.<br /> Example: to make a tile accept both COAL and IORE you could use this: <code style="color:darkgreen"><nowiki>accepted_cargos: [[COAL, 8], [IORE, 8]];</nowiki></code><br /> Example: for a tile that doesn't any cargos at all you'd use: <code style="color:darkgreen">accepted_cargos: [];</code>
			See also <code>INDTILE_FLAG_ACCEPT_ALL</code>.
	\|-		\|-
	\| land_shape_flags		\| land_shape_flags

Andythenorth: Undo revision 3999 by Andythenorth (talk)

2020-02-18T21:44:15Z

Undo revision 3999 by Andythenorth (talk)

← Older revision		Revision as of 21:44, 18 February 2020
Line 27:		Line 27:
	\| accepted_cargos		\| accepted_cargos
	\| Array with up to 3 [cargo_id, amount]-pairs.		\| Array with up to 3 [cargo_id, amount]-pairs.
	{{nml 0.5}} {{ottdp\|1.9\|no}}Array with up to 16 [cargo_id, amount]-pairs.
	\| The cargos that are accepted by this tile. CargoID is a cargo type from your cargo translation table, amount is the acceptance of the given cargo in 1/8 units.<br /> Example: to make a tile accept both COAL and IORE you could use this: <code style="color:darkgreen"><nowiki>accepted_cargos: [[COAL, 8], [IORE, 8]];</nowiki></code><br /> Example: for a tile that doesn't any cargos at all you'd use: <code style="color:darkgreen">accepted_cargos: [];</code>		\| The cargos that are accepted by this tile. CargoID is a cargo type from your cargo translation table, amount is the acceptance of the given cargo in 1/8 units.<br /> Example: to make a tile accept both COAL and IORE you could use this: <code style="color:darkgreen"><nowiki>accepted_cargos: [[COAL, 8], [IORE, 8]];</nowiki></code><br /> Example: for a tile that doesn't any cargos at all you'd use: <code style="color:darkgreen">accepted_cargos: [];</code>
	See also <code>INDTILE_FLAG_ACCEPT_ALL</code>.
	\|-		\|-
	\| land_shape_flags		\| land_shape_flags

Andythenorth: /* Industry tile properties */

2020-02-18T21:44:04Z

Industry tile properties

← Older revision		Revision as of 21:44, 18 February 2020
Line 27:		Line 27:
	\| accepted_cargos		\| accepted_cargos
	\| Array with up to 3 [cargo_id, amount]-pairs.		\| Array with up to 3 [cargo_id, amount]-pairs.
			{{nml 0.5}} {{ottdp\|1.9\|no}}Array with up to 16 [cargo_id, amount]-pairs.
	\| The cargos that are accepted by this tile. CargoID is a cargo type from your cargo translation table, amount is the acceptance of the given cargo in 1/8 units.<br /> Example: to make a tile accept both COAL and IORE you could use this: <code style="color:darkgreen"><nowiki>accepted_cargos: [[COAL, 8], [IORE, 8]];</nowiki></code><br /> Example: for a tile that doesn't any cargos at all you'd use: <code style="color:darkgreen">accepted_cargos: [];</code>		\| The cargos that are accepted by this tile. CargoID is a cargo type from your cargo translation table, amount is the acceptance of the given cargo in 1/8 units.<br /> Example: to make a tile accept both COAL and IORE you could use this: <code style="color:darkgreen"><nowiki>accepted_cargos: [[COAL, 8], [IORE, 8]];</nowiki></code><br /> Example: for a tile that doesn't any cargos at all you'd use: <code style="color:darkgreen">accepted_cargos: [];</code>
			See also <code>INDTILE_FLAG_ACCEPT_ALL</code>.
	\|-		\|-
	\| land_shape_flags		\| land_shape_flags

Andythenorth: /* Industry tile properties */

2020-02-16T18:04:46Z

Industry tile properties

← Older revision		Revision as of 18:04, 16 February 2020
Line 60:		Line 60:
	;INDTILE_FLAG_ACCEPT_ALL {{nml\|0.5}} {{ottd\|1.9}}		;INDTILE_FLAG_ACCEPT_ALL {{nml\|0.5}} {{ottd\|1.9}}
	: In addition to the cargotypes set by accepted_cargos, the tile accepts all cargotypes which the industry accepts.		: In addition to the cargotypes set by accepted_cargos, the tile accepts all cargotypes which the industry accepts.
	* This considers industry ~~properties accept_cargo_types and~~ cargo_types and callback cargo_input.		* This considers industry property cargo_types and callback cargo_input.
	* This does not consider industry callback stop_accept_cargo.		* This does not consider industry callback stop_accept_cargo.
	* This property adds 8/8 acceptance for the matching cargotypes. You can list negative acceptances (-8/8) in property 13 to exclude specific cargos.		* This property adds 8/8 acceptance for the matching cargotypes. You can list negative acceptances (-8/8) in property 13 to exclude specific cargos.