NMLTutorial/Parameters - Revision history

FooBar: /* Enumeration parameter */ example was missing type

2014-08-02T19:48:14Z

Enumeration parameter: example was missing type

← Older revision		Revision as of 19:48, 2 August 2014
Line 65:		Line 65:
	param 0 {		param 0 {
	economy {		economy {
			type: int;
	name: string(STR_PARAM_NAME_ECONOMIES);		name: string(STR_PARAM_NAME_ECONOMIES);
	desc: string(STR_PARAM_DESC_ECONOMIES);		desc: string(STR_PARAM_DESC_ECONOMIES);

FooBar: Add bottom navbar

2011-08-27T21:51:31Z

Add bottom navbar

← Older revision		Revision as of 21:51, 27 August 2011
Line 77:		Line 77:
	}		}
	</pre>		</pre>

			{{NMLTutorialNavbar\|Train four part refit\|Train recolour}}

Planetmaker: made clearer that the for parameters is often optional

2011-08-27T21:51:02Z

made clearer that the <num> for parameters is often optional

← Older revision		Revision as of 21:51, 27 August 2011
Line 19:		Line 19:
	</pre>		</pre>

	Where <tt>name</tt> is the name the parameter is referenced further within the grf to read this parameter. <num> is the number of this parameter. The meaning of the ~~<num>~~ parameter should should remain constant throughout versions of the same NewGRF or the NewGRF might become incompatible with previous versions of the same NewGRF (thus you'd need to change min_compatible_version if you change the meaning of the parameters at <num>.		Where <code>name</code> is the name the parameter is referenced further within the grf to read this parameter. <num> is the number of this parameter. The <num> parameter is optional and not needed when parameters are not re-ordered throughout versions. It can be used to keep the meaning of a specific NewGRF parameter while re-ordering the code. The meaning of a NewGRF parameter should should remain constant throughout versions of the same NewGRF or the NewGRF might become incompatible with previous versions of the same NewGRF (thus you'd need to change min_compatible_version if you change the meaning of the parameters at <num>.

	== Parameter types ==		== Parameter types ==

Planetmaker: /* Numeric parameter */ numeric parameter examples

2011-08-26T09:28:59Z

Numeric parameter: numeric parameter examples

← Older revision		Revision as of 09:28, 26 August 2011
Line 44:		Line 44:

	=== Numeric parameter ===		=== Numeric parameter ===

			The numeric parameter allows to directly input an (integer) number. It needs to have a minimum and maximum value given and optionally - and usually a good idea - a default value for the parameter:
			<pre>
			param 1 {
			param_depot_year {
			type: int;
			name: string(STR_PARAM_DEPOTYEAR);
			desc: string(STR_PARAM_DEPOTYEAR_DESC);
			min_value: 0;
			max_value: 5000000;
			def_value: 1975;
			}
			}
			</pre>

			=== Enumeration parameter ===

			The enumeration parameter basically is a numeric parameter where the single values have (additionally) a string attached to describe their meaning. Not all values need a string description, but it usually is a good idea to do this consistently
			<pre>
			param 0 {
			economy {
			name: string(STR_PARAM_NAME_ECONOMIES);
			desc: string(STR_PARAM_DESC_ECONOMIES);
			min_value: 0;
			max_value: 1;
			def_value: 0;
			names: {
			0: string(STR_PARAM_VALUE_ECONOMIES_TEST_ECONOMY);
			1: string(STR_PARAM_VALUE_ECONOMIES_HARD_ECONOMY);
			};
			}
			}
			</pre>

Planetmaker: parameters: boolean parameters explained.

2011-08-26T09:19:31Z

parameters: boolean parameters explained.

New page

{{NMLTutorial}}

== Introduction ==
NewGRF Parameters in NML are part of the grf block
<pre>grf {
grfid: "NML\FF";
name: string(STR_GRF_NAME);
desc: string(STR_GRF_DESC);
version: 1;
min_compatible_version: 0;
param <num> {
<name> {
name: string(STR_PARAM_NAME_ECONOMIES);
desc: string(STR_PARAM_DESC_ECONOMIES);
<specifics>
}
}
}
</pre>

Where <tt>name</tt> is the name the parameter is referenced further within the grf to read this parameter. <num> is the number of this parameter. The meaning of the <num> parameter should should remain constant throughout versions of the same NewGRF or the NewGRF might become incompatible with previous versions of the same NewGRF (thus you'd need to change min_compatible_version if you change the meaning of the parameters at <num>.

== Parameter types ==
NML knows three different types of parameters, boolean, numeric ones and enumerations:

=== Boolean parameter ===
The boolean parameter is the easiest as it requires no further definitions besides the name and description. Optionally a single parameter can contain several boolean parameter values, each using a single bit, thus saving in the number of externally visible NewGRF parameters.
<pre>
param 3 { // 3rd parameter of the NewGRF
param_bool_1 { // 1st boolean value
name: string(STR_PARAM_NAME_DEBUG);
desc: string(STR_PARAM_DESC_DEBUG);
type: bool;
bit: 1; // uses 1st bit
}
param_bool_2 { // 2nd boolean value
name: string(STR_PARAM_NAME_DEBUG);
desc: string(STR_PARAM_DESC_DEBUG);
type: bool;
bit: 2; // uses 2nd bit
}
}
</pre>

=== Numeric parameter ===