The first video in the TASBot Re: (TASBot Revisited) series is out! TASBot Re: Gradius covers our first run from AGDQ 2014.

Historians wanted: Inquire here.

Template:Format run data: Difference between revisions

Template page
m (Fix typo)
Tag: 2017 source edit
m (Clarify relation to formatting templates)
 
(102 intermediate revisions by 5 users not shown)
Line 1: Line 1:
<onlyinclude><includeonly>{{#switch:{{{2}}}
<onlyinclude><includeonly>{{fail|format run data|transclude one of the subpages instead of this}}</includeonly></onlyinclude>
|SML2 Memory Tour={{{{{1|showcase}}}
 
|appearance-page=[[SGDQ 2016]]
This is not a template; rather, it serves as a common parent for a set of related templates, for example {{t|format run data/Brain Age}}, {{t|format run data/Pokemon Plays Twitch}}, and {{t|format run data/Triforce percent ESA Summer 2022}}.
|run={{TASVideos|/Userfiles/Info/31714711949576163|Super Mario Land 2 Memory Tour Showcase}}
<br>These child templates hold [[metawikimedia:Help:Array|data]] about the various runs showcased by TASBot and friends.
|run-branch-short=Memory Tour
A separate "callback" template handles the formatting, and that template needs to be specified by name (or left blank).
|game={{TASVideosG|452|Super Mario Land 2}}
<br>Each child template has a copy of usage docs&mdash;<!--
|game-pub-year=1992
-->visit any of them for instructions on how to make use of the data in an article.
|platform={{TASVideos|/Platforms#GameBoy|Game Boy}}
 
|author={{TASVideosU|link_7777}}
Known runs (click <q>Expand</q>):
|presenter=dwangoAC, link_7777
<div class="mw-collapsible mw-collapsed">
|recording={{YouTube video|1GF_LFPz34U|TASVideos (YouTube)}}, {{YouTube video|1=EHfw-BEuRO8?time_continue=429|2=GDQ (YouTube)}}
{{Special:PrefixIndex/Template:Format_run_data/}}
|lead=[[dwangoAC]]
<!-- we may want [[mw:Extension:SubPageList]] to customise how the list is formatted -->
}}
</div>
|VVVVVV={{{{{1|showcase}}}
<br><hr>
|appearance-page=[[SGDQ 2016]]
 
|game={{TASVideosG|1442|VVVVVV}}
Besides the default {{t|showcase}}, there are a couple of other formatter templates for niche use cases:
|game-pub-year=2010
* [[Runs/row]]
|platform=PC
* {{t|format run data meta/run name}}
|run={{TASVideosM|2715|VVVVVV 20 Trinkets, No Death}}
 
|run-branch-short=20 Trinkets, No Death
A formatter template can make use of the following parameters:
|author={{TASVideosU|Masterjun}}, Mundungu
<!-- TODO double-check data, then rewrite this to match -->
|presenter=dwangoAC, Mundungu
* <code>anchor</code>: (always present) The same as the page name (spaces, not underscores).<!-- this does work, though I can't see how --> The intention is to also use this as a section <code>id</code>/anchor, as {{t|showcase}} does.
|recording={{YouTube video|1GF_LFPz34U|TASVideos (YouTube)}}, {{YouTube video|1=EHfw-BEuRO8?time_continue=1310|2=GDQ (YouTube)}}
* <code>appearance</code>: (always present) The name of the relevant event appearance page, or the name of a redirect to it.
|lead=[[dwangoAC]]
* <code>author</code>: (always present) A rich text list of the run/playaround's authors.
}}
* <code>game-name</code>: (always present) The full name of the game, as plain text.
|{{t|format run data}}: <span style="color: red;">no such run "{{{2|}}}"</span>}}</includeonly></onlyinclude>
* <code>game-pub-year</code>: (always present) The year the game was published, as plain text.
* <code>lead</code>: (always present) A rich text list of the people who oversaw the presentation at the event.
* <code>platform</code>: (always present) The mnemonic of the system/platform the game is for (follows BizHawk; see {{t|TASVideosPF}} for details).
* <code>presenter</code>: (always present) A rich text list of the people who presented at the event.
* <code>recording</code>: (always present) A rich text list of links to videos.
* <code>run-branch</code>: (always present) The 'branch' or 'goal' of the run, e.g. <q>100%</q>, <q>credits warp</q>, <q>playaround</q>.
* <code>tasvideos-game</code>: (always present) The game's ID on TASVideos (without the 'G' suffix).
* <code>tasvideos-movie-template</code>: (always present) The name of one of the {{t|TASVideos}} family of templates, e.g. <code>TASVideosM</code>.
* <code>tasvideos-movie-value</code>: (always present) Depending on the value of <code>tasvideos-movie-template</code>:
** when it's {{t|TASVideosM}}, this is the run's publication ID on TASVideos (without the 'M' suffix);
** when it's {{t|TASVideos}}, this is the relative URI of some page on TASVideos that pertains to this run (i.e. without the <code><nowiki>https://tasvideos.org</nowiki></code> prefix);
** 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]] <!-- intentionally leaving this here for discoverability -->

Latest revision as of 21:02, 25 November 2024


This is not a template; rather, it serves as a common parent for a set of related templates, for example {{format run data/Brain Age}}, {{format run data/Pokemon Plays Twitch}}, and {{format run data/Triforce percent ESA Summer 2022}}.
These child templates hold data about the various runs showcased by TASBot and friends. A separate "callback" template handles the formatting, and that template needs to be specified by name (or left blank).
Each child template has a copy of usage docs—visit any of them for instructions on how to make use of the data in an article.

Known runs (click Expand):



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 section id/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 of tasvideos-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}}.