Drain Water Per Click

Our Methodology

1. How we collect data

Every value on this site lives in a validated dataset. We collect from official Roblox endpoints (game record, votes, group, thumbnails), the official game description, and third-party coverage (guide sites, community wikis, gameplay videos). Raw official API responses are archived with their fetch date before anything enters the dataset.

2. Source hierarchy

  1. Official — Roblox APIs and pages, the developer's own posts.
  2. In-game verification — direct play, UI screenshots, video frame checks.
  3. Community — player-measured values, video evidence.
  4. Third-party — guide sites and wikis.

Third-party claims are never promoted to fact on their own. When two sources agree we call it cross-verified; when they conflict we record both claims and label the entry.

3. Confidence labels

  • Verified — confirmed against an official source.
  • Cross-verified — two or more independent sources agree.
  • Likely — a single source, plausible, unchecked.
  • Unverified — conflicting or weak evidence; shown only with a warning.

When no reliable source documents a value at all, we print nothing. That's why some tables show "Not verified yet" where other sites show a number.

4. How calculators work

Tools and wiki pages share the same calculation library — the drain-time formula on a guide page is literally the same code as the Drain Time Calculator. The base is the official "+1 Water per click"; pump multipliers multiply that base. Because the game doesn't publish stacking rules, multiplier-product estimates are always labeled as estimates, and the calculators prefer values you enter from your own game UI.

5. How efficiency & tier scores are calculated

Efficiency = (multiplier − 1) ÷ Water price — the multiplier a pump grants per Water spent — normalized 0–100 against the best pump. Tier bands follow the roster's progression order, cross-checked against efficiency so a cheap big jump outranks an expensive small one. Both formulas are original to this site and fully reproducible from the published table.

6. How codes are tested

Codes are re-checked against multiple independent guides after every game update and event window (updates have gone live around 7:00 AM ET). We record the exact date of the last check on every code. We don't write "still working" without a fresh dated check — and reader reports of a dead code trigger a re-verification.

7. How corrections work

Spot an error? Contact us with what you saw in-game. Corrections re-run the full verification: source check, cross-check, then update with a new date. Every entity carries its own verifiedAt date, so corrections are visible per fact rather than hidden in a global "updated today."

8. Live counters

Player counts, visits and votes are snapshots from official Roblox APIs, always shown with their snapshot date. They're observations, not gameplay facts, and are never presented as permanent values.

Current source registry

35 registered sources, last accessed August 28, 2026:

Sources

Values on this page are only as reliable as their sources. See our methodology for how data is collected and verified.