Introduction
Before filing a bug report or adding your comments to one, it is important that you read and follow the guidelines in this post. To file a bug, please start a new thread in the Bug Reports forum.
Make sure you have found a bug!
Sometimes, what may be percieved as a bug may actually be an intended change in behaviour. While this is less likely to be the case after our Beta phase, it may still apply. Before you file a bug, make sure you check the Development Changelog to see if any recent changes match the description of your bug.
Check that your bug hasn't already been filed.
As the game grows, we will have more developers, testers and players, and it is increasingly likely that bugs will be filed sooner, rather than later.
To save your time as well as ours, please search to see if a bug report already exists for your problem. If it does, please do not file another bug, since unnecessary reports slow down development.
It's important that you don't skip this step. If you need help doing so, please ask.
Can you preproduce the bug?
If you can reproduce the bug every time, please write a step by step guide detailing how to do so. This will be valuable in fixing the bug. If you cannot reproduce the bug every time, give sufficient background information so that a developer can investigate.
REBOL Version
We will need to know which version of REBOL you have installed. You should be able to find this out from the OpenSpora client.
Golden Rules
- Do not add "me too" comments. Only add additional information if it is relevent to reproducing, pinning down or fixing the bug. If a bug is reported on the Windows operating system only, it is perfectly acceptable to mention that you also experience it on Linux (or another OS).
- Spam or off-topic posts in the bug report forum will not be tolerated.
- Do not repeat yourself in the bug report, developers will read the comments fully and only want to read them once. If you disagree with a decision, please only post further comments if you have more to add.
- Please use relevent abbreviations in the "Subject" field when filing a bug, as they will help in identifying bugs from requests, and will give a clear order of importance.
Bug type:
- [BUG] - Indicates that a bug has been identified or is suspected.
- [RFE] - A request for additional enhancements, changes or additions.
Importance:
- [C] - Critical (Crashes or instances where functionality is very broken)
- [N] - Normal (Regular bugs, things that don't work properly but aren't critical)
- [M] - Minor (Spelling mistakes, small glitches, graphical issues)
Resolution:
When developers close bugs, they will mark the resolution as fixed in the subject line. Possible resolutions include:
- [FIXED] - The bug was fixed.
- [WFM] - The bug could not be verified by a sufficient number of testers.
- [INVALID] - The bug is not a bug, i.e. intended behaviour or caused by other factors.
Example subject lines:
- [BUG][C] OpenSpora crashes when I click "Sell All".
- [BUG][M] There is a spelling mistake in the trade news.
- [RFE][N][FIXED] Need Autopatching.
By following this guide carefully, you will help us to improve OSpora with the least possible hassle. If you want to discuss a bug or a change in the game's behaviour, please visit the OSpora Discussion Forum.