# Guidance for Scribes

768pages on
this wiki

This is an evolving guide about how to make contributions to the wiki and what to work on.

The goal of Habitica's Scribes is to create and maintain an accurate, up-to-date, complete, and easy-to-use guide for players of Habitica. Join the Scribes in the Wizards of the Wiki guild to ask questions, discuss editing and learn new things.

## Quick Tips Edit

The tips in this section and the printable quick reference card to the right contain some of the critical parts of these guidelines, but please read through this Wiki page for full details.

• The tone should be informative and semi-professional. Use third person (e.g. the player, they) in the opening of an article. You can use second person in later paragraphs or sentences (like this one), but never write in the first person.
• The length of the page or section should be as long as needed but no longer; be informative and concise.
• Use text formatting (e.g., bold, italics) sparingly. Do not use colored text or text decorations (e.g., strikethrough, overline, underline).
• Use American English grammar and spelling, with the exception of "grey". Write in complete sentences unless in a table. Use the singular third-person pronoun "they" instead of alternatives such as "he/she". Capitalize Habitica terms that have a special meaning in the context of Habitica (e.g., XP, Dailies, Tavern).
• Avoid spoiling information about upcoming changes, additions, or events; if spoiling a feature that is already implemented, use the spoiler template.
• Add images if they are useful in the context of the article; search for the image you need in Special:NewFiles and in the various image categories before adding it to avoid duplicates. When updating an existing image, upload it as a new version of the same file instead of as a new image.
• Add categories to articles if an obvious/useful category is missing. Check a category's page for information before adding it to pages, and refrain from creating categories that are not in use.
• Include an informative and accurate edit summary whenever you make edits. This helps other editors check your work.
• Only rename a page if absolutely necessary; if you do, use WhatLinksHere to fix links to the page.
• If you believe a page needs to be deleted, go to Classic Editor -> Source and enter
`{{delete|Reason for deletion}}`
at the top of the page; please include the reason for deletion.
• Join the Wizards of the Wiki guild. Post there when you have questions. Discuss potential large changes there before making them.

## How to StartEdit

You can begin contributing to the Habitica Wiki by signing up for a Wikia account. Your username does not have to be the same as your Habitica username in order for you to earn credit for your work when requesting a contributor tier. Be sure to sign in to Wikia every time you edit so you can get credit for your edits and so that we can recognize your contributions.

After signing up, if you feel like testing the waters of the Habitica Wiki community and the Wikia editor, feel free to fill out your profile page with some information about yourself, and create a Blog Post about how you use your Habits and Dailies. Let us get to know you!

If you are new to wikis, you may want to read the tutorial and view the list of help pages for guidance.

If you need help editing, read Help:Editing or the tutorial.

### What to WriteEdit

Writing for the wiki isn't just about creating brand new pages; it's also about managing the quality of what currently exists.

Starting scribes with little to no previous Wikia creating or editing experience may want to begin by helping clean up existing articles. All of the Wiki Scribes are volunteer writers of various writing and national backgrounds who make changes at multiple points during the day; we will never quite be rid of typos and grammatical errors, so fixing the little things (even missing periods) has value. Consider making minor edits as a way to learn how to navigate the site and use the editor instead of trying to jump in immediately by making large additions to pages or creating full articles.

Habitica is an ever-evolving product; new features are added regularly, and some updates supersede previous facts about features. Scribes are encouraged to make changes to related pages as they find them. In addition to the Wizards of the Wiki guild mentioned above, where suggestions for editing ideas are often posted, you can consult the following to learn about and keep track of updates to Habitica:

As you become more comfortable with editing the wiki, check out Beyond the Classic Editor:Advanced Wiki Editing for instructions on making more advanced edits.

Before making major changes, use each article's talk page to discuss article contents, resolve any conflicts, and talk about anything specific to the article. Respect is key. Remember to sign edits to talk pages. For more general discussions, use the Wizards of the Wiki guild.

Reviewing and (when appropriate) editing or deleting speculative content helps to keep the wiki accurate.

You can find a list of useful templates at Category:Templates, some of which are documented on Habitica Wiki:Templates.

New wiki editors may want to exercise caution before making the following types of edits:

