A lot of you are beginners, a lot of you aren't. That doesn't matter. What does matter is that people get errors and they don't know how to fix it, so they ask here. Now that's all fine and dandy, but if you want help, you simply cannot afford to be vague about it - no one will help you, and even less people will bother. Here's a perfect example of what's bad in a help request:
"Well I have figured out how to model edit, but the head is the only problem I cant fix! Can someone help me with this? "
That's all that was said. That's like "WTF?" That doesn't give me any helpful information at all. You listed an extremely broad category of what was wrong. The head. What was wrong with the head? The helmet you are using isn't the right size? The hair is messed up? The facial textures on a race swap are wrong? What?! That being said, a very helpful error report would be as such:
"I changed a human to undead, but when I log in the helmet size is off. What's wrong?"
There. That's fantastic. It clearly states the issue and what caused it. All thats left is for people to help fix it. Now if you're getting a WoW Crash error like #132, then it gets more complicated. A good report for one of those would look like:
What Error: (WoW Crash; #132, Swap didn't work, etc)
Model Edit Fix on?: (Yes, No, Don't know)
What type of edit: (Standard, DBC, WDB)
- If DBC, what program used to edit DBC? (DBC convert ~> Excel, CSV'd, straight DBC editor, etc)
What you did: (Weapon Swap, race change, armor, whatever)
___
There. that's an even better error report, it helps people like me understand exactly what you did, what you used, and where you might have gone wrong. in fact, if every person asked for help using such a form, I'd probably help every one because it'd be so easy to read.
And there you have it, if you make your error reports clear and easy to read, you dramatically increase your changes for getting help and getting it resolved.