That bow of yours isn't quite right. It isn't solid deck there. Here's a nice image from below from a 3D-model reconstruction showing a nice view of the area: https://cdn1.epicgames.com/ue/product/Screenshot/ScreenShot00002-1920x1080-f0bde8cb76a0de8cd4b3f512f0091aeb.png?resize=1&w=1920

This ship uses a lattice of planks, many other sailing ships just use a rope net.

See more images here:

Yes, delete it, it is just leftover construction aids.

Generally a nice map, but I am not really sold on depicting the frozen ocean like that. It doesn't really look like an island in a frozen sea, but rather a huge landmass with a weird-looking mountain formation on it.

What makes it even more weird is the existing neighboring map which uses that fill for the frozen edges covering the actual landmass, i.e. not frozen sea.

Assuming an earth-like climate, which is the basis for Niberium, the island is also much to far south to have permanently frozen sea around the island, it's going to be clear most of the year, which then makes it a bit weird IMHO to depict the oceans in a frozen state, as a map is supposed to be usable year-round, but now it only shows a very limited snapshot in time, because even at times where it is frozen over, the edge of the ice will never bee in the same spot week to week.

Sorry, but it appears @Don V Anderson Jr. had the better guess here.

The full path of the missing image is D:\CC2\Atlas\FR\Work\HWScan\30042 Golden Mosque 2.bmp. The file name indicates it was a reference image used when working on the map.

The result you're getting is simply the image being in a format not used in CC3+ anymore, and the converter converts this to a plain polygon, and you are then seeing the specified fill style take effect (Everything in CC3+ has a fill style, although depending on the entity type, it may not normally have any effect, like on images)

As for raster fills, they were supported back in the CC2 days too, that fill you're seeing there is the old stone fill from back then. It only supported .bmp format though, and lacked proper scaling options.

It is a limitation of the Symbols Along command. It is really only made for handling a single path at a time, but the single pick option doesn't play nice with macros, so the macro version need to use the regular selection option instead, which also has the side effect of letting people pick more than one path even if the command itself doesn't support it.