• Edits to existing pages in The Keep. Since pages in The Keep are often personal pages (e.g., pages dedicated to a party, guides about how a particular player likes to use Habitica), most pages in the Keep do not need to be edited, even to add clarity/links or fix problems like formatting issues (exceptions include violations of the Community Guidelines). If a page in The Keep is not one person’s or party’s personal page and seems to be worth editing, please ask about it in the Wizards of the Wiki guild.
• Edits to pages with the Under Construction banner. Wiki editors may already be actively working on these pages, so additional edits, however minor, may disrupt their workflow. If you are interested in working on one of these pages, take a look at the history of the page (accessible via the Edit button’s dropdown menu, via the My Tools menu on the Wikia toolbar, or by appending `?action=history` to the end of the page’s URL). If there are recent edits, get in touch with the editor(s) responsible expressing your interest in helping with the page. If there are no recent edits, take a look at the Talk page for any notes on what needs to be done and feel free to ask about how to proceed in the Wizards of the Wiki guild.
• Links to wiki pages that do not currently exist. Note that the Habitica Wiki avoids using broken links. Additionally, for the most part, the links listed at Special:WantedPages do not need to be edited (nor those pages created) as they are generally from old wall messages/blog posts.

### Subscribing to ChangesEdit

If you want to follow changes to this wiki, or look out for new users and edits, use Special:RecentChanges or Special:WikiActivity. This is also a great way to learn about what changes occur regularly on the wiki.

### Newbie Wiki TipsEdit

• Using the source editor (rather than the visual or classic editor) is recommended, as it is more powerful, allows for more precise editing, and enables you to view helpful comments that may have been left by other editors.
• You can make it your default editor via the "Preferred editor" dropdown in the editing tab of your Wikia preferences. If the source editor is not your default editor, you can still access it by clicking the dropdown arrow on a page's "Edit" button.
• Note that the source editor uses the wikitext markup language.
• Badges help determine contributor tiers for scribes. One way of earning badges is by editing the wiki for a certain amount of consecutive days. The following are tips related to maintaining your editing streaks:
• When you first create a wiki account, set your timezone immediately in your Preferences. Changing the timezone can reset your editing streak.
• Wiki editing streaks are counted as edits per UTC day. To ensure you keep your streak, set a Daily to edit the wiki after midnight.
• While points from wiki badges are used as a rough guideline to determine eligibility for contributor tiers, they are not as important as the quality of your contributions to the wiki. Things that earn you badges but don't improve the wiki, such as pointless comments on old blog posts, will not help you earn a contributor tier.

## StyleEdit

### ToneEdit

The tone of the article should be informative and semi-professional. Basically, this means opening all articles with clear-cut and concise definitions of the topic in question, followed by a well-organized and thorough rundown of the topic in detail. Stick with the third person only in the openings, using words like "player" and "user" rather than "you." Once you get into the meat of an article, it should be fine to use the second person, as most articles will have instructions for users of the site to follow. Never use the first person under any circumstances. Writing in all caps is considered yelling, and as such it is an improper tone for this Wiki.

### Article LengthEdit

The article should be straight to the point and only as long as needed (especially for broader topics). However, do not go on a tangent and add fluff. Shorter articles are generally more accessible and usable than really long ones. Referencing related pages, however, is recommended and helpful for users in general. Always write the best that you can on all of your contributions.

## FormattingEdit

### WikitextEdit

Wikitext is the markup language used by this wiki. A markup language can add formatting (e.g., italics), as well as images, tables, links, and other visual changes. You can use wikitext via the source editor, or via source mode in VisualEditor (choose "Source Editor" under the menu at the right side of the toolbar). For more information about how to use wikitext, see Help:Wikitext.

Note that it is not necessary to use wikitext to edit the wiki. The default editor is the VisualEditor, which does not require use of wikitext. Each editor has a toolbar with buttons for basic formatting tasks like inserting an image or creating a bulleted list.

However, using wikitext in the source editor is recommended as it allows for more precise and powerful editing. You can make the source editor your preferred editor via the editing tab of your Wikia preferences. If the source editor is not your preferred editor, you can still access it by clicking the dropdown arrow on a page's "Edit" button.

### TextEdit

