Creating a Map: Difference between revisions

From Conflict of Heroes Wiki
Jump to navigation Jump to search
 
(20 intermediate revisions by the same user not shown)
Line 3: Line 3:
== Map Creation ==
== Map Creation ==


The easiest way to create a COH map is to start with an "Input Map." An Input Map is a 2048 x 2048 JPEG in which colors correspond to different types of terrain, terrain properties, and elevations.  
There are two ways to create a COH map: in-editor maps, and input maps.  


Here's a reduced-size input map called "Black Sea Coast" which I developed based on some Google Earth terrain:
====In-Editor Maps====


[[File:mapguide1.jpg|center|border|upright]]
In-editor maps are created entirely within the game editor; just start the COH Editor program, and begin designing your map.  You can pick from the pre-selected map sizes to size your map (Small, Medium, Large, Wide, and Huge).  To design maps in-editor, you can skip to [[#Manual Placement of Map Tiles|Manual Placement of Map Tiles]] below.


The shades of brown show elevation. Purples are houses / stone houses. Greens are forests. Reds are roads. Blue is water. White is clear. Note that you can have forests with roads running through them on heights by ensuring that a given hex contains all three colors.
====Input Maps====


Input Maps can be created in any reasonably sophisticated paint program. Creating an input map with reference to the underlying hex-grid allows the developer much more refined control over the map elements, and it's easiest to do this in a paint program that supports multiple layers, such as Photoshop or the free program GIMP.
An Input Map is a 2048 x 2048 JPEG in which colors correspond to different types of terrain, terrain properties, and elevations.  


== Parsing the Input Map ==
Here's a reduced-size input map called "Black Sea Coast" which I developed based on some Google Earth terrain:


After the user creates an Input Map he can parse that map in the game editor by clicking on the "Parse Input Map" and choosing the appropriate map file. Only maps that are in JPEG format that end in "_input" are allowed as input maps.
[[File:mapguide1.jpg|center|border|thumb|750px|A map hand-drawn in Photoshop, using a hex wireframe layer placed over a satellite photo]]


[[Image:mapguide2.jpg|center|border|upright]]
The shades of brown show elevation. Purples are houses / stone houses. Greens are forests. Reds are roads. Blue is water. White is clear. Note that you can have forests with roads running through them on heights by ensuring that a given hex contains all three colors.
 
It can take a minute or two to parse the Input Map. When it's done it turns the empty canvas into an *almost* fully-stocked map:
 
[[Image:mapguide3.jpg|center|border|upright]]
 
A few of the fussier elements can't be added through the input map mechanism.  You'll have to go through and add things like walls, bunkers, barbed wire, and so forth in the map editor after parsing an input map.  


The map creation process goes fairly quickly once you get all the mechanics sorted out. I did the map above in about 1.5 hours.
Input Maps can be created in any reasonably sophisticated paint program. Creating an input map with reference to the underlying hex-grid allows the developer much more refined control over the map elements, and it's easiest to do this in a paint program that supports multiple layers, such as Photoshop or the free program GIMP. To do this, take the input map hex template we provide, and input it into a layer in your paint program.


== Input Map Template ==
== Input Map Hex Template ==


Included in the /manuals sub-folder of your installation directory is a full-size template for creating input maps.
Included in the /manuals sub-folder of your installation directory is a full-size template for creating input maps.
Line 37: Line 31:
You should use a paint program that has layers, such as Photoshop or GIMP (freeware) to design input maps.
You should use a paint program that has layers, such as Photoshop or GIMP (freeware) to design input maps.


[[Image:hexmapframe.jpg|center|border|500px]]
[[Image:hexmapframe.jpg|center|border|thumb|500px]]


You will find a full-size copy of the above template in the /manuals sub-folder of your
You will find a full-size copy of the above template in the /manuals sub-folder of your
installation directory.
installation directory.
You'll need to make the hex template transparent, except for the hex grid, in whatever program you're using.


== Map Palette Guide ==
== Map Palette Guide ==


Here is the COH Palette Guide for creating input maps.
Here is the COH Palette Guide for creating input maps:


[[Image:mapcolorlegend.jpg|center|border|500px]]
[[Image:mapcolorlegend.jpg|center|thumb|500px]]


== Terrain Interactions ==
== Terrain Interactions ==
Line 52: Line 48:
Some types of terrain are obviously exclusive with other types of terrain, however some terrain features can co-exist in a hex with other features. Here's a zoomed-in shot showing how to add more than one type of terrain to a hex when designing an input map. This shows a road, some woods, and a height all in the same hex.  
Some types of terrain are obviously exclusive with other types of terrain, however some terrain features can co-exist in a hex with other features. Here's a zoomed-in shot showing how to add more than one type of terrain to a hex when designing an input map. This shows a road, some woods, and a height all in the same hex.  


[[Image:mapguide6.jpg|center|border|500px]]
[[Image:mapguide6.jpg|center|border|thumb|300px]]
 
== Avoid Anti-Aliasing ==
 
With any tools you use to make input maps, it's important to avoid anti-aliasing or smoothing the pixels in your image. As much as possible, you want to make sure that every pixel in your image is exactly one of the colors in the COH Palette Guide. The importer will do its best to figure out what you meant by pixels that aren't exactly the right color (it'll match them to the closest colors or ignore them). However, it's possible to introduce all sorts of stray features if you use too many pixel-smoothing tools.
 
[[Image:mapguide10.jpg|center|border|thumb|500px|]]
 
== Parsing the Input Map ==
 
After the user creates an Input Map he can parse that map in the game editor by clicking on the "Parse Input Map" and choosing the appropriate map file. Only maps that are in JPEG format that end in "_input" are allowed as input maps.
 
[[Image:mapguide2.jpg|center|border|thumb|750px]]
 
It can take a minute or two to parse the Input Map. When it's done it turns the empty canvas into an *almost* fully-stocked map.  A few of the fussier elements can't be added through the input map mechanism.  You'll have to go through and add things like walls, bunkers, barbed wire, and so forth in the map editor after parsing an input map.
 
The map creation process goes fairly quickly once you get all the mechanics sorted out. I did the map above in about 1.5 hours.
 
== Building Terrain in the Map Editor ==
 
Any and all terrain, and any map tile, can be assigned using the map editor. 
 
For example, heights can be added using the terrain sculpting controls:
 
*Enter "sculpting mode" using the Terrain --> Sculpting Mode button.
*Use the left mouse button to raise terrain in an individual hex, and use the right mouse button to lower terrain in an individual hex.
*You can also use keyboard commands instead: the [>] key raises terrain for an individual hex, and the [<] key lowers terrain for an individual hex.
*When you're done raising and lowering terrain, the Editor --> Rebuild Height button smooths the terrain heights.


== Manual Placement of Map Tiles ==
For example, the following map was created using the input process, but this map could also be created entirely within the editor:


Some map tile types cannot be placed using the input map and must be placed by hand.  
[[Image:mapguide3.jpg|center|border|thumb|750px]]


[[Image:mapguide7.jpg|center|border|upright]]
== Adding Obstacles, Units, and Other Map Features ==
 
You can add other terrain features as desired--bunkers, for example:
 
[[Image:mapguide7.jpg|center|border|thumb|750px|]]  


Place bunkers and other directional types by clicking on the map and dragging.  
Place bunkers and other directional types by clicking on the map and dragging.  


[[Image:mapguide7.jpg|center|border|upright]]
[[Image:mapguide8.jpg|center|border|thumb|750px|]]


Tiles that don't have directional information can be placed simply by clicking on the map.  
Tiles that don't have directional information can be placed simply by clicking on the map.  


[[Image:mapguide7.jpg|center|border|upright]]
[[Image:mapguide9.jpg|center|border|thumb|650px|]]


== Avoid Anti-Aliasing ==
Again, if parsing an input map, some map tiles can be placed during the input process, but some cannot, and must be placed by hand.


With any tools you use to make input maps, it's important to avoid anti-aliasing or smoothing the pixels in your image. As much as possible, you want to make sure that every pixel in your image is exactly one of the colors in the COH Palette Guide. The importer will do its best to figure out what you meant by pixels that aren't exactly the right color (it'll match them to the closest colors or ignore them). However, it's possible to introduce all sorts of stray features if you use too many pixel-smoothing tools.
== Building the LOS File ==


[[Image:mapguide10.jpg|center|border|upright]]
When you're done with your map, you'll have to build your LOS file before continuing on to scenario design: this can be found on the Editor menu drop-down.  This must be done before a map can be used for a scenario.  Building the LOS file may take some time for the editor to complete; you'll see a progress screen while the LOS file is building.  If you interrupt this process, you'll need to re-build the entire LOS file.


== Building the LOS File ==
'''Important''': the LOS file '''must''' be built before linking a map to a scenario.


You'll also have to build your LOS file; this can be found on the Editor menu drop-down.  This must be done before a map can be used for a scenario.  Building the LOS file may take some time for the editor to complete; you'll see a progress screen while the LOS file is building.  If you interrupt this process, you'll need to re-build the entire LOS file.
== Moving on to Scenario Design ==


'''Important''': the LOS file '''must''' be built before linking a map to a scenario.
Once you've created the map and built the LOS file, you can move on to [[Creating a Scenario]].

Latest revision as of 20:15, 4 June 2012

Before you work on a scenario you should create the map you want to use with the scenario. Maps and scenarios are independent entities in "Conflict of Heroes." You can have one map that is shared by multiple scenarios, for instance.

Map Creation

There are two ways to create a COH map: in-editor maps, and input maps.

In-Editor Maps

In-editor maps are created entirely within the game editor; just start the COH Editor program, and begin designing your map. You can pick from the pre-selected map sizes to size your map (Small, Medium, Large, Wide, and Huge). To design maps in-editor, you can skip to Manual Placement of Map Tiles below.

Input Maps

An Input Map is a 2048 x 2048 JPEG in which colors correspond to different types of terrain, terrain properties, and elevations.

Here's a reduced-size input map called "Black Sea Coast" which I developed based on some Google Earth terrain:

A map hand-drawn in Photoshop, using a hex wireframe layer placed over a satellite photo

The shades of brown show elevation. Purples are houses / stone houses. Greens are forests. Reds are roads. Blue is water. White is clear. Note that you can have forests with roads running through them on heights by ensuring that a given hex contains all three colors.

Input Maps can be created in any reasonably sophisticated paint program. Creating an input map with reference to the underlying hex-grid allows the developer much more refined control over the map elements, and it's easiest to do this in a paint program that supports multiple layers, such as Photoshop or the free program GIMP. To do this, take the input map hex template we provide, and input it into a layer in your paint program.

Input Map Hex Template

Included in the /manuals sub-folder of your installation directory is a full-size template for creating input maps.

The hex lines shouldn't actually be present on the final input map; this just shows where the hex lines are relative to the terrain information.

The blueish lines represent standard map sizes.

You should use a paint program that has layers, such as Photoshop or GIMP (freeware) to design input maps.

Hexmapframe.jpg

You will find a full-size copy of the above template in the /manuals sub-folder of your installation directory.

You'll need to make the hex template transparent, except for the hex grid, in whatever program you're using.

Map Palette Guide

Here is the COH Palette Guide for creating input maps:

Mapcolorlegend.jpg

Terrain Interactions

Some types of terrain are obviously exclusive with other types of terrain, however some terrain features can co-exist in a hex with other features. Here's a zoomed-in shot showing how to add more than one type of terrain to a hex when designing an input map. This shows a road, some woods, and a height all in the same hex.

Mapguide6.jpg

Avoid Anti-Aliasing

With any tools you use to make input maps, it's important to avoid anti-aliasing or smoothing the pixels in your image. As much as possible, you want to make sure that every pixel in your image is exactly one of the colors in the COH Palette Guide. The importer will do its best to figure out what you meant by pixels that aren't exactly the right color (it'll match them to the closest colors or ignore them). However, it's possible to introduce all sorts of stray features if you use too many pixel-smoothing tools.

Mapguide10.jpg

Parsing the Input Map

After the user creates an Input Map he can parse that map in the game editor by clicking on the "Parse Input Map" and choosing the appropriate map file. Only maps that are in JPEG format that end in "_input" are allowed as input maps.

Mapguide2.jpg

It can take a minute or two to parse the Input Map. When it's done it turns the empty canvas into an *almost* fully-stocked map. A few of the fussier elements can't be added through the input map mechanism. You'll have to go through and add things like walls, bunkers, barbed wire, and so forth in the map editor after parsing an input map.

The map creation process goes fairly quickly once you get all the mechanics sorted out. I did the map above in about 1.5 hours.

Building Terrain in the Map Editor

Any and all terrain, and any map tile, can be assigned using the map editor.

For example, heights can be added using the terrain sculpting controls:

  • Enter "sculpting mode" using the Terrain --> Sculpting Mode button.
  • Use the left mouse button to raise terrain in an individual hex, and use the right mouse button to lower terrain in an individual hex.
  • You can also use keyboard commands instead: the [>] key raises terrain for an individual hex, and the [<] key lowers terrain for an individual hex.
  • When you're done raising and lowering terrain, the Editor --> Rebuild Height button smooths the terrain heights.

For example, the following map was created using the input process, but this map could also be created entirely within the editor:

Mapguide3.jpg

Adding Obstacles, Units, and Other Map Features

You can add other terrain features as desired--bunkers, for example:

Mapguide7.jpg

Place bunkers and other directional types by clicking on the map and dragging.

Mapguide8.jpg

Tiles that don't have directional information can be placed simply by clicking on the map.

Mapguide9.jpg

Again, if parsing an input map, some map tiles can be placed during the input process, but some cannot, and must be placed by hand.

Building the LOS File

When you're done with your map, you'll have to build your LOS file before continuing on to scenario design: this can be found on the Editor menu drop-down. This must be done before a map can be used for a scenario. Building the LOS file may take some time for the editor to complete; you'll see a progress screen while the LOS file is building. If you interrupt this process, you'll need to re-build the entire LOS file.

Important: the LOS file must be built before linking a map to a scenario.

Moving on to Scenario Design

Once you've created the map and built the LOS file, you can move on to Creating a Scenario.