Sticky READ THIS FIRST BEFORE POSTING - Rules for Bug Reports

Forum Rules


*UPDATE* ONE BUG PER THREAD.

What is the purpose of this forum?
As the description implies, this forum is for reporting any bugs pertaining to the prototype of Castle Story. These reports should be posted here, and only here. The Sauropod team can leverage the information to address show-stopping bugs with the prototype, as well as potential problems with the beta client.

What are we allowed to discuss?
Bugs, bugs, bugs. In order to make this area as useful to the developers as possible, all posts will be heavily moderated - meaning, folks should refrain from responding unless they truly have something of note to share. Two and three word confirmations or acknowledgements of previous posts will not remain. Feedback that is in no way related to a prototype related bug will immediately be removed.

When should we make a contribution?
Please only create a new topic, or respond to an existing topic if you have new information to provide. Remember, this is for the developers, to help them improve the game we all admire. Please also use the "like" feature to indicate your own confirmation of an existing bug that gets posted (as opposed to making a "me too" post). The more likes a particular bug receives, the better the developers can determine how widespread the problem might be.

Remember, let's not bog down what could otherwise be helpful threads with meaningless content.

How can we help keep this place focused?
If you see new threads or responses to existing topics that are questionable, feel free to report them, and a moderator will address it as quickly as possible. Again, the more focused we can be here, the better it is for everyone: the developers have a wonderful source of community driven bug reports, and we get a much improved game in the end.

Is there a format for bug reporting?
Yes, in order to make it easier for the developers to understand the issue, and track the bugs, please use the following format:

Client version: This will obviously be exclusive to the prototype for now.
Bug description: In as much detail as needed, please describe the bug.
Steps to reproduce bug: Describe how one could reproduce the bug.
Image: If necessary, attach an image to display the bug.

Is there anything else we can provide to help troubleshoot the problem?
Yes, some of the staff are working on developing a means to let members upload their basic hardware configuration information (dxdiag.txt). Once that process is established, it would be useful if that file were provided as a part of your bug report.

I made the title way more flashy and caps-locky. Your welcome <3