Formatting of text can include bold or italic text, but these should be used sparingly. Text with too much formatting distracts the reader and decreases readability. Do not use text-decoration (overline, underline, etc.). Usual formatting of text does not need strikethrough, and underlined text can easily be confused with hyperlinks.

Margins and Padding are names for space around an element, be it text, image, table, etc. As a wiki editor, you usually do not have to worry about this. When you get further into it, this can be handled via CSS and the style attribute. You can read up on the use here: margins and padding.

### Grammar and SpellingEdit

On this wiki, we follow standard English grammar rules.

This includes (but is not limited to) spacing and punctuation. Use one space between sentences. Abbreviations should be followed by periods (for example, e.g. and i.e.). Entries should be made in sentences, not note form, unless entering data in a list or table. If you see improper grammar in a wiki page, feel free to edit it! In addition, make sure you double-check (and maybe even triple-check) your edits after writing them to make sure you don't have any grammar bugs lurking on the page.

Use singular "they" when you need a gender-neutral third-person pronoun. This is more inclusive and less awkward than alternatives like "he/she", and is accepted in many English style guides.

American English is the standard for spelling rules on this wiki. This means that colorpersonalize, and center are the correct spelling, whereas colourpersonalise, and centre are not. The one exception to this rule is the spelling of grey. While American English generally uses gray as the standard spelling, this wiki, as well as Habitica, does not. In order to remain consistent with the rest of the wiki and between the wiki and Habitica, the standard spelling shall be grey (read more). Don't make an edit solely to change British English to American English unless it interferes with the functioning of a link or it is the incorrect spelling of a name. It is acceptable to change it while other substantial edits are being done, though.

### CapitalizationEdit

Standard English rules of capitalization are almost always followed. This has two main cases:

1. At the beginning of sentences.
2. With certain nouns (usually proper nouns, or Habitica terms such as "Market") and some adjectives.

Proper nouns are capitalized (e.g., America, Habitica). (One exception is when a player has chosen to write their display name in lower case; please respect the player's choice and use the same capitalization they do, e.g., the moderator deilann should not have his name written as "Deilann".)

Terms that have a special meaning in the context of Habitica should be capitalized. For example, Strength is a character attribute; strength is something else (as in "I want to increase my physical strength so I have created several tasks with the Strength attribute"). Words that refer to more general concepts in the game do not need to be capitalized. For example, "sword" in Habitica has the same meaning as it has in the real world and so is lower case.

The tables below give some examples of those guidelines.

Capitalized Example
events Summer Splash
abbreviations XP, HP, MP, GP
character attributes Strength, Intelligence, Constitution, Perception
class names Healer, Rogue, Warrior, Mage
equipment Chain Mail, Orb of Rebirth
boss names (but the name should also match the quest scroll) The Dread Drag'on of Dilatory, The SnackLess Monster
background names Fairy Ring
names of eggs, pets, mounts Wolf Egg, Desert Fox
other words that have a unique meaning in Habitica the Tavern, Perfect Day, Grey Daily, Cron

Not capitalized

Example
food potatoes
names of items that a player can possess several of hatching potions
Gameplay terms that a) are not unique to Habitica and b) are unlikely to have another relevant meaning quest, party, boss, drop, health

As noted above, writing in all caps is considered yelling, and as such it is an improper tone for this Wiki.

### TablesEdit

Tables should be styled as they appear when the add table feature is used in the visual editing mode of the classic editor. This does not apply to sorting tables, or excessively large tables (see Mounts). Parameters in source mode for this are:

```border="0" cellpadding="1" cellspacing="1" class="article-table" style="width: 500px;
```
Example caption
Table contents

More contents

If you'd like to create tables using a graphical interface, TablesGenerator.com allows you easily create MediaWiki tables that then be copy-pasted into the wiki.

### ColorsEdit

Use colors sparingly so as not to disrupt the global style. Colors should not be used for any text as they can be confused with broken links or links to other pages.

Relevant internal links to articles help readers browse the wiki and help avoid dead-end pages. External links to GitHub issues and Trello cards can provide useful behind-the-scenes or historical information. Do not link to wiki pages that do not currently exist as the Habitica Wiki avoids using broken links.

