1. We have added the ability to collapse/expand forum categories and widgets on forum home.
    Dismiss Notice
  2. All Civ avatars are brought back and available for selection in the Avatar Gallery! There are 945 avatars total.
    Dismiss Notice
  3. To make the site more secure, we have installed SSL certificates and enabled HTTPS for both the main site and forums.
    Dismiss Notice
  4. Civ6 is released! Order now! (Amazon US | Amazon UK | Amazon CA | Amazon DE | Amazon FR)
    Dismiss Notice
  5. Dismiss Notice
  6. Forum account upgrades are available for ad-free browsing.
    Dismiss Notice

Please read: Bug reporting - Include the Patch Version in your thread title

Discussion in 'Civ6 - Bug Reports' started by Camikaze, Oct 20, 2016.

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

    Camikaze Administrator Administrator

    Joined:
    Dec 27, 2008
    Messages:
    26,859
    Location:
    Sydney
    No game is without flaws. Hopefully there aren't many, but if we find some, they can be fixed much faster with some good bug reporting. To help with this, please do the following:

    1. Do a search first. If someone else has reported the bug you have found already, then please post in that thread instead of creating a new one. This makes it easier to identify all instances of a particular bug.
    2. Include the Patch Version number in your thread title and post. This number can be found at the bottom of the menu screen. For example, you might use the title '[1.0.0.26] Bug description'.
    3. Be thorough with your descriptions. If you played the turn in a certain order and it caused a crash, try to note what exactly you did. A lot of times this isn't important, but for the few times it is having the exact order can be critical to reproducing an issue.
    4. Where possible, try to reproduce the bug. Load the save file, play in the same order, and show that it happens again. If you can do that, then post the save file along with what needs to be done to reproduce it. Add [reproducible] to the thread title.
    5. Try to post saves from BEFORE a bug manifests itself. Also ties into point #1. If we have a save where a bug occurs 100% that's the ideal situation. Most of the time spent "fixing bugs" actually involves trying to find out WHY a problem is happening, while the fix itself takes only a minute or two. Often times a save from after a problem has occurred is little help in determining what CAUSED the problem to begin with.
    6. Post what happened against what you expected to happen.

    And finally, please be civil. We realize that bugs can in some cases ruin your gaming experience, but that is no excuse to be rude.
     
    Last edited: Nov 19, 2016
Thread Status:
Not open for further replies.

Share This Page

Ebates: Get Paid to Shop