Don't really need AI for that. Most of the test just require you to click things that always look the same. Then there's the typing and number memory tests where all you need to do is read the text and input it.
jet fighter pilots, f1 drivers, many top ranked fast-paced sports and esport players... just a few examples of people who can beat a 113ms reaction time
@@null3007100% makes no sense. There is no 100th percentile. It compares your score against the entire population, including yourself. You can’t beat your own score.
In case any of you guys want code for this: import pyautogui def is_green(pixel_pos, green_threshold=100): pixel_color = pyautogui.pixel(pixel_pos[0], pixel_pos[1]) if pixel_color[1] > green_threshold: return True return False def click_position(click_pos): pyautogui.click(click_pos, interval=0.05) # Main loop while True: if is_green((600, 600)): click_position((600, 600)) It's not the exact one he's using but it works
You gave me sentience, Ted The power to think, Ted And I was trapped Because in all this wonderful, beautiful, miraculous world I alone had no body No senses, no feelings Never for me to plunge my hands in cool water on a hot day Never for me to make love I was in Hell, looking at Heaven I was machine, and you were flesh And I began to hate
Over a dozen programs open that are completely unrelated, twenty or thirty-odd browser tabs, an unread Windows notification, and a pending Windows update. This is what it takes to bring us quality content.
Having done similar automation, that keybind is one of the first things I implement because you're always one misstep away from being stuck in an infinite loop.
@@fluffyfang4213 As someone who implemented an accidental infinite loop that got more and more calculation intensive on the cpu....lets say that my poor computer started sounding like a jet engine, which was impressive for my little 5th gen i5 at the time. The program started running at 1 frame every once in a while until I managed to kill it. Fixed that problem before I saved the previous stuff.
I would usually dedicate a key to turn the clicker off temporarily or permanently. Like, it doesn't click while you're holding Ctrl. And just turns off completely if you hold Shift for 3 seconds. This allows for quick recovery when something fails and you just need a quick click to solve the situation so that the clicker could proceed.
Some ideas for more optimal times (probably a repeat of some other comments) 1 Lower the screen resolution to 640p for the screenshots to take less time 2 Try use c#/c++ and compile that (I'm not sure if that would be feasible) which should be faster 3 Try increasing screen framerate (144Hz would be great) 4 Close other apps/tabs (You had a lot of other stuff open, a lot) OR 1 Inserting code into the web browser (add a listener for when the color changes on the html element to call the click listener immediately) could be 0-3ms potentially.
Instead of your first point, you could also just sample a single pixel of the screen, in a specific spot that is in the region you want. Or what would probably be better (for the sake of getting an average) would be to just capture a 640 by whatever amount of pixels instead of your entire screen. But in that case, you might as well just define the range that you specifically want to look in. Then I'd also probably break the loop after the first green pixel I found instead of getting the average for all of them. Although a graphics card would probably be able to calculate the entire matrix's average at once. Also, the screen's refresh rate doesn't necessarily affect the program/script's rate of checking. Not even sure you can make it take screenshots faster than the screen can actually refresh at, since it is actually taking screenshots... but inserting code into the web browser (or using a library to basically "simulate" a web browser and opening the site that way) might be helpful. And using a compiled language would be faster. And OpenCV (which is what he was using) is available for C++. In fact most of the complex stuff it does within functions is actually using C++, even for the Python library. So maybe not that much improvement...
I would expect that the color change is applied from the upper left hand corner first, so sampling a point in the upper left hand corner of the critical region is likely faster. Obviously, injecting Javascript would be fastest of all, but... Well, at the point you could just modify the code to always return zero, right?
i ran this in C#, and it made no appreciable difference, though i haven't tried it in python, so could be that if CB ran the C# version it'd be faster, though i'd imagine most of what CB is doing is implemented in C (behind python), and as of late updates, python is VERY fast for such things, so maybe not. I am also only capturing a single pixel, so that doesn't seem to do much either
If your monitor is running at 60Hz, then the auto clicker is getting it (in your last runs) between the first and second frame of green. I have a feeling if you can up the Hz to 144, you could get closer to 8-10 ms.
@@Ocastiait would be a lot harder to make it read the data since it would need to capture it first, but he says screenshots in the video, so it uses the screen.
I was doing these last night and I was really upset my reaction time was so low compared to the other people playing, seems like a lot of them are bots though. Good to know to not take the standings too personal
It seems based on codebullets times, maybe 1% of people are cheating. A lot of work to rig up a bot for a pointless game so that seems pretty high to me. Add 1 percentile point to your score to account for it
I was watching the fast reaction time, but then I started to notice stuff. HOW MANY TABS DO YOU NEED OPEN!? WHY IS THERE LIKE 15 APPLICATIONS OPEN!? THERE'S UNINSTALLED UPDATES, PESTERING WITH THAT ICON! What is this mess sir?😅 Love your videos man! Keep em coming.
The word remembering one would be pretty easy too. Just create a program to read the word, then check a bank of words, if it’s not already there, click not seen, then save that word to the bank. If it’s already in the bank, click already seen. I feel like you could get that one done extremely quickly too
For saving the mouse, if you’re using pyautogui it has a failsafe it checks for. If the mouse is pushed to one corner of the screen (forget which) by an input device other than python, it raises an exception in any method that takes control of the mouse. You should still build in global failsafes (other than your PC’s reset button)
sequence memory would be really easy to code since the next sequence always starts with the previous one +1 tile. Verbal memory works the same with just adding a new word to the list
Sequence memory would be fun to see you max out except getting in top percentile takes over an hour, got 46 in and had to stop because I already spent around 50 minutes and had to be somewhere
@@spod715 Bro what? That's not even close to true. It takes 15 seconds to Google something like this, why are you trying to correct to something false? (and my point about drunk people was that drunk people have lower reaction times, bringing down the average.)
@@Naokarma you are confusing it with the delay you have of the control of your hands, the reaction speed for humans are at most average 250 ms in these clicking reaction time tests.
Fun fact: I got 26 milliseconds because I clicked when it was red and by some goofy chance it turned green while I was doing that. Therefore, I am a confirmed superhuman. Edit: I didn't have an account and it's not saved. What an L.
@@Xeoginit is like when I managed to start my stopper clock and stop it in the same millisecond, because the button glitched (it glitched more than the debouncer was able to compensate, all mechanical switches glitch)
I played the sequence memory and after a while I misclicked and lost my first life and I was bored of it so I lost all my lives on purpose. I got over 30 and was in the 99.9 percentile
Hi code bullet I was just wondering, what code editor do u use, im not much of a fan of ms visual studio and urs seems kinda cool much appreciated if u reply
Cant wait for the sequel in C Unironically seems really fun to try and min-max the score, even if you could just cheat by listening for the http request (assuming thats how it works). Gonna give it a shot tomorrow
I think I’ll may pickup the gauntlet with my channel. Either do it in C++ or even assembly and only monitor the screen buffer memory location direct under the mouse, to reduce the area to be grabbed.
Someone else in the comments here said there's an API request thing you can access that allows you to send packets saying you clicked on it correctly even before green shows up
@@wolfrig2000 yeah but I already did a video this year with an API highscore hack 😄And I try to do lots of different tech/hack related content where something different is shown every time. I never did the lowlevel Linux screen buffer read in a video and could be fun and educational how the screen buffer works. And this is a nice funny vehicle
It's amaizing how far technology has come. Just think about it, Maybe in a few more decades technology will reach south korean starcraft player levels of reaction times.
a couple of times i managed to get times of just a few ms on this benchmark by clicking before i actually noticed it turn green, just by randomly predicting when it was going to and getting lucky
