Charge

Support

Guide

Reports

How To Make A Bug Report

  • Hello bug hunters!

  • In this thread, you will learn all the important information on how and where you can report bugs.
    Before you report a bug, please read the information regarding bug reporting in this thread.
    As a result, we can process the bug reports faster and there are usually fewer queries,
    reducing the time between reporting and fixing the bug.


  • How do I report a bug?

  • If you find a bug, then you can easily send it by clicking here

    Please refrain from sending the same report several times.
    The support team will try to take care of the report as soon as possible and then inform you whether the whole thing could be reproduced and thus also forwarded.
    If we're missing specific information about your report, we'll ask you for more helpful information until the error is found.


  • Require Bug Information

  • In order to make the processing of the bugs as easy as possible, a uniform structure that always sorts and builds up all the information is extremely helpful.
    Please use or copy the following bug template in your [bug report]:

    Make sure you title your bug report ticket with the specifics of the bug you are reporting. The more specific, the better.
    1. Subject:
    2. Time:
    3. Current situation:
    4. Expected situation:
    5. Client Version:
    6. Reproduction:
    7. Screenshots / Videos:


  • Here you can find an example on how to fill the template:

  • Subject: Please select as subject a short description of the bug you want to report.

    Time: When did this issue occur? Please be as specific as possible. If it happens repeatedly at all times, please include that information as well.

    Example: Level 61 - Quest - "Reward for the Dark Crystal" not received

    Current situation: Please write here under what circumstances the bug occurs and describe in short sentences what exactly the error is.

    Expected situation: Please explain how the result should be if the bug did not occur or does not exist.

    Client Version: Please specify the version of the client where the bug occurs.

    Reproduction: Please indicate how often the bug can be reproduced and what steps may need to be repeated for it. You have the following options:

    Always: The bug always occurs when reproduced according to your specifications.
    Sometimes: The bug only occurs sometimes or irregularly when reproduced according to your specifications.
    By chance: You do not know exactly how or what you did or the bug occurs under different circumstances.
    No statement: You can not say anything about the reproduction.

    Screenshots / Videos: Please make a screenshot or a video for each bug report and attach it to the bug report.
    If possible, mark the issue spot in red.[Guide for ScreenShot]
    Videos should be limited to the essentials, meaning that the videos may be cut as long as no significant information about the bug is lost.
    In addition, we ask that you do not deposit the videos with any background music, as these are only disturbing and out of place.
    Furthermore, the quality of hosters such as YouTube for purposes of use must be at least 720p.
    Based on the screenshots or videos, we should be able to reproduce the bug, but reproduction information is always helpful.


    Keep in mind that even though your post will be read, you may not receive a development team response. However, any changes made in regards to bug reports are be listed in the Seiya patch notes.
    Subscribe