Bug Reports
If you find a bug in TURBU, please let me know about it so I can fix it. There are a couple different ways to send in a bug report.
The preferred way is to use the issue tracker on my Google Code project site. Click on “New issue” and write up a quick report. It’ll automatically notify me by email when someone posts a new issue. Having issues submitted there makes things a lot more convenient for several reasons:
- You can attach files, such as screenshots, screencap videos, or the output of the error reporting tool built into TURBU.
- When I make progress, close the issue, or add a comment, it’ll notify you by email.
- It allows other users to comment on it and provide feedback.
- It keeps a “paper trail” of what’s been done and what hasn’t.
You need a Google account to use the issue tracker. I’m aware that some people don’t feel comfortable with opening a Google account, though, and I can respect that. If you find a problem and you don’t want to use the issue tracker to report it, you can post about it as a comment on the dev blog, preferably on the announcement page for the release you found it in. If you want to post a comment this way, please include your real email address so I can get in touch with you. (No one but me will be able to see it, and I won’t share it with anyone.)
Either way, in order to fix a problem, I need to be able to reproduce it at my end first. To do that, I need to know exactly what you did to cause the problem, and I need to be able to repeat it. So please include a detailed description of the problem, including a download link for your project if I don’t already have it. For example:
The trees in the lower left corner of map “Big Forest” display the wrong tiles. You can find my project at www.example.com/download.html.
Or:
On map “Ruined Fortress – Interior 3”, opening the guard at the top of the map in the Object Editor and switching to event page 2 causes an error. I’ve attached the error report. You can find my project at www.example.com/download.html.
The more relevant information you can give, the better. Simply saying “X doesn’t work” is no good for any but the most absolutely obvious bugs, since it doesn’t tell me anything I can use to figure out what’s going wrong.