This bitmap isn't really intended to be used as a main background, rather it is meant to be used with drawing tools to draw patches of heath on top of your terrain background.

One limitation with CC3+ is that fills can't be categorized. So the background fill picker in the new map wizard will simply show all the bitmap fills available in the map, it has no idea which fills are suitable and which are not.

I can't remember if there is a better way off the top of my head, but you can control the number formatting pretty well if you do it manually, like in my simplified and overly verbose example here:

MACRO TTT
GV a 1/7
GN b a*100
GN c a/100
GV d a-c
GN e d*100
GL out Your values
APND out 
APND out Original: 
APND out a
APND out 
APND out Formatted: 
APND out c
APND out .
APND out e
APND out m
MSGBOX Message;out;
ENDM

Sounds good. Have fun. Add cats.

It depends a bit on what you did. If you just clicked :CC2SYMPATH: you should be able to click it again to toggle style.

Maps should also set the correct filter on load (commands in the OnOpenMacro map note), so simply reloading the map should normally reset the filter to the right one.

If it doesn't, make sure you haven't actually edited the global master filter definitions. If you right click the :CC2SYMPATH: button and pick master filters, you get to the edit dialog. You should then be able to load the appropriate list by hitting the load button. (You should check the map macro first to see which setting it is trying to load) and then make sure the first entry in the list is correctly set as CA177. (It is normal that the second entry is CD3 Bitmap A)

You can't have the macro in a separate file, it needs to be in the main fcw32.mac macro file found in the CC3+ data directory (Not the installation directory from your screenshot).

Technically, you can have it in a separate file, but that means loading the file first with LOADMAC, but that isn't a very good idea since that causes the main macro file to be unloaded, and CC3+ relies quite a bit on that one.

Macros can also be stored in separate files if you load them as script files (*.scr), these can then be run directly with the SCRIPT command. Script files only contain one macro, and should not have the MACRO and ENDM lines at the start/end, but are otherwise the same.

I think such aids is best left as an exercise for the watcher to create. And I'll probably put it on VHS tape to make jumping around in the video more interesting.

Enjoy

One note though, remember to clean out the export folder manually after each export if you do this. The export script assumes that the TileExport folder is empty before each export.

Are you one of my students?

Thanks. I am a bit behind unfortunately, you may have noticed I haven't been able to push out all the competition maps yet. I think these are first in Queue after the competition maps, but some of the competition maps have forced me to do other areas just to have the location they go.

It's not more maps that is is needed, but the fact that many competition maps were set on overland maps that were developed at the same time, meaning I had to also process those overland maps before I could process the competition maps, leading to a delay in processing competition maps due to extra work needed up front.