Map guidelines

From Warzone Wiki
(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
 
This section lists general guidelines that make exceptional maps.  For a list of the requirements that a map '''must''' pass to be approved, see the [[map requirements]].
 
This section lists general guidelines that make exceptional maps.  For a list of the requirements that a map '''must''' pass to be approved, see the [[map requirements]].
  
==Border overlap==
+
== Border overlap ==
  
 
It is recommended that the borders of territories in the same bonus overlap, whereas the borders of territories in different bonuses should be adjacent.  
 
It is recommended that the borders of territories in the same bonus overlap, whereas the borders of territories in different bonuses should be adjacent.  
Line 9: Line 9:
 
http://warlight.net/Images/MapDesignBorders.png
 
http://warlight.net/Images/MapDesignBorders.png
  
==Connection Lines==
+
== Minimize long connections or drastically uneven territory size ==
  
If you wish for two territories to connect, but they aren't physically touching each other on the map, it's necessary to include a line on the map so that players can easily see that they're connected.
+
One property of a great map is that players can tell at a glance, without doing an analysis, approximately how many turns it takes to get from one territory to another.
  
==No Tiny Territories==
+
For example, on the [[http://warlight.net/SinglePlayer.aspx?PreviewMap=12 Earth map]], all territories are approximately the same size, and all connections between territories over water happen between territories that are relatively close to begin with.
  
All territories must be big enough to completely fit a single-digit army number, at a minimum.  Preferably, territories should be big enough to fit a three-digit army number with a little space around each digit.
+
Contrast that with this example, where territory labeled B is actually significantly closer to A than C is, even though it appears to be further away:
  
==See also==
+
http://blog.warlight.net/Images/LongConnections.png
 +
 
 +
Long connections like this make it harder to spatially visualize the map layout.  A similar effect can happen when territories are drastically uneven in size.  Just like before, B is much closer to A than C is, even though it appears further away:
 +
 
 +
http://blog.warlight.net/Images/UnevenTerritorySizes.png
 +
 
 +
This happens due to an extremely large territory being nearby to very small territories.
 +
 
 +
== See also ==
  
 
* [[Map Making]]
 
* [[Map Making]]
 
* [[Creating the SVG]]
 
* [[Creating the SVG]]
 +
* [[Map requirements]]
  
 
[[Category:Map Making|Guidelines]]
 
[[Category:Map Making|Guidelines]]

Revision as of 00:06, 12 February 2012

This section lists general guidelines that make exceptional maps. For a list of the requirements that a map must pass to be approved, see the map requirements.

Border overlap

It is recommended that the borders of territories in the same bonus overlap, whereas the borders of territories in different bonuses should be adjacent.

For example, take a look at part of South Africa in Grundie's Earth map:

MapDesignBorders.png

Minimize long connections or drastically uneven territory size

One property of a great map is that players can tell at a glance, without doing an analysis, approximately how many turns it takes to get from one territory to another.

For example, on the [Earth map], all territories are approximately the same size, and all connections between territories over water happen between territories that are relatively close to begin with.

Contrast that with this example, where territory labeled B is actually significantly closer to A than C is, even though it appears to be further away:

LongConnections.png

Long connections like this make it harder to spatially visualize the map layout. A similar effect can happen when territories are drastically uneven in size. Just like before, B is much closer to A than C is, even though it appears further away:

UnevenTerritorySizes.png

This happens due to an extremely large territory being nearby to very small territories.

See also

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox