Minecraft Wiki:Talk page guidelines

Talk pages are useful for discussion, but lose their use if they are not used in an organized fashion. Below are some guidelines for using the talk pages.

General

 * 1) Talk pages are only for discussing the related content page. Topics should discuss the content of page as an article. Talk pages should not be used for any of the following:
 * 2) * Suggesting a new feature for Minecraft
 * 3) * Reporting issues with the topic's behavior in Minecraft
 * 4) * Discussing your opinion on the topic's existence or usage in Minecraft
 * 5) * Acting as a tutorial, tutorial content should instead exist on the Tutorials sub pages.
 * 6) * Acting as a content page or a proposed page or page rewrite. Content pages should be in a content namespace, and page proposals should be made in either in the Minecraft Wiki sandbox or a personal sandbox, and then may be linked to discuss.
 * 7) When replying to a topic, keep to the same topic as the initial topic. If the topic does not cover what you want to say, consider starting a new topic on the page. If replying to multiple topics at the same time, answer each topic within its own topic, rather than placing all replies in one place.
 * 8) Don't edit other user's comments, except to sign unsigned comments or fix formatting.
 * 9) Don't edit archives. They are called archives for a reason. Instead of replying to an archived topic, start a new topic with an optional link to the old one. You should also generally avoid replying to topics with the last post over a year ago, as your solution likely did not exist back then.
 * 10) Follow rule #5 maintaining civil discussions with no harassment, insults, or ad hominem.

User talk pages may be used for anything provided they follow rules 3 and 5. It is also advised to follow rule 1, except in the case of the main talk page, which is advised to be used for direct discussion with the user.

Signing
Always sign your posts using. Your signature can be changed in your preferences, provided it fits the following criteria:
 * Your signature should either contain a link to your user page, or your username directly.
 * Do not impersonate another user, such as by displaying their name and linking to their page.
 * Your signature may not contain a template unless it is always substituted. The resulting code must be no more than 250 characters.
 * Do not use excessively large files, text, or formatting in your signature.
 * Avoid using font colors that are similar to the background color, and font sizes that are excessively small.

If someone else did not sign their comment, sign it for them using unsigned.

Formatting
Along with following rules for usage of talk pages, good talk page formatting is helpful too. On talk pages, topics are denoted using an h2 header, and sub-topics can be denoted using an h3 header.

Always indent your replies to one level after the comment to which you are replying. If a large number of indents are reached, usually around eight, you may add outdent before your comment instead of indenting. When making a proposal, usually all responses are only one indent, and using comment is advised.

For clarity on the editing screen, it is advised to leave a blank line between comments by separate users.

Generally avoid using templates that are not designed for talk pages, as they may change or break at any time without ease of updating them. A list of talk page templates can be found here.

When discussing a category or a file, you should escape it using a colon before the namespace in the link.

Example
Note that only a single line break is used between comments here for compactness

A single topic
Initial topic -User 1
 * Reply -User 2
 * Reply to user 2 -User 3
 * Reply to user 1 -User 4
 * Reply with a link -User 2
 * Reply with a Category:Main -User 3

A subtopic
Initial sub topic post -User 5
 * Reply -User 1

A proposal topic
A proposal -User 1
 * -User 2
 * Reason -User 3
 * Comment on user 3's post -User 4
 * -User 5
 * -User 6