## Refer below list for explanations.

DoubleClickCPS: 20
ClickCheck: 100
Count Right and Left together: N
Debug: N
DoubleClickKick: 50
DoubleClickBan: 80
Kick Message: "You were kicked for clicking too fast."
Ban Message: "You were banned for suspected autoclicking."
Plugin Handles Bans: N
Certainty Allowed: 80.0

# DOUBLECLICKCPS: Calculates in ms (1000ms / CPS = 50ms). So 20 = 50ms.
# CLICKCHECK: Number of previous clicks to analyze before deciding to kick
# COUNT RIGHT AND LEFT TOGETHER: Always keep left/right tracked separately - Recommend to keep disabled mostly for Debugging
# DEBUG: Defaults to No, ALL players can toggle with /odcp - Gives view for plugin "logic" to be shown. Allows you to test autoclickers or a desired rate of clicks to ban more clearly
# DOUBLECLICKICK: Percent range to trigger a kick (EX. 50–79%) -- If "Plugin Handles Bans: is = N then kicks for 50%-100%
# DOUBLECLICKBAN: Percent range to trigger a ban (EX. 80–100%) -- "Plugin handles Bans" must be enabled
# KICK MESSAGE: Create your own kick message - Will always be followed by -L/R (Server Certainty) P.C (Player Certainty)
# BAN MESSAGE: Create your own ban message - Will always be followed by -L/R (Server Certainty) P.C (Player Certainty)
# Plugin Handles Bans: If set to "N", plugin logs but does NOT execute the ban command
# CERTAINTY ALLOWED: Minimum % certainty (based on tick timing) for clicks to count -- Recommended to be below 90 to ensure less false kick/bans due to server lag ex. Local servers typically sit around 99.5%