NML:Industries - Revision history

Rito12: /* Industry variables */ fix has_badge return value

2026-01-04T14:36:18Z

Industry variables: fix has_badge return value

← Older revision		Revision as of 14:36, 4 January 2026
Line 462:		Line 462:
	\| has_badge		\| has_badge
	\| Label from the [[NML:Badgetable\|badgetable]].		\| Label from the [[NML:Badgetable\|badgetable]].
		⚫	\| {{ottd\|15.0}} Check if the industry has that specific badge attached. Returns 0 or 1.
	\| [0 <nowiki>\|</nowiki> 1]
⚫	\| {{ottd\|15.0}} Check if the industry has that specific badge attached.
	\|}		\|}

Rito12: /* Industry variables */ has_badge

2026-01-04T14:34:56Z

Industry variables: has_badge

← Older revision		Revision as of 14:34, 4 January 2026
Line 458:		Line 458:
	\| production_rate		\| production_rate
	\| cargo label from the cargotable		\| cargo label from the cargotable
	\| {{nml\|0.5}} For the given cargo label, amount of output cargo that is produced every 256 ticks. Initial value from the <code>cargo_types</code> property, but it will change accordingly when the production level changes. Returns 0..255. Example: <code>production_rate("SUGR")</code>.		\| {{nml\|0.5}} For the given cargo label, amount of output cargo that is produced every 256 ticks. Initial value from the <code>cargo_types</code> property, but it will change accordingly when the production level changes. Returns 0..255. Example: <code>production_rate("SUGR")</code>.
			\|-
			\| has_badge
			\| Label from the [[NML:Badgetable\|badgetable]].
			\| [0 <nowiki>\|</nowiki> 1]
			\| {{ottd\|15.0}} Check if the industry has that specific badge attached.
	\|}		\|}

Rito12: /* Industry properties */ badges property

2026-01-03T21:30:21Z

Industry properties: badges property

← Older revision		Revision as of 21:30, 3 January 2026
Line 143:		Line 143:
	To follow the "<Town Name> <Industry Name>" convention, the string should include a "{STRING}" at the position the town name shall be inserted. For example:		To follow the "<Town Name> <Industry Name>" convention, the string should include a "{STRING}" at the position the town name shall be inserted. For example:
	STR_HARBOR_NEARBY_NAME :{STRING} water side		STR_HARBOR_NEARBY_NAME :{STRING} water side
			\|-
			\| badges
			\| Array of badge labels from the [[NML:Badgetable\|badgetable]].
			\| Since {{ottd\|15.0}}
	\|}		\|}

Athenarises: Added example code for setting a specific bit to return a custom message

2024-10-26T08:12:54Z

Added example code for setting a specific bit to return a custom message

← Older revision		Revision as of 08:12, 26 October 2024
Line 621:		Line 621:
	\|}		\|}

	Setting bit 7 of the result disables the associated news message.<br /> Setting bit 8 replaces the news message with a custom message, read from register 0x100 bits 0 .. 15.		Setting bit 7 of the result disables the associated news message.<br /> Setting bit 8 replaces the news message with a custom message, read from register 0x100 bits 0 .. 15.<br />

			You can set specific bits in the return value by using a <code>bitmask</code>:

			switch(FEAT_INDUSTRIES, SELF, upscale_production, [
			STORE_TEMP(STR_NEWS_INDUSTRY_PRODUCTION_INCREASE_CUSTOM, 0x100)
			]) {
			return CB_RESULT_IND_PROD_DOUBLE \| bitmask(8);
			}

	===Industry creation types===		===Industry creation types===

Frosch: FIRS does things in weird ways, possibly due to templating. Give a non-FIRS example for nearby_station_name.

2023-06-03T23:40:36Z

FIRS does things in weird ways, possibly due to templating. Give a non-FIRS example for nearby_station_name.

← Older revision		Revision as of 23:40, 3 June 2023
Line 141:		Line 141:
	\| string		\| string
	\| Default name for a nearby station.		\| Default name for a nearby station.
		⚫	To follow the "<Town Name> <Industry Name>" convention, the string should include a "{STRING}" at the position the town name shall be inserted. For example:
			STR_HARBOR_NEARBY_NAME :{STRING} water side
	\|}		\|}
⚫	To follow the "<Town Name> <Industry Name>" convention the ~~nearby_station_name~~ should be:
	nearby_station_name: string(STR_STATION, string(STR_TOWN), string(STR_YOUR_INDUSTRY_NAME));

	and this should be added to your lang files:
	STR_TOWN :{STRING}
	STR_STATION :{STRING} {STRING}

	===Cargo types array===		===Cargo types array===

Pickpacket at 08:23, 2 June 2023

2023-06-02T08:23:26Z

