bug What to do when things go wrong

[GrantSP]

With the latest update of MO, 1.2.15, some users are apparently overly concerned with some minor issues.

Currently Tannin has locked the Nexus forum due to the amount of pointless questions that are asking the same thing that was answered only a handful of posts previously.

A similar thing does occur here in the MO support forum, and also in the wider STEP forum.

 

So, what steps should you take if think you need to post a question?

 

1. Observe the Pins -- At the top of the Mod Organizer Support forum is a bunch of stickies (this is one of them). There are solutions to common problems there. Check there first.
2. Search the forum -- In the top right hand corner is the 'Search' function. It works. It works REALLY WELL. Use it.
3. Search the forum again -- If your chosen search parameters didn't yield the answer you wanted, choose something else.
4. Search the forum yet again -- Yes I do mean this. Sometimes the answer may be in a post that isn't directly related to your issue.
5. Read the posts -- As well as searching for direct answers, read a section of current threads as often snippets of information that are valid for a wide range of issues may be mentioned.
6. Don't worry -- Mostly the issues you have are minor and wont affect your gaming experience.
7. Phrase your post in a way that elicits helpful replies -- "Why did your update break my game?" or "This function is stupid" are not very attractive even though that is what you may be feeling at the time. We've all done it, posted in the heat of update rage. From now on though, just take a minutes break and calm first, then word your question.
8. Does your input really need to be added? -- Is what you are asking, or stating, add to the overall infobase about the issue? Could you just wait and see if others have similar problems and thus verify that what YOU are seeing is actually an issue.
9. Be helpful -- Along with asking the question, provide as much detail as you can. Any settings that you have that will be needed to replicate the issue. Use 

   [spoiler]text[/spoiler]

    tags or post them into a hosting service like PasteBin. Include screenshots if they help. The more you tell, the quicker the solution will be.

10. When the answer is provided, it will be helpful to mark that response as 'Answered' thus assisting the users to see where their attention can be directed
11. Come back -- When you feel like adding to the experience and you have something you can assist with, feel free to do so.
12. Avoid the "Einstellung Effect". -- That is asking for help with your solution rather than asking for help with your problem. That is, you are trying to solve problem X and you think solution Y would work. But instead of asking about X when you run into trouble, you ask about Y.
    

     

Edited November 9, 2015 by GrantSP

[GrantSP]

About time this topic had a bit more substance to it so I was going to add some more information when it dawned on me: "why not just provide a link to one of the best articles around that discusses this subject?"

 

The following link is to Lee Dohm's blog. He is currently one of the moderators on the Atom forum and has a wealth of knowledge on handling issues, and those that post them.

 

So, before you run off and completely dismiss his blog and continue on to posting your report, please read it.

 

Writing Good Bug Reports