When creating links on a page, make sure that you link to the current page for the topic in question, and that the target link in the source code (or edit link box) is appropriately capitalized.

You can add internal links by putting double square brackets around text designating the title of the page you want to link to. For example, `[[Gold Points]]` becomes Gold Points. You can also use a vertical bar (|) to customize the link title. For example, typing `[[Gold Points|gold]]` will produce gold. You can add external links by placing the URL within single square brackets. For example, `[http://www.tablesgenerator.com/mediawiki_tables TablesGenerator.com]` becomes TablesGenerator.com. Note the use of a space (not a bar |) to separate the URL from the optional link text.

Plural versions of links can be formed by appending an 's' after the closing brackets. For example, `[[Rogue]]s` displays as Rogues. This has several benefits over the alternative (`[[Rogue|Rogues]]`): it is easier to type, clearer to read in the source code, and less likely to result in typos. This also works when adding a suffix (e.g., ‑ing, ‑ed, or ‑est) to a link. However, it is not necessary to make an edit solely to change link code from, say, `[[Rogue|Rogues]]` to `[[Rogue]]s`.

When copying pages in order to create new ones of the same type, e.g., using an existing Quest page as a template for a new Quest page, be sure not to copy/import the interlanguage links. Having an incorrect link to a translated page can be confusing for wiki users, especially if the page they originally wanted to read does not exist or is not fully translated at that point.

### TitlesEdit

When creating a new page, do not use parentheses () in the title. Wiki pages with parentheses in the title will glitch due to a conflict with the formatting in the Tavern.

Liberal use of headers breaks up articles, enables easier reading, and allows the automatic generation of tables of contents. However, too many subheadings makes the text harder to read, especially if related content is being broken up unnecessarily. To keep text easy to follow, try to strike a balance in the number of headings used.

Headers and subheadings are capitalized according to the rules described in Composition titles (a form of title case). However, if you see an existing header that does not have correct capitalization, please do not change it unless you are certain that there are no links to it.

### InfoboxesEdit

Individual item pages should have an infobox with an image, the tooltip description, and buy/sell prices - instead of listing this info in paragraph form. Example code for the template is as follows.

```   {{infobox item
| title         = Snowball
| image         = Snowball.png
| imagewidth    = 51 [default: 210 pixels]
| imagecaption  = Throw a snowball at a party member.
| sell          = -
}}
```

The table of contents (TOC) will automatically generate after the fourth main sub-heading. The TOC can be forced to appear with less than four sub-headings by including the following code in the source view of the editor at the start of the wiki document: __TOC__ To shift the TOC to the right of the page, enter the following code into the source view of the editor at the top of the wiki document:

```{| align="right"
| __TOC__
|}
```

### Math Expressions and Formulas Edit

The Habitica wiki supports mathematical markup using a variant of LaTeX. This is well documented in the Wikia Community Documentation, with further details about specific markup elements available in the Wikipedia help pages.

By default, the mathematical markup should render as black text with a transparent background, e.g.:

`[itex]{y = x^2 + 7x - 2}[/itex]` produces $correct maths sample$

Note that currently you can only enter mathematical markup in the source editor.

### Emoji Edit

Emoji are rarely used in the wiki - usually only when quoting text from Habitica that contains them. If copying and pasting the emoji doesn't work, another way to include an emoji in a wiki page is to write its HTML entity in the source editor. For example, for 🐘, you would write `&#128024;` (its HTML entity with decimal number) or `&#x1f418;` (its HTML entity with hexadecimal number) - it doesn't matter which one.

You can find an emoji's HTML entity on the internet. One good place to look it up is FileFormat.Info. Either find the emoji in their list of emoji, then click on the corresponding Unicode link on the right side, or enter the emoji's name (in this example, "elephant") in the search field.

There are emoji which don't have a corresponding Unicode character and for which this method doesn't work - but in most cases, it does.

Another good source to look up different versions of emoji and copy them directly is Emojipedia.

## Avoiding SpoilersEdit

When looking for new information to add to the main namespace, stick to features that are already implemented, visible, and accessible to all players on Habitica. Information about planned or upcoming features available on GitHub and the various Trello boards may contain spoilers that the staff wish to keep as surprises for players. This is particularly important for world events, particularly those with multiple event-based reveals like the battles with world bosses.

