User:Wizardboy777/Noticeboard Guide

This is a guide to posting on the Admin noticeboard.

General Guidlines

 * Don't make frivolous posts. If you post an issue and an admin resolves it, please don't post again to add "K, thanks" or something like that. It's unnecessary and makes the noticeboard pop up on everyone's watchlist again.
 * Try to avoid debating anything on the noticeboard. If an issue is becoming a topic of contention, move discussion to one of the talk pages involved, and post the link.

First things first

 * Check the table of contents to make sure no one has already posted the same problem.
 * Figure out which section it should go in. If you aren't sure, go with general issues.
 * Take a quick look through the other topics in that section to see if someone posted a similar problem.
 * Go to the corresponding section below for further instructions.

General Issues

 * If you're posting notice of a vandal, there's one thing you should check first: has anyone warned the him/her? If the user hasn't been warned, don't bother posting on the noticeboard yet - just warn them. Any user can do that, and unless the vandalism is rather serious, it's what whichever admin responds would probably do. If the user has continued to vandalize after being warned, then post it on the noticeboard.
 * Use a descriptive heading, and try to be clear and concise.

Build-specific Issues

 * Before posting on the noticeboard, attempt to get a response from the voter.
 * Start a section on the build's talk page detailing which votes you believe are wrong and why.
 * If the voter(s) in question does not respond, leave a note on his/her talk. Don't repeat your reasons for wanting the vote changed here - just link them to the build's talk page, preferably linking directly to the section you started (Do this by appending #sectionheader to the page title. For example, to link directly to the general issues section of the noticeboard, you would type Admin noticeboard, which shows up as follows: Admin noticeboard). This helps keep all discussion in one place. If the voter still does not respond or refuses to change/remove his/her vote, then post it on the noticeboard - again, link to the talk page instead of reiterating which votes and why.

General coding Issues

 * Keep in mind that Gcardinal's English is not the best. This can really be a problem when you're attempting to describe something that you don't really understand. Be clear and concise. If necessary, upload pictures and link to them (unless the pictures are very small, avoid placing them directly on the noticeboard to reduce clutter).
 * Double-check that no one has posted something similar. This section tends to build up a bit of a backlog, making it easy to miss things.

PvXcode Issues

 * Don't post anything about skill descriptions not having been changed since the last update or three. GWShack is responsible for that, not us, and they tend to be pretty slow about it. At some point, we may get a skill database so that we can update these things on our own, but for the moment you'll just have to live with the old descriptions.
 * Again, be clear and concise. Pictures are helpful, but avoid putting them on the noticeboard - just make a link.