And here's the map in the atlas. Thanks.

And now processed and in the atlas. Thanks.

Unfortunately no. The dialogs are implemented using the dialog from the standard windows libraries, which do not have support for easy user-resizable dialogs.

Maybe they'll be bigger in a future version. They have been increased over the different versions, but that only leads to people making up longer names :)

They're not approved for the atlas.

The main reason for this is that they lack proper CC3+ integration and symbol catalogs, meaning that while they might be free, it is hard to use them in a consistent manner that will let other users use maps with these symbols in them.

Wyvern is correct here. Basically, anything you can do with a symbol inside CC3+ is completely fine.

You're only running into problems with the atlas if you are doing anything to the actual .png files on disk, which includes copying, moving, renaming or modifying them. Also, if you import images as symbols into your map using the Import pngs command, you can only import images from atlas-legal sources in their original location, and make very sure NOT to check the "create other resolutions" or "copy to folder" options while doing so.

Thank you. I'll add them after the competition ends. Please remind me if I forget.

The axial tilt is 25 degrees.

I haven't noticed this before, but it does seem that something weird happens to the hyperlink if you change text properties on it using the change properties dialog. I've reported this to the developer.

For now, I recommend being careful with change properties and make sure only the text is selected and not the hyperlink (You can always make hyperlinks temporarily visible from the View Menu)

You should be able to make new ones though, at least I was able to after reproducing your issue. Just make sure to draw the hotspot properly around the entire text to link, the hotspot is a separate rectangle, not actually part of the text.

The menu_recovery.bat is a file installed by the various Vintyri-addons (CSUAC, Dundjinni Archive, etc) and is intended for use with those products.

I asked about the anti-virus because some of them can be a bit eager locking the files while they scan, preventing legitimate access long enough for a program to error out, but at this time, it was more of an exploratory question rather than nailing it as a culprit. It could be the issue, but it might just as well have nothing to do with it.

It is hard tracking down the problem, but it doesn't really seem Vintyri-related. The Menu_recovery.bat calls the standard CC3MenuConfig command, and based on the text in those error messages, it seems like a lot of errors are thrown from the "default" pass where it process the official CC3+ menu config file (Menu_recovery.bat first does a run to process the Vintyri-provided file, then finishes up by the standard PF one.)

But if it works for you after manual editing, I guess that is at least an acceptable workaround.