Quick answer: Reproduction steps that work on the developer's machine and nowhere else waste time. Specifying setup, build, version, and input precisely makes repros portable.
A repro that needs to be 'recreated' is barely a repro. Make it portable.
Specify build SHA
Bug report includes build SHA. Reproducer checks out that exact commit.
Document setup
'Settings: graphics low, audio off, language English'. Setup affects repro.
Input as data
Record exact inputs (key sequence, timings). Replay reproduces; less manual; more reliable.
Save state attachments
Save game file attached; reproducer loads, plays, sees bug.
“Repro is the contract between reporter and fixer. Strong contracts close bugs faster.”
Build a one-line repro recorder in your SDK. Records inputs; player triggers; engineer replays.