The No-Frauds Club » Cosmonarchy-BW » Sites » Mapmaker's Guidebook



Mapmaker's Guidebook



Welcome to the mapmaker's guidebook! This handy document is meant to serve as a reference to those who wish to add to Cosmonarchy's bounty of custom maps. This page assumes you already have an SCMDraft 2 profile set up for Cosmonarchy mapping, but if you don't, you can follow the mapping starter guide to get set up.

Because Cosmonarchy deviates so radically from stock Starcraft, it should be noted that many "old world" melee mapmaking techniques are either surplus to requirements, neutral and thus totally optional, or actively deleterious to general play. Use them at your own risk!

Click the box below for a reference of units and structures of interest that can be placed for player 12.


  • Assets with auras: When provided by neutral assets, auras which effect allies apply for all players
    • Applies for: Shaman, Ancile, Azazel, Crucible, Clarion, Matraleth
  • Refineries: Can be harvested by any player; cannot self-destruct
  • Addons: Can be claimed by any player; cannot self-destruct
  • Anchor, Tencendur: Can be garrisoned by any player; cannot lift off
  • Power nodes: Power fields provided by neutral Protoss structures can be used by any Protoss player
  • Cagra spreaders: Cagra spread by neutral Zerg structures can be built on by any race and player
  • Nydus Cesiant: Allows entry by any player; does not regress


There will eventually be more information on general map design and other techniques to look out for, in its own unique section of this guidebook.


Map Classifications


We use the following classifications as a way to categorize our competitive maps:
  • Empire-class: Actively used for premiere tournaments
  • Uprising-class: Recent creations that are deemed final by authors, but have yet to be vetted for competitive play
  • Bloodbath-class: Dated creations that still give acceptable matches, but have already served in premiere tournaments
  • Jester class: Maps which have been deemed unfit for purpose for one reason or another

A separate directory is also present for Work in Progress maps, which are still actively being iterated upon prior to their placement into the Uprising class.


Pre-Submission Checklist


Say you've made a map, and you want it to be added to the project's maps directory. There are distinct functional and aesthetic requirements maps must have in order to be accepted into the pool - though in the case of missing the proper custom tiles to do the job, aesthetics can be temporarily overlooked until new tiles are created.

Functional:
  • Make sure all Start Locations are placed in their own bases - including start locations for witness players!
  • Place Town Center Markers (Units -> Neutral -> Special) wherever AI should place town centers. You can place more than one per base if needed.
  • In 'Overlay Settings' below the minimap, untick 'Use Defaults', and tick 'AI Town Locations' to preview resource areas. Ensure that all resource areas are correct to avoid worker wandering and AI expansion issues.
  • Make sure you have something like this example trigger for computer players to run correctly. You can import this in Triggers dropdown -> Trigger Editor.

Resources:
  • Gas nodes should never be fully diagonal (i.e. primarily horizontal or vertical angles).
  • The majority of mineral nodes should be as close to the town center as possible.
  • All bases with horizontal mineral fields to the right of town center placement should have their mining tested with a Quarry addon.
  • See the image below for a before & after, following these rules!


Aesthetic:
  • Place Mineral Fields without having excessive repeats.
  • Place tiles without having excessive repeats.
  • Provide some indication as to where town centers should be placed in all expansions.
  • Make sure your map is adequately-decorated. Do not sacrifice function for aesthetics by placing too many unpathable or unbuildable tiles and doodads around the map.

Housekeeping:
  • The special witness character (copy and paste this!) should be used for the spectator force name.
  • Your map description can contain anything you like as the first line. This blurb should be followed by an empty new line and text that reads by [your username]. Please ensure that the authorship line is visible in the map selector!

Cover all this ground, and you'll be well on your way to having more pointed feedback about the actual construction of your map, instead of getting lots of feedback about the bare basics!