Lord_MiL
10th September 2002, 23:09
Hi all!
Well, I found this post in which some guy who claims to be a networking guru (really he doesn't seem to know jack, but that's beside the point) claims to have talked to a rep from blizz who told him how they are detecting maphackers:
http://www.theinclan.com/phpBB2/viewtopic.php?t=901
Check it out.
From what I can tell this is NOT how blizzard is detecting the maphacks. There are lots of maphackers still out there who haven't been caught and certainly some people who have not maphacked and have been banned.
IF however, this turns out to be how blizzard is catching the hackers, I think I *might* have a possible solution. If anyone here is experienced with coding/programming maybe you could help me out with this. Would a loader program solve this problem? Obviously this built in software is detecting when an outside program writes values to WC3's memory. So, if we write the maphack as a loader that loads the .exe into memory and alters the code in order to reveal the map right then, then this app wouldn't detect it, right?
Just a thought. Please read this above. I'm gonna go do some testing to see if this is feasible!
UPDATE:
Just in case they really are running an extra app that watches to see if any program pokes values into WC3's memory while playing on bnet, here is my suggestion:
Run Warcraft 3. AS SOON AS it is loaded, run the maphack and hit 'reveal map' this will poke the maphack code into the game. Close the maphack then log onto battle.net and play.
This way nothing edits your game while you are on battle.net. This would keep their detection from working IF it really works the way the guy above claims. Of course we don't know for sure how it works so you might still get banned :-)
Well, I found this post in which some guy who claims to be a networking guru (really he doesn't seem to know jack, but that's beside the point) claims to have talked to a rep from blizz who told him how they are detecting maphackers:
http://www.theinclan.com/phpBB2/viewtopic.php?t=901
Check it out.
From what I can tell this is NOT how blizzard is detecting the maphacks. There are lots of maphackers still out there who haven't been caught and certainly some people who have not maphacked and have been banned.
IF however, this turns out to be how blizzard is catching the hackers, I think I *might* have a possible solution. If anyone here is experienced with coding/programming maybe you could help me out with this. Would a loader program solve this problem? Obviously this built in software is detecting when an outside program writes values to WC3's memory. So, if we write the maphack as a loader that loads the .exe into memory and alters the code in order to reveal the map right then, then this app wouldn't detect it, right?
Just a thought. Please read this above. I'm gonna go do some testing to see if this is feasible!
UPDATE:
Just in case they really are running an extra app that watches to see if any program pokes values into WC3's memory while playing on bnet, here is my suggestion:
Run Warcraft 3. AS SOON AS it is loaded, run the maphack and hit 'reveal map' this will poke the maphack code into the game. Close the maphack then log onto battle.net and play.
This way nothing edits your game while you are on battle.net. This would keep their detection from working IF it really works the way the guy above claims. Of course we don't know for sure how it works so you might still get banned :-)