Bug reports must be properly formatted before the dev team can fix them. Once a bug has been discussed and there is a consensus on what to do then a report can be made. The report should be in the following format:
"Describe current behavior. Describe expected behavior"
That's it. It's as simple as that. No need to add background or justification since a consensus will have already been made. It should be as simple and concise as possible. For example:
A good bug report, simple, complete, describes expected behavior:
"If a character's attack target is destroyed the character will sometimes continue to walk to the target's last location. The character should stop moving once it's target is destroy."
A bad bug report, does not describe expected behavior:
"Unconsciousness prevents you from being targeted by hostile creatures unless you are specifically targeted and unconscious characters are not visible to the spell farsight."
Once a bug report has been accepted by the team we will flag it to let everyone know its in the process of being worked on.
"Describe current behavior. Describe expected behavior"
That's it. It's as simple as that. No need to add background or justification since a consensus will have already been made. It should be as simple and concise as possible. For example:
A good bug report, simple, complete, describes expected behavior:
"If a character's attack target is destroyed the character will sometimes continue to walk to the target's last location. The character should stop moving once it's target is destroy."
A bad bug report, does not describe expected behavior:
"Unconsciousness prevents you from being targeted by hostile creatures unless you are specifically targeted and unconscious characters are not visible to the spell farsight."
Once a bug report has been accepted by the team we will flag it to let everyone know its in the process of being worked on.