For spoilers of already implemented content, such as resolution text for boss or collection quests, you can use the templates for spoilers: Template:Spoiler start and Template:Spoiler end. The spoiler warning template, Template:Spoiler, should be used on any pages where most or all content consists of spoilers.

## ImagesEdit

Images should be added if they are useful in the context of the article, for example, if they help make a concept more clear, with the exception of the Whats New pages which should match the Bailey announcements in old news.

Before uploading a new image, search for it in Special:Images and in the various Images categories. The image you want might already be uploaded and if so, you should not upload a duplicate (see Replacing v. Deleting below for more information). If it has not already been uploaded, you can find most of the original Habitica images used on the website (including items, food, pets, and mounts) in GitHub under the website/assets/sprites/spritesmith and website/assets/sprites/spritesmith_large directories in the "habitrpg" repository.

### File TypesEdit

Images should be uploaded as PNG with the highest resolution available. Under special circumstances, different image formats are allowed (e.g., if an animated GIF is essential).

Images should have transparent backgrounds unless the background is essential to understanding the information that the image is trying to present.

### File Names Edit

Standard images from Habitica, such as images of equipment and pets, as well as quest-related images, should use the file names that are used in Habitica itself; this is of especial importance for equipment and quest scrolls. For example, the Winter 2015 Healer armor has the file name broad_armor_special_winter2015Healer.png. File names can be found in GitHub under website/assets/sprites/spritesmith/. Don't use file names beginning with "shop_..." even if the shop version of the image is uploaded; instead, use the file name for the normal version of the image (e.g., use weapon_healer_1.png rather than shop_weapon_healer_1.png).

Other images such as example avatars or task should be uploaded named with generic but descriptive titles. The name should accurately reflect the content of the image, distinguishing it from other images, without describing elements of the image that may be changed as Habitica evolves.

Try to avoid using words in the name that would be inaccurate should the image need to be updated in the future to represent changes to Habitica. For example, the image on the right was uploaded to show what the buff icon looks like on an avatar. It was correctly named Avatar_Buff.png.

Avoid including any words in the image's name that are likely to become irrelevant when the image changes:

• Dates (e.g., Avatar_Buff_August_2014.png)
• Version numbers (e.g., Avatar_Buff_version_1.png) or words indicating a new version (e.g., Avatar_Buff_updated.png or Avatar_Buff_modified.png)
• Avatar names (e.g., Deborah_Buff.png)
• Elements in the image that might change when the site is updated, such as colors or shapes (e.g., Buff_White_Arrow.png)

An exception can be made if it is absolutely necessary and not likely to change (e.g., July_2014_Mystery_Item.png).

### CaptionsEdit

Use the caption to explain what the picture shows, and to clarify why it is included in the page.

#### Wide Captions Edit

When paired with smaller images, some captions may wrap undesirably as seen to the right.

You can use the {{infobox item}} template as follows to render the image without undesired wrapping:

```{{infobox item
| title         =
| image         = Snowball.png
| imagecaption  = Throw a snowball at a party member.
}}
```

### Replacing v. DeletingEdit

Outdated images should be replaced rather than deleted if at all possible. Go to the image's page, then select the drop-down menu on the edit button next to the title. You will see the following options: History and Replace. Click on replace, then use the form displayed to upload the updated image. You can write a brief description of what has changed in the image, or why a new version is needed.

Once the form is submitted, the old version of the image will be replaced by the new one, but the old version will still be available in the file's history tab.

Note: There is an ongoing issue with the Wikia caching so that for a little while after a replacement image is uploaded, the old image still shows. Wikia seems to occasionally have very aggressive caching that can hold on to the old version of an image for hours. It should rectify itself within a day, but if it doesn't, the issue can be reported to wiki staff and they'll manually clear out their cache. See also the Wikia Community Central's Help:Purge page.

Using this method to replace an old image has a lot of advantages over uploading a completely new image. It means that you can see all versions of an image in one place, and it's very easy to revert to an old version if needed. It means that all links on the wiki and elsewhere will keep on working. It reduces clutter in the wiki's "Photo" section because there's only one entry for each image.

