@Quayuazue Ok, done.

As long as you haven't actually changed your font in the .fcw, you can just use Info -> List on the text entity, and see exactly what font it is. Doesn't matter if it is currently displaying in a replacement font.

I might have a chance in the wits category, but the steel is going to get me every time.

Great map, but I did wonder a bit where the large lake in the middle of the largest island was getting it' water from.

The macro in itself should be fine, except that there shouldn't be a period after the macro name.

But you really shouldn't be using the Load Macro command, that unloads all the standard macros which is bad. If you develop a macro for personal use, put it in the main macro file (keep a copy somewhere though, an update may replace that file) and you have it always ready for use.

Of course, you cannot distribute macros this way with the community atlas. All macros need to be in hotspots embedded in the map (Tools -> Macro -> Make Hotspot). Note that these hotspots are like regular macros, but they don't have the MACRO/ENDM lines

Keep in mind that for the atlas, I prefer to keep information toggle macros in the map navbar (Which I add after receiving the map). Download the .fcw of this map in the atlas for a sample map with lots of toggles in the navbar (you may get red X'es if you don't have the right add-ons, but you should still see the navbar to the right just fine). What I need to build that is a list of the macros you need in the map. And keep in mind that each macro should be used independently and in any order, so you need to take care that each macro hides all the sheets that isn't required for that view, and show all that is.

Even if you are in an overland map, you can still just open the various symbol catalogs from City Designer using the :ICON_CATALOG: button. You can also use the drawing tools from CD3, but this require you to import the fill styles from the city map into your map.

BUT, I do not recommend this. Trying to draw a tiny village on an overland map generally just looks like a mess when you zoom out and view the whole map. It may work if the map is something like a small island with a village or two on it, but it doesn't work very well if the overland map is any greater scale than this. Remember that a properly scaled house on an overland map would be TINY.

There is also the issue of performance, if you try to map out a lot of tiny villages on your overland map, you are adding A LOT of extra entities to the map to do this, which can lead to poor performance if you take this far enough.

You need to change to a more macro-friendly selection method.

Personally, I love to use selection by layer (SELBYL) since that means you don't have to go for specific coordinates in the macro. Just make sure the hotspot is on the appropriate layer, and don't put anything else there.

Remember to reset the selection method when done. Usually best to save it with SELSAVE, and restore it a the end of the macro with SELREST

Try now, it should be fixed, it was some missing permissions.

As for deleting thing, users can delete their own comments, but not threads. This is because a deleting a thread would also mean deleting any comments in it, which may belong to other people. This is Vanilla's own reasoning for why the system is like that, and not an option I can toggle.

Hi there, and welcome to the forum.

That's a great map for a first map you've got there, well done.

That priority is the Sheets. The order of the sheets in the dialog is the drawing order, so if something is on a sheet further down the list, it will drawn after, and therefore on top of, things higher in the list.

You can always move things like the swamp to another sheet using :CC2MCHANGE: after you have draw it if it isn't on the sheet you want it to be. The drawing tool places it on it's default sheet automatically, but you can move these entities around as you want.

By stickers, I assume you mean symbols? You can always change the scale of a symbol before placing it by right clicking inside the map (with the symbol at the cursor) to get the symbol properties dialog, or you can hold down control and move the mouse up down to change the scale visually. You can also set the default scale from the :CC2PRESETS: dialog, this is the scale it will use when loading the map, or hitting set defaults in the symbol properties dialog.

The fact that you are wanting to reduce the size of this leads me to believe that you might be attempting to draw a bit too detailed map. You should always be carefull how detailed you make a map, for several reason. Reason 1 is simply performance. Every entity you add to the map is another thing CC3+ needs to keep track of and draw. CC3+ isn't like a bitmap editor where you just change the color of the pixels, but the performance is the same with a blank image as with a pattern-filled one. Trying to add to much detail also makes the map look very cluttered and unreadable when you try to zoom out to look at the overview of the map. The second reason is mapping fatigue. Trying to map out a large map in very tiny detail is extremely time-consuming, and most people who have attempted that burtn out long before they get clode to finish. I allways recommend keeping the detail level at a reasonable level, and instead make additional higher-detail regional maps of the more interesting regions, rather than tackle everything at once. Kind of like we are doing it in the community atlas.

Sounds like your map size is perfect. If you want it to be 6000 by 3800 km, then 6000x3800 is the correct values for the dialog when you started the map. You'll always want the number of map units to match the actual real-world size of the map. If you used those numbers, you shouldn't resize anything, since it is already correctly scaled.

If you don't like the scaling of the fills, change the fills. You can do that from the fill style dialog, just click the fill style indicator in the top right, go to the bitmap files tab. select the appropriate fill, and change the value for scaled.

If you need to change the sheet an entity is on, just use :CC2MCHANGE: on the entitie and put it on the correct sheet.

Edit: Seems I took a bit of time writing this, got ninja'ed by 3 comments :)