Bug Report Guidelines

[Tamamo]

• You may provide a link to a quest file to demonstrate the bug.

Let me reiterate to what DN was getting at. When it comes to duplicating bugs, its much more efficient to provide a testing quest. Cause most of the time something that causes the bug to happen isn't getting duplicated if we do it ourselves.

Remember folks, videos and screenshots are helpful. But are by no means a replacement for a testing quest. It is optional though, but it really helps us out.

tl;dr Provide a testing quest. It makes everyone's livesmuch easier.

[ZoriaRPG]

Let me reiterate to what DN was getting at. When it comes to duplicating bugs, its much more efficient to provide a testing quest. Cause most of the time something that causes the bug to happen isn't getting duplicated if we do it ourselves.

Remember folks, videos and screenshots are helpful. But are by no means a replacement for a testing quest. It is optional though, but it really helps us out.

tl;dr Provide a testing quest. It makes everyone's livesmuch easier.

This, likewise, is why when reporting a scripting bug, unless you provide a step-by-step explanation of how to produce it, or some kind of report that makes it damned easy, it's extremely helpful to have whatever script is causing the problem. This simultaneously saves us time, and allows us to determine if it was a script error, and not a ZC bug, that is at the root of things.

I know that I don't really want to muck about trying to figure out what is causing anything on vague assertions.

Other than that, I changed my wording above mid-stream, from 'should submit', to 'may submit'--certainly not 'must'--above; as I'd rather at least have a report, so that we know that a problem exists. I can't overstress how crucial it is to have these reports, and few-enough users from Pure, or elsewhere, sign up here just to file them. To those that do, thank you kindly.