Grinding Companion

The drop rate probability engine is built on the geometric distribution, a fundamental model in probability theory for counting the number of independent Bernoulli trials needed to achieve a first success. If each attempt has a constant probability p of yielding a drop, then P(at least one drop in n attempts) = 1 − (1 − p)^n. This formula forms the core of the 'Prob. of at Least 1 Drop' metric displayed by the tool. The expected number of attempts per drop is E[X] = 1/p, giving a concrete benchmark players can compare against their actual run count. These calculations remain valid as long as each attempt is independent and the drop rate is constant — which is generally the design intent in games that use a flat RNG roll per attempt.

The luck ratio is defined as (observed drop rate) / (nominal drop rate) = (drops / attempts) / p. A ratio of 1.0 means observed performance exactly matches the statistical expectation. Values above 1.25 are highlighted in green (favorable), values above 2.0 in gold (extremely lucky), values below 0.8 in blue (slightly unlucky), and values below 0.5 in red (significantly unlucky). The luck gauge gradient bar provides an immediate visual impression of session luck without requiring the player to interpret raw probabilities. This design draws on the principle of pre-attentive visual processing: color and spatial position on a gradient are processed automatically before conscious attention is engaged, making good/bad luck legible at a glance.

The dry streak detector activates when drops = 0. In this case the standard luck ratio is undefined (0/0), so the tool instead computes the complementary probability: P(zero drops in n attempts) = (1 − p)^n. This answers 'How unlikely was it to get zero drops in this many runs?' and directly quantifies the severity of the dry streak. For example, with a 2% nominal rate over 200 attempts, P(zero drops) = 0.98^200 ≈ 1.8% — a 1-in-55 event. Displaying this probability gives players a statistically grounded understanding of whether their dry streak is within normal variance or genuinely exceptional.

The Document Picture-in-Picture (Document PiP) overlay architecture addresses a fundamental challenge of web-based gaming utilities: keeping the tool visible while full-screen or focus-locked games are running. Unlike standard Video PiP, the Document PiP API (Chrome 116+, W3C proposal) allows arbitrary HTML/CSS/JS to be rendered in the floating window. This tool uses ReactDOM.createRoot() to mount a React subtree inside the PiP window's document body, copying parent stylesheets automatically. Interactive controls (toggle timer, increment cycle) are wired via a pipHandlersRef pattern: a mutable ref is updated synchronously on every render of the main component, and PiP button onClick handlers call pipHandlersRef.current.fn(). This ensures that the PiP overlay always calls the most recently captured closure without ever requiring the PiP useEffect to re-run — eliminating stale state bugs entirely.