[HOW TO] Report a Bug in Age of Empires IV

Thank you for coming to the official Age forums to report your bug or issue encountered with Age of Empires IV. Please follow these guidelines when making your report as they help our teams to prioritize and reproduce issues so that they can be addressed.

:mag: Before You Post - Scout for Other Reports!

Bug reporting is a community effort, so before you post about a bug, check to see if the issue has already been reported:

  • :heavy_check_mark: Read the Age of Empires IV Support Pages for frequently asked questions, technical issues and troubleshooting support.

  • :heavy_check_mark: Check out the Age of Empires IV Known Issues & Solutions to see a summary of issues our Development Team is currently focused on tracking.

  • :heavy_check_mark: Search the Age of Empires IV Bug Forums for existing reports of the same issue by other players - if another player has already reported the issue, please add your report to the same thread, and give the main post a Like image to add visibility to the issue.


:pick: What You Will Need - Gathering Resources!

Here is what you should aim to collect and provide when reporting a bug (either new or a reply):

  • :heavy_check_mark: Gather keywords to describe the issue.
    Keywords should be things such as the error code or error message that you encountered, the impacted unit, building, or civ, and/or a brief description of the action that triggered the issue and its result. We know some error codes can be long, but please try to include the entire code when possible.

  • :heavy_check_mark: Take a screenshot of the issue if you are able.
    Sometimes a visual helps to highlight the issue. You can use the Print Screen button on your keyboard, or the Windows Snipping Tool (Windows Icon + SHIFT + S) to easily capture a screenshot for pasting (CTRL + V) into the forums.

  • :heavy_check_mark: Try to reproduce the issue.
    Knowing the steps needed to replicate an issue goes a long way to helping us track down a bug, and can help with writing reproduction steps into your report. If you cannot reproduce an issue, please still report it!

  • :heavy_check_mark: Submit other requested information.
    Sometimes staff may ask that users experiencing a particular issue should submit additional information, such as DxDiags, Warning Logs, or Save Game files. Directions on gathering that info can be found HERE and should be submitted to support HERE.


:hammer: Posting a New Bug Thread - Building a Report!

When starting a new thread, your bug report should contain the folowing information at a minimum:

  • :heavy_check_mark: Include the game version number.
    The version or “build” number can be found in the game on the Settings menu, in the top-right. This helps isolate if the issue is from a previous build, or a more recent update.

  • :heavy_check_mark: Explain the problem.
    Provide as many details as possible! Pictures are great to include, but also type a text-summary of the issue. Let us know what you experienced versus what you expected. Try thinking about how you might explain the issue to a new player.

  • :heavy_check_mark: Callout any triggering events.
    What map and game type were you on? Did this occur early, mid, or late game? How much time had passed in the match before the issue occured? What game events occurred right before the issue? Did a player just Age-up? Did the match host surrender? Were you queuing-up a particular unit or building? Was a massive battle taking place?

  • :heavy_check_mark: Provide reproduction steps.
    A numbered list of steps we can take to reproduce the issue can help us track it down in our internal environments.


:sparkles: Posting Etiquette - Age Up Your Bug Report!

These guidelines help to keep these forums tidy, and assist other users in finding reports about a bug or issue:

  • :heavy_check_mark: Create a clear and concise title.
    Use keywords in your post title to create a small summary of the bug. The helps us and other users know what your post is about.

  • :heavy_check_mark: One Thread = One Issue.
    Please try to keep each thread limited to one issue. If you have multiple issues to report, please make a separate report for each issue.

  • :heavy_check_mark: Code of Conduct.
    Please respect the rules and general Age of Empires Forum Code of Conduct while in this space. Thank you!


2 Likes