Action0/Global Settings - Revision history

Brickblock1: /* Roadtype translation table (16) */

2025-05-24T14:39:44Z

Roadtype translation table (16)

← Older revision		Revision as of 14:39, 24 May 2025
Line 171:		Line 171:
	=== Roadtype translation table (16) ===		=== Roadtype translation table (16) ===

	Provides ability to specify roadtypes via a translation table, similar to using a cargo translation table. Each roadtype label is a DWord. The default labels are ROAD ~~and ELRD~~.		Provides ability to specify roadtypes via a translation table, similar to using a cargo translation table. Each roadtype label is a DWord. The default labels are ROAD.

	Note that labels are not shared between features, so the same label can be used for multiple items. For example, the label "RAIL" can be used for a railtype, roadtype, tramtype, and cargotype simultaneously without conflict.		Note that labels are not shared between features, so the same label can be used for multiple items. For example, the label "RAIL" can be used for a railtype, roadtype, tramtype, and cargotype simultaneously without conflict.

Brickblock1: /* Tramtype translation table (17) */ RAIL is not provided by the game

2025-05-24T14:39:14Z

Tramtype translation table (17): RAIL is not provided by the game

← Older revision		Revision as of 14:39, 24 May 2025
Line 177:		Line 177:
	=== Tramtype translation table (17) ===		=== Tramtype translation table (17) ===

	Provides ability to specify tramtypes via a translation table, similar to using a cargo translation table. Each tramtype label is a DWord. The default labels ~~are RAIL and~~ ELRL.		Provides ability to specify tramtypes via a translation table, similar to using a cargo translation table. Each tramtype label is a DWord. The default labels is ELRL.

	Note that labels are not shared between features, so the same label can be used for multiple items. For example, the label "RAIL" can be used for a railtype, roadtype, tramtype, and cargotype simultaneously without conflict.		Note that labels are not shared between features, so the same label can be used for multiple items. For example, the label "RAIL" can be used for a railtype, roadtype, tramtype, and cargotype simultaneously without conflict.

Peter1138: /* Tramtype translation table (17) */

2025-02-17T16:43:28Z

Tramtype translation table (17)

← Older revision		Revision as of 16:43, 17 February 2025
Line 180:		Line 180:

	Note that labels are not shared between features, so the same label can be used for multiple items. For example, the label "RAIL" can be used for a railtype, roadtype, tramtype, and cargotype simultaneously without conflict.		Note that labels are not shared between features, so the same label can be used for multiple items. For example, the label "RAIL" can be used for a railtype, roadtype, tramtype, and cargotype simultaneously without conflict.

			=== Badge translation table (18) ===

			Required to allow badges to be assigned to other items. Each badge translation table entry is zero-terminated string corresponding to the badge's label.

			Unlike the other DWord label systems, a badge listed in a translation will automatically be created if it is not otherwise provided, and is fully usable internally.

Peter1138: /* Properties */

2025-02-17T14:59:18Z

Properties

← Older revision		Revision as of 14:59, 17 February 2025
Line 37:		Line 37:
	\|-		\|-
	\|16,17\|\|D\|\|{{ottdp\|1.10\|no}}\|\|Road-/tramtype translation table		\|16,17\|\|D\|\|{{ottdp\|1.10\|no}}\|\|Road-/tramtype translation table
			\|-
			\|18\|\|S\|\|{{ottdp\|15}}\|\|Badge translation table
	\|}		\|}

Frosch: add property 16/17 to summary table

2020-02-20T19:00:08Z

add property 16/17 to summary table

← Older revision		Revision as of 19:00, 20 February 2020
Line 35:		Line 35:
	\|-		\|-
	\|15\|\|B\|\|{{ottdp\|1.1\|no\|ottdrev=r21216}} {{grfFrom\|7}}\|\|Plural form		\|15\|\|B\|\|{{ottdp\|1.1\|no\|ottdrev=r21216}} {{grfFrom\|7}}\|\|Plural form
			\|-
			\|16,17\|\|D\|\|{{ottdp\|1.10\|no}}\|\|Road-/tramtype translation table
	\|}		\|}

