NML:Replace TTD sprites - Revision history

Supercheese: Clarify meaning by better comma placement

2013-02-28T06:35:56Z

Clarify meaning by better comma placement

← Older revision		Revision as of 06:35, 28 February 2013
Line 17:		Line 17:
	<b>Note</b>: this only applies for the sprites in the five base grfs (thus up to sprite #4984 when looking at sprite numbers in OpenTTD), but not to the sprites defined in a base set's extra grf - they require the <code style="color:darkgreen">[[NML:Replace new sprites\|replacenew]]</code> command.		<b>Note</b>: this only applies for the sprites in the five base grfs (thus up to sprite #4984 when looking at sprite numbers in OpenTTD), but not to the sprites defined in a base set's extra grf - they require the <code style="color:darkgreen">[[NML:Replace new sprites\|replacenew]]</code> command.

	A <code style="color:darkgreen"><block_name></code> is optional but required, if you want to define [[NML:Alternative sprites\|alternative sprites]] for the sprite block so that it can be referenced there.		A <code style="color:darkgreen"><block_name></code> is optional, but required if you want to define [[NML:Alternative sprites\|alternative sprites]] for the sprite block so that it can be referenced there.

	The first parameter <code style="color:darkgreen"><sprite-id></code> indicates the sprite number of the first sprite to replace. Sprite numbers are equal to the sprite numbers in the base graphics file. The [http://mz.openttdcoop.org/opengfx/authors/script.php?feature=spritesbyfile&q= OpenGFX author overview] can be used as a reference to look up these sprite numbers.		The first parameter <code style="color:darkgreen"><sprite-id></code> indicates the sprite number of the first sprite to replace. Sprite numbers are equal to the sprite numbers in the base graphics file. The [http://mz.openttdcoop.org/opengfx/authors/script.php?feature=spritesbyfile&q= OpenGFX author overview] can be used as a reference to look up these sprite numbers.

Planetmaker: make clearer when replace and replacenew need be used

2013-02-20T01:21:16Z

make clearer when replace and replacenew need be used

← Older revision		Revision as of 01:21, 20 February 2013
Line 13:		Line 13:
	}		}

	respectively		respectively.

			<b>Note</b>: this only applies for the sprites in the five base grfs (thus up to sprite #4984 when looking at sprite numbers in OpenTTD), but not to the sprites defined in a base set's extra grf - they require the <code style="color:darkgreen">[[NML:Replace new sprites\|replacenew]]</code> command.

	A <code style="color:darkgreen"><block_name></code> is optional but required, if you want to define [[NML:Alternative sprites\|alternative sprites]] for the sprite block so that it can be referenced there.		A <code style="color:darkgreen"><block_name></code> is optional but required, if you want to define [[NML:Alternative sprites\|alternative sprites]] for the sprite block so that it can be referenced there.

Planetmaker: Add link to page with terrain sprite numbers (tile list)

2012-03-06T04:19:54Z

Add link to page with terrain sprite numbers (tile list)

← Older revision		Revision as of 04:19, 6 March 2012
Line 1:		Line 1:
	{{NMLNavBlocksyntax}}		{{NMLNavBlocksyntax}}

	Using a <code style="color:darkgreen">replace</code> block, it is possible to replace TTD's built-in sprites or for base grfs to define sprites via the <code style="color:darkgreen">base_graphics</code> block. The syntax is as follows:		Using a <code style="color:darkgreen">replace</code> block, it is possible to replace TTD's built-in sprites or for base grfs to define sprites via the <code style="color:darkgreen">base_graphics</code> block. Unlike many other features, this is the only way to change the terrain (see [[NML:List_of_tiles\|the tile list]] for a list of terrain sprites). The syntax is as follows:

	replace [<block_name>](<sprite-id>[, <image-file>]) {		replace [<block_name>](<sprite-id>[, <image-file>]) {

Hirundo: Mark image-file as optional

2012-03-03T21:24:39Z

Mark image-file as optional

← Older revision		Revision as of 21:24, 3 March 2012
Line 3:		Line 3:
	Using a <code style="color:darkgreen">replace</code> block, it is possible to replace TTD's built-in sprites or for base grfs to define sprites via the <code style="color:darkgreen">base_graphics</code> block. The syntax is as follows:		Using a <code style="color:darkgreen">replace</code> block, it is possible to replace TTD's built-in sprites or for base grfs to define sprites via the <code style="color:darkgreen">base_graphics</code> block. The syntax is as follows:

	replace [<block_name>](<sprite-id>, <image-file>) {		replace [<block_name>](<sprite-id>[, <image-file>]) {
	[[#real sprites\|list of realsprites]]		[[#real sprites\|list of realsprites]]
	}		}
Line 9:		Line 9:
	and		and

	base_graphics [<block_name>](<sprite-id>, <image-file>) {		base_graphics [<block_name>](<sprite-id>[, <image-file>]) {
	[[#real sprites\|list of realsprites]]		[[#real sprites\|list of realsprites]]
	}		}
Line 17:		Line 17:
	A <code style="color:darkgreen"><block_name></code> is optional but required, if you want to define [[NML:Alternative sprites\|alternative sprites]] for the sprite block so that it can be referenced there.		A <code style="color:darkgreen"><block_name></code> is optional but required, if you want to define [[NML:Alternative sprites\|alternative sprites]] for the sprite block so that it can be referenced there.

	The first parameter <code style="color:darkgreen"><sprite-id></code> indicates the sprite number of the first sprite to replace. Sprite numbers are equal to the sprite numbers in the base graphics file. The [http://mz.openttdcoop.org/opengfx/authors/script.php?feature=spritesbyfile&q= OpenGFX author overview] can be used as a reference to look up these sprite numbers. The second parameter <code style="color:darkgreen"><image-file></code> specifies the image file that contains the new sprites. A series of real sprites has to be specified between the curly braces (<code style="color:darkgreen">{</code> and <code style="color:darkgreen">}</code>). The first sprite in this list replaces the sprite with id <code style="color:darkgreen">sprite-id</code>, the second replaces <code style="color:darkgreen">sprite-id + 1</code> and so on. Sprite templates can be used as well. For example:		The first parameter <code style="color:darkgreen"><sprite-id></code> indicates the sprite number of the first sprite to replace. Sprite numbers are equal to the sprite numbers in the base graphics file. The [http://mz.openttdcoop.org/opengfx/authors/script.php?feature=spritesbyfile&q= OpenGFX author overview] can be used as a reference to look up these sprite numbers.

			The second parameter <code style="color:darkgreen"><image-file></code> (optional) specifies the default image file to use for the new sprites.

			A series of real (or recolour) sprites has to be specified between the curly braces (<code style="color:darkgreen">{</code> and <code style="color:darkgreen">}</code>). The first sprite in this list replaces the sprite with id <code style="color:darkgreen">sprite-id</code>, the second replaces <code style="color:darkgreen">sprite-id + 1</code> and so on. Sprite templates can be used as well. For example:

	<pre style="color:blue">		<pre style="color:blue">

Planetmaker: Document the use of a block name for the replace and base_graphics block

2012-03-02T08:24:33Z

Document the use of a block name for the replace and base_graphics block

← Older revision		Revision as of 08:24, 2 March 2012
Line 3:		Line 3:
	Using a <code style="color:darkgreen">replace</code> block, it is possible to replace TTD's built-in sprites or for base grfs to define sprites via the <code style="color:darkgreen">base_graphics</code> block. The syntax is as follows:		Using a <code style="color:darkgreen">replace</code> block, it is possible to replace TTD's built-in sprites or for base grfs to define sprites via the <code style="color:darkgreen">base_graphics</code> block. The syntax is as follows:

	replace(<sprite-id>, <image-file>) {		replace [<block_name>](<sprite-id>, <image-file>) {
	[[#real sprites\|list of realsprites]]		[[#real sprites\|list of realsprites]]
	}		}
Line 9:		Line 9:
	and		and

	base_graphics(<sprite-id>, <image-file>) {		base_graphics [<block_name>](<sprite-id>, <image-file>) {
	[[#real sprites\|list of realsprites]]		[[#real sprites\|list of realsprites]]
	}		}

	respectively		respectively

			A <code style="color:darkgreen"><block_name></code> is optional but required, if you want to define [[NML:Alternative sprites\|alternative sprites]] for the sprite block so that it can be referenced there.

	The first parameter <code style="color:darkgreen"><sprite-id></code> indicates the sprite number of the first sprite to replace. Sprite numbers are equal to the sprite numbers in the base graphics file. The [http://mz.openttdcoop.org/opengfx/authors/script.php?feature=spritesbyfile&q= OpenGFX author overview] can be used as a reference to look up these sprite numbers. The second parameter <code style="color:darkgreen"><image-file></code> specifies the image file that contains the new sprites. A series of real sprites has to be specified between the curly braces (<code style="color:darkgreen">{</code> and <code style="color:darkgreen">}</code>). The first sprite in this list replaces the sprite with id <code style="color:darkgreen">sprite-id</code>, the second replaces <code style="color:darkgreen">sprite-id + 1</code> and so on. Sprite templates can be used as well. For example:		The first parameter <code style="color:darkgreen"><sprite-id></code> indicates the sprite number of the first sprite to replace. Sprite numbers are equal to the sprite numbers in the base graphics file. The [http://mz.openttdcoop.org/opengfx/authors/script.php?feature=spritesbyfile&q= OpenGFX author overview] can be used as a reference to look up these sprite numbers. The second parameter <code style="color:darkgreen"><image-file></code> specifies the image file that contains the new sprites. A series of real sprites has to be specified between the curly braces (<code style="color:darkgreen">{</code> and <code style="color:darkgreen">}</code>). The first sprite in this list replaces the sprite with id <code style="color:darkgreen">sprite-id</code>, the second replaces <code style="color:darkgreen">sprite-id + 1</code> and so on. Sprite templates can be used as well. For example:
Line 19:		Line 21:
	<pre style="color:blue">		<pre style="color:blue">
	// Rail overlays for crossings		// Rail overlays for crossings
	replace (1005, "src/gfx/rails_overlays.png") {		replace rail_overlays(1005, "src/gfx/rails_overlays.png") {
	[ 20,198, 40,21, -20, 5]		[ 20,198, 40,21, -20, 5]
	[ 71,198, 40,21, -20, 5]		[ 71,198, 40,21, -20, 5]

Ammler: no need to preselect the biggest file and making loading of the page that long

2011-10-07T07:33:34Z

no need to preselect the biggest file and making loading of the page that long

← Older revision		Revision as of 07:33, 7 October 2011
Line 15:		Line 15:
	respectively		respectively

	The first parameter <code style="color:darkgreen"><sprite-id></code> indicates the sprite number of the first sprite to replace. Sprite numbers are equal to the sprite numbers in the base graphics file. The [http://mz.openttdcoop.org/opengfx/authors/script.php?feature=spritesbyfile&q=~~ogfx1_base~~ OpenGFX author overview] can be used as a reference to look up these sprite numbers. The second parameter <code style="color:darkgreen"><image-file></code> specifies the image file that contains the new sprites. A series of real sprites has to be specified between the curly braces (<code style="color:darkgreen">{</code> and <code style="color:darkgreen">}</code>). The first sprite in this list replaces the sprite with id <code style="color:darkgreen">sprite-id</code>, the second replaces <code style="color:darkgreen">sprite-id + 1</code> and so on. Sprite templates can be used as well. For example:		The first parameter <code style="color:darkgreen"><sprite-id></code> indicates the sprite number of the first sprite to replace. Sprite numbers are equal to the sprite numbers in the base graphics file. The [http://mz.openttdcoop.org/opengfx/authors/script.php?feature=spritesbyfile&q= OpenGFX author overview] can be used as a reference to look up these sprite numbers. The second parameter <code style="color:darkgreen"><image-file></code> specifies the image file that contains the new sprites. A series of real sprites has to be specified between the curly braces (<code style="color:darkgreen">{</code> and <code style="color:darkgreen">}</code>). The first sprite in this list replaces the sprite with id <code style="color:darkgreen">sprite-id</code>, the second replaces <code style="color:darkgreen">sprite-id + 1</code> and so on. Sprite templates can be used as well. For example:

	<pre style="color:blue">		<pre style="color:blue">

Planetmaker: Add base_graphics block, too as it follows the exact same syntax

2011-10-06T22:47:45Z

Add base_graphics block, too as it follows the exact same syntax

← Older revision		Revision as of 22:47, 6 October 2011
Line 1:		Line 1:
	{{NMLNavBlocksyntax}}		{{NMLNavBlocksyntax}}

	Using a <code style="color:darkgreen">replace</code> block, it is possible to replace TTD's built-in sprites. The syntax is as follows:		Using a <code style="color:darkgreen">replace</code> block, it is possible to replace TTD's built-in sprites or for base grfs to define sprites via the <code style="color:darkgreen">base_graphics</code> block. The syntax is as follows:

	replace(<sprite-id>, <image-file>) {		replace(<sprite-id>, <image-file>) {
	[[#real sprites\|list of realsprites]]		[[#real sprites\|list of realsprites]]
	}		}

			and

			base_graphics(<sprite-id>, <image-file>) {
			[[#real sprites\|list of realsprites]]
			}

			respectively

	The first parameter <code style="color:darkgreen"><sprite-id></code> indicates the sprite number of the first sprite to replace. Sprite numbers are equal to the sprite numbers in the base graphics file. The [http://mz.openttdcoop.org/opengfx/authors/script.php?feature=spritesbyfile&q=ogfx1_base OpenGFX author overview] can be used as a reference to look up these sprite numbers. The second parameter <code style="color:darkgreen"><image-file></code> specifies the image file that contains the new sprites. A series of real sprites has to be specified between the curly braces (<code style="color:darkgreen">{</code> and <code style="color:darkgreen">}</code>). The first sprite in this list replaces the sprite with id <code style="color:darkgreen">sprite-id</code>, the second replaces <code style="color:darkgreen">sprite-id + 1</code> and so on. Sprite templates can be used as well. For example:		The first parameter <code style="color:darkgreen"><sprite-id></code> indicates the sprite number of the first sprite to replace. Sprite numbers are equal to the sprite numbers in the base graphics file. The [http://mz.openttdcoop.org/opengfx/authors/script.php?feature=spritesbyfile&q=ogfx1_base OpenGFX author overview] can be used as a reference to look up these sprite numbers. The second parameter <code style="color:darkgreen"><image-file></code> specifies the image file that contains the new sprites. A series of real sprites has to be specified between the curly braces (<code style="color:darkgreen">{</code> and <code style="color:darkgreen">}</code>). The first sprite in this list replaces the sprite with id <code style="color:darkgreen">sprite-id</code>, the second replaces <code style="color:darkgreen">sprite-id + 1</code> and so on. Sprite templates can be used as well. For example:

FooBar: add nav template

2011-08-21T16:36:55Z

add nav template

← Older revision		Revision as of 16:36, 21 August 2011
Line 1:		Line 1:
			{{NMLNavBlocksyntax}}

	Using a <code style="color:darkgreen">replace</code> block, it is possible to replace TTD's built-in sprites. The syntax is as follows:		Using a <code style="color:darkgreen">replace</code> block, it is possible to replace TTD's built-in sprites. The syntax is as follows:

FooBar: content of nml r1625

2011-08-21T11:40:23Z

content of nml r1625

New page

Using a <code style="color:darkgreen">replace</code> block, it is possible to replace TTD's built-in sprites. The syntax is as follows:

replace(<sprite-id>, <image-file>) {
[[#real sprites|list of realsprites]]
}

The first parameter <code style="color:darkgreen"><sprite-id></code> indicates the sprite number of the first sprite to replace. Sprite numbers are equal to the sprite numbers in the base graphics file. The [http://mz.openttdcoop.org/opengfx/authors/script.php?feature=spritesbyfile&q=ogfx1_base OpenGFX author overview] can be used as a reference to look up these sprite numbers. The second parameter <code style="color:darkgreen"><image-file></code> specifies the image file that contains the new sprites. A series of real sprites has to be specified between the curly braces (<code style="color:darkgreen">{</code> and <code style="color:darkgreen">}</code>). The first sprite in this list replaces the sprite with id <code style="color:darkgreen">sprite-id</code>, the second replaces <code style="color:darkgreen">sprite-id + 1</code> and so on. Sprite templates can be used as well. For example:

<pre style="color:blue">
// Rail overlays for crossings
replace (1005, "src/gfx/rails_overlays.png") {
[ 20,198, 40,21, -20, 5]
[ 71,198, 40,21, -20, 5]
[117,198, 40, 7, -20, 5]
[165,198, 40, 7, -20, 21]
[216,198, 12,19, 10, 5]
[248,198, 12,19, -24, 11]
}
</pre>