The following is a list of sections detailing the outlines that should be applied on all content and resource articles. Additional sections may only be added under special circumstances, and only if such information does not belong appropriately in any other designated section. This page is linked from the Manual of Style, and more guideline information can be found there.

Content Pages

Game Information Pages




===Standard Gameplay===
===Battle Gameplay===

==Release Overview==

==Version History==




==External Links==

{{Game Template}}
{{Game Character Template}}
{{Game Location Template}}
[[Category:Mothership Titles]], [[Category:Escort Titles]], or [[Category:Mobile Titles]]

The Story section details the setting and entire plot of the game as a player would experience it while playing the actual game. Subsections should be provided for clarity, grouping events into loose or informal chapters.

The Characters section should provide a list of all joinable characters, including any pets or mascots, and only the most significant supporting characters and antagonists. A fair guideline for choosing which characters to display here is to list the same characters mentioned on the official Japanese Tales Channel websites for each game. Each listing of a single character should provide his or her name in both English and Japanese releases and follow with a very brief description of the character. More detailed descriptions belong on that character's respective article.

The Gameplay section is separated into two general subsections, though additional subsections may be provided as needed. Standard Gameplay refers to game mechanics that do not relate to the battle system, such as overworld map movement or skit systems. Battle Gameplay is used to explain the battle mechanics of a game, most of which will not be related to the Linear Motion Battle System variation used by that game. This includes the arte-cost system, the combo chaining system, Over Limit mode and similar functions, and shortcut usage. All details may be explained further on their own pages if they exist. This section should be used to provide a decent amount of explanation without going into the fine details of damage formulas or status effects. As for information related to the LMBS, the first paragraph of this section should provide an overview of the new LMBS benefits, keeping in mind that the LMBS only relates to movement within battle through various gimmicks like the use of three lines or Around Step.

The Release Overview section should explain all details about every major version of a game, providing specifics about its entire development cycle, including advertisements and delayed release dates, if such information is known. The Version History section that follows afterward is a list table that displays many important statistics about a game, showing every possible version that has been released for any console and region, as well as displaying catalog numbers and release dates for each version. This must include all demos, limited editions, and reprints.

Character Information Pages



==Appearance and Personality==

==Fighting Style==

==Other Appearances==



{{Individual Character Template}}
{{Game Character Template}}

The History section is a full description of a single character's role throughout an entire game, or multiple games in the same timeline. This should focus on the primary timeline of games in which the character appears, usually starting with the game that introduces him or her into the series. This story should be written in the order that a player would learn of the character's perceived role and past, not the chronological truth, as some might be inclined to write. This means that any false histories must be written as truth until the actual truth is revealed.

The Appearance and Personality section includes the character's initial and/or default visual appearance, including any changes made to the character throughout the game, as well as his or her motives, general thoughts, and emotions. Alternative costume designs for playable characters should not be included, but enemies who change their outfits as part of the story should have all appearances described. Common traits and interests can be included here, including favorite foods and hobbies or personality quirks.

The Fighting Style section involves the character's ability to attack or defend in battle with a chosen weapon. Each character has some unique abilities compared to others in the same game, relating to their speed and damage ratios or focus on specific elements or spellcasting styles. This section should not have anything that makes a character "more" effective compared to others or similar, potentially bias-implied comments, just that they are simply effective at doing what they do. Specific numbers should not be provided, and listings of a character's attack repertoire should be limited to a small handful of selected examples, never an all-inclusive list. Other pages exist to showcase this information.

The Other Appearances section includes a detailed description of a character's role in games that are not part of the timeline from which he or she originates. These tend to be non-canon appearances; see this section for specifics on determining what is canon or not. Each game should be listed in its own subsection, sorted chronologically by release date. Keep in mind that the section headers should not have links in them, and any links must be provided within the first sentence of that section instead. Ensure all sections actually explain the character's role in these side materials; if nothing can be said beyond how a character merely appears in it, then there is no reason to keep that subsection. Again, single sentences are pointless and should be expanded or deleted.

