As with any game, there are bound to be errors or issues which cause unanticipated or unexpected results while you’re playing. These are known as “bugs,” and this is where you can report them!
Before you start a new post…
…please checkout the following support pages:
- Age of Empires II: Definitive Edition Support & FAQ - This page covers common questions and technical issues, and offers some base troubleshooting advice.
- Age of Empires II: Definitive Edition Known Issues & Solutions - This page contains issues that our developers are aware of and tracking, and may contain special reporting instructions.
- Age of Empires II: Definitive Edition Bug Forums - Search the forums for existing bug reports or other users who may have encountered the same issue. If you find an existing thread for the issue, add your bug report as a reply to that thread.
Reporting a New Bug
When you encounter a bug, here are the first steps you can take when it happens:
- Capture a screenshot! A picture is worth a thousand words; if you’re able, capture an image that highlights the issue. You can use the in-game screenshot key, or you can press the Print Screen key and paste ( CTRL+V ) the image into an image editor to save for later.
- Take notes. It can be difficult to take notes on the fly, but it’s a good idea to jot down a line or two about what you experienced when it happens. Doing this will help you remember the details when you’re posting about the issue them later.
What should I Provide?
Here is what you should aim to collect and provide when reporting a bug (either new or a reply):
- Create a clear and concise title. If you’re creating a new thread, make sure others have an idea of the problem before they ever click into the forum post.
- Include the game version number. The version or “build” number is displayed on the home screen of the game. Include this information so we know when the issue appeared.
- Explain the problem. Provide as many details as possible! Where did it happen? When did it happen? What circumstances may have led to the problem?
- 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.
- Include an image. A good picture is worth a thousand words; a video or gif clearly highlighting the problem is even better!
- One thread = one issue. It can be hard to discuss and respond to issues when there are a hundred listed in a single thread. Try to keep each thread focused on one problem.
That’s it! The more information we receive about an issue, the easier it is for us to pass it to our testing teams for review. Keep the bugs coming and we’ll keep trying to squish them!