Regression runs
Retest by version and fix round: fixed, still reproducible, or newly introduced.
LUCK666DUCK A tester's ledger · public · open to mod authors 2026-09-05
Covered: reproducible bugs · regression rounds · cross-mod compatibility
Independent Minecraft mod tester
I run regression, cross-mod compatibility, localization, and mechanic checks, then turn findings into reports authors can act on.
currently on bench
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
02What 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.
Retest by version and fix round: fixed, still reproducible, or newly introduced.
Run with common mods, shaders, and multiplayer setups to expose interaction bugs.
Check zh-CN, zh-HK/TW, Japanese, and English for missing text, mistranslation, terminology, and UI fit.
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
03Public 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.
If the public ledger can verify it, I do not need to say it twice. House rule №2
Case studies
04Three cases for three testing scenarios: a public collaboration, a high-volume triage, a multi-round regression.
Field notes
05A few rough notes scribbled at the workbench. Longer methodology, case retrospectives, and data observations will grow into this column over time.
How crashes, mechanics, compatibility, localization, and visual issues become author-actionable categories.
Notes on reproducing interactions with CarryOn, Cold Sweat, Serene Seasons, Alex-series mods, and other common setups.
A future data-oriented pass can turn this portfolio into lightweight research material.