(Make it an error to use this template directly) |
(Rewrite most of the documentation to reflect the new structure) |
||
Line 1: | Line 1: | ||
<onlyinclude><includeonly>{{fail|{{PAGENAME}}|transclude one of the subpages instead of this}}</includeonly></onlyinclude> | <onlyinclude><includeonly>{{fail|{{PAGENAME}}|transclude one of the subpages instead of this}}</includeonly></onlyinclude> | ||
This is not a template; rather, it serves as documentation and a common parent for a set of related templates, which are listed below. | |||
These templates hold [[metawikimedia:Help:Array|data]] about the various runs showcased by TASBot and friends. | |||
They need to be paired with a "callback" template for formatting. See any child page for usage docs. | |||
. | |||
Known runs: | Known runs: | ||
Line 30: | Line 9: | ||
<!-- we may want [[mw:Extension:SubPageList]] to customise how the list is formatted --> | <!-- we may want [[mw:Extension:SubPageList]] to customise how the list is formatted --> | ||
Besides the default {{t|showcase}}, there are a couple of other formatter templates for niche use cases: | |||
* <code>anchor</code>: (always present) The same | * [[Runs/row]] | ||
* {{t|format run data meta/run name}} | |||
A formatter template can make use of the following parameters: | |||
<!-- TODO double-check data, then rewrite this to match --> | |||
* <code>anchor</code>: (always present) The same as the page name (spaces, not underscores). The intention is to also use this as a section <code>id</code>/anchor, as {{t|showcase}} does. | |||
* <code>appearance</code>: (always present) The name of the relevant event appearance page, or the name of a redirect to it. | * <code>appearance</code>: (always present) The name of the relevant event appearance page, or the name of a redirect to it. | ||
* <code>author</code>: (always present) A rich text list of the run/playaround's authors. | * <code>author</code>: (always present) A rich text list of the run/playaround's authors. | ||
Line 48: | Line 32: | ||
** in any case it should be passed on to the template specified by <code>tasvideos-movie-template</code> without processing. | ** in any case it should be passed on to the template specified by <code>tasvideos-movie-template</code> without processing. | ||
{{ | The child templates all call {{t|format run data meta/base template}} as a single-source-of-truth, should we want to change something later. | ||
Their documentation is generated with {{t|format run data meta/template docs page}}. | |||
[[Category:General-use_block_templates]] | [[Category:General-use_block_templates]] <!-- intentionally leaving this here for discoverability --> |
Revision as of 09:47, 3 August 2024
This is not a template; rather, it serves as documentation and a common parent for a set of related templates, which are listed below.
These templates hold data about the various runs showcased by TASBot and friends.
They need to be paired with a "callback" template for formatting. See any child page for usage docs.
Known runs:
- Format run data/10 years panel
- Format run data/ALttP
- Format run data/Brain Age
- Format run data/Celeste
- Format run data/Diablo MAGWest panel
- Format run data/Gradius Any
- Format run data/Ikaruga
- Format run data/MK64 Special Cup
- Format run data/NESBot Wizards and Warriors
- Format run data/Pokemon Blue NSC
- Format run data/Pokemon Plays Twitch
- Format run data/Rockman SGDQ 2015
- Format run data/SMB1 and 2U and 2J and 3
- Format run data/SMB3 Any
- Format run data/SMB3 Final Kaizo
- Format run data/SMB3 Hot Pocket
- Format run data/SML2 Memory Tour
- Format run data/SMW ACE
- Format run data/SSBB
- Format run data/SmashBot
- Format run data/Sonic Advance
- Format run data/Super Dram World 2
- Format run data/Super Metroid Encode
- Format run data/Super Monkey Ball
- Format run data/Super Scribblenauts
- Format run data/Triforce percent ESA Summer 2022
- Format run data/Triforce percent SGDQ 2022
- Format run data/VVVVVV 20 Trinkets
- Format run data/VVVVVV Game End Glitch
Besides the default {{showcase}}, there are a couple of other formatter templates for niche use cases:
A formatter template can make use of the following parameters:
anchor
: (always present) The same as the page name (spaces, not underscores). The intention is to also use this as a sectionid
/anchor, as {{showcase}} does.appearance
: (always present) The name of the relevant event appearance page, or the name of a redirect to it.author
: (always present) A rich text list of the run/playaround's authors.game-name
: (always present) The full name of the game, as plain text.game-pub-year
: (always present) The year the game was published, as plain text.lead
: (always present) A rich text list of the people who oversaw the presentation at the event.platform
: (always present) The mnemonic of the system/platform the game is for (follows BizHawk; see {{TASVideosPF}} for details).presenter
: (always present) A rich text list of the people who presented at the event.recording
: (always present) A rich text list of links to videos.run-branch
: (always present) The 'branch' or 'goal' of the run, e.g.100%
,credits warp
,playaround
.tasvideos-game
: (always present) The game's ID on TASVideos (without the 'G' suffix).tasvideos-movie-template
: (always present) The name of one of the {{TASVideos}} family of templates, e.g.TASVideosM
.tasvideos-movie-value
: (always present) Depending on the value oftasvideos-movie-template
:- when it's {{TASVideosM}}, this is the run's publication ID on TASVideos (without the 'M' suffix);
- when it's {{TASVideos}}, this is the relative URI of some page on TASVideos that pertains to this run (i.e. without the
https://tasvideos.org
prefix); - in any case it should be passed on to the template specified by
tasvideos-movie-template
without processing.
The child templates all call {{format run data meta/base template}} as a single-source-of-truth, should we want to change something later. Their documentation is generated with {{format run data meta/template docs page}}.