anyway to stop people from autoclicking?

A1Programmer

anyone have any ideas to stop autoclicking, maybe a delay or something?

Yusei-Fudo

If this isn't what you want, tell me,

Or simply just use a wait () secs block.

Last edited by Yusei-Fudo (May 7, 2021 00:13:46)

TheAnomalousPseudo

wait until <not<mouse down?>>

Yusei-Fudo

TheAnomalousPseudo wrote:
wait until <not<mouse down?>>

Then you condition will only work for mouse down.

PS. If you don't know what Mouse down is, it basically detects when you click in the area of the stage.

Last edited by Yusei-Fudo (May 7, 2021 00:20:35)

TheAnomalousPseudo

Yusei-Fudo wrote:
TheAnomalousPseudo wrote:
wait until <not<mouse down?>>
Then you condition will only work for mouse down.

PS. If you don't know what Mouse down is, it basically detects when you click in the area of the stage.

I assumed “autoclicking” means mouse.

A1Programmer

TheAnomalousPseudo wrote:
Yusei-Fudo wrote:
TheAnomalousPseudo wrote:
wait until <not<mouse down?>>
Then you condition will only work for mouse down.

PS. If you don't know what Mouse down is, it basically detects when you click in the area of the stage.
I assumed “autoclicking” means mouse.

i can still autoclick with your code sadly

Yusei-Fudo

A1Programmer wrote:
TheAnomalousPseudo wrote:
Yusei-Fudo wrote:
TheAnomalousPseudo wrote:
wait until <not<mouse down?>>
Then you condition will only work for mouse down.

PS. If you don't know what Mouse down is, it basically detects when you click in the area of the stage.
I assumed “autoclicking” means mouse.
i can still autoclick with your code sadly

Then… Can you explain to us what autoclicking is? None of us seems to know what autoclicking is.

A1Programmer

Yusei-Fudo wrote:
A1Programmer wrote:
TheAnomalousPseudo wrote:
Yusei-Fudo wrote:
TheAnomalousPseudo wrote:
wait until <not<mouse down?>>
Then you condition will only work for mouse down.

PS. If you don't know what Mouse down is, it basically detects when you click in the area of the stage.
I assumed “autoclicking” means mouse.
i can still autoclick with your code sadly
Then… Can you explain to us what autoclicking is? None of us seems to know what autoclicking is.

using a bot/program to click really fast (like 50 clicks per second).

Last edited by A1Programmer (May 7, 2021 00:34:04)

Yusei-Fudo

A1Programmer wrote:
Yusei-Fudo wrote:
A1Programmer wrote:
TheAnomalousPseudo wrote:
Yusei-Fudo wrote:
TheAnomalousPseudo wrote:
wait until <not<mouse down?>>
Then you condition will only work for mouse down.

PS. If you don't know what Mouse down is, it basically detects when you click in the area of the stage.
I assumed “autoclicking” means mouse.
i can still autoclick with your code sadly
Then… Can you explain to us what autoclicking is? None of us seems to know what autoclicking is.
using a bot/program to click really fast (like 50 clicks per second).

Hm, I'll have to think about that .

jdmdigital

Maybe somehow emulate the one “im not a robot” function

-Qlec-

forever
if <mouse down?> then
wait (0.06) secs
end
end

Be sure not to raise it too high though. Some people can have 12 CPS or higher.

The_Imaginarium

The highest cps is 14.1 so we can implement that into our code:

set [Initial_timer v] to ((days since 2000)*(86400)) // much more accurate than a timer
repeat until <(((days since 2000)*(86400))-(Initial_timer)) < [1]>
if <mouse down?> then
change [clicks v] by (1)
wait until <not <mouse down?>>
end
end
if <(Clicks) > [15]> then
say [your a hacker]
stop [all v]
end

theanonymousweirdo

You could try this:

when green flag clicked
delete all of [timers v]::list
repeat [4]
add [] to [timers v]
end
when this sprite clicked
set [i v] to [1]
repeat [3]
replace item (i) of [timers v] with (item ((i)+[1]) of [timers v])
change [i v] by [1]
end
replace item [4] of [timers v] with (timer)
if <<((item [4] of [timers v]) - (item [3] of [timers v])) = ((item [3] of [timers v]) - (item [2] of [timers v]))> and <((item [3] of [timers v]) - (item [2] of [timers v])) = ((item [2] of [timers v]) - (item [1] of [timers v]))>> then
autoclicker

