Decide how to cover Mario Kart Tour bonus challenges on course articlesTemplate:ProposalOutcome The layout of each bonus challenge in Mario Kart Tour (e.g. Ring Race) depends on the course in which it is set. It tracks, therefore, that these challenges should be covered in detail on their relevant course articles in addition to their parent article. If you wish to see how a course article would look with coverage of its bonus challenges, scroll down to the "Mario Kart Tour" section in the "History" section here. However, bonus challenges have been observed to appear multiple times across the game's tours, sometimes with changed objectives, which prompts wiki users to regularly update their list entries. Simply copying and pasting these entries onto another article would make it more difficult for users to be aware of which needs to be updated where. On the other hand, adding a way to transclude entire entries (allow information entered on a page to be automatically transferred to another) would spaghettify the original code and potentially deter users from updating it with new information. For instance, this is how the code for an average bonus challenge entry currently looks: |- |[[File:MKT Tour1 YoshiCupChallenge.png|200px]] |[[New York Minute]] |[[File:MKT Icon Yoshi.png|50px]]<br>[[Yoshi]] |[[File:MKT Icon PipeFrameLimeGreen.png|50px]]<br>[[Pipe Frame]] |[[File:MKT Icon SuperGliderLimeGreen.png|50px]]<br>[[Super Glider]] | *5 *8 *12 |[[New York Tour]] (source: Do Jump Boosts article) and this is how it would look with a transclusion mechanism in place: <onlyinclude>{{#ifeq:{{{transcludesection|Do Jump Boosts New York Minute}}}|Do Jump Boosts New York Minute|
{{!}}-
{{!}}[[File:MKT Tour1 YoshiCupChallenge.png|200px]]
{{!}}
{{#ifeq:{{PAGENAME}}|Do Jump Boosts|[[New York Minute]]|Regular}}
{{!}}[[File:MKT Icon Yoshi.png|50px]]<br>[[Yoshi]]
{{!}}[[File:MKT Icon PipeFrameLimeGreen.png|50px]]<br>[[Pipe Frame]]
{{!}}[[File:MKT Icon SuperGliderLimeGreen.png|50px]]<br>[[Super Glider]]
{{!}}
*5
*8
*12
{{!}}[[New York Tour]]}}</onlyinclude>
A bit ugly, innit? On average, this would only save a small number of bytes on the target article--less than 100, really. Picture, now, an entire table with the same code plastered repeatedly. I believe the wiki should account for editor friendliness too, especially when the returns of optimisation are disappointing. I am not sure how to proceed here. I am unwilling to go ahead with either option unless I have a clear-cut vision of each one's net advantages. I will thus be resorting to the community's choice. Proposer: Koopa con Carne (talk) Copy-paste table sectionsTransclude sections
Leave as is (bonus challenges will continue to be listed in image galleries)
CommentsMario Kart Tour's tables tend to be pretty sloppy overall (no offense but this ranked cup table is rather monstrous though other tables don't fare much better) though I'm not really understanding this proposal. Probably repetitive content? Maybe the table format just isn't suitable for this sort of thing?
|