← Older revision		Revision as of 08:23, 2 June 2023
Line 140:		Line 140:
	\| nearby_station_name		\| nearby_station_name
	\| string		\| string
	\| Default ~~additional~~ name for a nearby station		\| Default name for a nearby station.
	\|}		\|}
			To follow the "<Town Name> <Industry Name>" convention the nearby_station_name should be:
			nearby_station_name: string(STR_STATION, string(STR_TOWN), string(STR_YOUR_INDUSTRY_NAME));

			and this should be added to your lang files:
			STR_TOWN :{STRING}
			STR_STATION :{STRING} {STRING}

	===Cargo types array===		===Cargo types array===

Heresy: Changed from table to sortable.

2022-08-30T21:32:54Z

Changed from table to sortable.

← Older revision		Revision as of 21:32, 30 August 2022
Line 12:		Line 12:
	Industry properties. Default industry type numbers can be found at [[NML:Default industries\|default industries]].		Industry properties. Default industry type numbers can be found at [[NML:Default industries\|default industries]].

	{\| class="t"		{\| class="wikitable sortable"
	! property		! property
	! value range		! value range
Line 168:		Line 168:
	===Industry special flags===		===Industry special flags===

	{\| class="t"		{\| class="wikitable sortable"
	! flag		! flag
	! meaning		! meaning
Line 237:		Line 237:
	==Industry variables==		==Industry variables==

	{\| class="t"		{\| class="wikitable sortable"
	! name		! name
	! value range		! value range
Line 383:		Line 383:
	<br /> Variables that require some parameters.		<br /> Variables that require some parameters.

	{\| class="t"		{\| class="wikitable sortable"
	! name		! name
	! arguments		! arguments
Line 457:		Line 457:
	==Industry callbacks==		==Industry callbacks==

	{\| class="t"		{\| class="wikitable sortable"
	! callback		! callback
	! return value		! return value
Line 566:		Line 566:
	===Production change callback results===		===Production change callback results===

	{\| class="t"		{\| class="wikitable sortable"
	! value		! value
	! meaning		! meaning
Line 623:		Line 623:
	===Industry creation types===		===Industry creation types===

	{\| class="t"		{\| class="wikitable sortable"
	! value		! value
	! meaning		! meaning

Andythenorth: /* Industry special flags */

2022-05-28T07:35:26Z

Industry special flags

← Older revision		Revision as of 07:35, 28 May 2022
Line 230:		Line 230:
	\|-		\|-
	\| IND_FLAG_DO_NOT_CLAMP_PASSENGER_PRODUCTION		\| IND_FLAG_DO_NOT_CLAMP_PASSENGER_PRODUCTION
	\| {{nml\|0.7}} {{~~ottdp~~\|1.11}} By default OpenTTD's smooth economy clamps the production of passenger (like for oil rigs). This flag disables the clamping.		\| {{nml\|0.7}} {{ottd\|1.11}} By default OpenTTD's smooth economy clamps the production of passenger (like for oil rigs). This flag disables the clamping.
	\|}		\|}

Andythenorth: /* Industry special flags */

2022-05-28T07:35:12Z

Industry special flags

← Older revision		Revision as of 07:35, 28 May 2022
Line 230:		Line 230:
	\|-		\|-
	\| IND_FLAG_DO_NOT_CLAMP_PASSENGER_PRODUCTION		\| IND_FLAG_DO_NOT_CLAMP_PASSENGER_PRODUCTION
	\| {{nml\|0.7}} {{ottdp\|1.11}}By default OpenTTD's smooth economy clamps the production of passenger (like for oil rigs). This flag disables the clamping.		\| {{nml\|0.7}} {{ottdp\|1.11}} By default OpenTTD's smooth economy clamps the production of passenger (like for oil rigs). This flag disables the clamping.
	\|}		\|}

Andythenorth: /* Industry special flags */ add IND_FLAG_DO_NOT_CLAMP_PASSENGER_PRODUCTION

2022-05-28T07:34:58Z

Industry special flags: add IND_FLAG_DO_NOT_CLAMP_PASSENGER_PRODUCTION

← Older revision		Revision as of 07:34, 28 May 2022
Line 228:		Line 228:
	\| IND_FLAG_LONG_CARGO_TYPE_LISTS		\| IND_FLAG_LONG_CARGO_TYPE_LISTS
	\| New format for callbacks <code>callbacks cargo_subtype_display</code>, <code>cargo_input</code>, <code> cargo_output</code> to support more input/output cargos. See the callbacks for details.		\| New format for callbacks <code>callbacks cargo_subtype_display</code>, <code>cargo_input</code>, <code> cargo_output</code> to support more input/output cargos. See the callbacks for details.
			\|-
			\| IND_FLAG_DO_NOT_CLAMP_PASSENGER_PRODUCTION
			\| {{nml\|0.7}} {{ottdp\|1.11}}By default OpenTTD's smooth economy clamps the production of passenger (like for oil rigs). This flag disables the clamping.
	\|}		\|}