Wookieepedia
Advertisement
Wookieepedia

This page is a basic how-to guide to using your sysop tools. It is by no means exhaustive, and the page does not cover the policies that you must follow before doing these. Please familiarize yourself with all of Wookieepedia's policies and guidelines before utilizing these tools; likewise, being familiar with these pages will assist you in becoming a trusted and accountable administrator. Your fellow administrators are more than happy to help you with using the sysop tools.

For further reading, you can check out Fandom's Admin Help pages and the Help pages on MediaWiki.org.

Blocking

Administrators can block IP addresses, IP ranges, and accounts, for a specific or indefinite duration. Guidelines for blocking can be found in the Blocking policy.

Special:Block is used to issue blocks and can be accessed via a user's Contributions page or via links in the Recent changes or page histories. The blocking form allows you to use a preset reason or a custom one, as well as set the duration and other parameters. Once a block is issued, it will be recorded in the block log. In addition, the text "blocked" will appear in the user's masthead and the relevant block log entry will be displayed at the top of their Contributions page.

Special:BlockList shows a list of all currently blocked users and IP addresses.

IP range blocks

MediaWiki allows administrators to issue rangeblocks as large as /16 (IPv4) and /64 (IPv6). Larger ranges cannot be blocked due to software limitations. Please be careful when issuing rangeblocks, as these can affect thousands of users. The MediaWiki help page explains how rangeblocks work.

Unblocking

Administrators can unblock IP addresses, IP ranges, and accounts that are currently blocked. Please note that blocks fall under Administrative autonomy and can only be overturned in specific circumstances.

Special:Unblock is used to remove blocks and can be accessed via links from Special:BlockList, the block log, or a user's Contributions page. Once a block is lifted, it will be recorded in the block log.

It is impossible to unblock specific IPs within a blocked IP range due to software limitations.

Interface management

Administrators can change certain aspects of the interface by editing pages in the MediaWiki namespace, as listed on Special:AllMessages. A trick for finding a certain MediaWiki page is to append ?uselang=qqx or &uselang=qqx to an URL (example); in this view, the system message content will be replaced with the system message page title. These pages cannot be edited by non-administrators. Note that some MediaWiki pages are locked even to administrators and require Fandom staff to modify.

In accordance with community consensus and Fandom's Terms of Use, administrators can edit the appearance of the user interface by editing MediaWiki:Common.css and MediaWiki:Fandomdesktop.css. You can also edit the functionality of the user interface by editing MediaWiki:Common.js. Edits to JavaScript pages do not go live immediately after saving and must be submitted for review by Fandom staff.

Special:ThemeDesigner is used to edit the theme, background, and wiki wordmark. The wiki top navigation bar can be edited via MediaWiki:Wiki-navigation.

Please be careful when editing MediaWiki pages, as they are visible to all users on the wiki and any mistakes, even if reverted, can be visible for a long time due to caching.

Announcements

Administrators can send community announcements using the following methods:

Page moving

All registered users can move pages, but only administrators can move files or pages that have been protected from moving. Administrators cannot move categories or Special pages.

Administrators can move a page without leaving a redirect in its wake (suppress redirects) by ticking a box in the move interface. Administrators can also move pages on top of existing titles—essentially deleting pages to make way for a move. The move interface will have you confirm that you want to delete the existing target page if you attempt this.

Administrators can also automatically move any subpages when moving the base page. The move interface will have you confirm that you want to move subpages as well.

Page deletion

Administrators can delete and restore most pages (exceptions include Special pages). Administrators can also preview deleted revisions and view revisions whose visibility has been changed (RevisionDelete; see below).

Individual file revisions can be deleted in the "File history" section on file description pages. Please note that restoring files is sometimes not possible due to technical reasons.

The deletion interface can be accessed via the edit button dropdown found on all pages. You can also append ?action=delete to the URL. For help with the interface, see Help:Deleting.

You should always use a deletion summary when deleting pages.

Always double-check the edit history before deleting a page. You might be viewing a vandalized revision.

All page deletions are visible in the deletion log.

Restoring

Like with deleting, administrators can restore most pages, from single revisions to complete edit histories. The undeletion interface is accessible via Special:Undelete. You will also find a link on the deleted page itself. When an existing page has deleted revisions, a link to restore these revisions will appear just below the heading in the page history.

If you wish to restore only certain revisions, use the checkboxes in the undeletion interface.

Like deletions, all acts of undeletion are visible in the deletion log.

Always provide a reason for restoring a page. If you are restoring a page deleted by another administrator, please make sure to comply with Administrative autonomy.

Viewing hidden revisions

