Virtual tabletops (VTTs) are a great way of playing role-playing games together when you can’t meet physically. They make it easier to play with people from all over the world, and are a nice substitute when it becomes impossible to bring the old gang together in the same location any more.
One of the main attractions for these programs when compared to general-purpose meeting/teleconference software is their focus on displaying maps to the the players, enabling you to fight your miniature battles digitally. And maps are always an important aspect in most role playing games. I myself actually use VTT software to display the battle maps, even if my group always meet physically at my place and roll physical dice, because I can more easily do things like display the map on a projector, and only display what the players see (automatic fog-of-war/lighting/sight ranges).
So, today we will look at how to take those dungeon maps you’ve lovingly crafted in DD3 and make them available for use in the a VTT environment. Now, there are lots of different VTT software to choose from out there, and I can’t really cover them all, but I’ve tried to cover some of the more popular ones, such as MapTool, Fantasy Grounds, Roll20 and D20Pro. And many things, especially all the various concerns when exporting the map from DD3 will be the same for most software solutions, so this article should help you out no matter the system.
Welcome back to this article series on mapping as worldbuilding for large cities and towns. In the last article in this series, we covered developing the geographical setting for your city, identifying the main purpose or economy of the city, dividing it into districts, deciding between functional and residential districts, and we even talked a little bit about transportation. Recall that by way of example, I’ve been mostly using the city of New Cassia which I recently mapped as a means of illustration of the ideas here.
In this article, I’d like to cover some more about ways to go about laying out the canvas for your city by exploring textures, terrains and landmarks. We’ll apply this to district building next, and in a later article we’ll go into some more of the technical pieces on how to actually construct each district in CC3+ but for now we’ll stick with planning as it relates to storytelling and worldbuilding.
The most important piece to start with: in general, work on your city one district at a time. Doing so provides cohesiveness in what you’re working on, and also gives you a concrete deliverable that you can complete and then take a break. I like to do a nice quality export of each district I finish as a milestone marker to record my progress over time, as well as share with the CC3 community for any feedback.
We last left New Cassia with some districts and main roads.
Road Types, Sizes and Materials
In the previous article, we ended with defining the major thoroughfares of our city. Let’s cover that in a bit more detail. Not all roads in a city are the same size in most cities you could probably think of, so thoroughfares are the largest of these roads. Depending on the scale of your city, these may be 10′ or 20′ wide (using Imperial measurements, but applicable with the equivalent metric sizes as well). New Cassia is a large city, so its main thoroughfares will be 20′ wide; this will visually stand out as well as define the routes the city’s inhabitants will take for most navigation.
Stepping stones in a Pompeii street
We also need to decide the material of these main roads: are they wide, paved cobblestone walkways? Are they well-entrenched dirt roads? Are they waterways with sidewalks, such as in Pompeii? Or are they other textures like mud, grass, sand or even more exotic materials like lava, water, or sludge? This decision point can have an easy to miss but significant effect on the story and history of your city.
Also, keep in mind, not all roads in a city need to be the same; you can mix stone, dirt and exotic roads along with varying sizes (I like to swap out stone roads for dirt in poorer residential areas). You can also think about which areas will have no roads at all. Roads are all about access; poor quality or no roads will usually lead to less access to an area. Maybe this is to keep outsiders out (or undesirables in), or maybe the government can’t be bothered to pave an older, decrepit neighborhood.
Keeping a Microdecision Log for Inspiration
Think about the implications of each microdecision. If your main roads are sludge, that suggests a sewer-dwelling city, or perhaps the Underdark. Do people use boats or rafts to traverse them, or do they walk on foot? Each of these questions can lead to interesting story developments, like defining the daily experience of a resident (or visitor, which may differ) or leading to questions about why it is that way, or how commonplace non-walking modes of transportation are.
Each time you make one of these microdecisions, you can write down a question or two about it. For each mapping session, you’ll build up a short or medium list of questions. You can then ponder these in between mapping sessions. You don’t need to answer all or even most of them, but each answer will flesh out your world. You can come back to sticky questions that keep coming up, or discard them and move on.
So hopefully now we’ve at least decided on our main roads, and maybe even begun to ruminate on other road styles throughout the city. Great job! Now we can turn our attention to individual sections of the city.
Constructing our First Landmark
As a warm up exercise to district building, let’s do our first exercise in landmark construction. I recommend thinking about what the most defining building is going to be in your whole city. You figure out what “defining” means to you – it could be culturally, religiously, politically or economically. In some cases this might be a seat of government – a keep, a castle, a mayoral palace, a parliamentary house or any other such building. Sometimes a city may be oriented around this place; other times it might be at the city edge, and still others may have accidentally evolved the location of this building. These are all okay, but are microdecisions worth writing down and maybe asking yourself questions about.
Sapphire Citadel, home of the Mages’ Academy, is one of the most notable landmarks in New Cassia.
Once you’ve identified this building and a suitable location, build it! Whether it is a symbol (we’ll talk more about symbols later) or some more custom construction, orienting around it will get you a feel for what characteristics you want to demonstrate. Don’t be shy about experimenting – place something, delete it, try again, change size and color…try things out until it seems right to you. And even if you need to settle for good enough, you can always come back to it and redo it easily.
Now you’ve built or placed one building. Think about what supporting buildings may surround it, and place those. A keep may have additional administrative offices around it. A military training facility may have barracks nearby. A mages’ academy may have a library nearby. Or, maybe you’ll decide this building is solitary: a grand wizard’s tower at the peak of a tall hill, with nothing else daring to surround it!
The Sapphire Citadel, with some supporting academic buildings and the Great Library of Ytron. Notice how the mix of grassy terrain gives more depth to the district. Also note the dirt path mixed with stone roads.
Terrain Surrounding the Landmark
Think about what terrain you expect to surround the main building. A castle may be built atop paved stone; a monument to a town’s founder may be in the heart of a central park, surrounded by grass and dirt roads; a demon’s spire may be surrounded by a lava most. Now place that.
As you’re placing the terrain and supporting buildings, ask yourself a question or two (not too many, we don’t want to rathole on this) about why they are there or what their nature is. If something (or even better, someone) interesting pops up, write that down somewhere.
Now, one finishing touch: label it! Just plop some text down on or near it with either a name (if you’ve got one; if not, you can punt on that till later) or a short description to remind you of what it is and why it’s there. Note: you do not have to do this on your main TEXT sheet; you can create another one such as TEXT ANNOTATIONS that you can use just for your own notes and labels about notable buildings. This sheet can be hidden during your final export if you don’t want to show them (we’ll talk about labeling towards the end of the series). But recalling the purpose and name of each place can help us build up stories in our city.
Congratulations! You’ve just constructed your first (and most important) landmark! We’ll be going through this process a bunch, but hopefully you’ve learned a few things from doing this:
It’s okay to experiment, sometimes extensively. We’ll develop ways to keep this from ballooning too much all over the city.
The process of building a landmark does not have to be scary, and can be as simple as a few local decisions.
A landmark can help define the area around itself, such as the terrain and the nearby roads. We’ll need this as we build up our districts.
Noting down random thoughts about why a building is where it is can lead to interesting story hooks.
Textures, terrains and materials can define a lot of character, history and culture about an area.
Next time, I hope to cover planning each district, and discuss how to make each district unique stylistically and feature-wise (including landmarks!).
Ari Gilder is a software engineer, and has been interested in maps for a long time. He spent seven years working on Google Maps, working on features like local business search, Google Maps and Navigation on mobile, and studying the way users understand maps. He even proposed to his wife using maps. He often spends hours staring at maps in fantasy novels, and in 2013 starting putting together some of his own dungeon and battle maps for a D&D campaign. After a hiatus of several years, he recently dived back into cartography with CC3+, tackling more overland and city maps in preparation for a new D&D campaign. He is a father of two, and has recently introduced his older daughter to cartography, both hand-drawn and with CC3+ where she insists that black and purple varicolor trees must surround everything.
Comments Off on Bringing Your City to Life – Part 2 (by Ari Gilder)
What it’s in the works here are Profantasy HQ at the moment do you ask? Well, apart from behind the scenes work on Campaign Cartographer itself, the ongoing Annual development and the daily routine, we are getting close to finishing the next installment of the Token Treasury series.
The artist, Rich Longmore, has delivered as wonderful new collection of nasties (and not so nasties) for your games and maps, and I am now converting them to CC3+ format, creating varicolor versions and building catalogs. Look for the release later this month! You can check out the first installment of the Token Treasury here.
Recently, I completed a large-scale city map over the course of about three months. It is only my second map with City Designer 3, so I am by no means an expert, but between the two maps I’ve recently spent a lot of hours with the tools, learning some of the ins and outs of the how as well as the why.
Both of the cities (well, one city and one town) I’ve built have been quite large for their size. I’d specifically like to consider these kinds of settlements, as opposed to a quaint fishing village or a small farming hamlet. Because these are smaller settlements, by definition less time will go into them. Also, when I was doing my research on how to start mapping a large city or town, I found very few resources on how to tackle such an ambitious project. Continue reading »
One of my favorite player visualizations is a spinning globe. Nothing makes a world come so alive when the players are able to properly visualize the entire planet.
This is also why I prefer to always start my new worlds in Fractal Terrains, as it lets me get a proper grip on the planet before I move on. Starting directly with a flat map in CC3+ gives so many possibilities for missteps when mapping a sphere, and I also just love to click through the auto-generated FT3 worlds until I find the perfect one. When I picked the world for my current campaign world of Virana, I probably clicked through hundreds of generated worlds and tweaked the settings a dozen times before I found the right one.
Now, this article isn’t about creating your FT3 world however, but rather on how to best make one of those nice spinning globes you can use to show it off.
So your New Year’s Resolution for 2020 was to finally start (or re-start) using Campaign Cartographer 3 Plus, but you don’t know where to begin? Let us help you out with a selection of great tutorials and starting points.
Video Tutorials
If you are a visual learner and want to follow video tutorials, here are some we would recommend to start out with.
Josh Plunkett does a great job at introducing you to the basics of CC3+ as a newcomer in his first video.
Follow that up with his tutorial on overland mapping and you’ve got the basics down for any overland map straight out of CC3+:
For a longer look at creating a whole overland map, check our own video with Ralf describing the process of creating a map.
PDF Guides
If you prefer reading your tutorials and follow a pdf guide, there are some great choices too.
Campaign Cartographer 3 Plus comes with a pdf Manual, that is probably still one of the best ways to learn the software. Check it out here, and follow the instructions starting on page 24 to draw your first map.
A slightly less detailed, but still very useful step by step guide to creating a map, comes with the mapping guide for the Herwin Wielink style, that comes with CC3+, available in the Documentation folder or from this link.
Comments Off on New Year’s Resolution: (Re-)Start your Mapping with Campaign Cartographer 3+
In my previous installment of this series, I talked about, among other things, composite symbols made up from multiple raster images. This is cool and all, but it raises one interesting question; what about effects? When you place a symbol, all parts of that symbol is grouped together into one entity, which lives on a single sheet.
If you make a symbol that contains a small cottage, with a tree and a few bushes outside, you’ll probably want different shadow lengths on each of these components. But, to do that, you need different sheets, right?
This is where multi-sheet symbols come in. Basically, a multi-sheet symbol is a symbol that gets split into multiple symbols when you place it, thereby putting each component of the symbol on the appropriate sheet. This may sound a bit like exploding a symbol, but with multi-sheet symbols, it is the designer of the symbol that decides which sheet each part should go on without any manual intervention from the symbol user.
Colors are important for any CC3+ map. Now, you can make beautiful Black & White maps too, but it would be a bit boring if that was the only option available.
Colors in CC3+ comes in two main flavors. CC3+ has it’s own color palette from which you can pick colors and use for entities you create in CC3+. And then you have the colors used in raster symbols and fills, which are part of the image these are based upon, and which are not changeable inside CC3+ (with the exception of varicolor symbols, but that is a separate topic).
The CC3+ color palette will be the focus of today’s article.
One of the limiting factors with the palette is that it only supports 256 colors, which means that it might not contain the exact colors we want for our map. Fortunately, it is easy to edit the palette. You can bring up the dialog at any time by clicking the color indicator on the status bar, pick one of the existing colors, and hit the Define Color button. This lets us define it as any color in the standard 24-bit color spectrum (over 16 million different colors available). Just remember that if you edit a color, it will affect existing entities in the map, you cannot get around the 256 color limit by first using a color and then changing it. Now, changing the colors are easy, but let us look a bit more a palette-wide options. Continue reading »
Comments Off on Managing the Color Palette in CC3+
In FT3 you can simply change your colour scheme by loading a new one. With some minor limitation this is now also possible for your topographical maps in CC3+. Here are some supporting files:
Exporting coloured topographical maps from FT3 to CC3+
Fractal Terrains 3 (FT3) is a great tool to create new worlds or to visualize our own – earth. Here I will focus on how you can export a topographical map to Campaign Cartographer 3+ (CC3+) and change its style easily.
When you export contour maps from FT3 and CC3+ you usually get the expected results – as long as you use the predefined colours from the built in palette or standard colouring schemes that follow with FT3. As soon as you start to use non predefined colours in your map the export from FT3 to CC3+ will give unexpected results.
The built-in colour palette in FT3 matches the default palette used in CC3+. As long as you only use the predefined colours when you design your own style for topographical maps, the colours in both FT3 and CC3+ will match. As soon as you start to use your own or blended colours, the result in CC3+ will look different and usually not match your style anymore.
How to use other colour styles
With the November 2019 issue of the Cartographer’s Annual come several very useful and inspiring colour schemes by the artist Sue Daniel. These where actually made for use with Wilbur (another very handy application by Joe Slayton, the creator of Fractal Terrains). She also gives an example of a colour palette for CC3+ that can be used to colourize your imported height contours from FT3. But you have to do it the manual way – one by one.
While you can change the look of your maps completely in FT3 only by loading another colour scheme, you have to colorize each contour again from scratch in CC3+. You also have to adjust the 256-colour palette when you not find your favourite colours that match your style.
This had me thinking about a workaround. There must be a way to skip the manual work of colouring contours and there should be also a possibility to make it much easier to change the
style of your map – just only by changing the colour palette in CC3+ which has become much easier since Profantasy introduced the new command PALLOAD.
Sue used 10 colours for different sea depths and 25 for altitudes. She replaced “unusual” colours in the 256 colour palette of CC3+. Why not expanding those colours ranges was one of my first thoughts. Why shouldn’t I force FT3 to use a certain colour instead of leaving it up to the program itself (trying to find a matching colour)? And how could several colour styles be used without having to export a map several times from FT3?
I decided to use 32 colours for altitudes and 16 for the sea. If you always use colour no. 223 for the lowest land level and no. 192 for the highest one then you make use of exactly 32 colours for altitudes. The same applies when you always use colour number 224 for the sallowest sea and no. 239 for the deepest. This way you use 16 colours for the sea. (Note that I changed the order of colours for altitudes over land compared with Sue’s approach).
If your world is between -32.000 ft and 32.000 ft – what are the needed depths and altitudes to be exported from FT3? If you want to have equidistant high levels then we have 32.000 ft / 32 colours = 1.000 ft / colour (and for the sea 2.000 ft, because we have only 16 colours here).
So in this case you have to set up a Campaign Cartographer Export in FT3 that exports 32 altitude levels from 0 ft to 31.000 ft (32 levels, the last one reaches up to 32.000 ft).
You force FT3 to use colour no. 223 for the first level – 0 ft. For the second level 1.000 ft use no. 222, for the third one no. 221 and so on. Concentrate on the numbers and do not get disturbed by the pink/purple or nearly black colours that you select when setting up the template. Then you generate 16 levels of depth from -32.000 ft to -2.000 ft and force the level -2.000 ft to choose colour no. 224, the next lower level uses no. 225 and so on. This is the most time consuming part of this procedure.
If your world expands from let’s say -4.800 m to 4.800 m you have to define another Export template with 150 m steps for altitudes and 300 m steps for the sea. Unfortunately you cannot change the height levels afterwards. You have to delete existing ones and have to add new ones when you have copied an existing template. Basically you can set up your heights and depths as you wish – as long as you follow the procedure above with exactly 32 levels for the altitude and 16 for the sea.
You may object that setting up an individual export is as time consuming as having to colourize each contour separately. You are right as long as you only want to create a single map and do not want to change the style of it afterwards. Until now there are only quite a few colour palettes available for CC3+ and almost all existing colour schemes in FT3 do not match the above approach with 48 colours.
So my personnel challenge was to create colour palettes that fulfill my requirements and the matching colour palettes for CC3+. With a little programming my PC did this job. And now you can take a look at your exported map. When you still have the default palette loaded it will look like the one on the right! This is not quite the look we wanted – but it is the style we defined in our FT3 to CC3+ export template!
And now to the fun part: Start loading the new specialized colour palettes and see what happens. Download some example color schemes for FT and CC3+ here.
We start by typing PALLOAD into the command line and press enter. We press enter once again – no entry given for the palette name. A file selection dialog opens and you can pick the colour palette of your choice – here I use the one with the same name that I used for my FT3 visualisation. It’s the Wilbur Old Map style – based on an idea by Sue. (Eventually you have to press enter two times again before the effect takes place).
Compared to the original map (generated in FT3) this one exactly matches our style in CC3+. Finally, you can change the style easily only by loading another colour palette – and there are quite a lot to choose from. Your map gets a totally different look in no time…
Here are a couple examples in the Dark Parchment and Arctic styles.
About André alias WeathermanSweden
André has been working as a forecaster southwest of Sweden’s Capital Stockholm for many years. While weather maps were his daily duty he always had a big favour for astronomical and topographical maps as well. He is fascinated by fantasy worlds and loves all the incredible maps presented by the community. Since he has been back to his roots in northern Germany he runs a little campsite together with his parents south of Lübeck. Despite the weather and the stars he is also interested in 3D rendering, photography and nature, where he spends a lot of time with his dog.
Some places just deserve to be exported in a nice high-quality export so you can properly examine all the details of the map.
The City of Sanctuary from the community atlas is certainly one of these places. This lovely city by master mapper Christina Trani and resident artist Sue Daniel is a visual masterwork of a city map. So, I decided to try to make a proper high resolution export of this map. The result is a map 200,000 by 200,000 pixels, or 40 gigapixels in size. The .png file for this map is over 12GB in size, and even though I have a powerful computer, actually opening this source image in an image editor is almost impossible without it crashing.
Of course, providing such an image for download is useless, since nobody can actually use it, but a far better approach is to provide it as a zoomable image on the atlas website. The image viewer used for such a zoomable image loads different images depending on your zoom level, ensure that you only load what you need at any one time, making it reasonably easy to explore this gigantic export with reasonable loading times as you zoom or scroll. You can explore this zoomable image yourself by going to the City of Sanctuary map page, and then click the Zoomable Image button located over the map image. It should load reasonably quickly, but your physical distance from my server would affect loading times. I recommend you click the fullscreen button in the toolbar at the bottom of the zoomable image viewer for a much more impressive experience.
So, how did I accomplish this feat? Well, let me start by underlining that this was not a simple one-click task, it did require quite some work and a lot of computer time. Continue reading »
Comments Off on Sanctuary – Largest CC3+ export ever?
Virtual tabletops (VTTs) are a great way of playing role-playing games together when you can’t meet physically. They make it easier to play with people from all over the world, and are a nice substitute when it becomes impossible to bring the old gang together in the same location any more.
What it’s in the works here are Profantasy HQ at the moment do you ask? Well, apart from behind the scenes work on Campaign Cartographer itself, the ongoing Annual development and the daily routine, we are getting close to finishing the next installment of the Token Treasury series. 
As soon as you start to use non predefined colours in your map the export from FT3 to CC3+ will give unexpected results. 
This had me thinking about a workaround. There must be a way to skip the manual work of colouring contours and there should be also a possibility to make it much easier to change the
I decided to use 32 colours for altitudes and 16 for the sea. If you always use colour no. 223 for the lowest land level and no. 192 for the highest one then you make use of exactly 32 colours for altitudes. The same applies when you always use colour number 224 for the sallowest sea and no. 239 for the deepest. This way you use 16 colours for the sea. (Note that I changed the order of colours for altitudes over land compared with Sue’s approach).
So in this case you have to set up a Campaign Cartographer Export in FT3 that exports 32 altitude levels from 0 ft to 31.000 ft (32 levels, the last one reaches up to 32.000 ft).
