Reporting Bugs

Unfortunately, bugs happen from time to time -- and in general, will be fixed as quickly as possible. Our Discord has a good track record of things being fixed in a timely manner.

If you've encountered a bug and want to get it addressed, a few things will help it get fixed.

1. Determine if the problem occurred in the Editor or the Engine. If you're play-testing a game and that fails, your issue is in the Engine. If you're editing the game from the user interface, your issue is in the Editor.
2. Determine that the problem is actually a bug. There are a number of misconfigurations that can create problems. Feel free to reach out to the community in any of the support channels.

Crashes (generally, unless extremely catastrophic) generate logs. The output is different, depending on the source.

Please refer to Troubleshooting to learn how to find logs for RPG Architect editor or engine.

Please share the exact steps that were required to create your issue and include your entire project directory (which should include RPG.project and the Content directory) in a compressed file (.zip is ideal). The issue should be easily accessible with minimal steps and be adjusted in such a way that additional steps can be removed (e.g. starting a new game, talking to the first NPC, recruiting the second hero, etc).

You can provide the content on Discord or send it to support AT rpg-architect DOT com. If your compressed file is too large, you can upload it to Google Drive, One Drive, etc, and provide a link.

Additionally, if your project is sensitive or has private resources, you are more than welcome to notify of the bug on public channels, along with reproduction steps, and contact Locke privately with the actual link or .zip file.