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.

When you save a custom pal, it saves a file called fcw32.pal in your CC3+ data directory. If this file is present, ALL maps that doesn't have an attached palette will use this instead of the default palette. So the solution is to delete or rename this file, and CC3+ will revert to using the default again.

Sounds like a good approach to the problem to me @Alberto Giuffrida. Would be nice just having a simple script to run that can be distributed without having to distribute copyrighted material.

Check that you haven't disabled Hotspot under Tools -> Options -> Links and Hotspot are active.

You might also simply not be increasing it enough. Keep in mind that when exporting to an image, you take a very high-detailed setup in CC3+ and tell it to squeeze it in to a limited number of pixels. This means something sometimes have to give and give up some of their pixels to other elements in the map. An line can feel plenty thick in CC3+ itself, but when competing with the rest of the map for those precious pixels, it may still be too thin for export.