The Trivia section includes interesting facts non-mergeable in any other section. If said bit of information can be merged, however, then it should be, as the trivia section should not be cluttered with meaningless and unnecessary information. Speculation is forbidden in this section. Trivia sections should follow some sort of order scheme for the sake of uniformity and neatness. Etymology, if any, should be listed first, followed by interesting facts concerning the character him or herself, then anything dealing with them in their primary title game, and finally, anything dealing with them in other game titles.

Location Information Pages






{{Game Location Template}}

The Geography of a location relates to its climate, architectural styles, and lifestyles of the people who might live there. The area's known religious and social structures, along with common business and agricultural interests, should be mentioned. A description of the surrounding region may be helpful, and named buildings and shops can be listed.

The History section relates to the role of the location within the story of a game, once again following the chain of events that a player would experience. This should provide information that relates specifically to the location and its people.

Arte Information Pages

==Arte Description and History==

{{Arte Appearances

==Fan-Translated Names==

==In-Game Descriptions and Battle Quotes==


==External Links==

[[Category:<Arte Categories>]]

The lead of arte information pages should be short but display the arte's Japanese name and, if it exists, its current localization.

The Arte Description and History section details a description of the arte. It can also detail the arte's movements or what makes the arte significant to the games in which it appears or to the series as a whole. It can contain information on etymology, if relevant. Data such as levels, damage, or TP costs, however, should not be included. Multiple single-sentence or otherwise short/choppy/broken paragraphs should be merged for aesthetic purposes and a fluid, transitional writing style.

The Appearances section is separated into subsections based on titles in which the arte is used. This section mainly concerns instances where the arte is used in battle. Instances where artes are only used outside of battle should be noted with the term "Cutscene". The format is:

*'''[[<Game Name>]]''' - <Users> (<Localized Name>)

In order to maintain correct order of appearances based on the media they appear in the user of Template:Arte Appearances is mandatory. If an arte appears in only one version the title order has listed as grouped, it can be split into several lines to retain correctness. The users should be organized accordingly: Playable Characters, Non-playable Characters, Generic Enemies. Note that enemies should be listed according to their name in battle. If the character uses the arte indirectly, such as through another arte, or as a skill, that information is also noted with colons and separated by semicolons. If more than one localized name exists for the title, those instances are separated by commas within the above groups. Examples:

Example Explanation
Tales of Vesperia (X360) - Flynn Scifo, Traitor to Heaven (Demon Fang)

Tales of Vesperia has two releases: X360 and PS3. The PS3 version adds a user of Demon Fang, so what is normally just Tales of Vesperia is split into two lines with indications of which version it is referring to. Additionally, because the PS3 version is not localized, it lacks a localized name in parentheses. On the other hand, Overlord Reign Impact is used by Karol in all versions of Tales of Vesperia, so it remains on one line.

Tales of Vesperia (PS3) - Flynn Scifo, Leblanc, Traitor to Heaven
Tales of Vesperia - Karol Capel (Overlord Reign Impact)
Tales of Eternia - Reid Hershel (Spiral Attack), Cress Albane (Spiral Destruction) Spiral Attack is localized by two different names in the same game, so they are separated by a comma.
Tales of Vesperia (PS3) - Estelle; Gamble Cast: Patty Fleur With this arte, Estelle uses it normally, but Patty Fleur can use it indirectly through the Gamble Cast arte, so this is noted with the colon.
Tales of Xillia 2 - Cutscene: Mint Adenade (Time Stop) Mint only uses this arte in a cutscene, so it is listed as such here.
Tales of Link - Mint Adenade, Tear Grants (First Aid), Kratos (First-Aid), Laphicet; Skill: Hisui Hearts (First Aid), Remi A combination of multiple rules, the situation is as follows:
  • Mint, Tear, Kratos, and Laphicet have access to First Aid as artes; Hisui and Remi have access to them as a skill. Arte is the default and needs to qualifier, but skill does, so the two groups are separated by a semicolon, with the latter being qualified with "Skill:".
  • Kratos uses the arte when fought as just "Kratos", so his name is just that as opposed to his full name.
  • The arte is localized as "First Aid" when used by Mint and Tear, as "First-Aid" when used by Kratos, and unlocalized when used by Laphicet. In this situation, commas separate all of them due to the above rule. Player usage (First Aid) takes precedence over enemy usage (First-Aid), while unlocalized versions dangle at the end. All of this is before the semicolon that represents the Skill grouping.
  • The skill is localized as "First Aid" when used by Hisui and unlocalized when used by Remi. The same rule applies as above.

The Fan-Translated Names section lists all of the names artes are listed as in various fan translations. The format is:

'''<Game Name> (<Release Group Name>):''' <Fan Translation Name>

The In-Game Descriptions and Battle Quotes section lists transcriptions of arte descriptions copied directly from the game and the quotes from the users. It is organized in the same order as the appearances, though not explicitly separated into title classes. Quotes and descriptions should have the format described here. If more than one user exists for a game and descriptions and/or quotes differ, each should also be organized underneath a User section like below:

User: <User>
Japanese Quote: [Japanese Text]
Romanized Quote: Romanized Text
Translated Quote: "Literal Translation"
Localized Quote: "Localized Text"

If more than one arte is covered on a page, the Appearances, Fan-Translated Names, and In-Game Descriptions and Battle Quotes should apply the tabber function with each table associated with one arte.

When categorizing arte pages, please follow the order of categories listed here.

Feature Information Pages




Features typically encompass a wide variety of games in the series and are difficult to categorize as gameplay or storytelling as a result. Because features appear in so many games, categorizing the games in which the features appear is not necessary.

The Description section is optional here, but it is worth implementing if the basics of the feature require some form of explanation.

Appearances can be divided into Appearances in Mothership/Escort/Mobile Tiles if the topic ventures into more than one title category. Otherwise, "Appearances" is all that should be listed. This section overviews the feature in all games in which it appears, incorporating any information that may be relevant.

Gameplay Information Pages



[[Category:Gameplay Mechanics]]
[[Category:<Relevant Game(s)>]]

The Function section should detail the particular use of the mechanic in the game, paying close attention to its significance in overall gameplay.

The History section exists only to elaborate on the particular mechanic's relevance in the story of the game. Not all gameplay mechanics pages require this section, however, and it should only be applied where necessary.

As with all information pages, exceptions do arise, particularly when the page topic encompasses more than one main category.

Storytelling Information Pages






[[Category:<Relevant Game(s)>]]

Events, languages, natural phenomena, organizations, races, technology, and terminology all fall under the category of storytelling mechanics, and these pages abide by a similar format as a result.

The Description section should provide an overview of the topic paying close attention to usage and physical appearance, if applicable.

The History section should explain how the topic relates to the story as a whole, its relevance, and any other information pertaining to the game's plot.

A List section can be used on certain pages, usually terminology and race pages, to provide a list of types relating to the topic or notable members of a particular race. A Members section is to be used strictly with organization pages, listing all relevant members of the group.

A Gallery section, in this case, should primarily be used for the purpose of displaying images of the members listed above. The images should be formatted into a table, drawing from this gallery for dimensional consistency.

A Trivia section, in this case, will most likely only be used for etymological purposes.

As with all information pages, exceptions do arise, particularly when the page topic encompasses more than one main category. Also keep in mind that organizations have their own template, which can be found here.

Soundtrack Information Pages


==Track Listing==


[[Category:<Relevant Game>

Soundtrack page outlines should be very simple, including only the template, a brief introduction paragraph, a Track Listing section, and a References section. Track listing should be listed in Wikia's hashtag (#) numbered style. Song names should be contained within quotation marks and should avoid any stylization. Even if lyric pages exist on this wiki for the songs, do not link them.

Lyric pages are part of a very small and dead project. Linking song titles would ultimately lead to countless red links that will never be satisfied with pages. Artists should be linked to their appropriate Wikipedia page, if such exists. If not, they should remain unlinked. Unless the article's information derives from one's personal copy of the soundtrack, a source providing the soundtrack's information and track listing should be provided. RPGFan is an ideal source to reference for such information.

Song Information Pages

==Game Version Lyrics==

==Full Version Lyrics==


Game Version Lyrics refers to the portion of the song that is used in the game, while Full Version Lyrics refers to the full version of the song. All lyrics should be sorted within tables as follows:

Japanese Lyrics Romanized Lyrics
Translated Lyrics
English Lyrics

English lyrics refers to what has been localized. If one or more of these lyric categories are not available, simply omit the section from the table and only include what is available.

People Information Pages


===Mothership Titles===
===Escort Titles===
===Mobile Titles===


==External Links==

[[Category:Character Designers]] or [[Category:Music]]

The Biography section should detail the person's work in their field, particularly relating to career beginnings and possibly early works. These details should not expand greatly and inevitably tie into the person's work specifically in the Tales series of games.

The Works section should list, in bulleted style, all works in the Tales series to which he or she has contributed. The organization is structured identically to the "Appearances" section of arte information pages. Again, titles should be ordered based on this list. Details regarding the specifics of whom or what he or she designed/composed can be listed beside the title.

The References section of these articles should include a link to the person's Wikipedia page, if such exists.

The External Links section of these articles may include links to the person's official website(s), if such exist.

Categorize with "Character Designers" for character designers and "Music" for composers.

Resource Pages

An outline or template for these pages will not be provided here since every game features different mechanics and functions that will force changes that must be added manually to each list table. However, a few guidelines will be listed here, so future pages can follow a generally-uniform design.

General Guidelines

All list tables of a single type should follow the same color scheme, regardless of game or character. The specific colors that are to be used with each type of list table can be found on this page. Names that are listed in the first column should be displayed using the format described here.

The next columns should relate to functionality of the arte/skill/title/item, with the single-word-based information given priority toward the left side of the table. The Requirements and Customization/Synthesis columns, typically the most text-heavy columns, are to be placed at the far-right. The remaining numerical data is placed between both sets of columns.

The numerical data columns should be arranged so that functionality information such as damage, hit counts, or stat parameters is closer to the left side and requirement/acquisition information such as usage costs and levels is closer to the right side. All numerical columns should be displayed within 25pt-width columns to minimalize whitespace due to the header names in the first row.

Finally, any auxiliary information like healing percentages or alternative effects through increased usage must be placed on a nested second row. The rowspan and colspan keys enable this through the source code, so space will not be limited to the width of a single column. No column for "function" should be provided unless there are not enough columns to make a nested row visually appealing.

Default Sorting Method

For item-based lists, the initial sorting method should always be the way they are sorted within the Collector's Book, also providing the number associated with that item at the extreme left of the table and colored in the same manner as the item name column. Any other lists that follow a numbered system, such as monster lists and sometimes title lists, should follow the same sorting pattern on the list pages. If a game does not have a Collector's Book or some other system of cataloging items, other than an alphabetical sorting system, which will not be used by default on this wiki, the items should be sorted by parameter, such as ascending physical attack or defense.

Arte lists should always be separated into different tables based on the arte type and tier, and then sorted within each table in the order that characters will obtain those artes, typically by level, with the event-obtained artes listed at the bottom of each table. This may be different from the sort method used by the game itself, which may mix artes of different tiers together on the same list, or even include event-based artes in the middle of the list. For the games that do not have a level-based system of learning attacks, such as Tales of Destiny 2, Tales of Hearts, and Tales of Graces, the arte lists for that game should still separate by type and tier, then follow the sort method of that game.

Sortable Functionality

It is possible to add sorting functions to each column, allowing the reader to decide how he or she wants to view the page and compare its data. These functions should be enabled only on pages where most information is organized as a single table, such as equipment, recipe, or monster list pages. Do not add these functions to arte or passive skill lists.

Sortable functions are enabled by adding the words class="sortable" to the first line of code that creates a table. Due to issues with columns that contain both numerical and string data, a special override function was developed to minimalize and hopefully prevent table display glitches through the use of hidden sort keys that must be added manually on every table with sortable functions enabled. A sort key must be provided at the top and bottom of every column, providing an extremely high or low value that will always force one or the other to appear at the top of a sorted column. For strings, the two values should be &a and ~z, and for numerical columns, the values should be -9999 and 9999, give or take a few more "9" digits depending on the content of a row.

Community content is available under CC-BY-SA unless otherwise noted.