I found an issue right away when I tried running/installing the ARE checker.
The TP2 code responsible:
// ensures are regexp search doesn't die COPY_EXISTING ~ar0087.are~ ~override/xr2400.are~ ~ar0087.are~ ~override/xr2600.are~I've cleansed my install of unused areas, thanks to NI's help, so neither the XR* areas or the AR0087 area exist. I have them extracted to a special backup folder and removed from the KEY index so I don't have to deal with them in my general editing.
Now I may be the only person who has done this, which would be par for the course. Regardless, I suggest checking for the presence of XR* areas first, and for the presence of the area you want to override them with. In my case it was a simple matter of commenting out the two lines, after which the area checker ran beautifully.
The other checkers ran great. I see what you mean about Map Notes. Bioware apparently updates the offset in memory if the user adds new notes, but otherwise leaves it 'floating' so long as there are no notes present. NI is flexible in this regard by not showing map note structures if there aren't any. Your checker could do the same by checking the map note count first, and then only worrying about the offset if there are map notes present. As it stands, all reports for areas with no map notes are non-issues that clutter up the logs.
Thanks again, I'm off to read the logs and check files.