Detecting Software-Based Macros

Detecting macros stored on the PC involves locating and examining the configuration files and settings associated with the player's specific mouse software. Most gaming mouse manufacturers provide software that allows users extensive customization, including macro creation and assignment. These settings are typically saved in specific files or database entries within standard user or system data locations.

Detection by Mouse Brand (Software Config Files/Locations)

The precise location and format of macro configuration data vary significantly between manufacturers and even different software versions from the same manufacturer. Here are known or commonly suspected locations for several popular brands:

  • Logitech:

    • Logitech Gaming Software (LGS - Older): Check %localappdata%\Logitech\Logitech Gaming Software\. Look for files like settings.json or potentially .xml files containing profile and macro definitions.

    • Logitech G HUB (Newer): Check %localappdata%\LGHUB\. The primary configuration is often within settings.db (an SQLite database, requires a DB browser to view) or related files/folders within this directory. Analyze modification times first.

  • Razer:

    • Synapse 2 (Legacy): Examine installation folders (C:\Program Files (x86)\Razer, etc.) and %localappdata%\Razer or %programdata%\Razer for profile/macro files (often .xml).

    • Synapse 3: Configuration is more complex, potentially involving cloud sync. Check C:\ProgramData\Razer\Synapse3\Accounts\ for account-specific data and %localappdata%\Razer\Synapse3\Log\ for activity logs that might indicate macro usage or profile switches. Macro definitions might be within complex profile structures or potentially stored server-side, making direct file analysis difficult. Checking the software GUI is crucial.

  • SteelSeries:

    • SteelSeries Engine / GG: Check %localappdata%\steelseries-engine-3-client\Local Storage\leveldb\ or similar paths within %localappdata% or %programdata%. SteelSeries often uses LevelDB databases, which require specialized tools (like LevelDB readers/editors) for reliable inspection. Also check associated .json or configuration files in nearby directories.

  • Roccat:

    • Roccat Swarm: Check %appdata%\ROCCAT\SWARM\. Look for subfolders like macro containing files such as custom_macro_list.xml or macro_list.dat. Analyze .xml files for macro definitions.

  • Red Dragon:

    • Paths can vary by model. Check %homepath%\Documents\ for folders named like M### Gaming Mouse (where ### might be model numbers). Inside, look for subfolders like MacroDB containing files such as MacroData.db.

  • Glorious:

    • Check %appdata%\BY-COMBO2\ (path might vary slightly based on specific software/model). Look for .json or .ini configuration files. Examine subfolders, particularly any named Mac or Macro.

  • Cooler Master:

    • Check standard locations: %localappdata%\CoolerMaster, %appdata%\CoolerMaster, or %programdata%\CoolerMaster for software configuration files (.json, .xml, .ini, potentially .db).

  • Bloody:

    • Check the installation directory, e.g., C:\Program Files (x86)\Bloody7\Bloody7\Data\Mouse\English\ScriptsMacros\GunLib\ for Bloody7 software. Also check AppData folders for related configuration files (.ini, .amc2).

  • Mad Catz: Check installation directory and common AppData locations for config files.

  • Mars Gaming: Check installation directory and AppData for .xml or .ini config files.

  • Ayax (Noganet): Check installation path, e.g., C:\Program Files\AYAX GamingMouse\. Look for files like record.ini.

  • Krom (Kolt model): Check %AppData%\Local\VirtualStore\Program Files (x86)\KROM KOLT\Config (path reflects virtualization if software runs with non-standard permissions). Look for sequence.dat.

  • BlackWeb: Check installation path, e.g., C:\Blackweb Gaming AP\config\. Look for files with unusual extensions like .MA32AIY.

  • YanPol (Often similar hardware/software to Glorious/Ajazz): Check %appdata%\BYCOMBO-2\ (or similar) and look for Mac\ subfolders.

  • MotoSpeed (V60 model example): Check installation path, e.g., C:\Program Files (x86)\MotoSpeed Gaming Mouse\V60\modules. Look within subfolders like Settings for .bin or config files.

  • Asus (ROG Armoury): Check C:\Users\%username%\Documents\ASUS\ROG\ROG Armoury\common\. Look for a Macro subfolder.

  • Corsair (iCUE): Check C:\Users\%username%\AppData\Roaming\Corsair\CUE (or Local instead of Roaming). Look within Config.cuecfg (or similar complex config files). Searching inside for strings like RecMouseCLicksEnable might reveal relevant settings. Process memory dumping of iCUE.exe and filtering for strings like MemberFuncSlot has also been suggested as an advanced technique.

Analysis Steps for Software Macros:

  1. Identify Mouse: Determine the player's exact mouse brand and model. Ask the player or check Windows device settings if necessary.

  2. Check Software GUI: The most direct method is often to open the mouse's official software (e.g., G HUB, Synapse, Swarm, iCUE) and navigate to the macro definition and button assignment sections. Look for any macros bound to buttons, especially those involving rapid left/right clicks.

  3. Check Config File Locations: Navigate to the potential configuration paths listed above corresponding to the identified brand.

  4. Examine Modification Dates: Check the "Date modified" timestamps of relevant configuration files, databases, or folders. Recent modifications shortly before the screenshare are highly suspicious, suggesting potential setup or deletion of macros.

  5. Analyze File Contents:

    • Open text-based config files (.json, .xml, .ini) in a text editor and search for keywords like "macro," "click," "delay," "repeat," or specific button bindings (e.g., "LeftMouseButton," "Button 4"). Look for sequences defining rapid clicks with low delays.

    • Open database files (.db) using an appropriate SQLite browser (like DB Browser for SQLite) and examine tables related to profiles, macros, or bindings.

    • Analyze LevelDB or other formats using specialized tools if necessary (more advanced).

  6. Check Logs: Examine any log files generated by the mouse software (e.g., Razer logs) for entries related to profile switching, macro execution, errors, or enabling specific performance modes (like "Turbo").

PreviousDefinition and Purpose in CheatingNextDetecting On-Board Macros

Last updated