• Welcome

  • Help

  • Who's Who

  • Bug Reports

  • The Game

  • Data

  • Walkthrough
    		•

    Doing bug reports

    This chapter won't deal with how to do bug reports, as this is covered well enough on the beta site. You should take the time to read through the bug report page and the parts of the FAQ concerning bugs at least once. Good bug reports are essential to getting this game up to release standards as soon as possible.

    I will point out some important issues concerning bugs and bug reports. It might involve repeating some of the info you will find on the beta site, but this is important. Bug reports are really what you are here for.

    Don't spread exploits

    To test properly, especially when it comes to play balance, it's important to minimize the impact of a fault in the system. If everyone were to create high level characters through an exploit, leveling and play balance would not get properly tested. So report those exploits, and keep them to yourself, please.

    Check the known bugs list

    It's no use reporting a bug that is already known, and the team has enough info about. However if the bug is not listed, even though you know it's been reported by someone else, you should report it. The team might need some extra info that you might just have.

    Include important information

    (Copied from the beta FAQ)
    1) Whenever possible, use the ingame tool to report the bug. Usually when the client crashes, a bug report tool should open automatically. It will contain a lot of useful debug info for the team. If this doesn't work, follow the instructions in item 2 - 4.
    2) Copy the last 50 lines of the file out.dat into the bug-report. This is found on the root of the directory where you have Anarchy Online.
    3) Copy the file anarchycrashlog.txt into the bug-report. This file is also found on the root of the directory of Anarchy Online.
    4) Include as much information as possible about your hardware and drivers.
    5) Investigate if it is possible to reproduce the crash bug, and include information about this in the bug report.
    6) Concentrate on describing the bug, avoid to diagnose the problem.

    Step 4 can be made easier by collecting some info in a text file and just copy it into the bug report.

    Get your e-mail address right

    You normally don't get a reply on a bug report, but the team might want to get in touch with you to get some more info.

    Hosted by www.Geocities.ws

    1