Andythenorth: Document prop 16 roadtype table and prop 17 tramtype table

2020-02-20T08:38:38Z

Document prop 16 roadtype table and prop 17 tramtype table

@@ Line 136: / Line 136: @@
 Provides ability to specify railtypes via a translation table, similar to using a cargo translation table. Each railtype label is a DWord. The default labels are RAIL, ELRL, MONO and MGLV. If a table is installed, then changing engine traction type will not affect the railtype.
 === Gender/case translation table (13,14) ===
@@ Line 162: / Line 164: @@
 Defines the plural form for a language. The ID used is the Action 4 (GRF version 7 or higher) language-id, i.e. this only works with GRF version 7 or higher. Language-id 7F (any) is not allowed. More information about the different valid plural forms can be found on the [[StringCodes]] page. This property is used for [[StringCodes|StringCode]] 9A 15.

Andythenorth: Generally we seem to use 'railtype' not 'rail type'

2020-02-20T08:35:39Z

Generally we seem to use 'railtype' not 'rail type'

← Older revision		Revision as of 08:35, 20 February 2020
Line 30:		Line 30:
	\|11\|\|2*D\|\|{{ottdp\|0.7\|no\|ottdrev=r12924}}\|\|GRFID overrides for engines		\|11\|\|2*D\|\|{{ottdp\|0.7\|no\|ottdrev=r12924}}\|\|GRFID overrides for engines
	\|-		\|-
	\|12\|\|D\|\|{{ottdp\|0.7\|no\|ottdrev=r15417}}\|\|~~Rail type~~ translation table		\|12\|\|D\|\|{{ottdp\|0.7\|no\|ottdrev=r15417}}\|\|Railtype translation table
	\|-		\|-
	\|13,14\|\|V\|\|{{ottdp\|1.1\|no\|ottdrev=r21208}} {{grfFrom\|7}}\|\|Gender/case translation table		\|13,14\|\|V\|\|{{ottdp\|1.1\|no\|ottdrev=r21208}} {{grfFrom\|7}}\|\|Gender/case translation table
Line 133:		Line 133:
	The scope of this feature is quite limited and it should be used only for sets that modify data of another set, for example the DBSetXL ECS addon for DBSetXL, or the censored version of LV4.		The scope of this feature is quite limited and it should be used only for sets that modify data of another set, for example the DBSetXL ECS addon for DBSetXL, or the censored version of LV4.

	=== ~~Rail type~~ translation table (12) ===		=== Railtype translation table (12) ===

	Provides ability to specify ~~rail types~~ via a translation table, similar to using a cargo translation table. Each ~~rail type~~ label is a DWord. The default labels are RAIL, ELRL, MONO and MGLV. If a table is installed, then changing engine traction type will not affect the ~~rail type~~.		Provides ability to specify railtypes via a translation table, similar to using a cargo translation table. Each railtype label is a DWord. The default labels are RAIL, ELRL, MONO and MGLV. If a table is installed, then changing engine traction type will not affect the railtype.

	=== Gender/case translation table (13,14) ===		=== Gender/case translation table (13,14) ===

Andythenorth: Remove unused 'Example' heading

2020-02-20T08:34:56Z

Remove unused 'Example' heading

← Older revision		Revision as of 08:34, 20 February 2020
Line 162:		Line 162:

	Defines the plural form for a language. The ID used is the Action 4 (GRF version 7 or higher) language-id, i.e. this only works with GRF version 7 or higher. Language-id 7F (any) is not allowed. More information about the different valid plural forms can be found on the [[StringCodes]] page. This property is used for [[StringCodes\|StringCode]] 9A 15.		Defines the plural form for a language. The ID used is the Action 4 (GRF version 7 or higher) language-id, i.e. this only works with GRF version 7 or higher. Language-id 7F (any) is not allowed. More information about the different valid plural forms can be found on the [[StringCodes]] page. This property is used for [[StringCodes\|StringCode]] 9A 15.

	== Example ==

