Editing Map requirements
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 6: | Line 6: | ||
=== Connections are Visible === | === Connections are Visible === | ||
− | + | It must be obvious when looking at the map which territories connect and which don't. | |
− | The biggest mistake some map creators make is to connect two territories over water, but don't include any indication on the map that they connect. It's customary to use yellow lines to show where the connections are - see the [ | + | The biggest mistake some map creators make is to connect two territories over water, but don't include any indication on the map that they connect. It's customary to use yellow lines to show where the connections are - see the [http://warlight.net/SinglePlayer.aspx?PreviewMap=12 Earth Map] for an example. It's not necessary to use yellow lines, it just must be obvious where the connections are. It may be obvious that the territories connect in the map designer, but it needs to be obvious in the real game too. |
− | + | http://blog.warlight.net/Images/ConnectionMissing.png | |
− | + | ||
− | + | ||
=== Tiny Territories === | === Tiny Territories === | ||
− | All territories must be big enough to fit a two-digit army number. Often people's first instinct is to keep territories real-life sized, however this doesn't work well in | + | All territories must be big enough to fit a two-digit army number. Often people's first instinct is to keep territories real-life sized, however this doesn't work well in WarLight's engine. This is especially evident once you try playing the [[Mobile Client|mobile version of WarLight]]. |
− | Take, for example, Hawaii in the [ | + | Take, for example, Hawaii in the [http://warlight.net/SinglePlayer.aspx?PreviewMap=12 Earth Map]. Hawaii is a very small island, but in the Earth map it's sized significantly larger so that it can fit the army number. |
− | In the map designer, you'll find a button labeled Show Example Armies. When clicking this, all | + | In the map designer, you'll find a button labeled Show Example Armies. When clicking this, all territories must be big enough to fit the entire army number. |
− | + | http://blog.warlight.net/Images/TinyTerritories.png | |
See [[Inkscape tips]] for a guide on how to enlarge territories to make them fit their army number. | See [[Inkscape tips]] for a guide on how to enlarge territories to make them fit their army number. | ||
Line 28: | Line 26: | ||
=== Copyright Violations === | === Copyright Violations === | ||
− | By uploading a map to | + | By uploading a map to WarLight, you are asserting that you own or have the necessary licenses, rights, consents, and permissions to the content within. See the [http://warlight.net/TermsOfService.aspx Terms of Service] for full details. |
=== Missing or Mistaken Connections === | === Missing or Mistaken Connections === | ||
− | Maps | + | Maps should make an effort to find and missing or mistaken territory connections. Missing connections are a very common problem, as it is difficult to find every last connection error within the map designer alone. |
− | + | To avoid this issue, you may try to use the [[Automating the map creation process#Connections|automatic connection creating tool]]. However, please remember that it is not perfect (some of the caveats are listed on the linked page), and the map will still require manual checking. | |
− | Incorrect or missing connections are also much more pronounced in the map previewer (which you can access via links in the Get Link for Sharing window), where all territories connected to the clicked one turn bright yellow. Map creators should create several [[Testing maps|test games]] on their map with real human players and play them out. | + | The best way to find these kinds of mistakes is to play the map with real humans. Incorrect or missing connections are also much more pronounced in the map previewer (which you can access via links in the Get Link for Sharing window), where all territories connected to the clicked one turn bright yellow. Map creators should create several [[Testing maps|test games]] on their map with real human players and play them out. |
+ | |||
+ | If you need help finding players to test your map, make a thread on the map development [[forum]] asking for volunteers to help test your map. There are always lots of people willing to help test. | ||
=== Territories are named === | === Territories are named === | ||
− | All territories should be named appropriately. Naming | + | All territories should be named appropriately. Naming every territory the same thing, or just typing gibberish makes it hard for players to coordinate in team games. |
− | === Bonus Links === | + | === Bonus Links exist === |
− | Bonus Links are the small boxes that show | + | Bonus Links are the small boxes that show many armies each bonus is worth. Without these, it is difficult to tell where the bonuses are. See [[Creating the SVG]] for instructions on how to add bonus links. |
− | + | ||
− | + | ||
=== Appropriate Size === | === Appropriate Size === | ||
− | The SVG file specifies the width and height of the map in pixels. The recommended starting point is 1000x1000, however map creators can reduce this if they are making a small map or increase it if they're making a big map. | + | The SVG file specifies the width and height of the map in pixels. The recommended starting point is 1000x1000, however map creators can reduce this if they are making a small map or increase it if they're making a big map. |
The size specified in the SVG file determines how big the army numbers will be on the map. This size must be appropriate for the map. If a very small map is stretched into a huge SVG file, the army numbers will be too small to see without zooming in. In order to avoid unnecessary zooming, a large SVG file should only be used if the map really needs that much room to fit all of its territories. | The size specified in the SVG file determines how big the army numbers will be on the map. This size must be appropriate for the map. If a very small map is stretched into a huge SVG file, the army numbers will be too small to see without zooming in. In order to avoid unnecessary zooming, a large SVG file should only be used if the map really needs that much room to fit all of its territories. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
=== Testing Maps === | === Testing Maps === | ||
− | The map must be a real map and not just a test. It's a good idea to make your first map just a couple | + | The map must be a real map and not just a test. It's a good idea to make your first map just a couple territories to proove you understand how to make a real map, however these simple maps should not go public. You're free to put these into testing mode to play games on them, however. |
== Grandfathered Maps == | == Grandfathered Maps == | ||
− | Players sometimes notice maps that are already public that don't meet some of these requirements. Older maps that were created before these requirements existed are grandfathered in, such as the Wheel map that does not have bonus links or the United States Big map that | + | Players sometimes notice maps that are already public that don't meet some of these requirements. Older maps that were created before these requirements existed are grandfathered in, such as the Wheel map that does not have bonus links or the United States Big map that has tiny territories. The presense of the old violations does not exempt new maps from the requirements. |
== See Also == | == See Also == | ||
* [[Map Making]] | * [[Map Making]] | ||
− | |||
− | |||
* [[Map guidelines]] | * [[Map guidelines]] | ||
* [[Inkscape tips]] | * [[Inkscape tips]] | ||
[[Category:Map Making]] | [[Category:Map Making]] |