Not as long as it is attached to the drawing. That embeds the palette into the map itself instead of relying on the external palette file.

But you can also keep it around under a new name, and then manually load it using PALLOAD if you ever need to.

No, there isn't any way of exporting the functional links, the index only becomes a text reference on export. Remember that CC3+ really just support exporting to image formats, and none of those have any support for interactive elements themselves.

I guess it would be possible to export the hyperlinks as some sort of list of coordinates if someone felt up for creating an XP module for doing that, don't think that would be really hard, but again, that couldn't be used just as it was, it would need to be imported into some other program that supported interactivity.

Keep in mind that line styles, just as fill styles, are on a per-map basis. It is not something that gets installed globally. This means that if you see a random option in the line style dialog or not, depends on if the template you started that had from had such a line style. It is not dependent on installing any particular annual or other product. These installations will never change anything in existing maps regarding line styles.

I have files from the CC2 era with this line style in them. (Check @Tutorials\UserManual\Selection.FCW)

The map have now been added to the atlas. Thanks for the contribution.

Note that CC3+ do also have non-drawing entities that you can't find in the drawing window, but still lives on a layer and blocks it from deletion. Map notes are one example that comes to mind. And there is no user-facing UI to figure out which entities these might be.

Well, since the map is 40.5 hexes tall, you can try to export it setting the height to 2025, just set the width to something ridiculously high, like 10000, and then make sure the crop image to aspect ratio is checked, this way the width will end up being whatever it needs to to fit the specified height.

This should end up with a file that is 50 pixels for each hex, measured by the hex height.

The issue is probably the #-character, which refer to the installation directory, you want the @ which refers to the data directory, like this:

#27,@Bitmaps\Icons\CONS.bmp:[Construction sheet/layer]{}|MCONS;

(@ was new with CC3+, which means older instructions use # because everything was in the install directory then)

And yea, you also need those number suffix files, those are for different toolbar sizes.

Great work. I am also pretty certain that none of my players have above 12 INT, because they suck at puzzles. But what about the characters? They just as bad?

It's a nice map, but I think the Ironfist Mountains look a bit sparse right now. Unless it is the intention to have a spare mountain range, I would recommend placing the symbols closer together, making it more dense. Don't be afraid of some overlaps.

If you have your old drive (you said it was a motherboard issue, so I would assume you do), all your old font files are safely tucked away on x:\windows\fonts on the old drive (where X is whatever drive letter it might end up with) and can just drag them into the fonts folder on the new PC.