Just for the sanity check, I assume you have tried restarting CC3+, as well as also trying with a new map.

There are situations where a command can "hang", but restarting CC3+ should take care of that. Do you experience similar issues with other toolbars, or just the Source Maps ones?

As for the buttons not having any tools, these tools are connected to the style of your current map. So if you start a new map in say Dungeons of Schley, it is quite natural that the park button doesn't have any tools, because there are no tool sin that style named "Park". These buttons are actually just filters, that show all the tools belonging to the current style that matches the filter set by the button. The Park button from CIT is unlikely to produce any results with most styles except the SM Cities style map itself since it is a specialized tool made for that style (which is also why the Park button doesn't normally show up, only when you switch to that add-on. It is possible to change your map to fetch tools from another style, but you're unlikely to actually want this as their visual style aren't designed to mesh well with your current map, whatever that might be.

This is a very nice map.

I guess you are using it for a battle-map though? Personally, I am not too fond when everything lines up with the grid, but that is often a tradeoff when you make battle maps, since it makes things much clearer for combat purposes.

I am not sure what you mean by "terrain" in this context, but there is no way to embed images into a drawing, none of the official ProFantasy art is embedded either.

What is normally done is to either store external images in a subfolder in your CC3+ data directory, because you can then refer to it in the map using the relative @-indicator in the path. For your own custom artwork/images, you can also store it in the same directory as the map itself, and then use the map-relative identifier ($) in the image path to refer to these resources, that way, you can keep everything in the same folder and it will continue to work no matter how much you move it around, as long as you always move the entire folder with map and artwork together.

Great looking map.

Do note that while the image size in posts are limited, you can upload much larger images in your gallery if you want to show off a high-res version.

For CC3+, there will not be much of a difference between those two. A lot of operations in CC3+ are single threaded, in which those two score pretty much the same (but about 50% better than your old one).

Some processes, like some effects do take advantage of multiple cores, but it is unlikely to fully saturate your CPU, so even if the 7700 is better, I doubt you would observe much difference between them. But the 7700 do have two extra cores that can work on other things the same time as CC3+ works though, which can be an advantage.

There shouldn't be a max limit, but I have currently set it to 25 images per page so people with slower or metered connections can still use the albums without having the entire internet thrown at them at once.

But I noticed that the gallery page itself seems to lack page navigation controls, so everything beyond the 25th gallery get hidden. Seems like something the coders of the gallery plugin forgot about and nobody noticed before now. All the galleries are there, but they're not accessible. I'll try to figure out a way to fix it when I get some time.

She's is preparing to become a proper Catographer.

Unfortunately, it doesn't support ranges.

Maybe doing selections by name instead will help? (It's a bit down the page in the article)

Yes, you can just copy stuff over from one CC3+ data directory to another, including symbols and drawtools and anything else in there. Just make sure you don't overwrite something you didn't intend to. But unless you have messed up your old data directory somehow, and you are running the latest update, most files should be the same anyway.

The only thing to be aware of when it comes to custom stuff, is the question if you made sure to always use relative paths. Of course, if the locations are exactly the same on the new PC it doesn't matter, but if they aren't, you may end up with some red X's if you have used absolute paths in your symbol catalogs and such.

Autosave deliberately save to a separate file to make sure to not accidentally overwrite your actual map file with what is perhaps unwanted changes, for example when testing things.. This is how autosave works in most software. I guess a more correct name would be "recovery save" or something like that, but autosave has just stuck in most software as the common term. It is not a replacement for manual saves, just an extra layer of security, so yes, you should always manually save before exiting. (Personally, I have autosave on, but the dialog off, so it autosaves silently in the background, which is what most other software does by default)