Page 1 of 1

Bug reports guideline (updated)

PostPosted: Sun Dec 30, 2018 9:32 am
by DaVinci
Nothing speeds up the fixes creation as good as a properly composed bug report ^_^
That's just a little tip on how to compose one.

Normally, that should include the following:
- Brief description
- Expected behavior
- How it actually works
- Steps to reproduce it
- (if possible) Some visual attachments, be it a screenshots and/or gif/video recording.

Attachments are not required, but having a snapshots of a game when some weird stuff happens might help a lot in issue pinpointing process - it's pretty normal that some bugs might be hard to reproduce, thus inflating the work time just because a dev tries to get that to work as reported.
That's pretty much it. If you have any suggestions/objections/propositions - feel free to reply!

Cheers!

Re: Bug reports guideline

PostPosted: Tue Jun 11, 2019 6:14 pm
by Allan
We have created a bug reporting list on github.
this would be preferable to posting here, but if you dont have a github account, post your bug here and one of us will port it to github. (with a note to the original author/finder)

the link for the github bug page is https://github.com/zhyrohaad/AlasiyaEvE/issues


ALSO NOTE:
when bug is thought to be fixed, the original author/finder will be messaged to test again for proper operation.