I'd say that's up to you.

My general "rule" for the atlas is that if you map a feature, it needs an appropriate symbol on the parent map to be linked from, no placing something in an empty spot on the map just because it could conceivably be there. If no such symbol exist, an appropriate intermediate overland map needs to be made. Same for a map of a single place inside a settlement, a floorplan map shouldn't be linked directly from a city symbol on an overland map.

However, in this case, there is already a tower symbol on the overland map, so I have no issues linking your tower directly to this one. But if you want to make intermediate maps, be it overland and/or settlement that is great. After all, there is no rule to say there can't be a settlement around a tower, a symbol is often used to show the most prominent feature of the place after all.

AA in itself can't really be the issue. All turning on AA does is making CC3+ export a slightly larger image than requested, so the imagemagick processing after export can generate AA by reducing it down to the requested size.

Now, what I did notice is that when I export at 5000x5000, it is completed in a single pass, but if I bump it to 33% antialias, the resulting size increase leads to a 2-pass operation. Is that what you see as well?

My suspicion is that something weird is happening with the color key with that gigantic entity, but in this case, because turning on antialias forced it to become two-pass, it became divided over two smaller ones instead which was then handled correctly.

I think that's because those images are using the wrong relative reference. They are using the #-reference, which means the CC3+ installation directory, instead of the @-reference which means the CC3+ data directory.

Try running the FFIX command first before running my command again.

If you need to know exactly what is from which add-on, you can use the IRD command (D stands for Detail).

And that cobble fill is some weird reference that turns up in some templates.

Ah, yea, you need a newer build of the dll file too.

I've uploaded an updated zip with a new dll file too. Remember to close all instances of CC3+ before replacing it.