What makes a report useful
A useful report points to one issue and gives enough context to verify it without guessing. If the problem is a count, send the current AO3 source you checked. If it is a layout issue, include the device and route.
Signal channel
Send a report we can act on
Use this channel for count fixes, source evidence, broken images, and gameplay issues. Precise reports move fastest.
Count correction
Entry name, visible count, expected count, and the AO3 source page.
Broken image
Entry name, page where it appeared, and whether the fallback loaded.
Gameplay bug
Route, mode, device, and what happened after your click.
G
Review queue
Example anchor
Glaceon
Include the entry name and the page where the issue appeared.
Keep secrets out of reports
Do not send passwords, private tokens, archive account data, or database credentials. AO3dle only needs public source context and a clear description of the issue.