Detection by Mouse Brand

The ability to adjust debounce, and the inherent debounce characteristics, vary by brand and model:

• Glorious: Models like the Model O/D/I often feature adjustable debounce time via a slider in their software (Glorious Core or older software). Check the software GUI and the config files in %appdata%\BY-COMBO2\ (or similar). Settings below the server's threshold are typically bannable.

• Cooler Master: Many Cooler Master gaming mice also offer adjustable debounce time via software sliders. Check their specific software (MasterPlus+, etc.) and associated configuration files in AppData.

• Roccat: Some Roccat models (especially newer ones) might have software settings (e.g., "Zero Debounce"). However, Roccat mice, particularly older models (like Kone Pure Owl-Eye, Kone AIMO), are widely known and acknowledged in clicking communities to have inherently low effective debounce times (often well below 10ms) due to their switch implementation and firmware, regardless of the software setting (which might not even exist or be effective on older models).

  • Ban Logic: If a player is using a known low-debounce Roccat model, achieves very high CPS consistent with mouse abuse (e.g., 20-30+ CPS via drag/butterfly clicking), and the server bans debounce settings below 10ms, this can constitute grounds for a ban, even if no software setting is found or if it appears set higher. The hardware itself provides the unfair advantage the rule aims to prevent. However, context is crucial. Simply finding a Roccat mouse during a screenshare for an unrelated reason (e.g., suspected reach) without witnessing or having evidence of high CPS / mouse abuse is not sufficient grounds for a debounce-related ban, although the mouse model might be noted. Server rules need to be clear on whether possession of certain known-abusable hardware constitutes an offense.

• Bloody: Similar to Roccat, many Bloody gaming mice (especially those popular for drag clicking) have software sliders for debounce adjustment but are also notorious for having inherently faulty or low effective debounce times (< 10ms) even when the slider is set higher. The same ban logic and critical need for context (observed high CPS/abuse) as described for Roccat apply.

• Red Dragon: Some Red Dragon models allow debounce adjustment via software. Check their specific software and configuration file locations (e.g., %homepath%\Documents\M### Gaming Mouse\MacroDB\).

• Mad Catz: Certain Mad Catz models (especially older R.A.T. series) were known for having virtually no effective debounce timer or double-click prevention, making them easily abusable for high CPS. The same ban logic and context considerations as Roccat/Bloody apply if mouse abuse is suspected.

• Mars Gaming: Models often implement debounce time adjustment via software sliders. Check their software and AppData config files.

Important Consideration: Always correlate findings related to potentially low debounce times (whether via software setting or inherent hardware characteristics) with the reason for the screenshare and observed player behavior (e.g., documented instances of suspiciously high CPS). Avoid issuing bans solely based on the possession of a specific mouse model unless server rules explicitly prohibit that model or clear evidence of mouse abuse (exploiting low debounce for inflated CPS) was witnessed and documented.