PyroKid
Member!
Please don't post any more questions asking if MapHack is detectable because it is all right here.
There's been some contraversy over MapHack being detectable or not. Or more specifically, if viewing other's items is detectable. Here's the answer: NO!
But that's not all I'm gonna say. Here's why it isnt detectable:
When your client enters the game, the server sends a barage of data to the client telling it all the information such as who's in the game and which mapfile to load.
One of the packets tells the client what a player is wearing. Without this packet all players would look naked (with their original clothes, not completely naked you pervert
). Here is an example of that packet:
Your diablo client receives a variant of that packet and parses it once for every player in the game. Your diablo client saves that in a very long array of variables for easy access. When you press Install on maphack, a long procedure takes place. One of the things it does is finds and identifies the address of that array and redirects it to go through maphack first. Now maphack knows what everyone is wearing.
Another thing is that when someone takes off or changes one of there clothes, it lets everyone know so the clients can update the player image with the new piece of clothing. Along with the player image changing, the item array changes as well. Now maphack knows again exactly what the person is wearing.
The reason that maphack can't see what's in the actual inventory (charms, tomes, scrolls, etc) is because your client doesn't need that information to update the player image and therefore the server doesnt send it. Most people don't know this, but when you press "0" on the number line at the top of your keyboard, your client does nothing.
When you press "0" on your keyboard, the keydown function gets captured by maphack and when the value is checked, maphack finds out that the number "0" was pressed. Maphack tells the client to execute the open inventory function, and then tells the client (using dll calls, not packets), what to fill in for the body parts. Everything that you can see when you look at the player on the screen is shown in the inventory now.
There! That's how maphack's view other's items feature works.
However, some parts of maphack are detectable. Here they are:
There's been some contraversy over MapHack being detectable or not. Or more specifically, if viewing other's items is detectable. Here's the answer: NO!
But that's not all I'm gonna say. Here's why it isnt detectable:
When your client enters the game, the server sends a barage of data to the client telling it all the information such as who's in the game and which mapfile to load.
One of the packets tells the client what a player is wearing. Without this packet all players would look naked (with their original clothes, not completely naked you pervert
). Here is an example of that packet:Ok so now you're saying "That's all just crap, but what does it mean?" Well it's telling the client exactly what the player is wearing. Think of it as 10xSimplified 9d packets crammed into one piece of information. Each body piece must be accounted for along with it's stats.
Your diablo client receives a variant of that packet and parses it once for every player in the game. Your diablo client saves that in a very long array of variables for easy access. When you press Install on maphack, a long procedure takes place. One of the things it does is finds and identifies the address of that array and redirects it to go through maphack first. Now maphack knows what everyone is wearing.
Another thing is that when someone takes off or changes one of there clothes, it lets everyone know so the clients can update the player image with the new piece of clothing. Along with the player image changing, the item array changes as well. Now maphack knows again exactly what the person is wearing.
The reason that maphack can't see what's in the actual inventory (charms, tomes, scrolls, etc) is because your client doesn't need that information to update the player image and therefore the server doesnt send it. Most people don't know this, but when you press "0" on the number line at the top of your keyboard, your client does nothing.
When you press "0" on your keyboard, the keydown function gets captured by maphack and when the value is checked, maphack finds out that the number "0" was pressed. Maphack tells the client to execute the open inventory function, and then tells the client (using dll calls, not packets), what to fill in for the body parts. Everything that you can see when you look at the player on the screen is shown in the inventory now.
There! That's how maphack's view other's items feature works.
However, some parts of maphack are detectable. Here they are:
- Socket Protection - This is very detectable and why it is is very obvious. You simply can't switch a socketable item with an item that has open sockets. The client tells the server to socket the items, but maphack stops that packet and sends the one instead to switch the items. A simple check of the item types by the server will prove that socket protection is enabled. Socket protection is disabled by default and you can disable it in the settings ini file.
- Virtual Map Scrolling - Anything that allows you to shoot farther then you're supposed to is a hack and the server knows that. Just don't enable this and you're fine.
