This repo doesn't have any code, it's just a convenient dumping ground for any issues users might find in the test builds for DQ1-haxe and DQ2-haxe.
You'll need a Github account to report issues and bugs.
Normal users can't add labels and do much besides create and comment on issues. But if you really, really, like hanging out on our bugtracker for some reason, I can make you a collaborator and give you more power. It's like being a forum moderator, but for bug tracking. Just ping me @larsiusprime in some issue comment if you're into this sort of thing.
In order to fix a bug, we have to be able to reproduce the error or problem you've encountered.
Therefore, please follow the example format below.
(Or just take a look at the EXAMPLE ISSUE)
*Version # is at the bottom-right of the settings screen
**Optional info is just anything else you think might be important
This information lets us know which build/version of the game has a problem
1. Create a new Recipe
2. Tapp on add ingredient
3. Dismiss the view
4. Tapp on new steps
...
If we can't reproduce the bug, we can't fix it!
I expected to see the screen to write my new step
Knowing what you were actually expecting to happen is much more helpful than only knowing what the error was.
The app crash
When I relaunch the app I was expecting to continue my recipe but I had to start from scratch
This lets us know what the allegedly bad result was.