P.MysteryUniverse Wiki:Manual of Style

This is the manual of style for. While this wiki is free for anyone and everyone to contribute to and edit, it still has certain formalities when it comes to writing on articles, formatting and the like, in order to keep it consistent and adequate.

General Article Style

 * Article titles and headers use (e.g. "Manual of Style", but not "Manual Of Style" or "Manual of style"). When you're unsure about what words should or shouldn't be capitalized, you can always use a converter.
 * Articles don't start with headers.
 * The beginning of an article should have the name or another acceptable sentence/word bolded.
 * Do not copy and paste information (e.g. Ability effect summaries, move descriptions, etc.) from other sites such as . How something works in PMU tends to differ from the main series' and PMD games. Please confirm info you want to put onto the wiki. These sites can still be referenced for things such as what Ability a Pokémon may have, names, and other generally consistent things about the series.
 * Write articles formally with clean grammar.
 * No use of the symbols &, @, or # for shortening what words could be used in place.
 * Contractions (when used appropriately) and proper acronyms are fine. For example, "HP" vs. "Heath Points", given that it's stylized as "HP" in-game, or "PMU" rather than "Pokémon Mystery Universe".
 * "Pokémon" and "Poké" should be used just as so. Do not shorten to "PKMN", "PK", "Mon", etc. An "e" with the accent (é) should always be included.
 * Acronyms for dungeons are only used in articles when mentioning it at the beginning of the dungeon page and in the master list of dungeons on the Dungeons page itself.
 * While most values are void of decimals in-game, please use commas when necessary for readability. The only exception to this rule is sell price on item pages.
 * Pokémon recruit rates (and generally all numbers) should only use a decimal point if the rate/number isn't whole (e.g. "4.5%", but not "5.0%").
 * While third-person perspective is wikiversally preferred, the use of "you" (e.g. "You obtain an Engraved Tablet" vs. "The player obtains an Engraved Tablet") is not strictly forbidden, especially on community articles or pages such as this one. However, a lot of pages shouldn't use it. There's no need to address the reader on the description/usage for items or Abilities, for example.
 * Article text should use American English spelling for words that would otherwise be different in the British English (e.g. "color" or "apologize" instead of "colour" or "apologise").
 * Text in quotation marks and parenthesis should have a period after instead of treating the end of the quote or parenthesis as the end of the sentence it's in.
 * Types are written as "[Type name]-type" (e.g. "Fairy-type") or just "[Type]" for short.
 * Single-digit numbers are written as the word (e.g. "there are two boxes" instead of "there are 2 boxes") unless particularly referencing something that always uses number values like currencies or HP. If the number is in front of a word like "Level" or "Floor", always use the digits. Don't use "1st" or "2nd" instead of "first" and "second" and so on, unless that's how it's stylized in-game (e.g. "1st Place Ribbon").
 * If you need to use a, please use the rather than Tt, as WDSToolTips works for mobile users and can use links and wikitext. Although it should be noted that WDSToolTips aren't perfect and in the case their display breaks or doesn't look right in any given use, Tt can be used instead.
 * When a certain key needs to be specified, use Btn (e.g. "attack using 🇧🇹" instead of "attack using F").

All of that being said, oversights happen. Don't fret over mistakes, but fix them if possible and be sure to check your edits if you can. Dialogue should be written as is in-game, typos included.

Personal Areas
When it comes to your userpage, a blog, or messages in Discussions or talk pages, it's fine to type how it is comfortable for you. Personal pages (a blog post or your userpage) are still property of the wiki and available to the public view. The most they'll be tampered with by admins is for readability and general maintenance unless something is requested.

Articles for guilds may be created and are considered personal pages to a degree, but should still follow basic formatting simply to not look awful. A guild page should be in the Guild and PMU 7 guilds categories and the Community namespace by prepending "Community:" to the title when creating the page. Make sure to actually put things on it, instead of limiting it to "this is a guild and I made it", or it may have to be deleted.

Images used in personal areas should adhere to the file guidelines like any other.

Capitalization
Capitalization is the term used for making the first letter of a word capital.

Tables
Tables are what is used on several pages, such as item pages, to display data or format/design a page. For the latter,  s can be used for the same purpose.

Code of the example table.

Our tables on content pages use specific styling added by the  class. The color can be changed to a region's color scheme if appropriate, by appending a hyphen and a region's name to the pmutable class (e.g. ).

Styles and classes can be tedious to type out repeatedly when they're needed, so there is the TableStart template to help build a table. It has parameters for certain customization if needed, which can be read into on its page.

To make a table for basic usage, put  on a page, and follow that up with   under it. This is a header, signifying what the data under it represents.

