|
| 1 | +# UnrealDemoScanner |
| 2 | +#### The .dem file scanner is designed to analyze and scan Counter-Strike 1.6 demo files for the presence of prohibited programs. |
| 3 | +#### It does not require the game to be installed or even present on the computer, and unlike ViewDemoHelper, it can detect a large number of cheat programs without false positives. |
| 4 | + |
| 5 | +--- |
| 6 | +Differences from ViewDemoHelper: |
| 7 | +- |
| 8 | +### Advantages: |
| 9 | +- No need for the game to be installed |
| 10 | +- Works with clean input data |
| 11 | +- Detects all types of cheats released up until 2020 |
| 12 | +- Ability to scan multiple demo files at once |
| 13 | +### Disadvantages: |
| 14 | +- Console application with no quick view of moments |
| 15 | +- Does not have access to the game API, so it consumes extra RAM to simulate the game engine's work and cannot catch some types of cheats (checking if the player is alive, what weapon they have, storing extra data in memory, etc.). Scanning a 100 MB demo file requires from 0.5 GB to 1 GB of RAM. |
| 16 | +- Scanning large demo files can take considerable time. |
| 17 | + |
| 18 | +# Installation and Running |
| 19 | +- Unzip **unrealdemoscanner.zip** into a separate folder |
| 20 | +- Run **UnrealDemoScanner.exe** |
| 21 | +- Drag the player's demo file into the console or enter the path manually |
| 22 | +- Press the **Enter** key once |
| 23 | +- Wait for the scan to complete |
| 24 | +- After scanning, you can enter one of the commands to view additional information |
| 25 | + |
| 26 | +# Description of Aimbots and Other Cheats |
| 27 | +- AIM TYPE 1 - Attack delay |
| 28 | + |
| 29 | +- AIM TYPE 2 - Autoattack with pistols |
| 30 | + |
| 31 | +- AIM TYPE 3 - Sharp aim jumps (incomplete) |
| 32 | + |
| 33 | +- AIM TYPE 4, FAKELAG - Fake lag |
| 34 | + |
| 35 | +- AIM TYPE 5 - Smooth angles/etc - Software angle smoothing |
| 36 | + |
| 37 | +- AIM TYPE 6 - HPP Autoattack - Autoattack from HPP v5 |
| 38 | + |
| 39 | +- AIM TYPE 7 - HPP Trigger bot - Trigger bot (from HPP) or hard aimbot |
| 40 | + |
| 41 | +- AIM TYPE 8 - Universal AIMBOT detection |
| 42 | + |
| 43 | +- TRIGGER BOT, KNIFEBOT BOT - Old aim hacks |
| 44 | + |
| 45 | +- FPS HACK - Cheat allowing to bypass FPS limit, part of other cheats |
| 46 | + |
| 47 | +- CMD HACK - Game frame modification (e.g., CMD HACK TYPE 1 allows you to hang in the air) |
| 48 | + |
| 49 | +- MOVEMENT HACK - Software movement |
| 50 | + |
| 51 | +- DUCK HACK - Software crouching |
| 52 | + |
| 53 | +- JUMP HACK - Software jumping |
| 54 | + |
| 55 | +- Many other cheat features. |
| 56 | + |
| 57 | +# Command Line, Launch Parameters |
| 58 | +- **-dump** — saves the entire demo file in human readable text format, making it possible to read the demo file as text, can be used to analyze cheat programs without modifying the scanner's source code |
| 59 | +- **-debug** — outputs debug information |
| 60 | +- **-alive** — marks the player as alive at the beginning of the demo (forcefully) |
| 61 | + |
| 62 | +## False Positives |
| 63 | +##### [WARNING] Alerts |
| 64 | +- may appear from time to time when the scanner considers the moment suspicious but not enough to consider it 100% cheat usage. Such moments should be reviewed manually. I recommend using View Demo Helper or similar programs to examine the moment accurately. In other words, having multiple warnings does not mean the player is a cheater unless you review the moments in the game. |
| 65 | + |
| 66 | +##### [DETECTED] Alerts |
| 67 | +- are displayed when the scanner is absolutely sure that this moment is a cheat or a cheat script, and should not have false positives. *(But due to some exceptional situations, I allow 1-2 false positives per 10-20 minutes of the entire demo length.)* |
| 68 | +- Detects almost all cheats released up until 2020-2021, but modern cheats may not be detected by the scanner, so the absence of detections does not mean that the player is not a cheater. |
| 69 | + |
| 70 | +# Support |
| 71 | +If you find that your demo has multiple false [DETECTED] alerts, send the demo to me for analysis and to release fixes. |
| 72 | + |
| 73 | +As I no longer play CS 1.6, scanner updates are released rarely. If you are a developer and know methods of work for cheats that are not detected by the scanner, or if you want to join the scanner's development, you can contact me. |
| 74 | + |
| 75 | +For viewing moments in the demo, I recommend using [ViewDemoHelper](https://github.com/radiusr16/view_demo_helper) or other similar programs. |
| 76 | + |
| 77 | +## Demo Files Used for Testing |
| 78 | +- You can get them from the archive: https://github.com/UnrealKaraulov/UnrealDemoScanner/tree/1935a1c9ba62c998bdf74125866728b0ddf4b58b, large demo files are left there. Only short demo files without all the extras are stored in the repository. |
| 79 | + |
| 80 | +## RUSSIAN VERSION: |
| 81 | +[Read in Russian](README.md) |
0 commit comments