Administrators can view revisions and associated data that bureaucrats have hidden using RevisionDelete. A link to show the hidden revision will appear in the page history next to any hidden revision.

Merging page histories

Fixing cut-and-paste moves involving deleting a page, moving another page there and undeleting the original over the top of the one you just moved. This is very complicated to undo in case you mess up—please do not attempt it unless you understand the procedure described on this Wikipedia help page.

Protecting pages

Administrators can protect and unprotect most pages (exceptions include Special pages) from being edited and/or moved. There are two protection levels in the built-in protection interface:

  • Semi-protected (sprot): Only autoconfirmed users will be able to edit and/or move the page.
  • Fully protected (fprot): Only administrators will be able to edit and/or move the page.

Separate protection levels can be applied for editing and moving, respectively. Furthermore, AbuseFilter #23 can be used when semi-protection is insufficient but full protection would be unnecessary.

  • Super semi-protection (ssprot): Only users with more than 150 global edits (across all of Fandom) will be able to edit the page.

After protecting a page, please add the appropriate protection icon to {{Top}}.

The protection interface can be accessed via the edit button dropdown found on all pages. You can also append ?action=protect to the URL. For help with the interface, see Help:Page protection.

Titles can be protected from creation in the same manner as any existing page.

All page protections are logged.

Cascading protection

Page protection can be applied to be cascading. Any pages transcluded on a page with cascading protection enabled will receive the same protection level as the parent page. A checkbox is available in the protection interface for enabling cascading protection.

Cascading protection can only be used with a full protection level.

ProtectSite

Administrators can restrict edits, page creations, moves, and file uploads to autoconfirmed users or administrators by toggling AbuseFilter #31. Additionally, toggling AbuseFilter #56 restricts editing to bots and administrators only. This is an extreme measure reserved only for serious waves of vandalism that can't be stopped using conventional anti-vandalism methods.

Rollback

Administrators, just like Wookieepedians elected to become rollbackers, have the rollback permission. This allows one-click reversion of a user's edits by clicking the "rollback" link ([rollback]) in the Recent changes, on a user's Contributions page, or in page histories. While any user can undo multiple edits via the edit history, rollback is faster and also does not add the page in question to your watchlist. Rollbacks have a standard edit summary (Reverted edits by X to last version by Y) and are automatically marked as minor edits.

Bot rollback

Unlike rollbackers, administrators can hide rollbacked edits from the Recent changes. This can come handy in cases of large-scale vandalism. Bot rollback is accessed by appending &bot=1 to the URL of a user's Contributions page—for example, https://starwars.fandom.com/index.php?title=Special:Contributions&target=Vandal&bot=1. Rollbacking edits from this Contributions page will automatically hide them from the Recent changes by tagging them as bot edits.

Large-scale vandalism

In cases of extreme vandalism—such as coordinated efforts from multiple accounts or IP addresses/ranges—it may be prudent to temporarily lock down the site using AbuseFilter #31, as explained above. For cleanup of large-scale vandalism, administrators can use tools such as WHAM, which can be enabled as a gadget in your Preferences. WHAM allows you to, among other things, revert all edits and delete all pages created by a user with a single click.

Spam filter

Administrators can manage the local spamfilter, called Special:AbuseFilter. You can create new filters and modify existing ones. The interface also allows you to test edits against custom filters and examine past edits. All instances where a filter is tripped are logged in the Abuse log.

Filters use a special syntax and regular expressions (regex). Please exercise caution when modifying filters.

Administrators are encouraged to monitor Wookieepedia:Spamfilter problems to address any false positives.

In addition to the local spamfilter, there exists a global spamfilter managed by Fandom staff and the Spam Obliteration and Prevention (SOAP). Problems with global spamfilters should be reported on the SOAP Wiki.

Moderation of chat platforms

As an administrators, you receive privileges on our official chat platforms, Discord and IRC. These are third-party services where you are personally responsible for your account security. Please pick a good and secure password and consider enabling two-factor authentication on Discord.

Discord

You will be granted the "administrators" role, which allows you to kick and ban users, among other server moderator actions.

IRC

Blue-arrow.png See also: Wookieepedia:IRC

You will be granted channel operator privileges on Wookieepedia's IRC channels, which allow you to kick and ban users, among other actions. You will also receive an administrator IRC cloak on the freenode IRC network.

Consensus votes

Administrators, like all Wookieepedians, are encouraged to participate in community consensus votes—namely in Consensus track votes and Trash compactor threads.

Voting eligibility

Striking invalid votes is an administrative responsibility. If a user votes in a forum without meeting the requirements outlined in the Voting eligibility policy, the vote should be struck by an administrator using {{Votestruck}}. You can inform the users of their vote being struck on their talk page using {{Msg-votestruck}}.

