Mapdev:metal - Revision history

Gajop: /* mapinfo.lua */

2020-09-16T14:08:41Z

mapinfo.lua

← Older revision		Revision as of 15:08, 16 September 2020
Line 14:		Line 14:
	== mapinfo.lua ==		== mapinfo.lua ==
	* [[Mapdev:mapinfo.lua\|mapinfo.lua]]		* [[Mapdev:mapinfo.lua\|mapinfo.lua]]
	~~<code>~~<pre>mapinfo ={		<pre>mapinfo ={
	...		...
	maxMetal = 0.02,		maxMetal = 0.02,
Line 26:		Line 26:
	},		},
	...		...
	}</pre~~></code~~>		}</pre>

	== Image File ==		== Image File ==

Enetheru: /* Image File */ added overrides

2015-04-19T04:04:46Z

Image File: added overrides

← Older revision		Revision as of 05:04, 19 April 2015
Line 32:		Line 32:
	{\| class="wikitable" width="100%"		{\| class="wikitable" width="100%"
	! width="15%" \| File Location		! width="15%" \| File Location
	\| The metal map is an intermediary file compiled into the SMF file using [[MapConv]] or [[MapConvNG]].		\| The metal map is an intermediary file compiled into the SMF file using [[MapConv]] or [[MapConvNG]], it can also be specified in the mapinfo.lua.
	\|-		\|-
	! File Format		! File Format

Enetheru: /* mapinfo.lua */ added lua overrides

2015-04-19T04:01:51Z

mapinfo.lua: added lua overrides

← Older revision		Revision as of 05:01, 19 April 2015
Line 20:		Line 20:
	autoShowMetal = true,		autoShowMetal = true,
	...		...
			smf = {
			....
			metalmapTex = "",
			....
			},
			...
	}</pre></code>		}</pre></code>

Enetheru: /* Image File */ how this has been wrong for so long bothers me.

2015-04-06T06:13:54Z

Image File: how this has been wrong for so long bothers me.

← Older revision		Revision as of 07:13, 6 April 2015
Line 35:		Line 35:
	\|-		\|-
	! Channels		! Channels
	\| ~~RGB~~		\| Greyscale
	\|-		\|-
	! Resolution		! Resolution