Under the header(s) you will need to start a row by adding, then some cells with the data you want to display by using a horizontal bar   under the row. You'll need as many cells on a row as there are headers so there aren't empty blocks. Add more lines and cells as needed and close the table by putting  on a new line.

Otherwise, un-styled tables can be used to position things on a page a certain way.

Also see P.MysteryUniverse Wiki:Templates for other table templates.

Opinion and Bias
Being that this is a wiki, which is meant to share knowledge and information with others, we are obviously to write things from a mostly neutral standpoint. The word "mostly" is used due to the existence of community pages and the "Tips" section used on some dungeon pages.

For example, the Training Locations page. Most of the dungeons listed here are widely agreed on to be good for training. One person could disagree on one dungeon there or another. Hence why it's a community—or, "meta" page. These pages exist due to being historic and PMU itself being community-based. They still end up helping others and that's the purpose of a wiki so they live.

Tips on dungeon pages should be relevant to the dungeon and simplified. In a dungeon that has Fire-types, you can suggest running with a Pokémon that has Thick Fat, rather than putting "use Mobile Scarf with 4x speed nub" which is just forcing your playstyle on others. There's also no need to suggest something like your entire set-up when you beat the dungeon. There is a general tips page and you can always make a blog post for an in-depth dungeon guide.

Dialogue
How dialogue is displayed depends on the article and where in-game: Any other dialogue from "cutscenes" (such as the Exbel Woods tutorial) use listed text, inside collapse:
 * For NPCs you press F to talk to (including in set dungeon floors), it should be conveyed in a table with NPCHeader and Dialogue (example: Grassroot Town, Sunny Hillside). NPCHeader should only be used in dungeon pages if there's more than one NPC. If the NPC has more than one dialog box of text, keep everything in one paragraph. When the player is addressed, use.
 * An NPC like this with dialogue choices should have Tick before the menu text and the dialogue for that choice on a list line, as well as utilizing Mwct on the menu text and Mwcc on the dialogue (example: Housing Center).
 * For dungeon bosses, there's a template specifically for it: BossDialogue. See below.
 * Feel free to use  if the dialogue is only a few dialog boxes long.
 * The name of the speaker should be italicized.
 * When the player is addressed or says something, use
 * For "actions" in dialogue not lead by a speaker's name with a colon, use an indent instead of an asterisk (by putting  before a line). It should be noted that there are cases where story dialogue doesn't have names at all. In said cases, names shouldn't be added unless there's multiple speakers that need to be differentiated.
 * When the story allows a choice, display the choices indented and with Tick. The text unique to that choice should be indented as well. If both choices lead to the same thing, then no indention.
 * If dialogue can be repeated through a certain choice, utilize Re.
 * See.

Signs

 * Some dungeons have signs in them (Ash Forest, Concealed Laboratory). ChatSign should be used for them.
 * Not inherently a sign but some dungeons or areas have notices (Mt. Skylift). Notices will have black and grey (#808080) text. Use Color to color the text appropriately, wrap the entire text in quotes and also italicize it.

Item Pages

 * Items on item pages are listed in tables using ItemRow/t and ItemRow. Depending on the items being listed there tends to be a Summary and Effect header. Some tables don't have locations listed when it's one or a few items being described and/or the location is mentioned in text.
 * The locations go on a line of a list, in alphabetical order, separated by commas. Where applicable, lines go in this order: Dungeon names, shops, missions, then other miscellaneous methods of obtaining the item, all on separate lines.
 * All details, such as what floor and tiles the item spawns on, go in (parenthesis) next to the dungeon name. Where applicable, details go in this order: floors + tiles + hidden, end room, end box, Secret Room box, boss drop, Kecleon Shop. Separate any tiles with a forward slash (/).
 * Ss should be used for some details. See the page for how to use it.
 * If an item spawns on all floors and only on the ground, nothing needs to be specified for floors or tiles. Only if the item spawns on the floor and other tiles, or is also obtained through boxes or etc. should "floor" be specified.
 * When a list line has more than 30 entries, use . This regex can be used to do it automatically.
 * Use Items Navbox at the end of item pages.

Ability Pages

 * All pages should have two headers at the least; "Effect" and "Pokémon with [Ability]".
 * If a Pokémon in the list of Pokémon with the Ability is not able to be obtained by players in PMU yet, put  after its name.
 * There are items in PMU which give the effect of an Ability. Please make sure that these are referenced on the page of the real Ability. These items also sometimes give text different from the actual Ability in the Battle Log when taking effect. Have a screenshot of both (example: Strong Jaw).
 * For pictures, see P.MysteryUniverse Wiki:File Policy.