User Tag List

Results 1 to 4 of 4

Thread: Bug Report Guidelines

  1. #1
    Heavenly Knight Tamamo's Avatar
    Join Date
    May 2011
    Location
    Colorado
    Age
    27
    Posts
    711
    Mentioned
    69 Post(s)
    Tagged
    2 Thread(s)

    Exclamation Bug Report Guidelines

    With us now in Open Source, we might have to put forth some new guide lines. Here's what I came up with. The previous Bug forums where a mess. I would much appreciate it, if that did not happen again. :)
    DNs previous post. <-Seriously why was this moved in the first place.

    List of Icons and meanings
    Dead Bug: Bug has been confirmed fixed
    New Bug: Bug that was recently reported, this the icon you should use. It's icon will be changed later don't worry.
    Not a Bug: Behavior is intentional and a consensus has been reached that nothing should be changed.
    Sick Bug: Has attempted to be fixed, awaiting confirmation.
    Unverified Bug: A bug that has yet to be verified.
    Verified Bug: A bug that has yet to be addressed but has been verified.

    Moved bug is no longer used. Since we don't have categories.

    The Debugging Cycle
    Find A Bug
    Report Bug
    Gets Categorized by Moderators
    Gets Vertified by members
    Gets Fixed by coders
    Fix is Confirmed by members
    Last edited by Tamamo; 06-18-2016 at 10:12 AM.

  2. #2
    Mad, Mad, Author ZoriaRPG's Avatar
    Join Date
    Oct 2006
    Location
    Prydon Academy
    Posts
    699
    Mentioned
    61 Post(s)
    Tagged
    1 Thread(s)
    I'll add to this:

    • Specify the version of ZC, or ZQ, in which you observed the bug. It's a good idea to put this in the topic title, too.
    • Specify the platform (Windows, Linux, OSX) and your OS version.
    • Provide a detailed account of the problem.
    • If the bug relates to ZScript, please supply the script, and/or a quest file.
    • Please do not submit reports for ancient/old beta versions of ZC, unless the bug persists in the latest 'final' release.
    • If possible, provide screenshots, if they will be helpf to comprehend the problem.
    • You may provide a link to a quest file to demonstrate the bug.


    Script Headers: RPG.zh ( v. a0.97.1 ) ( RPG.zh Thread ) | stdArguments.zh (v.6.9.9/1) | | Timers.zh (v.1.5)
    ZScript | ZC Dev | ZC 2.53 | Alucard's: stdCombos.zh (v1.1) | stdWeapons.zh | particles.z
    All of the code that I create and publish here is free for use, modification and distribution under the GPL v2.0.

  3. #3
    Heavenly Knight Tamamo's Avatar
    Join Date
    May 2011
    Location
    Colorado
    Age
    27
    Posts
    711
    Mentioned
    69 Post(s)
    Tagged
    2 Thread(s)
    Quote Originally Posted by ZoriaRPG View Post
    • 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.

  4. #4
    Mad, Mad, Author ZoriaRPG's Avatar
    Join Date
    Oct 2006
    Location
    Prydon Academy
    Posts
    699
    Mentioned
    61 Post(s)
    Tagged
    1 Thread(s)
    Quote Originally Posted by Tamamo View Post
    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.


    Script Headers: RPG.zh ( v. a0.97.1 ) ( RPG.zh Thread ) | stdArguments.zh (v.6.9.9/1) | | Timers.zh (v.1.5)
    ZScript | ZC Dev | ZC 2.53 | Alucard's: stdCombos.zh (v1.1) | stdWeapons.zh | particles.z
    All of the code that I create and publish here is free for use, modification and distribution under the GPL v2.0.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
About us
Armageddon Games is a game development group founded in 1997. We are extremely passionate about our work and our inspirations are mostly drawn from games of the 8-bit and 16-bit era.
Social