REPORTING BUGS
When reporting a bug please be sure and check that there is not already a recent thread dedicated to the issue you have come across as well as the Bug Index Page. If there doesn't seem to be an existing thread reporting the error, start a new one.
On the grid (on most game pages and found via the drop down), you will find a bug report form which asks a few questions to help us narrow down exactly what is causing the bug. Please fill out the form as completely as possible when you submit a bug report. Submitting the bug report from the grid automatically starts a new thread on the bug report forum.
Please also, when possible, try to submit reports for bugs which could be game breaking and beneficial (such as a bug that lets you gain experience without expending energy) directly to Caligrace, the Bug Admin and Developer. Mark as URGENT in the title if the bug is one that can be abused.
WHAT TO DO/EXPECT
After you report the bug:
There are numerous ways to help with the bug fixing process. You can try to replicate the bug and report your findings if asked. Note though, that if you're caught abusing a beneficial bug for character benefit (and you have not reported it, or in reporting it have misrepresented certain facts), you will be subject to having any benefit stripped along with potential for reprimand. Mind you, this is only an issue if you're not being transparent in your helping with the testing.
It's very helpful for questions to be asked as to narrow down and link similar, or related bugs, but we would prefer for no irrelevant conversations to be held on the bug forum. This is to help condense and keep searches easier. If a bug requires conversation, please separate and move it so it can be discussed in full. For future suggestions, please let one of us know.
Any posts which do not help with the bug fixing process, or pertain to the bug itself will be deleted. If it’s a common occurrence, further action may be taken.
Also, keep in mind that bug fixing can be a long process. Patience is key.
SPECIAL LABELS
Special labels are usually placed on thread topics by Developers, but you can do it yourself if you have a good understanding of the bug fixing process. Please note, if you tag a post yourself, it is subject to be changed once the bug admin has a chance to look the bug over.
Please put the label at the beginning of the bug title, as it’s easier for the bug admin to search through and pick out the urgent bugs.
Example of a labeled title: [f] Bug Title Here.
"[a]" -- Urgent bug. Interruption to gameplay, or something which makes it harder to play the game for one or more characters.
"" -- Medium Urgency. Something which might be annoying, but doesn't interrupt or ruin gameplay for anyone.
"[c]" -- Minor. Probably something to be added to the list of known minor bugs. Superficial bugs or bugs which are easy to avoid are given this category.
"[x]" -- Not a bug. Soon to be archived.
"[f]" -- Fixed. Soon to be archived, allowing time though for testing.
"[?]" -- This label is given when the developers or bug mods have looked at the bug and require more people to give feedback or information. Can be used with other labels.
"" -- This means that the bug is unconfirmed. Some bugs are reported due to various mistakes, and we don't usually go digging through the code looking for a bug until either multiple people have confirmed it, or it's easy to identify as a bug.
"[h]" -- This means that the bug is either hard to fix, or we can't work out what's causing it, despite our best efforts. These bugs will usually take longer to get fixed.
When reporting a bug please be sure and check that there is not already a recent thread dedicated to the issue you have come across as well as the Bug Index Page. If there doesn't seem to be an existing thread reporting the error, start a new one.
On the grid (on most game pages and found via the drop down), you will find a bug report form which asks a few questions to help us narrow down exactly what is causing the bug. Please fill out the form as completely as possible when you submit a bug report. Submitting the bug report from the grid automatically starts a new thread on the bug report forum.
Please also, when possible, try to submit reports for bugs which could be game breaking and beneficial (such as a bug that lets you gain experience without expending energy) directly to Caligrace, the Bug Admin and Developer. Mark as URGENT in the title if the bug is one that can be abused.
WHAT TO DO/EXPECT
After you report the bug:
- The bug is replicated (by bug mods or devs only unless asked otherwise.)
- The bug is marked for severity (by bug form submission or developers). See the special labels section below for further details.
- Bugs will be processed as quickly as possible, usually in order of severity.
- When a bug is being worked on, a Dev will post that they are going to attempt a fix. This will also act as a heads up in case something goes wrong while they are working with the code. If you get seemingly random error messages on the grid while one of these notices is up, that is likely the case.
- The Dev will post again when they think the bug may be fixed and mark the title accordingly. There will be a small wait period to ensure it’s fixed and no other issues have arisen.
- If there are no further issues, a Developer will archive the bug!
There are numerous ways to help with the bug fixing process. You can try to replicate the bug and report your findings if asked. Note though, that if you're caught abusing a beneficial bug for character benefit (and you have not reported it, or in reporting it have misrepresented certain facts), you will be subject to having any benefit stripped along with potential for reprimand. Mind you, this is only an issue if you're not being transparent in your helping with the testing.
It's very helpful for questions to be asked as to narrow down and link similar, or related bugs, but we would prefer for no irrelevant conversations to be held on the bug forum. This is to help condense and keep searches easier. If a bug requires conversation, please separate and move it so it can be discussed in full. For future suggestions, please let one of us know.
Any posts which do not help with the bug fixing process, or pertain to the bug itself will be deleted. If it’s a common occurrence, further action may be taken.
Also, keep in mind that bug fixing can be a long process. Patience is key.
SPECIAL LABELS
Special labels are usually placed on thread topics by Developers, but you can do it yourself if you have a good understanding of the bug fixing process. Please note, if you tag a post yourself, it is subject to be changed once the bug admin has a chance to look the bug over.
Please put the label at the beginning of the bug title, as it’s easier for the bug admin to search through and pick out the urgent bugs.
Example of a labeled title: [f] Bug Title Here.
"[a]" -- Urgent bug. Interruption to gameplay, or something which makes it harder to play the game for one or more characters.
"" -- Medium Urgency. Something which might be annoying, but doesn't interrupt or ruin gameplay for anyone.
"[c]" -- Minor. Probably something to be added to the list of known minor bugs. Superficial bugs or bugs which are easy to avoid are given this category.
"[x]" -- Not a bug. Soon to be archived.
"[f]" -- Fixed. Soon to be archived, allowing time though for testing.
"[?]" -- This label is given when the developers or bug mods have looked at the bug and require more people to give feedback or information. Can be used with other labels.
"" -- This means that the bug is unconfirmed. Some bugs are reported due to various mistakes, and we don't usually go digging through the code looking for a bug until either multiple people have confirmed it, or it's easy to identify as a bug.
"[h]" -- This means that the bug is either hard to fix, or we can't work out what's causing it, despite our best efforts. These bugs will usually take longer to get fixed.
