RuneScape:Protection policy

Administrators can protect pages to restrict editing.
 * Full protection disables editing for everyone except other administrators. Fully protected images cannot be overwritten by new uploads.
 * Semi-protection disables editing from anonymous accounts and those accounts less than four days old.
 * Move protection protects the page solely from moves. Fully protected pages are move protected as well, by default.
 * Cascading protection fully protects any page transcluded onto the protected page.

Any type of protection, as well as unprotection, may be requested at Requests for page protection. Non-admins can propose changes to protected pages on the related talk page, using the editprotected template if necessary to draw attention to the request. All protections and unprotections are automatically logged in the protection log.

Full protection
Indefinite full protections are used for:
 * High visibility pages such as the Main Page in order to prevent vandalism. This includes templates transcluded to these pages.
 * The site's logo, press releases, and key copyright and license pages, for legal reasons. Admins should not make significant changes to these pages without prior discussion.
 * Certain "system administration" pages, including many editorial, deletion and stub templates, and the entire MediaWiki namespace. These are pages that need rarely be changed, and that because of widespread usage can cause large-scale disruption if vandalized, or modified ill-advisedly. Again, admins should not make significant changes to these pages without prior discussion.
 * Pages deleted by consensus that are repeatedly recreated. These are listed in either Category:Protected deleted pages or Protected titles. Requests to overturn such a deletion should be made through the deletion review process.
 * Personal css and js pages like User:Example/monobook.css or User:Example/cologneblue.js are automatically fully protected by the MediaWiki software. Only the account associated with these pages and admins are able to edit them.

Temporary full protections are used for:
 * Enforcing a "cool down" period to stop an edit war.
 * A history-only review of the article during some discussions on deletion review.
 * Preventing abuse of the unblock template or other disruptions by a blocked user on their user talk page.

Content disputes
Except in cases of clear vandalism, pages protected in an edit war are protected in whatever version they happen to be currently in. Protection during an edit war is not an endorsement of the current version. Editors should not ask for a specific version of a page to be protected or, if it has already been protected, reverted to a different version. Instead, editors should attempt to resolve the dispute on the related talk page. See also The Wrong Version.

During edit wars, admins should not protect pages when they are involved as a party to the dispute, except in the case of simple vandalism or libel issues against living people. Admins should not edit pages that are protected due to a content dispute, unless all parties agree to the change, or the change is unrelated to the dispute. However, this should only be done with great caution, and administrators doing so should indicate this on the article's talk page.

Semi-protection
Indefinite semi-protection may be used for:
 * Articles subject to heavy and continued vandalism, such as George W. Bush, Atlantic Records, and this page.
 * Biographies subject to vandalism and/or POV-pushing that aren't widely watchlisted.
 * User pages (but not user talk pages), when requested by the user.

Temporary semi-protection may be used for:
 * Preventing vandalism when blocking users individually is not a feasible option, such as a high rate of vandalism from a wide range of anonymous IP addresses.
 * Article talk pages that are being disrupted; this should be used sparingly because it prevents new users and anons from being part of discussions.

Semi-protection should not be used:
 * As a preemptive measure against vandalism before any vandalism has occurred.
 * In a content dispute between registered users and anonymous users, with the intention to lock out the anonymous users.
 * To prevent vandalism to the day's Featured Article except as discussed at Main Page featured article protection. Other pages linked from the Main Page may be protected if under attack, though more leeway should be given with these than with most articles.
 * To prohibit anonymous editing in general.

Move protection
Page move protection is used for:
 * Cases of frequent or on-going page-move vandalism
 * During a page name dispute
 * High-visibility pages which have no reason to be moved, such as Administrator intervention against vandalism.

Fully protected pages are by default also move protected. If a protected page is moved by an admin, the page will be protected at the new location, and the redirect will be unprotected at the page's original location.

The same restrictions that apply to full protection during a dispute also apply to move protection during a dispute (for example, admins should avoid favouring one name over another, and protection is not an endorsement of the current name).

New accounts cannot move any pages, as described at User access levels.

Unprotection
With the exception of any pages tagged with the office or reset templates, any admin may unprotect any page after a reasonable period has lapsed, particularly if there is no discussion on the talk page. However, unless consensus has been reached, pages should not be unprotected soon after protection without prior consultation with the admin who first protected the page. This is particularly important in the case of controversial pages, where the conflict may start up again and the protecting admin may be in touch with the disputants.

When protecting a page, an admin can set a time limit; when this limit expires, the page is automatically unprotected.