Posted by Kim on December 13, 2019, 4:00am
We've been on 2.0 for a few days now, and gotten past the initial crashes we were experiencing. The lag is often still with us, but slowly receding, fixed bug by fixed bug and improvement by improvement.The site is doing better now because of people like YOU helping me to track down issues. But you might be the sort of person who hesitates before sending a bug report -- what if it bothers Kim? What if nothing is actually wrong and I'm just clicking in the wrong place? What if someone has already pointed it out and I'm just creating spam? It is very kind of you to worry about things like this. You're a good person. But let me set your mind at ease.
Should You Send a Bug Report?
-
I found something that I think might be wrong, but it might also just not be done yet. Should I send a bug report?
Yes! Please send a bug report about anything you are even slightly suspicious of.
I found something but I think it's so obvious, someone must have already reported it. Should I bother you with another one?
Yes! Please send a bug report even if you think it's something really obvious.
I think I found something, but it's so small, or maybe just a typo - should I bother you with a bug report?
PLEASE send that bug report! It's not a bother!
I'm not sure--
For sure send a bug report! Even if I write back that it's working as intended, or that it's simply not finished yet, you've still done the right thing. You are never being a bother by being on the lookout for potential ways the site might be improved!
How to Submit an Excellent Bug Report
- Submit the bug report through the bug report form. To get to the bug report form, go to Help > Report a Problem in the top nav. If for some reason you can't use that form, you can also email admin@rprepository.com
DO NOT send it through private messages, forums, news comments, Discord, or any other message. Or, if you do send it through one of those methods, please also submit it via the bug report form. This will help me stay organized and on top of the things you find!
Include as many details as you can. Bug reports should contain a thorough description of the situation. Please don't write and say "it won't let me..." or "I can't..." and then nothing else.
If the problem occurred on a specific page, link me to that page. If it occurred when using a specific character, let me know which one. If you got an error message, include the error message (or your best recollection thereof.) Let me know if you were on a mobile phone or a desktop computer. Let me know what browser you were using at the time. The more details you can provide, the better chance I have to find the problem and fix it!
A good script for submitting a bug report: "I was trying to ______ by clicking ________ on the page _______. I was expecting _______ to happen, but instead _________ happened."
What Should You Test?
Literally everything. The entire site was built from scratch - every single line of code re-written. Anything could have been broken. Make sure all your favorite/most used features are working!
And Remember...
I give accolades to people who submit bug reports, when the issue they reported is fixed! This is a great opportunity to collect some cool prizes for your profile.
KatrinaPride
December 13, 2019
7:41pm