quizlet time patcher

slows down time in quizlet match

You will need to install an extension such as Tampermonkey, Greasemonkey or Violentmonkey to install this script.

You will need to install an extension such as Tampermonkey to install this script.

You will need to install an extension such as Tampermonkey or Violentmonkey to install this script.

You will need to install an extension such as Tampermonkey or Userscripts to install this script.

You will need to install an extension such as Tampermonkey to install this script.

You will need to install a user script manager extension to install this script.

(I already have a user script manager, let me install it!)

You will need to install an extension such as Stylus to install this style.

You will need to install an extension such as Stylus to install this style.

You will need to install an extension such as Stylus to install this style.

You will need to install a user style manager extension to install this style.

You will need to install a user style manager extension to install this style.

You will need to install a user style manager extension to install this style.

(I already have a user style manager, let me install it!)

// ==UserScript==
// @name         quizlet time patcher
// @namespace    http://tampermonkey.net/
// @version      2026-01-16
// @description  slows down time in quizlet match
// @author       Max-0
// @match        https://quizlet.com/*
// @icon         https://www.google.com/s2/favicons?sz=64&domain=quizlet.com
// @grant        none
// @run-at       document-start
// ==/UserScript==

const time_scale = 0.1;

// date override attempt (not helpful)
/*
const realDateNow = Date.now;

Date.now = () => { return realDateNow() * window.time_scale; };

Object.freeze(Date.now)
Object.seal(Date.now)
*/

// debugging attempt
// i put a breakpoint on when the time div changes in Matching game
// go back far on the stack trace all the way to "x", which is soon after (above) the postMessage
// i saw "performance" used for getting current time.
// i wasn't sure exactly what was going on, but i knew it related to the counter via p.expirationTime and unstable_now() and other functions.
// lets try to hijack the "perfomance" object

const real_perf_now = performance.now.bind(performance);

performance.now = () => {
  return Math.floor(real_perf_now() * time_scale);
};

Object.freeze(performance.now);
Object.seal(performance.now);