m (Lume moved page Template:MoveDataCargoTest/Query to Template:MoveDataCargoTest/Inherit without leaving a redirect: this should store new move in a table, plain Query should just display without any stores or overrides) |
RogerDodger (talk | contribs) (share documentation with Template:MoveInherit) |
||
| (3 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
<includeonly>{{#invoke: | <includeonly>{{#invoke:Move7|inherit}}</includeonly><noinclude>{{documentation|Template:MoveInherit}}</noinclude> | ||
Latest revision as of 12:32, 5 March 2024
 |
This template uses Cargo: |
 |
This template uses Lua: |
| Movelist templates |
|---|
|
| Punishment templates |
|
{{MoveInherit7}} is the same as {{MoveInherit}} but uses Special:CargoTables/Move7 instead.
This template defines a new move based on an already existing one.
Main use is to define a move based on a generic move, e.g. Generic-d+1 is shared by most of the cast but its range, tracking, and input differs for each character.
It can also be helpful when writing movelists to avoid duplication, e.g. when a character has distinct moves that are largely the same.
Usage
{{MoveInherit|Generic-d+1
|id=Lidia-d+1
|input=db+1
|range=1.82
}}
Parameters
Parameters are largely the same as {{Move}}, with the addition of 1 which is the id of the move to be inherited.
If no id parameter is given, the new move won't be saved in the database.
If any of the following parameters are given, the new move is not considered a clone (meaning no clonedFrom link will be generated): target, damage, startup, recv, tot, crush, block, hit, ch, notes.
- The above documentation is from Template:MoveInherit/doc
- Editors should experiment in this template’s sandbox and testcases pages