PikkaBird: /* GRFID overrides for engines (11) */ leaving the name of the property as-is for hysterical reasons, but "engines" -> "vehicles" in the description for clarity.

2014-02-01T10:54:47Z

GRFID overrides for engines (11): leaving the name of the property as-is for hysterical reasons, but "engines" -> "vehicles" in the description for clarity.

← Older revision		Revision as of 10:54, 1 February 2014
Line 129:		Line 129:
	=== GRFID overrides for engines (11) ===		=== GRFID overrides for engines (11) ===

	Allows you to provide a list of 'source' and 'target' GRFIDs to let ~~engines~~ in the source GRF override those in the target GRF, when dynamic engines is enabled. Each entry is 8 bytes, containing two GRFIDs. Multiple entries can be used, and different GRFs can be set to override the same 'target' GRF, but only the last instance of a 'source' GRF is active. GRFIDs that are not present will have no effect.		Allows you to provide a list of 'source' and 'target' GRFIDs to let vehicles in the source GRF override those in the target GRF, when dynamic engines is enabled. Each entry is 8 bytes, containing two GRFIDs. Multiple entries can be used, and different GRFs can be set to override the same 'target' GRF, but only the last instance of a 'source' GRF is active. GRFIDs that are not present will have no effect.

	The scope of this feature is quite limited and it should be used only for sets that modify data of another set, for example the DBSetXL ECS addon for DBSetXL, or the censored version of LV4.		The scope of this feature is quite limited and it should be used only for sets that modify data of another set, for example the DBSetXL ECS addon for DBSetXL, or the censored version of LV4.

Frosch: use new grf templates

2012-04-01T13:00:31Z

use new grf templates

← Older revision		Revision as of 13:00, 1 April 2012
Line 32:		Line 32:
	\|12\|\|D\|\|{{ottdp\|0.7\|no\|ottdrev=r15417}}\|\|Rail type translation table		\|12\|\|D\|\|{{ottdp\|0.7\|no\|ottdrev=r15417}}\|\|Rail type translation table
	\|-		\|-
	\|13,14\|\|V\|\|{{ottdp\|1.1\|no\|ottdrev=r21208}} {{~~grf~~\|7}}\|\|Gender/case translation table		\|13,14\|\|V\|\|{{ottdp\|1.1\|no\|ottdrev=r21208}} {{grfFrom\|7}}\|\|Gender/case translation table
	\|-		\|-
	\|15\|\|B\|\|{{ottdp\|1.1\|no\|ottdrev=r21216}} {{~~grf~~\|7}}\|\|Plural form		\|15\|\|B\|\|{{ottdp\|1.1\|no\|ottdrev=r21216}} {{grfFrom\|7}}\|\|Plural form
	\|}		\|}

Line 117:		Line 117:
	This property allows you to specify the snow line height for every day of the year. The only ID you can set is 0, and the value must be 12*32=384 bytes long. To simplify things for the patch, every month has 32 entries, and the impossible combinations (like 32th January or 31th April) will never be read.		This property allows you to specify the snow line height for every day of the year. The only ID you can set is 0, and the value must be 12*32=384 bytes long. To simplify things for the patch, every month has 32 entries, and the impossible combinations (like 32th January or 31th April) will never be read.

	{{~~grf~~\|7}} For GRF version 7 and below: The values should be multiple of 8 between 10h and 88h.		{{grfTill\|7}} For GRF version 7 and below: The values should be multiple of 8 between 10h and 88h.
	Values below 10h and above EFh may result in overflow and should not be used. Since the highest possible land is 78h high, giving 88h or above will effectively disable the snow line.		Values below 10h and above EFh may result in overflow and should not be used. Since the highest possible land is 78h high, giving 88h or above will effectively disable the snow line.

	{{~~grf~~\|8}} For GRF version 8 and above: The values can be any value between 0 and FFh.		{{grfFrom\|8}} For GRF version 8 and above: The values can be any value between 0 and FFh.
	FF means 'no snow'; other values are scaled to the number of possible heightlevels of the map.		FF means 'no snow'; other values are scaled to the number of possible heightlevels of the map.