Closing votes

Administrators are responsible for closing consensus votes and executing consensus decisions. As per Wookieepedia:Consensus, two weeks is provided as the standard time frame for a consensus vote, although a forum may be closed early in the instance that a clear consensus is achieved:

  • Snowball: A vote may be closed after seven days if the votes overwhelmingly support one option
  • Curb Stomp: A vote may be closed after five days if one option achieves 20-0 support

A consensus vote may be closed as no consensus if the vote has been open for two weeks, its forum has not been edited by a vote-eligible Wookieepedian for at least five days, and it has yet to achieve consensus.

The following table can be used as a quick reference for determining which rules apply in different votes on Wookieepedia.

Vote Affected by
WP:VOTE
Pursuant
to WP:CON
50+ edits 50+ edits
within 6 months
Vote struck
if blocked
Must wait 2
weeks after block
to vote
Productivity
requirement
applies
CT
TC
WOTM
RFU/RFRUR
FAN/GAN/CAN
Mister/Miss SW

The ratios required for consensus are found in the Consensus policy, but the following table can be used for convenience.

Insufficient vote count - no consensus No consensus Success Failure
Supporting votes →
Opposing votes ↓
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
0 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
2 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
3 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
4 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
5 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
6 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
7 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
8 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
9 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33
10 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
11 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
12 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 34 34 35 36
13 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 34 35 37
14 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38
15 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
16 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
17 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41
18 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42
19 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43
20 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44
21 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45
22 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46
23 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
24 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48

In particularly difficult cases where the interpretation of consensus is unclear or disputed, final determination falls to the Wookieepedia Bureaucrats.

Closing instructions

Before closing a Consensus vote, ensure consensus has been reached! Ask another administrator if you are unsure.

Consensus track

In the forum thread itself:

  • Change {{Cttop}} to {{Cttop-arc}}.
  • Add {{subst:CTarchive|result|~~~~}} below the header.
  • Add </div> to the bottom of the page.

If a vote item passes:

Trash compactor

On the Trash compactor page itself:

  • Change {{Tctop}} to {{Tctop-arc}}
  • Add {{subst:Tc-closed|result|~~~~}} below the header.
  • Change the category at the bottom of the page to [[Category:Trash compactor archive]].
  • Add a </div> at the bottom of the page.

If the result was DELETE:

  • Delete the affected page(s)
  • Fully create-protect the page(s) from being recreated. TC decisions are binding and pages that have been deleted should not be recreated without a renewed vote. Use the pre-set protection reason "3.2 Trash compacted page".
    • If the deleted page has a counterpart in the other continuity: For example, if the community votes to delete the Canon article "Foo" but not the Legends counterpart "Foo/Legends", the latter should be moved back to the base title "Foo" and "Foo/Canon" should be create-protected.
  • Remove any links leading to the page. You can do this yourself or leave a bot request.

If the result was anything else:

  • Remove {{Tc}} from the affected page(s)
    • Execute any other decision, if applicable. For example, if the decision was redirect, go ahead and redirect the page.
  • Add the following to the talk page of affected page(s):
{{Ahh}}
{{Ahm
|date=Nomination date
|link=Wookieepedia:Trash compactor/{{subst:PAGENAME}}
|process=TC
|oldid=Nomination revision
|result=Result of the discussion}}
{{Ahf|status=K}}

Wookieepedian of the Month

  • Add a new entry to the top of Wookieepedia:Wookieepedian of the Month/History and follow the redlink to the archive page.
  • Create the archive page:
    • Add {{subst:WotMarchive|~~~~}} to the top.
    • Paste the contents of the vote.
    • Add </div> to the bottom.
  • Remove the vote from Wookieepedia:Wookieepedian of the Month and update the winner text on that page.
  • Congratulate the winner by placing {{WotM notify}} on their talk page.
  • Post a congratulatory announcement in #announcements on Discord.

Dealing with abusive editors

An increasing number of admins have found themselves being threatened or harassed on and off-site, and in some cases in real life. This is usually possible because they have inadvertently left enough information in their contributions or on their user pages for abusive editors to be able to piece together who they are. If you find yourself being expected to deal with an abusive editor, and you're worried that they may identify you, please approach a Bureaucrat in assisting you with making difficult blocks. These blocks can range from IPs, new users, or even established users. Please do not hesitate to find help when facing a difficult situation.

Being useful

Admin rights can be particularly useful in certain areas of Wookieepedia. Most of these cases can/should be brought up using the Administrators' noticeboard:

Admins will also find their rights useful for Recent Changes patrolling and New page patrolling.

Related pages

Advertisement