Bugs, Ideas, and Typos - Imperian Online Help
19.6 Bugs, Ideas, and Typos
First, some general guidelines: - DO Include as much relevant detail as possible (we'll get into this more later) - DO give us any information required to reproduce the issue. - DO file bugs and typos from within the room they occur, if applicable - your current room is automatically included in the report. - DON'T include anything extra. Commentary, editorializing, even just trying to be clever, make it harder to read your reports and fix the issues. - Please DON'T file a report if it is merely a matter of opinion. This applies more to typos than to bugs, but is a general guideline nonetheless. - Please DON'T file bugs exclusively via out-of-game methods (such as the forums). ALWAYS post a report in-game first. Additionally, if you are filing a new bug to clarify one that has been closed, please treat it as a NEW report, and include all of the information from the original report. Closed reports are purged over time, and referencing one in a new report may be meaningless when we actually get to fixing it! If you've already filed a report, but need to add additional information to it before it is resolved, you can do so using the COMMENTBUG command. This will add a comment that we can see. In some cases, an individual investigating or triaging a bug may send you a message asking for clarification or comments. Some additional tips for bug reporting 1) If it is a skill related bug start off your bug report by saying the skill and ability names. 2) Bugs are tracked down through messages received and user input. Please include whatever errant message you got and what you typed. 3) If there were multiple steps to the bug, or you are able to replicate it, please include what happened and in what order. Now that the preliminary is out of the way, let's talk about TYPO reports! We'll move on to bugs after that. The TYPO queue doesn't only represent typos in the classical sense. A typo report should be filed any time some text in the game is incorrect. This includes traditional typos (a letter or word is wrong, grammar is incorrect), as well as: - Mistakes in skill help files (AB) such as outdated, incorrect, or missing information. - Mistakes in general help files (HELP) such as outdated, incorrect, or missing information. - Mistakes in game messages (ambient messages, skill messages, etc). When filing a typo report, include AS MUCH of the following information as possible (and that applies): - If a typo relating to an item or mobile, include the item or mobile number (found via II or IH) - If a typo in a room description, please file the report from within the room, and note that it applies to the room you're in. * If you aren't able to return to the room, please make every effort to give us the name or room number of the room! - Include the line that contains a typo. - Include the specific mistake in that line. Just pasting in the line may not be helpful, because we might not notice what you noticed! Now for the BUG queue. The BUG queue should contain any report that isn't a TYPO or an IDEA. If you submit something that should properly be classified in one of the other queues, it may be moved to the appropriate queue, or may be removed as not a bug. As with typos, include AS MUCH of the following information as possible (and that applies): - As much information as possible about the bug, and how to replicate it. This is especially important with skill bugs and quest bugs, as it is not always obvious how to create a situation where obscure bugs can be found and thus fixed. - If the bug relates to an item or mobile, include the item or mobile number (found via II or IH) - If the bug is in a room or room effect, please file the report from within the room, and note that it applies to the room you're in. * If you aren't able to return to the room, please make every effort to give us the name or room number of the room! - If relating to a skill, include the skill that has a problem, as well as any mitigating or contributing factors that may be impacting the behavior. - If relating to a quest, where possible include the name of the quest and information about the stage of the quest. There are a lot of quests in Imperian, and none of us know the details about all of them. - Bugs are tracked down through messages received and user input. Please include whatever errant message you got and what you typed. Here are a few examples of bug reports that lack information (avoid these!): bug <ability> in <skillname> doesn't work' - This bug is not sufficient. Please be as detailed as possible. Explain how it doesn't work. What do you expect to happen, and what happens instead. bug The boar in the forest hit me with a sword. It shouldn't have a sword' - This bug is also not sufficient. If you're reporting bugs that deal, in any way, with items or mobiles, it is necessary for you to report the number of the object that you're reporting. There could be many boars in the forest, and without knowing which one you are referring to, the bug is impossible to track down. You may also submit ideas to the design team using the IDEA command. The syntax is simply: IDEA <your idea>. Relevant commands: BUG <whatever> - Submit a bug report to the administration. BUGSHOW - See a list of all the bugs you have submitted. BUGSHOW [<#>] - Shows you what you submitted for a particular bug number as well as any comments on it. COMMENTBUG <#> <whatever> CB <#> <whatever> - Comment upon a bug you previously submitted. TYPO <whatever> - Submits a typo to the administration. IDEA <whatever> - Submits an idea to the design team. IDEASHOW [<#>] - Show all of your submitted ideas, or optionally, just one. If you have an issue that is an emergency that needs dealing with, please type HELP ISSUES to see how to report it.