The orange line is the roof ridge for that style (It looks better when you zoom in much further). The reason it sometimes seem to disappear when you zoom out is that it simply becomes to narrow. Your screen only have a finite amount of pixels, and when something gets thinner than a single pixel, a decision will be made if that pixel should be displayed or not. Being less than a pixel, if you use a pixel to display it, you take away space from something else, so showing everything is simply not a technical possibility.

The same is the case for exports. A sufficient high res export may have more than one pixel available for each ridge, eliminating the problem, but generally, every export will have it's limits, just how images work.

My players would murder me. They're terrible with number puzzles..

Embedding should work fine as long as you give it a nice clean Twitter link to the tweet:

Make sure to only use it on maps/templates though, and not on symbol catalogs, since a symbol catalog by it's very nature is a collection of symbol definitions that aren't being used anywhere.

Looks nice, but that road in the top right part looks a tad to compass rose straight. Would look a bit more natural if both that and the bridge was on a bit of an angle.

The oasis is now found in the community atlas. Thanks for the contribution and welcome to the atlas.

Your roads are a bitmap fill style, which means it should show up on the Bitmap Files tab in the fill style dialog. And you can use Info -> List on the road to find the exact name of the fill from the dialog if required, then from the dialog you can find the file name and path, if needed.

As long as the image file is installed by an official product, and it lives in the CC3+ data directory, it is ok. If it isn't already a symbol, be careful when making it into one though. If it doesn't already have the four different resolutions (_VH, _HI, _LO, _VL), DO NOT tell CC3+ to create them when importing as a symbol, as that would change the image name, resulting in something only you have. Image files must be used exactly as they were installed by the product.

Setting up a linux machine to run CC3+ is just a matter of installing linux, installing wine through the package manager for that linux distro, and then simply install CC3+ as you would on windows (Wine should associate itself with .exe files, allowing you to run the installer easily).

CC3+ should run just fine on any distro (as long as it is recently new/up to date), most of them contain Wine for installing through their package manager (if you manage to find one without easy access to wine, then it would be unsuitable). Personally, I recommend users just use the distributions they are familiar with (and if they aren't familiar with any, I wouldn't recommend they go ahead. Using CC3+ on linux is a good enough option if you already use linux, but if they don't already have a desire for using linux, taking on the effort of learning a new OS for no good reason isn't sensible, and there are some quirks with CC3+ on linux as well)

Generally, CC3+ works just fine on linux, the main issue I've had is that fonts doesn't render the same size as under Windows. This isn't a huge problem when mapping, but it is a problem if you plan to share .fcw files with Windows users (for example if you wish to download an .fcw from the atlas, or contribute one). See the Wine AppDB

Don't use the line tool if you want filled entities. Remember, CC3+ is a CAD-based drawing tool and is all about the entities, it isn't like a painting program where you can just flood fill any area that looks enclosed, you need to have an actual entity wherever you want fill.

Use something like the :CC2POLY: tool instead. (And make sure line width is set to 0 when you draw it, otherwise only the outline will be filled.)