The_Imaginarium

-Qlec- wrote:
forever
if <mouse down?> then
wait (0.06) secs
end
end
Be sure not to raise it too high though. Some people can have 12 CPS or higher.

That won't work. The timer is not accurate enough to detect such small amounts.
You could do:

if <mouse down?> then
set [Initial_Time v] to ((days since 2000)*(86400))
wait until <(((days since 2000)*(86400))-(Initial_Time)) > ((1)/(15))>
end

han614698

jdmdigital wrote:
Maybe somehow emulate the one “im not a robot” function

Not really, how autoclickers work is you use your normal mouse until you get to the point where you need an autoclicked, then, you press a certain key, usually f5 and it will auto click. The code would be (I'm assuming you're programming a clicker):

That only allows 2 clicks/second.

If you want more, equation:
x = wanted clicks/second limit
((1/x) + 0.001)
Replace the reporter input in the ‘wait () secs’ block with your result.

A1Programmer

The_Imaginarium wrote:

The highest cps is 14.1 so we can implement that into our code:

set [Initial_timer v] to ((days since 2000)*(86400)) // much more accurate than a timer
repeat until <(((days since 2000)*(86400))-(Initial_timer)) < [1]>
if <mouse down?> then
change [clicks v] by (1)
wait until <not <mouse down?>>
end
end
if <(Clicks) > [15]> then
say [your a hacker]
stop [all v]
end

do i add this to the “when sprite is clicked”

Yusei-Fudo

A1Programmer wrote:
The_Imaginarium wrote:
The highest cps is 14.1 so we can implement that into our code:
set [Initial_timer v] to ((days since 2000)*(86400)) // much more accurate than a timer
repeat until <(((days since 2000)*(86400))-(Initial_timer)) < [1]>
if <mouse down?> then
change [clicks v] by (1)
wait until <not <mouse down?>>
end
end
if <(Clicks) > [15]> then
say [your a hacker]
stop [all v]
end
do i add this to the “when sprite is clicked”

You probably would be better off putting that script in the script that you are using to deal with clicking or something.

SansStudios

The_Imaginarium wrote:
The highest cps is 14.1 so we can implement that into our code:
... :: color 5

The highest cps is not 14.1, I can easily get higher.

Also, ratelimiting clicks isn't a viable solution either. Many people can click very quickly but only for a short period of time.

If you are using different methods of clicking (drag, jitter), above 14.1 is easy. However, sustaining high cps is the real issue.

Autoclicker detection is usually done by calculating the time between clicks. For example, Hypixel's autoclicker detection looks to see if your clicks are all happening on a specific delay, and if you click too many times with that delay (say you click 100 times and you wait 0.01 seconds exactly between each click), the anticheat will notice and ban you. This works because it is extremely hard for users to get a specific perfect delay that an autoclicker is programmed to use.

To create a suitable anticheat you would need to:

1) Record the time in between each click
2) Look for irregular patterns
3) Restrict cheaters

@theanonymousweirdo has the best code that does this:

theanonymousweirdo wrote:

You could try this:

when green flag clicked
delete all of [timers v]::list
repeat [4]
add [] to [timers v]
end
when this sprite clicked
set [i v] to [1]
repeat [3]
replace item (i) of [timers v] with (item ((i)+[1]) of [timers v])
change [i v] by [1]
end
replace item [4] of [timers v] with (timer)
if <<((item [4] of [timers v]) - (item [3] of [timers v])) = ((item [3] of [timers v]) - (item [2] of [timers v]))> and <((item [3] of [timers v]) - (item [2] of [timers v])) = ((item [2] of [timers v]) - (item [1] of [timers v]))>> then
autoclicker

Last edited by SansStudios (May 7, 2021 01:55:14)

cobalt61

wait until <not mouse down>

My suggestion

A1Programmer wrote:
anyone have any ideas to stop autoclicking, maybe a delay or something?

Last edited by cobalt61 (May 7, 2021 03:27:09)

QuantumCodes

if he is clicking at more than 8 times a second or he is clicking at the same exact spot for like 5-10 mins then he is a autoclicker.

Discuss Scratch