Wavu:Character pages

The top of all the character pages should have a {{Navbox fighter}} on it, which has the following standard pages:

This {{Navbox fighter}} should not be directly included on any pages. Instead, a template based on it exists for each character, and that template goes on the top of each of the pages linked. These templates are called e.g. {{Navbox Lee}} for the Lee navbox.

(For Tekken 7 these are just named after the character, e.g. {{Lee}} is the Lee navbox for Tekken 7.)

The changelog pages all already exist and source everything from Module:Patch. To update these, update the relevant patch page.

More pages can be added to the navbox if necessary on a per-character basis, as in e.g. {{Lee}}. Don't add the character name to the title unless there's ambiguity, e.g. call the page Acid Rain and not Lee Acid Rain or Acid Rain (Lee), because there's no other character with Acid Rain.

Overview

The overview page (e.g. Lee) should have on it {{Infobox fighter}}, {{BlueRed}}, {{KeyTechs}}, {{Punishment}}, and {{Navbox fighters}} transcludes. The bio on this page should be aggressively brief, ideally only 2–3 short paragraphs.

Tekken 7 pages should also have {{Archetype}} on it.

Movelist

Main page:

If you get an error saying "parent not found" and the missing parent is also new with your edit, you have to save the page twice for it to work.

This is a known, possibly unfixable issue when referring to a parent that is in the same edit.

Movelist pages primarily consist of {{Move}} transcludes. See that documentation for guidance on what to put in each field.

Miscellaneous

Generic moves can be included but a movelist is considered complete without them.

Usage tips should not appear in movelists. A movelist entry only describes what the move does, how it behaves, not how to use it. Further details belong elsewhere, such as the strategy or tech pages.

There is no robust standard currently for notating jumping moves or running moves.

Order

Within sections moves are ordered by stance first (no stance first, then alphabetical order on stance abbreviation), then direction (n first, then clockwise starting at f), then numerically by button (first 1, last 4; combinations ordered by number of buttons, then starting from the first button). So for example, 4 is before f+3 is before d+1 is before d+4 is before d+2+3 is before d+1+2+3.

Sections

Movelists are split into sections to make it easier for readers to find the move they're looking for. Each section should have a {{MoveDataHeader}} at the top of it.

The standard sections are:

• Heat
• n
• f
• df
• d
• db
• b
• u
• Motion input
• Crouch
• WS
• Character specific stances
• Others
• Throws
• 10 Strings
• External links

For Tekken 7 movelists, "Rage" replaces "Heat". For Tekken 8 movelists, Rage Art goes under Others.

Heat

The heat section contains any moves that use the heat gauge. The entries should be in this order:

1. Heat burst (2+3)
2. Heat smash(es) (H.2+3)
3. Moves that can only be done in heat
4. Heat engagers (indicated with {{HeatEngager}} in notes)
5. Moves that consume or replenish the heat bar or that have unique properties while in heat

Heat dash moves should not have a separate {{Move}} entry. {{HeatDash}} used in notes is enough to indicate a move can do a heat dash, e.g. {{HeatDash|+11g +26d}} indicates that a heat dash can be done and is +11g on block and +26d on hit.

Heat engagers are duplicated in the main movelist, making use of {{MoveQuery}}.

Moves in the 5th category are duplicated at the editors discretion, making use of {{MoveQuery}} or {{MoveInherit}} as appropriate.

Motion input

The motion input section contains dash, wr, and other moves that make use of a motion input but that don't belong in a specific stance section. Running moves are notated e.g. f,f,F+2, with "wr2" listed as an alternate input in notes. Dash moves are notated e.g. f,F+2.

Crouch

The crouch section contains hFC and FC moves, in that order.

The main listed input for these moves should not include the down input unless some other direction is also involved, so e.g. hFC.d+1 should instead be written hFC.1. Similarly, there's no need to mention that hFC.1 has e.g. hFC.db+1 as an alternate input, since this is implied.

Character specific stances

Each stance section contains any manual transitions at the top, followed by the stance's moves in regular order. Manual transitions can be duplicated elsewhere in the movelist at editors discretion, making use of {{MoveQuery}}.

Whether a stance goes in its own section is at editors' discretion. As a rough guideline, a stance goes in its own section if there are multiple ways of entering it or if it has 4 or more moves.

If a stance only has one transition and a few moves, it's usually more appropriate to list all the stance moves immediately after the transition. For example, Lei's db+1 has all Sitting Snake moves listed immediately after it in his Tekken 7 movelist.

The stance section heading must use the Wavu abbreviation of the stance, followed by full name of the stance (as mentioned in the in-game movelist) in parentheses and italicized e.g. Eddy's Bananeira stance heading would be -

== HSP (''Bananeira'') ==

