Getting Started:
Mapmaking Policies:
The Map Foundry:- The Drafting Room
Map Ideas & Recycling Box
Drafting RoomMain Foundry Workshops
Gameplay
GraphicsFinal Forge
XML
Beta & Quench
Helpful Information:Moderators: Cartographers, Global Moderators
Getting Started:
Mapmaking Policies:
The Map Foundry:
Map Ideas & Recycling Box
Drafting Room
Gameplay
Graphics
XML
Beta & Quench
Helpful Information:

Map Accuracy Disclaimer 
Title Requirements 
Information Requirements on the first post of a map thread 
General Rules 
Good Foundry Conduct 

The author retains copyright on their work, and gives Conquer Club permission to use the imagery free of charge, for as long as Conquer Club sees fit on the Conquer Club website. Conquer Club cannot sell, lease, or lend the right to use the images to anyone else. The author swears that their map is their own work, or a legal derivative work and by submitting it, do hereby claim all responsibility for that being true.

Vacationed Maps 
Abandoned Maps 

There is a maximum of two medal recipients per map. One Mapmaking Medal will be awarded to the graphical artist who has recognised ownership of the map imagery. At the discretion of the Foundry Foreman, a second mapmaking medal may be awarded to one other co-developer. These "Primary Developer(s)" don't necessarily have to be the Graphics and XML developers, but usually are. Co-developers are not guaranteed a medal. In cases where more than one person has collaborated/assumed primacy on a map, the Foundry Foreman and Cartography Assistants will determine who has made the most significant contribution to the development of map mechanics and graphics and decide whether or not a second medal should be awarded.

Melting Pot: Map Ideas 
Recycling Box 


Supersize Applications 


Balanced Deployment - It should be unlikely that one or more players can start the game with a major advantage as a result of the initial drop or getting the first turn. Conquer Club is primarily a strategy game, and we therefore like to minimise as many of the luck factors as possible - the dice are random enough!
Reasonable Bonus Structure - Bonuses should make sense given the size/style of the map, and be based on a consistent formula. Consideration should be given to balancing the strength of the board, ensuring that no specific area of the map gives an overwhelming advantage from the start of a game.
Game Type Flexibility - The map should support various game types and not be designed with specific/limited game settings in mind (standard, assassin, fog of war, 2 players, etc.). Maps designed for fewer than 8-players should be discouraged, and will only be approved if the map is really something special.
Player-friendliness - Any information you need to know to play a map should be easy to gather by looking at the map itself. The legend should be clear, concise and consistent, and the map itself should be free of unnecessary or cumbersome rules that push it over the line separating complex from confusing.
Open Play - There should be many ways a game might progress on a map, and many roads to victory. Such features as impassable borders should enhance, not limit, gameplay, and every effort should be made to limit the number of dead ends and bottlenecks in a map, unless they are justified by the desired play of the map. The map should be fun to play, not frustrating.
Function Trumps Form - The style of the graphics should not detract from ease of play: borders should be clear, titles and numbers easy to read, colors easy to distinguish, etc...
Form Must Follow Function - So important it's on the list twice! Expect to show some flexibility and be prepared to move away from complete geographical accuracy or historical authenticity: the look and theme of the map must be utterly subservient to gameplay and legibility.

Map Sizes - Each map must eventually be submitted in two sizes. The 'large' map may be up to 840px wide and 800px high (supersize up to 1200px wide and 1000px high). The 'small' map may be up to 630px wide and 600px high (supersize up to 780px wide and 650px high). Mapmakers are encouraged to make their 'large' maps smaller than the maximum size limits when possible. The 'large' map must be noticeably larger than the 'small' map; 9% larger is required but 33.3% (1/3) is recommended. The majority of mapmakers begin working on their large image; although it is worth ensuring that everything will remain clear and legible on the small image relatively early in development.
Army Numbers - Army numbers are an essential component of every CC map. Their placement is important - it must be clear which 'territory' each army belongs to, and there must be enough room to fit a three digit number without compromising legibility of borders or labels. You may wish to use CC Army Digit Images to see how the map looks with the addition of army numbers, and to check the placement of 'army circles' if you choose to use them.
Clarity and Readability - The image must present itself as clear and legible. Any information you need to know to play a map should be easy to gather by looking at the map itself: Borders and attack routes should be clear (or clearly explained if unconventional borders are used), bonus regions should be indicated clearly; any non-standard groupings, combinations, and permutations should be clearly explained. The legend should be clear, concise, and consistent. The map itself should be free of unnecessary or cumbersome rules that push it over the line separating complex from confusing.
Colorblind Check - Mapmakers must, where possible, reduce any disadvantage that can be caused to a colorblind individual. The image should be subjected to a Colorblind Check to ensure that regions, attack routes etc. are colorblind-friendly.
Thematic Consistency - The look and general appearance of the map should fit with the theme of the map. You will need to consider how all the visual aspects of map fit the theme (pixellated vs. smooth borders; bright vs. dark; clean vs. grunge; compatible font selection, etc. etc.).
Graphical Benchmarks - Both large and small maps' aesthetics must be to a presentable Foundry standard and must also satisfy the community at large.

The Development - The XML has to follow a precise schema, full details of which are available in the XML Tutorial. While you don't need anything more complicated than notepad to write your XML, the are a couple of community-developed tools that may help, the more noteworthy is certainly the Online Map XML Wizard.
XML Checking - Once the XML has been completed, it will need to be posted in your thread by uploading your file to a host site and posting a link to it in [/url] tags or attaching the file to your map thread. It is also necessary to submit map image/XML links in the Official Map XML Check Thread (Note: Make sure you've already validated and checked the XML, as specified, before posting for an official check).




Official Mapmaker XML Tool - Checks the validity of XML map code
Army Circles Images - The standard 22px diameter circle image ready-to-use, you only need to set the transparency according to your preferences.
Army Numbers Images - The 0-9, 88 and 888 digits in all colors. Useful in case you want to show neutral troops or test if everything fits on the map.
Bonus Calculator - An Excel Spreadsheet to assist you with the bonuses. Insert into the fields all the required data and it will give you the suggested values.
Bonus Probability Calculator - An Excel Spreadsheet to assist in determining how likely a player is to drop a specific bonus (regular or build-your-own).
Users browsing this forum: No registered users and 1 guest