I've never seen errors happen before when running the cc3menuconfig program, but there are some interesting observations there.

First of all, the instructions, which are visible along with the errors clearly indicate that all menu files be processed (*.mnu), but as seen from the errors, only a selection of the menu files generate errors (AAT, Per, CA, dioramas, dungeon), while others that I know for certain you would have (like fcw32 and city). I assume these are processed without errors since they don't appear.

Now, errors on some files and not others tells that there are most likely something weird going on with your install. I could think of a few possible things, one being that the file system permissions on those files are off, simply not allowing you to modify them. The other is that those files might be corrupt in some way.

File system permissions should normally be set by the CC3+ installer/updater, but it is worth having a check. Try opening up AAT.mnu in notepad (making sure to NOT use the "run as administrator" option. Can you open it at all? Do it look like a menu file (i.e is the contents similar to fcw32.mnu). Make a small minor change in the file like simply editng the spelling of "right" on the first line and try to save the file. Are you allowed to simply save it, or do notepad pop up the save as dialog even if you tried a standard save?

Did you also apply the color key effect to that sheet?

You can create cut-outs on as many sheets as you want, but there are a couple of things to check

For each sheet with a cut-out:

• There must be the color key effect on that sheet, and the color key effect must be the top effect in the list of effects for that sheet
• There must be a polygon in the cut-out color on that sheet, and that polygon must appear on top of the things you wish to cut
• And of course, the things to cut must also be on that sheet. Even if you set up the effect and poly correctly, it won't do any good if the entities to cut is on the wrong sheet. It only cuts things on the same sheet.

In simplified terms, the MERGE layer has id 0 internally in the software. What happens if something tries to go to a layer that doesn't exists, it will default to 0. Can be avoided by having the expected layers in the map.

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.

Well, you can still submit it to the competition if you plan to make a regional map later. There are several other participants submitting villages from yet-unfinished regional maps. Nearly a full day until the deadline.