Detection Logs
Ocean has several detection capabilities, including direct, generic, and specific detections. In this section, we will go step by step through the generic and specific detections, as it is practically impossible to describe all our direct detections.
Direct
Direct cheat detections using residues or other detection methods (e.g., Skript Loader).
Generic
Detections of highly suspicious executables; while they are not 100% certain detections (unless otherwise specified by this documentation), they indicate a strong likelihood of cheating.
Specific
Detections of tampering or modification methods used to gain illegal advantages, cheat dependencies, etc.
Overview of how Detects Logs work across all games. From here you can jump into per-game semantics.
- Global Detects Logs
Detections that apply to every game, such as files that are very likely cheats, direct connections to cheat authentication servers like KeyAuth, and bypass methods such as deleted Prefetch files.
- Minecraft Detects Logs
Minecraft Java detections, including ÆGIR Touch against cheats that use malicious internal functions, autoclickers built on JNativeHook and injections into the game process.
- FiveM Detects Logs
FiveM detections, such as illegal external injections into the game, changes in important folders and an active spoofer.
Besides detection logs, a scan report can show warnings, suspicious activity and integrity checks. Each has its own page:
- Warning Logs
Changes that can be used to evade detection but do not prove cheating on their own.
- Suspicious Logs
Executables that are likely but not certain cheats, such as VM checks, .NET binaries and packed files.
- Integrity Checks
Deeper checks, such as the recovery of deleted files on NTFS and FAT32 and the files that antivirus programs flagged.