Oh, and to save you a click on the explode button, you can configure a symbol to automatically explode on placement, although this option is not compatible with the multi-sheet option for symbols.

Mennidas' linage is now in the atlas. Thanks for the contribution Quenten.

Turn off snap (lower right corner) when working, this allows you to place nodes right outside the map border, and let the functionality that restricts it to the map border kick in.

With snap on, you are basically just placing nodes at the edge, but not over it, so it treats it as a regular corner. Note that you can achieve this with snap on too, but you need to move your cursor much farther out from the edge of the map to hit the snap points on the outside and not those at the border itself.

Yea, this particular article was written with the intent to hide things that are "outside" the structure.

When it comes to your house, that's a very tricky thing if you let the players have access to the entire map, as that clearly allows them a different view than a person there would have, and instantly reveals things like too-thick walls or suspicious corner. I would be tempted to give the players a modified version of the floor-plan, where the rooms are slightly larger, maybe the house slightly narrower to hide such thick walls. Only if they actually start measuring things should they be given the true map so they can see that there is something wrong here....

Of course, some players may call foul on such an approach, feeling mislead. And it also means preparing two maps instead of simply hiding something.

For reasons like this, I usually never let the players see the entire dungeon. I practice hiding everything they can't currently see. (Using MapTool hooked up to a projector)

Maybe you could write a blog article about the process and your thought patterns some time?

There isn't a setting for a default save location, but it should be remembering the last folder used.

For a workaround, you can also use Windows' only features, such as pinning a folder to quick access or making a library, since these are easily accessible from the save as dialog.

Looks like your current map is in the basic CC3 dungeon style. That style doesn't have additional catalogs, as it is just a vary simple preview style for dungeons. All symbols are in the symbol catalog being loaded with the map, the one currently in your symbol catalog window.

To save everyone's time, I'll just point out that I cannot accept maps that rely on custom artwork in the atlas. Details here.

You seem to have made a mistake when you drew your lines. If you followed Sue's tutorial, all your lines should end in that point in the middle of the circle, but it looks like you have drawn them so each line goes through the center and out the other side.

So, when trimming them, you are not just removing the part inside the circle, but the part that sticks out the other side. So when you get halfway round the circle, you don't have any more lines to trim (there is just a white remainder there that will go away on the next screen refresh).

You need to ensure that your lines end in the middle. You can do that with the :CC2SPLIT: command, but it is probably easier to just redrawing them, after all with the circular array, that's just a few seconds.

Sounds like an interesting, but also very difficult project. A CC3+ map is just a few bits of text really (stored in a binary format) that describes the layout of the entities in the map, so that means that unity would basically need to implement the full render from CC3+ to be able to turn that information into a visual representation of the map.

Lee started talking about the .fcw file format here. Unfortunately, he never finished the job: