EntGaming:DetectMaphack: Difference between revisions
m 1 revision imported |
imported>Haunt No edit summary |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
__FORCETOC__ | |||
== Maphack Detection Guide == | |||
There are a lot of ways to check for maphacks and there might be easier ways, so read and use what you can. Detection is a lot easier if you play the game yourself. However, with a few simple things, detecting maphack can also be easy. | |||
=== FCD and its bugs === | === FCD and its bugs === | ||
==== Warning ==== | |||
Using this script in-game is not allowed. Since it is a script, it is also considered a third party program/tool due to the user who gets information about something what they should not know in-game. This could be a ping but also just knowing who clicks who. This information is in violation to our [[EntGaming:Rules]]. So please refrain from using it in-game. | Using this script in-game is not allowed. Since it is a script, it is also considered a third party program/tool due to the user who gets information about something what they should not know in-game. This could be a ping but also just knowing who clicks who. This information is in violation to our [[EntGaming:Rules]]. So please refrain from using it in-game. | ||
==== Known bugs ==== | |||
* Clicking side shops: These clicks can not be confirmed to be maphacking. | * Clicking side shops: These clicks can not be confirmed to be maphacking. | ||
* Vile: Clicking the vile (middle shop) can be confirmed as a maphack if the player has never been inside vision of them before clicking. However, having vision at first and then losing selection after 0.1 second does not mean maphack but a delayed fog-click (not maphack). | * Vile: Clicking the vile (middle shop) can be confirmed as a maphack if the player has never been inside vision of them before clicking. However, having vision at first and then losing selection after 0.1 second does not mean maphack but a delayed fog-click (not maphack). | ||
| Line 31: | Line 17: | ||
* Bug on startup: Sometimes when the script is initiated, there is a markup displayed, that is false, which is not in the replay itself. This means all clicks must be checked according to the raw replay format. | * Bug on startup: Sometimes when the script is initiated, there is a markup displayed, that is false, which is not in the replay itself. This means all clicks must be checked according to the raw replay format. | ||
* And many more. Please read the two guides below to get more information. | * And many more. Please read the two guides below to get more information. | ||
==== Note ==== | |||
The enemy_click includes the DotaReplay manager and the Fog-Detectors.zip has 2 different fog-detectors. [[EntGaming:FCD]], [[EntGaming:AutoC]], [https://drive.google.com/file/d/0B8JoWU-WbXbeTzlIOVowWlFMTzg Download], [[User:Art)y|Art)y]] ([[User talk:Art)y|talk]]) 13:48, 28 June 2014 (CEST). | |||
The enemy_click includes the DotaReplay manager and the Fog-Detectors.zip has 2 different fog-detectors. | |||
=== Guide 1 === | === Guide 1 === | ||
[[File:Mh1.jpg|thumbnail||Copy the downloaded content to your warcraft 3 folder like shown.]] | [[File:Mh1.jpg|thumbnail||Copy the downloaded content to your warcraft 3 folder like shown.]] | ||
| Line 56: | Line 29: | ||
[[File:Mh5.jpg|thumbnail||The log-file is named fogclicks.txt. Here you can see all the "supposed" and not confirmed fog-clicks. Remember to keep in mind, that there are a lot of bugs when using tools like these. ]] | [[File:Mh5.jpg|thumbnail||The log-file is named fogclicks.txt. Here you can see all the "supposed" and not confirmed fog-clicks. Remember to keep in mind, that there are a lot of bugs when using tools like these. ]] | ||
# Use the fog-detector which logs the result in a .txt file. If you are using another one, get a pen and a paper to write them down. Copy the detector to your Warcraft 3 folder and find the replay you want to check and put it in "''\replays''". | # Use the fog-detector which logs the result in a .txt file. If you are using another one, get a pen and a paper to write them down. Copy the detector to your Warcraft 3 folder and find the replay you want to check and put it in "''\replays''". | ||
# Load the game. Select the replay. And run it at 8x speed to the end. Now if you are using the one with .log | # Load the game. Select the replay. And run it at 8x speed to the end. Now if you are using the one with .log built-in, go make some coffee or something. Since you do not need to write anything, the script does that for you. If you are using the one without you need to sit on your ass and write down when it displays "''fog-click detected''". | ||
#:: '''Note:''' Running fog click detectors on maximum speed can cause delayed fog clicks and imprecise results. | #:: '''Note:''' Running fog click detectors on maximum speed can cause delayed fog clicks and imprecise results. | ||
#:: '''Tip:''' To run a replay minimized with >8 maximum speed, read [[EntGaming:ReplaySeeker]]. | #:: '''Tip:''' To run a replay minimized with >8 maximum speed, read [[EntGaming:ReplaySeeker]]. | ||
| Line 122: | Line 95: | ||
=== Key Unit IDs === | === Key Unit IDs === | ||
A [http://wiki.entgaming.net/index.php?title=EntGaming:UnitIDs list] of the most important and rather rarely selected units. For a full list, check out the [[EntGaming:DRMF]] which automatically ''translates'' the [[EntGaming:DRM]]'s action log into read-able hero and object names. Same applies to [[EntGaming:FCD]] whose log you can simply compare with the DRMF quick filter result. | A [http://wiki.entgaming.net/index.php?title=EntGaming:UnitIDs list] of the most important and rather rarely selected units. For a full list, check out the [[EntGaming:DRMF]] which automatically ''translates'' the [[EntGaming:DRM]]'s action log into read-able hero and object names. Same applies to [[EntGaming:FCD]] whose log you can simply compare with the DRMF quick filter result. | ||
[[Category:Info]] | |||
[[Category:Guides]] | |||
__NOEDITSECTION__ | |||