Found a bug in Stonehearth? Help us fix it by telling us everything you know about it!
##Bug Report Guidelines
1) Check the other posts in the category to see if the bug has already been reported:
If it has been, open that thread and add whatever details that haven’t already been described.
If you have experienced the bug as well, please like the original post to help Team Radiant notice that it’s a bug that’s happening a lot.
2) If it’s a new bug, open a new thread for the bug and include the following information:
Title: A short title that briefly summarizes the bug for a quick read to get the idea. Prefix with Bug: so it's easy to search for all bugs at once. (ex. Bug: Every Morning, People Heads Are Replaced With Rabbit Heads) Summary: Describe the problem in detail. Exactly how did you get it to happen? Does it happen all the time, or only rarely? Add *anything* you think might be important to the bug report. Steps to reproduce: Distill what you did into as many steps as necessary. The more steps describing the bug the better. This is the most important part of the reporting process, as bugs that can't be reliable reproduced are exceptionally more difficult to resolve. It may seem silly, but don't assume we know exactly how you did what you did. :) Expected Results: What you thought would happen or what you might have expected to happen is not what was actually intended to happen (and then it's a slightly different bug, of expectation.) Actual Results: If significantly different from the summary, what actually did happen. Notes: Anything that didn't fit above Attachments: Short description of each attachment if necessary. Versions and Mods: What version of the game are you running? Did you install any 3rd party mods or make any mods yourself? If so, list them here too. Does the bug still happen if you remove all the mods? System Information: What system are you using? Especially for performance/graphics issues, note your OS, CPU, Memory, Graphics Card, and any other details you think might be relevant.
3) Discussion in a separate linked thread, please:
If you’d like to discuss a bug (ie, how you feel about it, how you think it reflects on the implementation of the game, how it changes the current gameplay balance etc) make a separate thread and link it to the description thread.
That way, while debugging, Team Radiant can get to the facts that will help us narrow down the relevant code-area as fast as possible, and look at the discussion section separately. Clean descriptive bugs will definitely be easier to address than vague ones!
Bus Report Status
As bugs are submitted, discussed and addressed, they will move through various stages. Moderators will apply tags to each report, and this list will explain what they mean:
No tags The initial bug report submission.
Topic-centric tags (ie. #building, #crafting, #ai) Initial moderator tagging.
#confirmed_by_users tag added One or more forum members have replied in the thread with the same bug, and has been confirmed to not be an isolated incident.
#acknowledged_by_devs tag added The bug has been acknowledged by Radiant, and they have added it to the running list of issues to resolve.
#fixed_for_next_build tag added The bug has been fixed by Radiant, and the fix will be in the next released build.
#fixed_for_next_alpha::tag tag added The bug has been fixed by Radiant, and the fix will be in the next alpha. This tag is used when a bug is fixed but development has already started on the next alpha.
#resolved tag added The bug has been resolved and the build with the fix has been released.
#not_a_bug tag added The reported issue was deemed to not be a bug, but perhaps a misunderstood, intended experience.
#not_reproducible tag added The reported issue may be a bug, but the developers were not able to recreate the issue in their testing, and thus cannot fix the error.
#no_longer_applicable tag added The reported issue may have been a bug, but the feature and/or code reported is no longer in use, and thus the bug report is no longer applicable.
#duplicate tag added The reported issue is the same as a previously reported bug, and the topics have been merged.