Covered: reproducible bugs · regression rounds · cross-mod compatibility

Independent Minecraft mod tester

Reproducible QA for mod authors.

I run regression, cross-mod compatibility, localization, and mechanic checks, then turn findings into reports authors can act on.

№01
13
mods tested
№02
24
test rounds
№03
4
public credits

currently on the bench

active rotation · click for the full tester log

A letter from the workbench

Hello.

I'm a duck who tests Minecraft mods. I keep a dozen or so on my workbench, and over the years I've filed several hundred reproducible bug reports back to their authors.

This site is the public side of that bench. Every test round, every reproducible step, every author response sits in the ledger. Nothing is summarised; scroll and you are reading it.

If you have just built a mod and want a careful pass before release, send the jar over. Hourly arrangements are also fine when the scope is larger.

LUCK666DUCK · written on a Tuesday

Field manual

02

Field manual

What a tester can do, and how. The goal is not just finding more issues. It is making each issue reproducible, prioritised, and ready for regression.

Regression runs

Retest by version and fix round: fixed, still reproducible, or newly introduced.

Compatibility checks

Run with common mods, shaders, and multiplayer setups to expose interaction bugs.

Localization checks

Check zh-CN, zh-HK/TW, Japanese, and English for missing text, mistranslation, terminology, and UI fit.

Actionable reports

Each entry keeps version, observation, category, severity, and regression status.

Regression testing is not about finding new bugs. It is about confirming the old ones are dead. House rule №1

Evidence

03

Evidence on file

Public tester credits, full test logs, and a clear bug taxonomy make the portfolio verifiable. Everything cross-checks against CurseForge member pages, tester fields, and live download counts.

MC 1.14 → 1.21 5 regression rounds Hot Bath 2.6M DL verified tester bilingual zh / en powered by duck
If the public ledger can verify it, I do not need to say it twice. House rule №2

Field notes

05

Field notes

A few rough notes scribbled at the workbench. Longer methodology, case retrospectives, and data observations will grow into this column over time.

№01 draft · planned

Mod QA taxonomy

How crashes, mechanics, compatibility, localization, and visual issues become author-actionable categories.

№02 draft · planned

Cross-mod reproduction

Notes on reproducing interactions with CarryOn, Cold Sweat, Serene Seasons, Alex-series mods, and other common setups.

№03 draft · planned

Observations from 433 bugs

A future data-oriented pass can turn this portfolio into lightweight research material.