Most importantly, it makes it impossible for anyone to accidentally use an old version of an image. Someone who's editing a page and needs to choose an image will find it hard to pick the right one, and if more than one similar image is used across the site, then all of them have to be updated when Habitica changes. But if new versions of images are uploaded to "replace" old images rather than uploaded as new images, this issue disappears.

Check out this thread for more explanation of why it's generally better to replace rather than delete.

All images on the wiki must have accurate copyright (license) information in their descriptions. Images from Habitica (artwork, screenshots, etc) are licensed under the CC-by-NC-SA 3.0 license. If your image is not from Habitica, please make sure you are allowed to use it (i.e., using it on the Habitica wiki does not break any copyright licenses).

You can add license information when you upload the image to the wiki (that's easiest and is strongly recommended) or you can edit the image after you've uploaded it.

1. click on the "More options" link that you'll see near the bottom right
2. find the "Licensing" drop-down list

1. click on the image to open it in a pop-up screen
2. click on the "more info" button at the top right of that screen to go to the image's own wiki page
3. click on the "edit" button (note: the source editor is recommended; if it is not your default editor, click the dropdown arrow on the "edit" button to access it)
4. in the text area that you will then see, copy and paste this text: == Licensing ==
5. on a new line under that text, paste in the correct code for the appropriate license:
• for images from Habitica (artwork, screenshots, etc), all you need to paste in is "{{CC-BY-NC-SA}}" (without the quote marks)
• for images from other sources, find the appropriate license code at Wikia's Help:Image copyright tags page
6. in the "Edit summary" box to the left of the edit page, paste in this text or similar: "adding copyright information"
7. click the "Publish" button.

### Adding Spacing and Preventing Awkward OverlapsEdit

If the image is creating issues with the layout, you can add the following code to create a clear space to fix it.

```{{clr}}
```

### Wiki Promotional ArtEdit

Some pages have decorative promotional art, depicting Habiticans engaging in activities relevant to the material on the page. These images can add flavor and help break up large areas of text. If you find a page that could benefit from this type of art and have an idea for it, submit your idea to the appropriate card on the Pixel Art Trello. Once your idea is approved, it will be added to a list of scenes needed. Artisans will then be able to claim and create the scene.

As wiki promotional art is decorative, it does not require captions.

## VideosEdit

Videos from Youtube and Vimeo can be included, but should only be used if they improve the article significantly.

## CategoriesEdit

Categories can be added to articles to group them according to a certain topic. However, having too many categories, especially when they contain very few pages, have vague topics, or are similar to other categories, can add unnecessary clutter to the wiki and make it more difficult for users to find the most helpful categories. Please refrain from adding categories that are not already in use without first discussing your idea with other experienced Scribes, such as in the Wizard of the Wiki guild.

Category pages (for example, Category:Contributing) can optionally contain one to two sentences to explain what the category is for. This is not necessary when the intention is obvious. Category pages should never contain more content than that because their primary purpose is to be a list of related articles. Check the page for a category before adding articles to the category, since it may contain guidance about what pages should or should not be added.

Most categories are reserved for certain types of pages--in particular, the categories listed in the Category Index should only be used for main wiki pages, unless noted otherwise (e.g. Category:Guilds and Category:Parties are for pages in the Armory). To avoid clutter, please don't add these categories to other types of pages (templates, blog posts, files, etc.).

## Edit SummariesEdit

When making edits, write a short summary of the changes that have been made in the 'Edit Summary' box before publishing. Depending on the edit, a few words may suffice, but major edits may need longer summaries or the inclusion of rationales. Providing these summaries allows other scribes to quickly get a sense of what has changed. It is also extremely helpful when filling out contributor tier applications, as these summaries are shown as part of the edit histories on user profiles in the 'Contributions' tab. In addition, it makes finding specific changes in a series of edits much easier.

If you have trouble remembering to fill out the edit summary, you can (if you have an account) set your user preferences to remind you if you forget to leave one. In the "Editing" section of your preferences, check the box reading "Prompt me if I leave a blank edit summary" (the third checkbox under "Editing experience") and save the change. This will remind you to fill in your edit summary if you leave it blank on any page (except your own user page) on any Wikia wiki. If your edit summary is blank and you click "Publish" you will be given a reminder reading "Reminder: You have not provided an edit summary. If you click Publish again, your edit will be published without one". You then have the option to type an edit summary as recommended or just save your edit without one.

## Renaming PagesEdit

On rare occasions, pages may need to be renamed. When pages are renamed, Wikia will automatically create a redirect page that will take old links to the new site. However, links on the wiki will not be updated automatically. The wiki will still function, but users will be alerted to the fact that the link is old with a message below the page title, "Redirected from [old page name]". To eliminate this message and maintain the sense of professionalism that the wiki strives for, you can use the special page WhatLinksHere to find those out of date links that renaming has created, and fix them. Simply type the old page title into the appropriate box, and they will be displayed.

## DeletingEdit

If there are occasions for pages to be renamed, there will also be occasions for pages to be deleted. Only wiki admins can delete pages. If you think a page should be deleted, enter the classic editor and open the source tab. At the top of the page, add the following code with your reason for suggesting deletion:

`{{delete|Reason for deletion}}`

Keep in mind that at this time, redirect pages are a permanent fixture for the wiki. The wiki is here to provide information to the users in a way that's convenient for them to use. Broken external links, whether from an outside site, the Habitica forums, or a page that a user bookmarked, make it less convenient for the readers to use the wiki. Therefore, redirect pages are kept in place so that these links will not give a "404 Page Not Found" error. This ensures that wiki users have a better experience when trying to locate information, and increases the wiki's efficiency in providing consistent, up-to-date information. Remember, our goal is to create and maintain an accurate, up-to-date and easy-to-use guide for players of Habitica, so if there is a redirect page that you firmly feel needs to be deleted, at the top of the page add the deletion code with the reason that the page should be deleted. From there, the wiki admins will discuss the reason and make a decision, and the page will either be deleted, or the deletion code can be removed.

## Creating a User SandboxEdit

Sandbox is a page that can be used to practice editing, to learn the formatting, and to put together drafts without necessarily publishing it to the main page. If you are someone who learns by doing, having a sandbox where you can try out code, formatting, and design can be very useful. Below are the steps to create your sandbox.

1. Go to your user page. You can do this by clicking on your user icon at the top right of any wiki page. You may have to click twice if the first click opens up the menu.

2. Add /Sandbox to the end of your URL. Click on the URL box in your browser, deselect the text, and type in /Sandbox at the very end of. Go to this page.

3. Since you have not yet created your sandbox, you will have the option to do so here. Right next to the page title, click the Create button.

4. If it opens up in the visual editor, select the option to open the source editor. You can find this option by clicking on the drop-down menu next to the Cancel and Publish buttons, and selecting Source Editor.

5. Paste the following code into the text box:

```{{Sandbox}}
<!--EDIT BELOW THIS LINE-->
```

6. Below this pasted text, you can begin to practice editing. One idea to begin with is to add a table of contents and links to useful templates and code that you often need to look up.

7. Whenever you are finished editing in the source editor, click Apply Changes on the bottom right of the frame.

8. Click on Publish to save your page.

9. To find your Sandbox easily, add a link to it on your profile page. You can do so by pasting the following code into the source editor of your user page (found by clicking on your user icon, selecting Edit Profile under the Profile tab, and selecting the Source Editor option), replacing "Username" with your own username:

```[[User:Username/Sandbox|My Sandbox]]
```

10. Voila! You now have a Sandbox of your own! Experiment with it as you please!

## Other Wiki Account Tips Edit

### Toolbar Edit

If you have a wiki account, you can utilize the toolbar that is at the bottom of your screen to use shortcuts and other tools to do various functions. You can find more info on the toolbar here.

If you have a Wiki account and wish to disable ads, you may go to your preference page, scroll down to the ads setting, select "Don't Show all Ads" and then save your preferences.

### Purging Pages Edit

Sometimes pages may be behaving oddly like not showing changes. If this is happening try adding ?action=purge to the end of the URL and going to that address. This causes the page to be reloaded and fixes many problems.

## Contributor Tier ProcessEdit

Please read The Keep:The Knights Chambers to understand the process for requesting a contributor tier and the kinds of wiki changes that are preferred. When you are ready, you can start your application through that page.