The only thing the EUD antihack catches now is the lowlatencyhack, and it's quite a bother really. And centerloc at the beginning, and beginning crashes as a whole are quite nonsensical, because I can turn maphack on at any point in the game later on... Sooo... Not much you can do anymore.

I was trying to detect fog of war as an anti-hack method. It was going well because I found the Minimap.cpp and the addresses changed when I used the map hack. Because the location of the Minimap.cpp changes every game it will be impossible to use this method.

Minimap.cpp is a debug string and doesn't change.

Then how come every game when I search for "minimap" in artmoney, the address changes every game. It comes up with three results. The first one, I think, is the terrain, the second one is the fog of war, and I didn't look at the third one.

Because that's how a Storm handle is created. It stores the line number and file name for that handle when those parameters are passed.
Example:
void* minimapHandle1 = SMemAlloc(mapHeight * mapWidth, "Starcraft\\SWAR\\lang\\minimap.cpp", 1636, 0);
Allocates width * height bytes with a default value of 0, stores the pointer to the data in minimapHandle1. This would probably be seen in Starcraft\SWAR\lang\minimap.cpp on line 1636 of the Starcraft source code, with different variable names of course.

One instance is a Handle for "game\blink.grp" from the MPQ archive.
Two others are the size of width * height. Minimap data.

It's like I said in an old Anti-hack topic a while back, in order to beat these hacks, you need to look for their effects, not the hack itself. When I posted that, it was because of the hacks updating and the EUDs becoming useless, but now it's even more true, since Oblivion now blocks EUDs detecting its presence, if we can detect the visual effect in SC of the map hack, then we can beat every new version that comes out of Oblivion, and it should take Zynastor quite a while to figure out a way around that one.