Become a Bug Hunter.
Help us find problems before they become bigger problems. Bug Hunters reproduce issues, create detailed reports, test fixes, and help make SeasonalBots more reliable for everyone.
You don't need to be a Bug Hunter to report a problem. Contributor access is for people who want to help investigate and verify issues regularly.
More than finding bugs
Finding a problem is only the beginning. A useful Bug Hunter helps us understand exactly what went wrong and gives our developers enough information to investigate it efficiently.
You don't need to be a developer. Being patient, curious, and able to explain what you've discovered is far more important.
Reproduce issues
Try to reproduce reported problems and identify the exact steps that cause them.
Create useful reports
Provide clear reproduction steps, expected behaviour, actual behaviour, and anything else that could help us investigate.
Test fixes
Help verify that completed fixes actually resolve the original problem without creating new issues.
Provide feedback
Share useful observations about unexpected behaviour, confusing experiences, and areas that could be improved.
Is this for you?
You might make a great Bug Hunter if...
Curiosity beats coding knowledge.
You don't need to understand the SeasonalBots codebase or know how to fix the issue yourself. Bug Hunters focus on discovering, reproducing, and documenting problems.
If you can turn "it doesn't work" into a clear explanation of exactly when, where, and how something goes wrong, you're already doing something incredibly useful.
What makes a good bug report?
Good reports save a huge amount of investigation time. These are the details that make a report genuinely useful.
What happened?
Clearly explain the problem instead of simply saying that something is broken.
What did you expect?
Tell us what you expected the feature or service to do instead.
How can we reproduce it?
Provide clear steps that allow another person to recreate the issue.
Where did it happen?
Include the affected bot, dashboard, page, command, service, or feature.
Can you provide evidence?
Screenshots, error messages, logs, or recordings can make an investigation much quicker.
Never share passwords, authentication tokens, private API keys, personal information, or other sensitive data in a bug report.
From bug to fix
Bug Hunters can help throughout the lifecycle of an issue, not just when it's first discovered.
01
Find or receive an issue
You discover unexpected behaviour yourself or help investigate something reported by another user.
02
Reproduce the problem
Test the issue carefully and work out which actions, conditions, or environments cause it.
03
Document what you found
Submit a structured report with reproduction steps and any useful screenshots, logs, or observations.
04
Verify the fix
Once a fix is available, test the original scenario again and confirm whether the problem has been resolved.
Contributor, not staff
Bug Hunter is a contributor role. It doesn't provide moderation, support, developer, or administrative access to SeasonalBots systems.
You'll only receive the access needed to participate in the Bug Hunter programme and collaborate with the team.
What we expect
Report findings accurately and honestly
Don't intentionally disrupt production services
Keep private or unreleased information private
Be respectful when discussing reports with other contributors and staff
Follow instructions when testing sensitive or unfinished features
Want to start testing now?
You don't need to wait for the Bug Hunter programme to get involved. SeasonalBots Beta is free to join and lets you test upcoming features before they're released publicly.
Bug Hunter is coming soon.
We're still preparing the Bug Hunter contributor programme. In the meantime, you can continue reporting bugs normally or join SeasonalBots Beta.