Last month, I talked about how to bring your DD3 map into various Virtual Table Top (VTT) systems. Now, that is all well and good, but simply exporting a flat image from CC3+ to a VTT do have some limitation. For example, if you make a beautiful forest, the player token would be walking atop your trees, and the players wouldn’t see what is below the trees. In the real world, when you take a walk in the forest, you actually see the forest floor, not the treetops. Same happens when your characters encounters this mysterious house in the forest. Your gorgeous maps shows the scene, and as with any outdoor map, seen from above, the map shows the roof of the house. Then your players announce they are going inside. What now?

There are two ways of handling this. The first is just to have separate maps, one for inside the house, and another for outside. Then you can just load the inside map whenever the players enter the house. But what if someone stays outside and someone goes inside? Well, you could have an identical map still showing the outside, but now revealing the insides of the house instead of the roof. But this approach still means you need to move the player/monster tokens from one map to the next.

The other approach is to have items in your battlemaps that can be hidden to show additional features. This is something we are quite used to doing inside CC3+ by hiding and showing sheets, and the subject of an earlier article. This is a very nice approach, but it is also a bit trickier. The problem here is that when we export a map from CC3+, we end up with a flat image file, we lose things like sheets and layer. There are image formats supporting layers, but CC3+ can’t export to these, nor can the VTT software import them, so we need to do it differently.

Continue reading »

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 »

This is the third article in my series about XP development. To understand this article properly, you should be familiar with the contents of the previous articles.

When writing commands for CC3+, we frequently need to communicate with the user. This is often in the form of requesting some data from the user, such as where to place a node or which color to use, or we want to provide information to the user, such as instructions on the command line or the information the user requested. In this article, I’ll talk about the Text Formatting & Output Service (FormSt) used to prepare data to display to the user, and the data request format (ReqData). We have been touching both of these briefly in the two prior articles, but it is time to discuss these a bit more in depth.

Continue reading »

Accompanying CC3+ and it’s addons are a host of different symbols, all arranged neatly into symbol catalogs. These catalogs are arranged by map type, map style, and symbol theme/content. For example, there is one symbol catalog containing structure symbols from the Mike Schley Overland style, while a completely different symbol catalog contains furniture symbols from the standard DD3 dungeon style. Generally, these catalogs are arranged in such a way that clicking the various symbol catalog buttons (the toolbar right above your mapping area) loads different symbol catalogs relevant to the current map type and style. And if you need a symbol catalog from a different style, you can always click the Load Symbol Catalog button and browse for a different symbol catalog manually.

But did you know that CC3+ allows you to easily manage these catalogs and their content? For example, you can create a new catalog containing all your favorite symbols, collecting symbols from different styles and even map types into one catalog. In this article, I’ll guide you trough making such a custom catalog; for this example, I’ll be making a catalog that collects all the statue symbols from the various dungeon styles I have available to me. I often use statues as dungeon/floorplan dressing, and it would be great to have all of these available in one place. This catalog will mix symbols from different styles, so not every symbol in this catalog will work in every map obviously, but you can often mix symbols from different styles with great success.

Continue reading »

This is the second article in my series about XP development. To understand this article properly, you should be familiar with the contents of the previous articles.

In this article, we’ll talk about how we can manipulate our drawing. In CC3+, a drawing is really a series of entities, so we are going to have a closer look at what an entity really is, how to create new entities in the map, and how to access and manipulate existing entities.

Entities

Everything in a CC3+ map is an entity; a symbol, a line, a landmass and so on. This term should be well known to all CC3+ mappers, as it is the term used in official documentation. However, it isn’t just these visible things that are entities, almost everything stored in a CC3+ drawing is an entity, such as a map note or an effect. We can view an entity as a data container for one specific thing or aspect of our map.

When working on an XP, you are almost always going to be handling entities. After all, manipulating entities is needed no matter what you want to do with the drawing, including extracting information from it, so understanding how to work with these is very important.

Continue reading »

Many gamers use some kind of digital solution such as virtual table-top software to display maps on a projector or computer screen even when running a local game (as opposed to running a game over the internet, where such software is pretty much required). All of these software solutions have their advantages and disadvantages, but  CC3+ itself may actually be a very good solution, depending on your needs. Now, just to start with the limitations, CC3+ don’t have any kind of remote viewing/projecting options, so this do require that you share the screen you are actually working on (This can be a secondary screen/projector that is set up to mirror yours, or it can be done through screen sharing software, which allow others to see your screen even over the internet).

So, why would you use CC3+ for this? What advantages does it have over other VTT software? Well, the main reason CC3+ is good for this is that this is where you made your map in the first place. This means that the map is fully interactive, and you have all your regular CC3+ tools available to you to manipulate the map during play. If you export the map from CC3+ to an image file for use in a VTT program, then everything becomes static. In CC3+ you can hide or show sheets and layers, you can move symbols and edit whatever you need to do.

Of course, CC3+ isn’t optimized for use during play, while a VTT program is made just for that purpose, so some things are probably a bit more complicated to do in CC3+, so it is up to you if the flexibility CC3+ offer with regards to what you can do with your map during game play is worth it. For this article, I’ll showcase a few features of CC3+ that helps you during play.

Continue reading »

