User:Skakid9090/PvX:DontBeADick

Many times comments on build pages are harsh and insulting. These are guidelines for being subtle about build comments.

Guidelines

 * Builds are written by people, not robots. Be aware of this fact.
 * Builds are sometimes incredibly bad, but instead of insulting it, take up the responsibility of teaching the build author what makes a good build a good build.
 * Suggestions help more than put-downs.

Bad Example
Hey guys. This is a pretty good build I use in AB, give it a shot. --- NoobXXX January 1, 2007
 * Wow. This is the biggest piece of shit build I've ever seen. How about instead of making stupid shit like this you make good builds. Never post this kind of crap again. --- Elitest9090 January 2, 2007

Good Example
Hey guys. This is a pretty good build I use in AB, give it a shot. --- NoobXXX January 1, 2007
 * The build isn't too great. The skills have limited synergy with one another, and it's not any stronger than our currently vetted builds. Try exchanging |Skill A| with |Skill B|, you should get better results. Also, check out |Build:UberLeetness|, which has the same goals as yours, but accomplishes it more effeciently. --- NiceGuy17 --- January 1,2007

OR

The build isn't good. --NiceGuy17 January 1,2007 In which example do you think NoobXXX will stay on the wiki and contribute and have a better idea of what a good build is, and which he will hate the wiki and continue to use his bad build?