Line 41:		Line 41:
	{\| class="wikitable" style="text-align: center;"		{\| class="wikitable" style="text-align: center;"
	!Spring Map Size<sup>*</sup>		!Spring Map Size<sup>*</sup>
	!pixels = Spring Map Size * ~~64 + 1~~		!pixels = Spring Map Size * 32
	\|-		\|-
	\| 2		\| 2
	\| ~~129~~		\| 64
	\|-		\|-
	\| 4		\| 4
	\| ~~257~~		\| 128
	\|-		\|-
	\| 6		\| 6
	\| ~~385~~		\| 256
	\|-		\|-
	\| ...		\| ...
Line 56:		Line 56:
	\|-		\|-
	\| 32		\| 32
	\| ~~2049~~		\| 1024
	\|-		\|-
	\| style="text-align: left;font-style:italic" colspan=2 \| * must be multiples of 2		\| style="text-align: left;font-style:italic" colspan=2 \| * must be multiples of 2

Flozi: /* Metal */ use Caution

2014-02-16T13:26:13Z

Metal: use Caution

← Older revision		Revision as of 14:26, 16 February 2014
Line 2:		Line 2:
	Metal maps are used for the built in resourcing scheme (Metal/Energy), they define metal areas on a battlefield based upon the values in the red channel of the metal map.		Metal maps are used for the built in resourcing scheme (Metal/Energy), they define metal areas on a battlefield based upon the values in the red channel of the metal map.

	{{~~infobox\|title=~~Caution\|~~icon=icon-caution.png\|icon-size=48\|color=rgba(255,0,0,0.1)~~		{{Caution\|There are several games for Spring which use their own resourcing system. If you are creating a map for one of those games a metal map may not be necessary, however it is always nice if you can make your maps as compatible with other games as possible, but this is a choice left entirely up to you.}}
	~~\|body=~~There are several games for Spring which use their own resourcing system. If you are creating a map for one of those games a metal map may not be necessary, however it is always nice if you can make your maps as compatible with other games as possible, but this is a choice left entirely up to you.}}
	<center>		<center>
	{\| class="wikitable"		{\| class="wikitable"

Flozi: 1cat

2013-03-20T20:14:31Z

1cat

← Older revision		Revision as of 21:14, 20 March 2013
Line 67:		Line 67:
	If you do want perfect metal patches, use a 6x6 pixel pencil in your image editor with a red value of 255. This combined with setting the "MaxMetal" tag in the definitions to 1, will result in a perfect 2.0 metal generation per patch (using Balanaced Annihilation values). The game use isn't the point however. The fact is that if you can predict how much each spot will output (typically), using the "MaxMetal" parameter, you can easily scale the values up and down. As an example of another extreme, Evolution RTS dictates that all metal patches will output 0.5 metal regardless of the map settings. So whether you need to put a lot of thought into your metal map values depends entirely upon the game for which you are creating the map.		If you do want perfect metal patches, use a 6x6 pixel pencil in your image editor with a red value of 255. This combined with setting the "MaxMetal" tag in the definitions to 1, will result in a perfect 2.0 metal generation per patch (using Balanaced Annihilation values). The game use isn't the point however. The fact is that if you can predict how much each spot will output (typically), using the "MaxMetal" parameter, you can easily scale the values up and down. As an example of another extreme, Evolution RTS dictates that all metal patches will output 0.5 metal regardless of the map settings. So whether you need to put a lot of thought into your metal map values depends entirely upon the game for which you are creating the map.

	[[Category:~~Mapdev]]~~		[[Category:Map Dev]]
	~~[[Category:Development~~]]

Enetheru: /* Image File */ used image template styling

2013-01-06T13:47:03Z

Image File: used image template styling

← Older revision		Revision as of 14:47, 6 January 2013
Line 24:		Line 24:

	== Image File ==		== Image File ==
	* The metal map is an intermediary file compiled into the SMF file using [[MapConv]] or [[MapConvNG]].
	* 8 bpp RGB
	* The red value of pixel corresponds to the metal value.		* The red value of pixel corresponds to the metal value.
	<center>		{\| class="wikitable" width="100%"
			! width="15%" \| File Location
			\| The metal map is an intermediary file compiled into the SMF file using [[MapConv]] or [[MapConvNG]].
			\|-
			! File Format
			\| Any that the Mapconv programs support
			\|-
			! Colour Depth
			\| 8bpp
			\|-
			! Channels
			\| RGB
			\|-
			! Resolution
			\| <center>
	{\| class="wikitable" style="text-align: center;"		{\| class="wikitable" style="text-align: center;"
	!Spring Map Size<sup>*</sup>		!Spring Map Size<sup>*</sup>
Line 49:		Line 61:
	\| style="text-align: left;font-style:italic" colspan=2 \| * must be multiples of 2		\| style="text-align: left;font-style:italic" colspan=2 \| * must be multiples of 2
	\|}</center>		\|}</center>
			\|}

	= Additional Information =		= Additional Information =

Enetheru: /* Image File */ removed fixme.

2012-12-28T06:04:06Z

Image File: removed fixme.

← Older revision		Revision as of 07:04, 28 December 2012
Line 26:		Line 26:
	* The metal map is an intermediary file compiled into the SMF file using [[MapConv]] or [[MapConvNG]].		* The metal map is an intermediary file compiled into the SMF file using [[MapConv]] or [[MapConvNG]].
	* 8 bpp RGB		* 8 bpp RGB
	* The red value of pixel corresponds to the metal value~~.({{FIXME}}would like a link to engine code that shows this)~~.		* The red value of pixel corresponds to the metal value.
	<center>		<center>
	{\| class="wikitable" style="text-align: center;"		{\| class="wikitable" style="text-align: center;"

Enetheru: cleaned some more.

2012-12-28T06:02:33Z

cleaned some more.

← Older revision		Revision as of 07:02, 28 December 2012
Line 26:		Line 26:
	* The metal map is an intermediary file compiled into the SMF file using [[MapConv]] or [[MapConvNG]].		* The metal map is an intermediary file compiled into the SMF file using [[MapConv]] or [[MapConvNG]].
	* 8 bpp RGB		* 8 bpp RGB
			* The red value of pixel corresponds to the metal value.({{FIXME}}would like a link to engine code that shows this).
			<center>
	{\| class="wikitable" style="text-align: center;"		{\| class="wikitable" style="text-align: center;"
	!Spring Map Size<sup>*</sup>		!Spring Map Size<sup>*</sup>
Line 46:		Line 48:
	\|-		\|-
	\| style="text-align: left;font-style:italic" colspan=2 \| * must be multiples of 2		\| style="text-align: left;font-style:italic" colspan=2 \| * must be multiples of 2
	\|}		\|}</center>

	* The red value of pixel corresponds to the metal value for that pixel.(would like to have a more detailed proof, perhaps pointing to some source code, or something.. unless its entirely defined by the game in which case blah).

	= Additional Information =		= Additional Information =
	== Patch Technique ==		== Patch Technique ==
	If you do want perfect metal patches, use a 6x6 pixel pencil in your image editor with a red value of 255. This combined with setting the "MaxMetal" tag in the definitions to 1, will result in a perfect 2.0 metal generation per patch (using Balanaced Annihilation values). The game use isn't the point however. The fact is that if you can predict how much each spot will output (typically), using the "MaxMetal" parameter, you can easily scale the values up and down. As an example of another extreme, Evolution RTS dictates that all metal patches will output 0.5 metal regardless of the map settings. So whether you need to put a lot of thought into your metal map values depends entirely upon the game for which you are creating the map.		If you do want perfect metal patches, use a 6x6 pixel pencil in your image editor with a red value of 255. This combined with setting the "MaxMetal" tag in the definitions to 1, will result in a perfect 2.0 metal generation per patch (using Balanaced Annihilation values). The game use isn't the point however. The fact is that if you can predict how much each spot will output (typically), using the "MaxMetal" parameter, you can easily scale the values up and down. As an example of another extreme, Evolution RTS dictates that all metal patches will output 0.5 metal regardless of the map settings. So whether you need to put a lot of thought into your metal map values depends entirely upon the game for which you are creating the map.

	[[Category:Mapdev]]		[[Category:Mapdev]]
	[[Category:Development]]		[[Category:Development]]

Enetheru: /* mapinfo.lua */ cleaned slightly.

2012-12-28T06:00:32Z

mapinfo.lua: cleaned slightly.

← Older revision		Revision as of 07:00, 28 December 2012
Line 14:		Line 14:
	= Specification =		= Specification =
	== mapinfo.lua ==		== mapinfo.lua ==
	~~relevant sections of the~~ [[~~Map_Making~~:mapinfo.lua\|mapinfo.lua]] ~~file are:~~		* [[Mapdev:mapinfo.lua\|mapinfo.lua]]
	<code><pre>mapinfo ={		<code><pre>mapinfo ={
	...		...