1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

[READ ME] Rules for bug report submission

Discussion in 'Game Bugs' started by CaptainMoebius, May 17, 2013.

Thread Status:
Not open for further replies.
  1. CaptainMoebius

    CaptainMoebius User

    Joined:
    26.03.13
    Messages:
    368
    Likes Received:
    93
    please use the following recommendations while composing threads/messages about the found bugs. the information provided properly will save a lot of time to the ones who will deal with the problem.

    1. name (summary, short bug description).
    this feature will help us to understand, what the actual problem is.
    name:
    • should contain the game component (npc, skill, quest, item, zone, etc.)
    • should make it different from all other bugs
    • should give an understanding what the problem is all about
    • should be short

    2. full description.
    this is the description of the concrete situation which is, in your point of view, a bug. it should contain as much useful information as possible.
    note: for functionality errors it is also important that you indicate whether the bug is 100% possible to reproduce or whether it occurs with a certain chance.


    3. steps needed to reproduce the error (functionality only).
    list of actions needed to follow in order to reproduce the bug. this step is non-obligatory, yet we advise you to do so, as the description might be overloaded with words.

    4. graphics data (screenshots, videos).
    please attach a screenshot or a video of the problem in the best quality possible and mark the places with errors on the screenshots.

    please also follow the rule: 1 bug = 1 post. do not make several posts dedicated to one problem, as well as indicate several different bugs in one post.
     
    Last edited by a moderator: Dec 16, 2015
Thread Status:
Not open for further replies.