Talking a bit with Joe here, it turns out that the problem is with the api from travellermap that we use with the importer.

If you look at the metadata for your sector, you see that travellermap simply do not give us a color for the sectors at all:

# Other
#
border 0107 0207 0307 0406 0506 0605 0606 0507 0407 0308 0208 0109 0108 0107

# Other
#
border 1821 1921 1920 1919 2019 2119 2219 2319 2418 2419 2420 2521 2522 2421 2322 2222 2123 2122 2021 1922 1821

# Other
#
border 1201 1302 1401 1501 1601 1701 1601 1502 1402 1303 1203 1202 1201

Normally, the color should be last on the the line for every border entry, and this is where the importer finds the color to use. And without travellermap providing us with a color, CC3+ defaults to white.

Here's an example of another sector which do provide colors correctly, notice the color names at the end of the border statements, after the coordinates:

# Plavian League
#
label 1814 Plavian League
border 1412 1512 1612 1712 1811 1911 2010 2011 2012 2113 2013 2014 2015 2016 2017 1918 1818 1718 1617 1616 1615 1614 1514 1413 1412 hotpink

# Renkard Union
#
label 3033 Renkard Union
border 3029 3129 3128 3227 3226 3227 3328 3329 3330 3331 3332 3333 3334 3335 3235 3135 3034 3033 3032 3031 3030 3029 red

# Swanfei Free Worlds
#
label 2721 Swanfei Free Worlds
border 2520 2619 2618 2718 2817 2918 2919 2920 2921 2821 2722 2621 2521 2520 white

I have no idea why travellermap doesn't give us the color for your sector, as there are clearly colors on the visible map.

Each sector is a polygon though, so it shouldn't be too time consuming to just change colors in CC3+ after the import.

I am unsure why it is happening, but it does seem like it is a problem with translating the colors from the website into CC3+ colors, so they all end up at the default. I couldn't get it to behave myself, so I've asked those that knows more about this than me to look at it.

But, I did notice that if you use the "generate script file" option from the import dialog, you get a script file you can run to make the drawing. And the advantage here is that this is a text file you can edit. The first part of it is all the polys for the borders, and you'll noticed they are all prefixed by a COLOR 15 statement. You can then simply edit these, changing them to other color numbers, and then run the script file from inside CC3+ (Tools -> Macros -> Script File). You'll be editing a little blind since it is difficult to envision the look of the polygon from these candidates, but at least you can just keep the script file, tweak it, and re-run it....

If a command seems stuck, it can also help just hitting the Esc key a couple of times.

CC3+ should handle negative numbers just fine, just make sure there isn't an extra space between the minus sign and the number.

Also keep in mind that you have two options when typing coordinates.

Either you type the destination coordinates outright (112,45 or 112,-45 etc.), and in that case you don't use negative numbers since all the coordinates in the map are positive (except some special templates)

Or, you use the relative coordinates for a relative movement from the move origin, in which case you prefix with @ and negative numbers means downwards and leftwards (ex @10,20 or @-10,20 or @-10,-20 etc.)

You can use the TRACED command to trace it automatically, but you do need to make a small config file change to work around a bug in the current version.