No edit summary |
|||
| Line 9: | Line 9: | ||
==Labeled Section Transclusion== | ==Labeled Section Transclusion (Deprecated)== | ||
Games that use Labeled Section Transclusion contain two section tags: <code>${X}</code> and <code>${X} Extra</code>. For example, [[P4AU/Yosuke Hanamura/Data]] has a section called <code>5A Data</code> with section tags <code>5A</code> and <code>5A Extra</code>. The former is for standard frame data while the later is for additional fields. | Games that use Labeled Section Transclusion contain two section tags: <code>${X}</code> and <code>${X} Extra</code>. For example, [[P4AU/Yosuke Hanamura/Data]] has a section called <code>5A Data</code> with section tags <code>5A</code> and <code>5A Extra</code>. The former is for standard frame data while the later is for additional fields. | ||
Revision as of 23:46, 19 September 2023
Frame data for the newer games is stored on a separate page under ${Game Abbreviation}/${Character}/Data ex DBFZ/Trunks/Data. This is so all the values are in one place and is meant to solve the issue of people updating the frame data on a character page, but not the frame data page.
We use the plugin Cargo to achieve this. Older pages use Labeled Section Transclusion, but this way of adding frame data is outdated.
Each move has a section ${X} Data that contains the data used by the other pages.
Cargo
Games that use Cargo have a template that contains all the frame data for a character that populates a database that we later retrieve values from on various character pages. For example DBFZ/Trunks/Data has the data that populates DBFZ/Trunks and DBFZ/Trunks/Frame Data
Labeled Section Transclusion (Deprecated)
Games that use Labeled Section Transclusion contain two section tags: ${X} and ${X} Extra. For example, P4AU/Yosuke Hanamura/Data has a section called 5A Data with section tags 5A and 5A Extra. The former is for standard frame data while the later is for additional fields.