How to Get Technical Support
The Game Code Mastery support system is designed to provide a robust support solution so more people get actual developer answers, not fewer. Questions are tracked in one place instead of getting buried, which makes it possible to manage support at a larger scale without leaving people waiting in a thread that never gets seen.
The official recommended methods are the forum, GitHub, and email. If you want technical support or an answer from the developer, you must use one of those.
TIP
Read the docs and search first. A large share of questions are already answered in Setup guides, Usage guides, or the AARPG FAQ.
Where to ask
| You want… | Go here |
|---|---|
| Official — forum | Help on the official forum |
| Official — GitHub | GameCodeMastery/support Issues |
| Official — email | support@gamecodemastery.com |
| Known issues / update notes | Forum Announcements |
| Feature requests and product suggestions | Forum Feedback |
WARNING
Discord is not officially supported. If you want technical support or an answer from the developer, use the forum, GitHub, or email.
Official support forum
The official support forum is powered by Discourse: https://discuss.gamecodemastery.com
This is one of the official recommended methods. Questions posted in Help get developer attention first: https://discuss.gamecodemastery.com/c/help/6
Use the right category:
| Category | Use it for |
|---|---|
| Help | Support questions and issue reports (read the topic template) |
| FAQ and Tutorials | Guides, reusable answers, how-tos |
| Announcements | Official news, updates, known issues |
| Feedback | Product / docs / forum suggestions and feature discussion |
| GCM Community | Introductions, showcases, community chat |
| General | Topics that don’t fit elsewhere |
| Offtopic | Everything else |
New here? Start with New users start here in FAQ and Tutorials.
GitHub
GitHub is an official recommended method: https://github.com/GameCodeMastery/support/issues
Open a new issue with the same details you would put in a forum post. Search existing issues first in case someone already asked.
Email is an official recommended method, and it’s checked and maintained often.
Include the same details you would put in a forum post or GitHub issue: product, engine version, whether it happens in the demo or your project, repro steps, expected vs actual behavior, and relevant log text.
The forum and GitHub are the better places when you want the answer to be public and searchable. Use email when you prefer a private conversation, or just prefer writing it that way.
Before you ask
- Search. Check this documentation, the AARPG FAQ, existing forum Help topics, and existing GitHub support issues.
- Read the relevant Setup / Usage guide for the system you’re using.
- Reproduce in the included demo when the question is about a purchased product. If it fails in the demo too, say so. If it only fails in your project, that’s usually setup or integration.
- One problem per topic when you can.
What to include
Clear reports get clearer answers. Include:
- Product (e.g. Advanced ARPG Combat) and product / build version
- Unreal Engine version
- Whether it happens in the demo project, your project, or both
- Exact steps to reproduce
- Expected vs actual behavior
- Relevant Output Log text (paste text in a code block — not only a screenshot)
- What you already tried from the docs
Good title: UE 5.4: melee montage plays but collision never hits after migrate
Bad title: Help / Broken / Combat
WARNING
Vague reports with no engine version, no repro steps, and no demo-vs-your-project distinction are hard to answer accurately.
For Advanced ARPG Combat, also see FAQ and Troubleshooting — it has the full diagnostic checklist and the most common migration failures (Gameplay Tags, plugins, Game Mode / Game Instance, collision, surfaces).