5 ms·

Speed-ran the game using this (well, I injected jquery first to select the element using $() because I'm an absolute Baboon) in about 45 seconds, spam clicking

• anais9 2y ago
  I envy your rig - mine glitched a lot to get it in <3min. Might not be doing myself a service by actually answering the Duolingo questions via LLM... https://www.youtube.com/watch?v=I-J0ppP-H9s https://www.youtube.com/watch?v=I-J0ppP-H9s
  • rkagerer 2y ago
    Ah, a new yardstick for browser performance :-P
  • p0w3n3d 2y ago
    Sir that's true evil! That's evil you know?
  • emberfiend 2y ago
    Majestic.
• stanmancan 2y ago
  I wonder what the limiting factor is here; I'm currently at 332,446,225,163,762,970,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000 stimulation 131,903,042,042,866,960,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000 stimulation per second And there doesn't seem to be an end in sight.
  • lightedman 2y ago
    going to the ocean is the end, I got there with only a couple dozen million stim
    • SamSkjord 2y ago
      My brain has never been happier to see a credits screen
    • mgrpowers 2y ago
      Nah, just remove the element and keep going.
• bambax 2y ago
  > I injected jquery first to select the element using $() In Chrome and Firefox, $ and $$ are available in the console as replacements for document.querySelector and document.querySelectorAll, respectively. This doesn't work in scripts though; only in the console. In a script you can use this: const $ = document.querySelector.bind(document);
• myfonj 2y ago
  Fun fact: browsers' devtools consoles have de-facto standardized convenience aliases for querying the DOM, similar to jQuery [0][1][2][3][4]. This means you could do something as simple as: setInterval(()=>$('.main-btn')?.click(), 0) setInterval(()=>$$('.upgrade')?.forEach(_=>_.click()), 1000) to create the simplest dependency-free cheat speed runner. (And, as mentioned earlier, shrinking -- or logically also zooming in -- the page results in more DVD bounces.) [0] https://devtoolstips.org/tips/en/query-dom-from-console/ https://devtoolstips.org/tips/en/query-dom-from-console/ [1] https://firefox-source-docs.mozilla.org/devtools-user/web_console/helpers/ https://firefox-source-docs.mozilla.org/devtools-user/web_co... [2] https://developer.chrome.com/docs/devtools/console/utilities/ https://developer.chrome.com/docs/devtools/console/utilities... [3] https://learn.microsoft.com/en-us/microsoft-edge/devtools-guide-chromium/console/utilities https://learn.microsoft.com/en-us/microsoft-edge/devtools-gu... [4] https://developer.apple.com/library/archive/documentation/AppleApplications/Conceptual/Safari_Developer_Guide/Console/Console.html https://developer.apple.com/library/archive/documentation/Ap...
  • r14n 2y ago
    I get a reference error when I try this (chrome stable on linux)
    • myfonj 2y ago
      Ah, thanks for the heads-up, apparently there is something borked in Chromium wrt $ / $$ encapsulation, as it seems they are nor reachable from the (global) context setInterval so doing `window.$ = $; window.$$ = $$;` fixes that in Chrome. Not sure why. (Yet again embarrassed myself by trying a snippet that "simply must work ® according all documentations ™" in single a browser only before posting. Sigh.)
      • myfonj 2y ago
        Filed as https://issues.chromium.org/issues/388437264 https://issues.chromium.org/issues/388437264