Usually we make a map in CC3+, and when done, we export it to an image or print it, turning it into a static thing. This is required when we wish to use the map outside of CC3+, but it also takes away many fun things we can do with the map.
CC3+ does allow us to make really dynamic maps however, maps that change based on triggers in the map. I’ve already talked about a simple version of this in the article on Showing and Hiding Map Features, but let us take this much further and make a map with a large selection of interactive elements.

Now, before reading any further, I strongly suggest that you download the example map and give it a good try before reading further (requires DD3). Another much simpler example shows moving lights (Works without DD3).

Continue reading »

In CC3+, drawing tools are great timesavers. The basic functionality of a drawing tool is that it works as a preset that contains all the various settings required, such as line style, fill style, line width, color, sheet and layer so that when you draw using a drawing tool you don’t have to go around setting all of these manually like we did in the good old days. Drawing tools also have some built-in nice features like being able to draw two separate entities at once, being able to stay within the map border, and the option to easily edit an existing shape.

However, there is another very important feature that exists for drawing tools, and that is to attach macros to them. A drawing tool can contain an embedded macro which follow the tool and isn’t dependent on your main CC3+ macro file and can contain macros that work in tandem with what you draw using the tool, or even functionality that isn’t connected to drawing at all. Today, we’ll look at how to create these tools and have a brief look at how they can make things easier for us.

Drawing with Macros

If you have been making overland maps, you’ll probably familiar with the forest drawing tools. If you pay attention when you use them, you’ll note that they ask you to draw a smooth shape, and then fills this shape with trees after you are done drawing it. This is a macro drawing tool at work. What happens is that the tool itself is only set up to draw that forest background, but it also contain a macro that gets called when you are done drawing that calls the Fill With Symbols command to fill the area you just drew with trees. Let us make a similar macro that uses the Symbols in Area command instead. I won’t go into detail about Symbols in Area here, since this is about making a macro tool that uses the command, rather than explain the command itself, but if you need a refresher for the command, you can look at this article.

Continue reading »

A new version of CC3+ is available now, fixing a few bugs and preparing CC3+ for the next releases.

Version Notes

CC3+ Version 3.89
=================
– Fixed grids not aligning correctly to snap points
– Fixed drawing tools not displaying preview
– Fixed Common sheet not being selectable in sheet dialog
– Fixed TEXPORT, TFIND, and TREPLACE not showing dialogs

CC3+ Version 3.88
=================
– Fixed bug with wall-cutting symbols not working properly

A new update for Campaign Cartographer 3+ is now available. We’ve done a lot of internal work (small bug fixes and improvements), but also improved some user interface issues and added a convenient new feature.

User Interface

Bitmap fill styles will now be displayed in a much larger format in any of the dialogs. That makes it much easier to recognize or judge one of the many detailed bitmap fills available in the template you are working on.

New Command

Have you ever wanted to enlarge or shrink the area of the map you’ve been working on? The new “Resize Drawing Area” command (available from the File menu) will now make this much easier and quicker. Just type in the new map dimensions, and the map border and background will scale to the new size, without affecting any of the content you’ve already drawn. From there you can add new content and enlarge the existing features with the help of the editing tools.

You can download the update from your registration page. It is available among the CC3+ files on the Downloads tab.

Version Notes

Here are the version notes for Update 18:

CC3+ Version 3.87
=================
– Added SCALEMAPEXT and SCALEMAPEXTM commands to scale map template things (MAP BORDER, BACKGROUND, and SCREEN).
– Added TOGL and TOGLF commands to toggle visibility of a specified layer.
– Added JPEGOPT, DWGOPT, EMFOPT, and FCWOPT commands to allow direct access to save options for the major file types.
– Added SYMPTFILTER command to support point filtering on symbol import. This change may reduce artifacts for some kinds of symbol creation.
– Added LISTCMDS command to list all of the available commands in the system (main program and XPs).
– Changed internal image representation to allow for more efficient imaging operations.
– Removed some unused legacy DLLs to reduce disk footprint.
– ZOOMSEL command should work better than it used to.
– Fixed crash with hotspots in symbols when the layer for the symbol reference is hidden.
– Fixed XML parser usage to properly serialize boolean values.
– Fixed rename problem with sheets that could cause effects to be added to the wrong sheet.
– Fixed out of memory error that could happen with certain drawings.
– Fixed memory corruption that could occur when reading an invalid drawing tool file.
– Fixed memory corruption and possible crash when dropping text longer than 4090 characters.
– Now visibly rejects attempts to drop unknown file types onto a drawing.
– Dropping a picture onto a drawing while holding down the Shift key now allows rotating and scaling the image.
– Dropping a picture onto a drawing from a browser no longer generates an old-style image entity.
– Widened the drop portion of fill style preview combo boxes to make it easier to read style names.
– Updated PNG loaders to improve protection against certain malformed image files.
– Built with Visual Studio 2017. Some code elements should be a bit faster.
– MenuConfig utility now offers better support for special path characters (#$@) in file names.
– Options button on Save As will respond better on higher-dpi displays.
– Floating prompt now displays better on higher-dpi displays (has a different visual appearance as well).
– Traveller sector importer now handles the new-style Traveller 5 sector file format.