Stance Abbreviations

Stance abbreviations are standardized in Wavu movelists as three-letter representations of the full stance name (e.g. HRS for Lidia's Horse stance). This is done in order to make communication about the stance, and stance move notation, more concise and easy.

Abbreviations are chosen by Wavu editors, but to serve the goals of easier communication, they should be chosen with heavy deference to existing community usage (as observed on spaces like character Discords, YouTube guides, shared Google Docs, or X/Twitter), or legacy (e.g., HSP for Eddy's Bananeira stance). In case of new stances, abbreviations should be chosen carefully to avoid clashes with existing stance abbreviations, and to intuitively suggest the original stance name as much as possible (e.g., MNT for Zafina's Mantis stance, WRA for Reina's Heaven's Wrath stance).

Others

The others section contains moves from stances like OTG, SS, and BT that most characters only have one or two moves for. If one of these stance has a substantial movelist (e.g. BT for Xiaoyu), it should be in its own section.

For Tekken 8 movelists, a character's Rage Art should be included in this section.

Throws

The throws section contains all non-striking throws. It does not contain parries, which are placed in the movelist based on their input.

The generic f+1+3 and f+2+4 throws have their own entry, making use of {{MoveInherit}} as appropriate.

For generic positional throws, these are notated with the inputs being "Left throw", "Right throw", and "Back throw".

10 Strings

Every hit of a 10 string should be included with a separate {{Move}} entry for each intermediate move in the string, just like how other strings are included.

Note: For historical reasons, a majority of the 10 strings are currently included as a MediaWiki table. These should be changed.

External Links

The "External links" section links to other movelists or frame data for this character. Every movelist should have a link to the respective English page on geppopotamus.info. Links to YouTube videos going through the in-game movelist are also appropriate.

Base template: {{Movelist}}

The movelist pages should primarily consist of {{Move}} transcludes ordered as follows. Sections: Rage, n, f, df, d, db, b, u, Motion input, Crouch, WS, {Char specific stances}, Others, Throws, 10 Strings. If a char has multiple BT transitions then BT should get its own section before Others. Within sections moves should be ordered by direction first (n first, then clockwise starting at f), then numerically by button (first 1, last 4; combinations ordered by number of buttons, then starting from the first button). So for example, BT.4 is before BT.f+3 is before BT.d+1 is before BT.d+4 is before BT.d+2+3 is before BT.d+1+2+3. Generic moves can be included but a movelist is considered complete without them.

The movelist pages should not contain usage tips in the notes. Notes should only address the technical details of what the move does. Further details belong elsewhere, such as the strategy or tech pages.

Strategy

Base template: {{Strategy}}

The strategy pages and others like it should avoid dumping frame data on the reader as much as possible. If someone wants the frame data they know where to find it. Write things about key moves that aren't obvious, and if that means there's nothing else to write (which isn't likely), don't bother writing anything.

Punishers

Base template: {{Punishers}}

The punishers page should have {{Infobox tricky moves}} and {{PunisherTable}} on it.

In the table, stance transitions should be indicated under frames. If it's an optional transition, make a separate row for the transition input. See Anna punishers. Damage of launchers should list the damage of just the launcher, and then the damage of the combo in brackets, with a link to the relevant section in the combos page, e.g. 30 (55).

Combos

Base template: {{Combos}}

The combos pages should have the combos ordered by damage, descending. If the character has a unique combo technique, it can be explained briefly at the start of the Staples section, e.g. Lee combos#Staples. Launchers should be grouped together as much as possible to simplify the page, but be careful not to overdo it.

If combo variations are only on the enders, e.g. there's 5 enders that work on all the various starters, don't list every possible combination of these. List all the enders for the starter that does the most damage, then leave it implied for the rest of them. It might also be better in some cases to explain the post-screw enders on their own.

Deprecated layout

Previously, the navboxes used a {{Row}} transclude, and each subpage was written in manually. These typically included some subpages that are no longer standard:

• Fighter neutral, scope is now covered by Fighter strategy.
• Fighter setups, scope is now covered by Fighter strategy.
• Fighter matchups, used to be based on {{Matchups}}. Scope is now handled by putting the information in one of the relevant subpages.
  • The idea behind these was that the matchup pages would be symmetrical, e.g. Kuma vs Lee would be written for and read by both Lee and Kuma players, and this would avoid redundancy. However, in practice, the scope of these pages rarely got beyond people listing their combos and punishers that were specific to the matchup (or even worse, copying the same combo to 5-10 different matchup pages), and this structure just ended up making that information scattered, disorganized, and less visible.
  • Any information currently in a matchup page should be moved to a more visible page. For example, all of the info in Kuma vs Lee can be moved to Lee combos.