Super Mario Wiki

MarioWiki:Proposals: Difference between revisions

Project page Discussion
 
Line 1: Line 1:
<table style="background:#fefffe;color:black;-moz-border-radius:8px;border:2px solid black;padding:4px" width=100%><tr><td>
{{/Header}}
<div class="proposal">
<center>http://img33.picoodle.com/img/img33/9/9/17/f_propcopym_9045f2d.png</center>
<br clear="all">
{| align="center" style="width: 85%; background-color: #f1f1de; border: 2px solid #996; padding: 5px; color:black"
|'''Proposals''' can be new features (such as an extension), removal of a previously added feature that has tired out, or new policies that must be approved via [[Wikipedia:Wikipedia:Consensus|consensus]] before any action(s) are done.
*Any user can support or oppose, but must have a strong reason for doing so, not, e.g., "I like this idea!"
*"Vote" periods last for one week.
*All past proposals are [[/Archive|archived]].
|}
A proposal section works like a discussion page: comments are brought up and replied to using indents (colons, such as : or ::::) and all edits are signed using the code <nowiki>{{user|</nowiki>''User name''<nowiki>}}</nowiki>. '''Signing with the signature code <nowiki>~~~(~)</nowiki> is not allowed''' due to technical issues.


<h2 style="color:black">How To</h2>
==Writing guidelines==
#Actions that users feel are appropriate to have community approval first can be added by anyone, but they must have a strong argument.
===Change how "infinitely respawning" enemies are counted in level enemy tables===<-Requesting cancelling
#Users then vote and discuss on the issue during that week. The "deadline" for the proposal is one week from posting at:
Currently, the wiki lists enemy counts for each level in tables located in that level's article. This is all well and good, but the problem arises when infinitely respawning ones (like piped ones) are included. As seen [[World 6-B (New Super Mario Bros.)|here]], this is awkwardly written as
##Monday to Thursday: 17:00 (5pm)
*"[number] (not including the infinite [enemy] spawning from [number] [method]),"
##Friday and Saturday: 20:00 (8pm)
and why shouldn't it include them? That method of writing is ungainly, misleading, and bloats the table's width unnecessarily. Therefore, I propose the alternate writing of
##Sunday: 15:00 (3pm)
*"[number] + (∞ x [number]),"
#Every vote should have a reason accompanying it.
with the "x [number]" and parentheses being removed if there is only one case. So in the linked example, it would be "6 + ∞," which says the same thing without contradicting itself with a lengthy diatribe.
#At any time a vote may be rejected if at least '''three''' active users believe the vote truly has no merit or was cast in bad faith. However, there must be strong reasons supporting the invalidation.
<br>(Also I had to restrain myself from using * rather than x because that's how I'm used to writing multiplication in equations. Thanks, higher-level math classes defaulting to "X" as a variable! But the asterisk could be used too, anyway.)
#"<nowiki>#&nbsp;</nowiki>" should be added under the last vote of each support/oppose section to show another blank line.
#Any proposal that has three votes or less at deadline will automatically be listed as "[[Wikipedia:Quorum|NO QUORUM]]." The original proposer then has the option to relist said proposal to generate more discussion.
#All proposals are archived. The original proposer must '''''take action''''' accordingly if the outcome of the proposal dictates it. If it requires the help of a sysop, the proposer can ask for that help.


The times are in EDT, and are set so that the user is more likely to be online at those times (after school, weekend nights).
'''Proposer''': {{User|Doc von Schmeltwick}}<br>
 
'''Deadline''': September 30, 2024, 23:59 GMT
So for example, if a proposal is added on Saturday night at 11:59 PM EDT, the deadline is the next Saturday night at 8:00 PM. If it is indeed a minute later, the deadline is a day plus 15 hours (Sunday), as opposed to a day minus 4 hours.
 
Also,
<br><span style="font-family:sans-serif;font-size:30px;line-height:30px;font-weight:900;">NO PROPOSALS ABOUT HAVING BANJO AND CONKER ARTICLES</span> -The Management.
 
__TOC__
 
<center><span style="font-size:200%">CURRENTLY: '''{{LOCALTIME}}, {{LOCALDAY}} {{LOCALMONTHNAME}} {{LOCALYEAR}} (EDT)'''</span></center>
 
==New Features==
''None at the moment.
 
==Removals==
''None at the moment.
 
==Splits & Merges==
===Repeated Info, Pointless Pages?===
 
If you look at the [[Final Smash]] page, you'll see that each one is listed in a table, along with a fairly large amount of info about it. Each one has a link to the page that is specifically about that particular Final Smash (e.g. the Aura Storm has its own page, etc). I've read these individual separate pages, and their info is practically the same as what it says on the main Final Smash page. So, are these small pages kind of pointless? In fact, some of the descriptions on the FS page are more detailed than on the page they link to, as they contain info about damage percentages and stuff.
 
I think either one of these options should be considered: We either remove all the individual FS pages (as in [[End of Day]], [[Mario Finale]], etc) and make the info in the table of Final Smash page more detailed...
 
OR we only include very small amounts of info on the main Final Smash page, so that it's actually worth having the linked pages.
 
'''Proposer''': [[User:Dom|Dom]]
 
'''Deadline''': July 13, 2008, 15:00


====Support====
====Support====
#{{User|Dom}} - I'm thinking my second option is the better one, after reading Pokemon DP's comment. In other words, I'm kind of supporting myself.
#{{User|Doc von Schmeltwick}} - Per
#{{User|Freekhenstra}} - See my comment
#{{User|Altendo}} - This doesn't sound like a bad idea, although I do think there should be an asterisk like "*" instead which leads to a note saying "not including the infinite [enemy] spawning from [number] [method]", as enemies can spawn in different ways, and showing how they spawn could still be useful. If we just show "∞ x [number]", it wouldn't show how Goombas are spawned in (the linked page doesn't specify how they are spawned in otherwise). But I do like the idea of shortening the "count" section of tables.
#{{User|MegaMario9910}} - Per Dom and Freekhenstra
<s>#{{User|ThePowerPlayer}} Per Altendo. This formatting is much better, but I also think some note of where the infinite enemy spawner(s) originate from should be preserved.</s><br>
#{{User|Pikax}} - Per Freekhenstra
<s>#{{User|Super Mario RPG}} Per all.</s>
#{{User|Tucayo}} - I support the idea of erasing the individula pages, it's better to have them in a unique, more complete page
#{{User|Glitchman}} - See my comment below.
#{{User|ItameMarioFan}} - Yes. The pages have the same description as on the [[Final Smash]] page. Only thing new is the throphies. Per Dom and Glitchman (comment below).
#{{user|Luigi001}} Per Dom and Pokemon DP. Expanding the individual pages would make much more sense than getting rid of them all.
#{{User|Walkazo}} - I guess something's better than nothing.
#{{user|Toadette 4evur}} Per DP.
#{{user|Yowuza}} Yeah, this isn't the SmashWiki, this is the Super Mario Wiki.
#{{user|Sonic64}} Per DP
#{{User:Luigi3000/sig}}Per 4Evar


====Oppose====
====Oppose====
#{{User|Hewer}} I don't see the benefit of changing this. The current wording is straightforward and succinct, I'd expect the reader to understand "6 (not including the infinite Goombas spawning from one Warp Pipe)" easily. Changing it to "6 + ∞" just makes it less clear for no reason, I'd definitely be confused if I saw that and didn't know this specific context. The fact that the other support votes have also brought up how doing this risks losing the specific information completely (and suggested a more long-winded solution that seems to contradict the proposal) compels me to oppose this more.
#{{User|Waluigi Time}} Per Hewer.
#{{User|FanOfYoshi}} Per all.
#{{User|Axii}} Per Hewer
#{{User|SolemnStormcloud}} Per all.
#{{User|EvieMaybe}} we don't need to throw a mathematical equation at people
#{{User|Sparks}} Per all.
#{{User|ThePowerPlayer}} I realized that this only makes sense if you have it explained to you like in the proposal description, which defeats the purpose.
#{{User|Arend}} I feel that "[number] (+ [number] infinite spawn points)" would be less awkward to write than what we currently do ''and'' more understandable fir most people than what is proposed here
#{{User|Killer Moth}} Per all.


====Comments====
{{@|Hewer}} - "succinct" would generally imply "short, sweet, and to-the-point," of which the current method is the exact opposite. I'm fine with including an asterisk-note next to the infinity, but the current one is much too bloated, outright admits to stating false information, and since the tables are center-aligned with that horizontal-bloat, it makes it look incredibly awkward. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 12:41, September 17, 2024 (EDT)
:I guess we just have totally opposing opinions on this one, because I don't personally find ten words of explanation to be "much too bloated", would rather "state false information" (not really what's happening because it's immediately clarified and the only way not to state any "false" info would be to just put "∞" which helps no one) than obscure the meaning of what we're trying to say, and I don't at all think the somewhat wider tables look "incredibly awkward". This is a case where I feel giving more explanation than "6 + ∞" is necessary for the sake of conveying clear information, so I'd rather prioritise that over having a thin table (which I still don't really see why that's so desirable). {{User:Hewer/sig}} 03:19, September 18, 2024 (EDT)


====Comments====
If this proposal passes, I think that a dedicated template should be made; something like <code><nowiki>{{infinite respawn|5|3}}</nowiki></code> that would produce "{{hover|5 + (∞ × 3)|5 (not including the 3 infinite spawning points)}}". Or at the very least, use an actual "×" symbol rather than "x". {{User:Jdtendo/sig}} 12:08, September 19, 2024 (EDT)
If the moves have articles, Final Smashes should have them too. The Final Smash article has too many details, Aura Storm for example. It can be shortened to just: "Lucario jumps high above the stage, then fires a beam of Aura, that the player can guide across the stage to devastate his opponents". The Final Smash article should have descriptions like that, while the article of the Final Smash itself could have the details. {{User|Freekhenstra}}
:I dislike the idea of hiding details in easily missable hover text and don't really see the benefit of using it. It just makes it more convoluted. {{User:Hewer/sig}} 11:12, September 20, 2024 (EDT)
:That sounds good in theory, but I'm going to respectfully disagree. While the idea of getting rid of information on the main page to make all of the pages incomplete would definitely lead to more proposals down the road, I do agree that we should get rid of all the off-shoot pages and have all of the final smashes on one big, complete page. Each of the final smashes would just have to redirect to that page. {{User|Glitchman}}


Uhh, I don't get what the proposal is saying, what are we supporting? I'm confused. {{User|Toadette 4evur}}
I'll refrain from voting because I have a visceral reaction to anything that resembles a math formula, and I want as little as possible for personal preference to seep into my vote. That's not to say I don't understand what's being proposed, in fact it makes perfect sense if you're aiming strictly for concision, but you'd need to take into account how accessibly that information is communicated--you'd need to establish that "infinity symbol" stands for infinite enemy spawning point, which is not immediately clear. At that point, you'd go for a relatively lengthy explanation nonetheless. Though, I agree that the phrasing in that page you linked doesn't sound inclusive. I think something like "5 individual, 3 infinite spawning points" works better if we're going down this path.<br>If the proposal passes, I'd like to see it implemented in the manner Jdtendo suggests above.<br>EDIT: I'm aware there's [[Mario Kart Tour race points system#Bonus-points boost|already plenty of math on this wiki that has potential to confound people]], but in that case, not only is its succinctness a better way to explain how the game's scoring system works (as opposed to paragraphs-long descriptions), but it's taken straight out of the game as well. I'd say, use math formulas only when you're sure prose would be of less service to its intended audience: people looking up how many enemies are in a level aren't necessarily interested in complex gameplay dynamics. {{User:Koopa con Carne/Sig}} 13:12, September 19, 2024 (EDT), edited 14:55, September 19, 2024 (EDT)
:Same, it's not really clear whether we're deleting the list or the articles, as it is now, "Support" is just saying we do ''something''. Anyway, I support Glitchman's idea, for all the reasons listed above as well as the fact that the Final Smash articles could be turned into redirects, wheras the list would be harder to deal with. However, if memory serves, a similar proposal was shot down a couple months/weeks ago, on the basis of Freekhanstr'a point that moves have articles too, and they're more minor than FSs. I say the moves ''and'' the Final Smashes should be nixed, though sadly I don't think that will fly. - {{User|Walkazo}}


I actually have to say, asking for all the respective pages to be deleted was the dumbest thing I ever heard. If we do that, we might as well delete all the special move articles, which would be of less importance than the Final Smashes. Regardless, I agree that the information on the Final Smash article is overboard. But do not touch the individual articles; ONLY the Final Smash article. {{User|Pokemon DP}}
I'd personally prefer if this was notated with ω instead of ∞, something like "{{hover|3ω+5|3 infinite spawn points and 5 others}}", but that would probably be too confusing to anyone not already familiar with transfinite ordinal notation. {{User:JanMisali/sig}} 10:01, September 21, 2024 (EDT)
:This should be written "ω⋅3+5" because 3⋅ω = ω; {{wp|Ordinal arithmetic#Multiplication|multiplication on transfinite ordinal numbers}} is not commutative. {{User:Jdtendo/sig}} 12:40, September 21, 2024 (EDT)


'''Note to Toadette 4evur:''' I guess the support means that you agree that some information should be moved/merged to or from the main FS page and the individual pages. That sounds a bit vague, I know. {{User|Dom}}
Maybe just have a table for finite enemies and a table for infinite enemies? There's horizontal space for both. [[User:Salmancer|Salmancer]] ([[User talk:Salmancer|talk]]) 11:33, September 21, 2024 (EDT)
:That just needlessly splits information, which I again don't see the benefit of (and I still don't really see how there's a problem here that needs fixing anyway). {{User:Hewer/sig}} 21:26, September 21, 2024 (EDT)


'''Note to Pokemon DP:''' I hope you weren't calling ''me'' dumb...  I'll admit it would be a bit harsh to delete all those articles, but that's why I mentioned 2 options. And I'm leaning towards the second one, the one you agreed was more appropriate. {{User|Dom}}
===Figure out how to handle <nowiki>{{classic}} and {{classic-link}}</nowiki> templates when discussing ''Mario Kart Tour'' classic courses===
This wiki has two templates used to format classic courses in the ''Mario Kart'' series: <nowiki>{{classic}} and {{classic-link}}</nowiki>. These templates convert text like "3DS Shy Guy Bazaar" into a format that closer resembles the one seen in games, with the prefix being written as such, a prefix, and not part of the courses name. So "3DS Shy Guy Bazaar" becomes "{{classic|3DS|Shy Guy Bazaar}}". However, there's an exception this wiki seems to have regarding this template: classic courses in ''[[Mario Kart Tour]]''.


But even considering to delete those articles as an option wasn't very wise... Well, whatever. I'm still all for shortening the (supposedly) brief descriptions on the Final Smash article. {{User|Pokemon DP}}
This is because the game does not structure the title of courses in such a way: instead it writes the prefix as large as the rest of the name, so it's written as "3DS Shy Guy Bazaar". However, I feel this creates a lot of inconsistency and confusion here on this wiki. For example, the page for a course like [[3DS Rock Rock Mountain]], a course featured as a classic in and out of ''Tour'' structures fellow course names both ways, with and without the template, simply because of the game the classic course appears in. To make things more confusing, when a ''Tour'' section on a course's page discusses classic courses outside of ''Tour'', it uses the template, as seen in a few course pages. Additionally, page titles for courses that are only classics in ''Tour'' still use a smaller font for the page name, such as [[GBA Lakeside Park]]. Finally, some courses in ''Tour'' don't even adhere to this rule that has been enforced before, such as [[Wii Maple Treeway]].
:What option do you vote for when supporting? I am for individual articles and less information on the Final Smash page. - {{User|Cobold}} 10:41, 7 July 2008 (EDT)


'''Note to Cobold:''' - Since my comments to 2 other users, I guess I've kind of confirmed that the Support means what you agreed to - less info on Final Smash page. {{User|Dom}}
(I cannot find the edit log, however I was informed by a moderator here that it is a rule that is enforced a while back)


===Paper Luigi===
So this proposal is asking for one thing: an enforcement to be decided on.


It is pretty hard to find all of the data from luigi's quest from The thousand year door, on this wiki. So I propose that we merge all the articles that have to do with luigi's quest in the waffle kingdom, into one single article. that way, if someone needs to look it up, they can easily find it.
The options are simple:
(I know that this is a pretty short proposal)
*Use the templates for all references to classic courses.
*Not use the template when referring to classic courses in ''Tour''.


'''Proposer''': [[User:Dryest bowser|Dryest bowser]]
RMX courses will not be affected by this since the "RMX" is established to be part of the course's name.


'''Deadline''': July 17, 2008, 17:00
'''Proposer''': {{User|YoYo}}<br>
'''Deadline''': October 2, 2024, 23:59 GMT


====Support====
====Use the templates for all classic course links====
#[[User:Dryest bowser|Dryest bowser]]- per myself
#{{User|YoYo}} per my proposal, I think that the template formats them in a way that distinguishes the prefix from course name, and I think consistency is important here.


====Oppose====
====Do not use the templates for ''Mario Kart Tour'' classic course links====
#{{User|Walkazo}} - See below.
#{{User|Pokemon DP}} - I couldn't - And still cannot - make any sense out of what Dryest Bowser hopes to accomplish. So... Per Walkazo.


====Comments====
====Comments====
I don't get this Proposal at all. {{User|Pokemon DP}}


Neither do I. I dont think weshould do it cus it is fine as is.{{User|Luigi3000}}
==New features==
''None at the moment.''


{{User|Dryest bowser}} I just want to make a single article for luigi's story in paper mario the thousand year door. it will make the wiki more organized. and we can stop having extremly short articless for all of the ccharacters and places
==Removals==
:As in [[Super Luigi Series|this]]? If not, kindly provide a link to the pages you '''are''' talking about. - {{User|Walkazo}}
''None at the moment.''


{{User|Dryest bowser}} I mean articles like [[jerry]],[[Hizza]] and [[torque]]. these articles are kind of minor,and It would be easier to merge them
==Changes==
:They're characters, and all characters get their own articles unless they're carbon copies of each other like the [[Board (Super Mario Galaxy)|Board]]s, or if they're always found together and do nothing significant individually, like [[Ashley and Red]] and [[Kat and Ana]]. The only one you can argue over is Hizza, since his article's a stub; and because he wasn't encountered by the player, meaning he could be considered an implied character and can therefore be relegated to the [[List of Implied Characters]], or converted into a redirect to [[Plumpbelly Village]]. However, neither of those options is what you want for this proposal; what you're asking just isn't feasible, sorry. - {{User|Walkazo}}
=== Add film and television ratings to [[Template:Ratings]] ===
Regarding ratings on the games we cover on this wiki, it's usually done very well and even shows off obscure rating companies hardly anyone talks about. It's educational and shows how the world rates a Super Mario game. However, when it comes to television shows and movies, they do not get the same treatment. Television shows ''don't even have ratings in their infobox.'' And while the movies do, they not only list ''just'' the MPAA, which for people who live in the United Kingdom or other countries, is '''not''' representative of the majority of the world, it's ''just'' the text, "PG". Sure, most people know it means "Parental Guidance," but imagine if we included more ratings. It's not super easy to find ratings for films and television shows in general, other than IMDB and there are no sources for proof of these ratings. When it comes to the Canadian Home Video Rating System, I can hardly find what rating was applied to that particular movie/TV show and I remember not being lucky for searching any other ratings for other movies (personal experience, but I remember searching on one of these websites and the site was rather buggy or didn't have the film/show in question).


[[user:Dryest bowser|Dryest bowser]]- ok, that's ok, let's do that, all the characters like hizza,crepe, and even princess eclair should be merged with the implied characters
The better solution is to '''add film and television ratings to the [[Template:Ratings|rating template]] so we can provide a wide variety of ratings for movies and television shows.''' In this case, users from around the world can view how movies are rated in almost every country. As for what ratings we add, it's a bit tricky. Because there is a lot, I would need some help here. Regardless, I got some EFIGS ratings in question. If you have more ratings, please let me know and I'll add it to the proposal These are split up into film and television.


==Changes==
<div id=fh4 class=mw-headline> Film </div>
===Fire and Ice Templates===
*[[Wikipedia:Motion Picture Association film rating system|Motion Picture Association film rating system (MPAA)]]
As I said on the [[Template_talk:Fire|Fire talk page]], too many things use fire (or ice) for these templates to be practical. Instead, I propose we alter these templates so that they only include things made of, or irrefutably linked to fire/ice. This is a better design because readers could then research creatures of fire or ice with as much ease as if they were using the [[Template:Birds|Bird]] or [[Template:Fish|Fish]] Templates to research those kinds of beings, instead of getting bogged down with species that only use fire or ice. For example, if someone wants to research Birds, anything else in the Bird Template that flies but isn't a bird would slow them down; however a misfile like this would be obvious as a bird is a clearly defined animal, while what can be considered appropriately placed under "Fire" and "Ice" is much more subjective. As such, I'm open to suggestions on what should or shouldn't be removed, my first attempt (complete with justifications for my choices) can be seen alongside the original templates [[User:Walkazo/Templates|here]]; as are newer split-template versions of Fire and Ice suggested by [[User:Soler|Soler]] below, which are now the designs I plan to put into effect if this proposal passes.
*[[Wikipedia:British Board of Film Classification|British Board of Film Classification (BBFC)]]
*[[Wikipedia:Freiwillige Selbstkontrolle der Filmwirtschaft|Freiwillige Selbstkontrolle der Filmwirtschaft (FSK)]]
*[[Wikipedia:Canadian Home Video Rating System|Canadian Home Video Rating System]] (It can also apply to DVDs of TV shows as well.)
 
<div id=fh4 class=mw-headline> Television </div>
*[[Wikipedia:TV Parental Guidelines|TV Parental Guidelines]]


'''Proposer''':[[User:Walkazo|Walkazo]]
My list so far is not comprehensive, but my idea is to add these ratings (and potentially others) to the template and make the infoboxes look much prettier and more visually educational. I have nothing else to say, so that's about it.


'''Deadline''': July 9, 2008, 17:00
'''Proposer''': {{User|TheUndescribableGhost}}<br>
'''Deadline''': October 1, 2024, 23:59 GMT


====Support====
====Support====
#{{User|Walkazo}} - My reasons above.
#{{User|TheUndescribableGhost}} Rated PR for per proposal.
#{{User|Pikax}} - I have seen what Walkazo plans to separate from the templates and why she wants to separate those things, and I have no objections to her plan.
#{{User|Technetium}} Never noticed ratings were missing from TV and movie coverage until now. It feels obvious ratings should be included like they are with games. Per proposal.
#{{User|Dryest bowser}}-per all
#{{User|FanOfRosalina2007}} This is something I never noticed, but I completely agree. I'm happy that there are observant people in this world! Per proposal.
#{{User|The Writing Guy}} - Per Walkazo.
#{{User|Arend}} Per all (fun fact: the Dutch rating system for movies and television, Kijkwijzer, is being utilized by {{wp|Netherlands Institute for the Classification of Audiovisual Media|NICAM}}, which happens to ''also'' rate games in Europe using PEGI. In fact, PEGI's ratings appear to be based on those of Kijkwijzer)
#{{user|ParaBob-omb}}- Per all.
#{{User|ThePowerPlayer}} Per all.
#{{User|Dom}} - Per the above users who are crushing my writing here with their heavy words. I say Soler's comment below which includes his 2 split templates is a perfect solution, that should be used instead of what currently exists.
#{{User|Nintendo101}} Per proposal.
#{{User|MegaMario9910}} - Per Walkazo and Soler's comment.
#{{User|Sparks}} Per all.
#{{User|Mrsdaisyluigi}} - Per all
#{{User|Mari0fan100}} Per all, especially since movies like ''The Super Mario Bros. Movie'' have classification ratings.
# {{User|Tucayo}} - Per Walkazo. They should be separated, its OK for characters like [[bowser]] to be removed, because the fact they spit fire doesnt make him a fire creature.
# {{User|Stooben Rooben}} - Per Walkazo, the Proposal-Genius. 23:18, 4 July 2008 (EDT)
#{{User|Soler}}: per all.
#{{User|Pokemon DP}} Per Walkazo.


====Oppose====
====Oppose====


====Comments====
====Comments====
 
Wait, couldn't this just be a talk page proposal on the template itself? It would affect many pages, yes, but this is specifically about editing a template… I'm honestly not so sure. [[User:Technetium|Technetium]] ([[User talk:Technetium|talk]]) 15:52, September 24, 2024 (EDT)
How about something like this for the Fire template, and something similar for the Ice? I tried to simulate Walkazo's formatting as best as I could: feel free to fix the formatting. I feel that this would serve both people with Walkazo's view of the term and those with a broader view of it. If the show/hide feature is unnecessary, please remove it. Another option would be to split the templates in two. —{{User|Soler}}. (I am going on holidays on Sunday, so please excuse me if I do not reply to your unrelenting criticism...)   
 
 
{| align="center" width=100% class="toccolours" cellspacing="0" cellpadding="2"
|-
| align=center bgcolor=orange style="border: 1px solid white"|<div style="background:#orange; text-align=center;">'''Fire Creatures'''<showhide><small>__HIDER__</small><hide><div>
{| width=100%
| align="center" style="font-size: smaller; background:ghostwhite" | [[Angry Sun]] | [[Blargg]] | [[Bomb (species)|Bomb]] | [[Burn Bit]] | [[Czar Dragon]] | [[Ember]] | [[Fiery Bubble]] | [[Fire Chomp]] | [[Fire Elemental Ghost]] | [[Fire Snake]] | [[Fireball (enemy)|Fireball]] | [[Fryguy]] | [[Fryguy (species)|Fryguys]] | [[Helio]] | [[Hot Foot]] | [[Hot Lips]] | [[Hothead]] | [[Kleever]] | [[Lava Bubble]] | [[Lava Bud]] | [[Lava Drop]] | [[Lava Ghost]] | [[Lava Piranha]] | [[Li'l Sparky]] | [[Mini Fryguy]] | [[Petit Piranha]] | [[Phantom Ember]] | [[Podoboo]] | [[Pyro Guy]] | [[Pyrosphere]] | [[Sparky]] | [[Sun (character)|Sun]] | [[Torcher]] | [[Trouble Bug]]
|}</div></hide></showhide></div>
|-
| align=center bgcolor=orange style="border: 1px solid white"|<div style="background:orange; text-align=center; color:black">'''Fire-Related Creatures'''<showhide><small>__HIDER__</small><hide><div>
{|
| align="center" style="font-size: smaller; background:ghostwhite" | [[Baby Bowser]] | [[Birdo]] | [[Bowser]] | [[Bowser Jr.]] | [[Calm Volcano Plant]] | [[Dhalsim]] | [[Dino-Torch]] | [[Fire Bro.]] | [[Flare]] | [[Gao]] | [[Iggy Koopa]] | [[Jumping Piranha Plant]] | [[King Totomesu]] | [[Lava Lotus]] | [[Ludwig von Koopa]] | [[Sumo Bro.]] |  [[Tryclyde]] | [[Venus Fire Trap]] | [[Vivian]] | [[Volcano Lotus]] | [[Zeus Guy (Bandit)]] | [[Zeus Guy (Snifit)]]
|}</div></hide></showhide></div>
|}
 
{{User|Dom}} - Hey, the User called ''Soler'' made these templates about fire! Get it? Solar...fire? Ha ha...........???
 
On a serious note: Soler's split templates are a brilliant idea, better than the all-in-one oversized template.
:Yeah, I definately like that idea, too!  Awesome work, Soler! {{User|Stumpers}}
::Oh, thanks! Does anyone think that two Ice and two Fire templates would be better than the above idea of a "double template"? (I myself think that the double one would be easier for navigation.) —{{User|Soler}}.
:::I prefer the double one, and I've taken your example and refined new split-templates for both Fire and Ice which I've put up [[User:Walkazo/Templates|here]] with the earlier versions. As I said in the added last line of the Proposal, I'd rather go with them than my earler attempts. Nice going! - {{User|Walkazo}}


==Miscellaneous==
==Miscellaneous==
''None at the moment.
''None at the moment.''

Latest revision as of 14:27, September 25, 2024

Image used as a banner for the Proposals page
Current time:
Wednesday, September 25th, 21:05 GMT
Proposals can be new features, the removal of previously-added features that have tired out, or new policies that must be approved via consensus before any action is taken.
  • "Vote" periods last for one week.
  • Any user can support or oppose, but must have a strong reason for doing so (not, e.g., "I like this idea!").
  • All proposals must be approved by a majority of voters, including proposals with more than two options.
  • For past proposals, see the proposal archive and the talk page proposal archive.

A proposal section works like a discussion page: comments are brought up and replied to using indents (colons, such as : or ::::) and all edits are signed using the code {{User|User name}}.

How to

Rules

  1. If users have an idea about improving the wiki or managing its community, but feel that they need community approval before acting upon that idea, they may make a proposal about it. They must have a strong argument supporting their idea and be willing to discuss it in detail with the other users, who will then vote about whether or not they think the idea should be used. Proposals should include links to all relevant pages and writing guidelines. Proposals must include a link to the draft page. Any pages that would be largely affected by the proposal should be marked with {{proposal notice}}.
  2. Only registered, autoconfirmed users can create, comment in, or vote on proposals and talk page proposals. Users may vote for more than one option, but they may not vote for every option available.
  3. Proposals end at the end of the day (23:59) one week after voting starts, except for writing guidelines and talk page proposals, which run for two weeks (all times GMT).
    • For example, if a proposal is added at any time on Monday, August 1, 2011, the voting starts immediately and the deadline is one week later on Monday, August 8, at 23:59 GMT.
  4. Every vote should have a strong, sensible reason accompanying it. Agreeing with a previously mentioned reason given by another user is accepted (including "per" votes), but tangential comments, heavy sarcasm, and other misleading or irrelevant quips are just as invalid as providing no reason at all.
  5. Users who feel that certain votes were cast in bad faith or which truly have no merit can address the votes in the comments section. Users can ask a voter to clarify their position, point out mistakes or flaws in their arguments, or call for the outright removal of the vote if it lacks sufficient reasoning. Users may not remove or alter the content of anyone else's votes. Voters can remove or rewrite their own vote(s) at any time, but the final decision to remove another user's vote lies solely with the administrators.
    • Users can also use the comments section to bring up any concerns or mistakes in regards to the proposal itself. In such cases, it's important the proposer addresses any concerns raised as soon as possible. Even if the supporting side might be winning by a wide margin, that should be no reason for such questions to be left unanswered. They may point out any missing details that might have been overlooked by the proposer, so it's a good idea as the proposer to check them frequently to achieve the most accurate outcome possible.
  6. If a user makes a vote and is subsequently blocked for any amount of time, their vote is removed. However, if the block ends before the proposal ends, then the user in question holds the right to re-cast their vote. If a proposer is blocked, their vote is removed and "(banned)" is added next to their name in the "Proposer:" line of the proposal, which runs until its deadline as normal. If the proposal passes, it falls to the supporters of the idea to enact any changes in a timely manner.
  7. No proposal can overturn the decision of a previous proposal that is less than 4 weeks (28 days) old.
  8. Any proposal where none of the options have at least four votes will be extended for another week. If after three extensions, no options have at least four votes, the proposal will be listed as "NO QUORUM." The original proposer then has the option to relist said proposal to generate more discussion.
  9. If a proposal reaches its deadline and there is a tie for first place, then the proposal is extended for another week.
  10. If a proposal reaches its deadline and the first place option is ahead of the second place option by three or more votes, then the first place option must have over 50% support to win. If the margin is only one or two votes, then the first place option must have at least 60% support to win. If the required support threshold is not met, then the proposal is extended for another week.
    • Use the {{proposal check}} tool to automate this calculation; see the template page for usage instructions and examples.
  11. Proposals can only be extended up to three times. If a consensus has not been reached by the fourth deadline, then the proposal fails and can only be re-proposed after four weeks (at the earliest).
  12. All proposals are archived. The original proposer must take action accordingly if the outcome of the proposal dictates it. If it requires the help of an administrator, the proposer can ask for that help.
  13. If the administrators deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to remove it at any time.
  14. Proposals can only be rewritten or canceled by their proposer within the first three days of their creation (six days for writing guidelines and talk page proposals). However, proposers can request that their proposal be canceled by an administrator at any time, provided they have a valid reason for it. Please note that canceled proposals must also be archived.
  15. Unless there is major disagreement about whether certain content should be included, there should not be proposals about creating, expanding, rewriting, or otherwise fixing up pages. To organize efforts about improving articles on neglected or completely missing subjects, try setting up a collaboration thread on the forums.
  16. Proposals cannot be made about promotions and demotions. Users can only be promoted and demoted by the will of the administration.
  17. No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
  18. Proposals must have a status quo option (e.g. Oppose, Do nothing) unless the status quo itself violates policy.

Basic proposal and support/oppose format

This is an example of what your proposal must look like, if you want it to be acknowledged. If you are inexperienced or unsure how to set up this format, simply copy the following and paste it into the fitting section. Then replace the [subject] - variables with information to customize your proposal, so it says what you wish. If you insert the information, be sure to replace the whole variable including the squared brackets, so "[insert info here]" becomes "This is the inserted information", not "[This is the inserted information]". Proposals presenting multiple alternative courses of action can have more than two voting options, but what each voting section is supporting must be clearly defined. Such options should also be kept to a minimum, and if something comes up in the comments, the proposal can be amended as necessary.

===[insert a title for your proposal here]===
[describe what issue this proposal is about and what changes you think should be made to improve how the wiki handles that issue]

'''Proposer''': {{User|[enter your username here]}}<br>
'''Deadline''': [insert a deadline here, 7 days after the proposal was created (14 for writing guidelines and talk page proposals), at 23:59 GMT, in the format: "September 25, 2024, 23:59 GMT"]

====Support====
#{{User|[enter your username here]}} [make a statement indicating that you support your proposal]

====Oppose====

====Comments====

Users will now be able to vote on your proposal, until the set deadline is reached. Remember, you are a user as well, so you can vote on your own proposal just like the others.

To support, or oppose, just insert "#{{User|[add your username here]}}" at the bottom of the section of your choice. Just don't forget to add a valid reason for your vote behind that tag if you are voting on another user's proposal. If you are voting on your own proposal, you can just say "Per my proposal".

Talk page proposals

Proposals concerning a single page or a limited group of pages are held on the most relevant talk page regarding the matter. Proposals dealing with a large amount of splits, merges, or deletions across the wiki should still be held on this page.

For a list of all settled talk page proposals, see MarioWiki:Proposals/TPP archive and Category:Settled talk page proposals.

Rules

  1. All active talk page proposals must be listed below in chronological order (new proposals go at the bottom) using {{TPP discuss}}. Include a brief description of the proposal while also mentioning any pages affected by it, a link to the talk page housing the discussion, and the deadline. If the proposal involves a page that is not yet made, use {{fake link}} to communicate its title in the description. Linking to pages not directly involved in the talk page proposal is not recommended, as it clutters the list with unnecessary links. Place {{TPP}} under the section's header, and once the proposal is over, replace the template with {{settled TPP}}.
  2. All rules for talk page proposals are the same as mainspace proposals (see the "How to" section above), with the exceptions made by Rules 3 and 4 as follows:
  3. Voting in talk page proposals will be open for two weeks, not one (all times GMT).
    • For example, if a proposal is added at any time on Monday, August 1, 2011, it ends two weeks later on Monday, August 15, 2011, at 23:59 GMT.
  4. The talk page proposal must pertain to the subject page of the talk page it is posted on.
  5. When a talk page proposal passes, it should be removed from this list and included in the list under the "Unimplemented proposals" section until the proposed changes have been enacted.

List of ongoing talk page proposals

  • Consider the "Blurp" and "Deep Cheep" in the Super Mario Maker games an alternate design of Cheep Cheep with the former twos' designs as a cameo rather than a full appearance of the former two, in line with the game's own classification (discuss) Deadline: September 25, 2024, 23:59 GMT
  • Add English to {{foreign names}} and retitle to {{international names}} (discuss) Deadline: September 26, 2024, 23:59 GMT
  • Allow usage of {{Release}} as a generic "flag list" template (discuss) Deadline: September 27, 2024, 23:59 GMT
  • Prune "sports" games from Black Shy Guy in line with White Shy Guy and Red Boo (discuss) Deadline: September 28, 2024, 23:59 GMT
  • Merge Preying Mantas with Jellyfish (discuss) Deadline: September 28, 2024, 23:59 GMT
  • Create article(s) for the SM64DS character rooms (discuss) Deadline: September 30, 2024, 23:59 GMT
  • Create an article for the Peach doll from Super Mario RPG: Legend of the Seven Stars (discuss) Deadline: September 30, 2024, 23:59 GMT
  • Remove the remaining non-Super Mario "stage gimmicks and hazards" from Super Smash Bros. (discuss) Deadline: October 1, 2024, 23:59 GMT
  • Remove non-Super Mario "stage cameos" from Super Smash Bros. (discuss) Deadline: October 1, 2024, 23:59 GMT
  • Rename {{Manga infobox}} to {{Publication infobox}} (discuss) Deadline: October 4, 2024, 23:59 GMT
  • Merge Play Nintendo secret message puzzles (discuss) Deadline: October 4, 2024, 23:59 GMT
  • Merge categories for Donkey Kong Country remakes with their base game's categories (discuss) Deadline: October 5, 2024, 23:59 GMT
  • Refer to "King Bill" as "Bull's-Eye Banzai" for coverage in New Super Mario Bros. Wii (discuss) Deadline: October 6, 2024, 23:59 GMT
  • Rename Perfect Edition of the Great Mario Character Encyclopedia to Perfect Ban Mario Character Daijiten (discuss) Deadline: October 7, 2024, 23:59 GMT

Unimplemented proposals

Proposals

Establish a standard for long course listings in articles for characters/enemies/items/etc., Koopa con Carne (ended June 8, 2023)
Break alphabetical order in enemy lists to list enemy variants below their base form, EvieMaybe (ended May 21, 2024)
Standardize sectioning for Super Mario series game articles, Nintendo101 (ended July 3, 2024)
^ NOTE: Not yet integrated for the New Super Mario Bros. games, the Super Mario Maker games, Super Mario Run, or Super Mario Bros. Wonder
Expand use of "rawsize" gallery class, Doc von Schmeltwick (ended July 19, 2024)
Do not use t-posing models as infobox images, Nightwicked Bowser (ended September 1, 2024)
Create new sections for gallery pages to cover "unused/pre-release/prototype/etc." graphics separate from the ones that appear in the finalized games, Doc von Schmeltwick (ended September 2, 2024)
Tag sections regarding the unofficially named planets/area in Super Mario Galaxy games with "Conjecture" and "Dev data" templates, GuntherBayBeee (ended September 10, 2024)
Rename the remaining baseball teams to their current titles, GuntherBayBeee (ended September 19, 2024)
Create MarioWiki:WikiLove and WikiLove templates, Super Mario RPG (ended September 20, 2024)
Only add in the current voice actor in the "latest portrayal" section in infoboxes, Altendo (ended September 21, 2024)

Talk page proposals

Split all the clothing, Doc von Schmeltwick (ended September 12, 2021)
Split machine parts, Robo-Rabbit, and flag from Super Duel Mode, Doc von Schmeltwick (ended September 30, 2022)
Make bestiary list pages for the Minion Quest and Bowser Jr.'s Journey modes, Doc von Schmeltwick (ended January 11, 2024)
Allow separate articles for Diddy Kong Pilot (2003)'s subjects, Doc von Schmeltwick (ended August 3, 2024)
Split Bowser's Flame from Fire Breath, Doc von Schmeltwick (ended September 18, 2024)
Split Banana Peel from Banana, Doc von Schmeltwick (ended September 18, 2024)
Split truck article into cargo truck and pickup truck articles, Doc von Schmeltwick (ended September 21, 2024)
Merge Crocodile Isle (Donkey Kong 64) with Crocodile Isle, Doc von Schmeltwick (ended September 21, 2024)

Writing guidelines

===Change how "infinitely respawning" enemies are counted in level enemy tables===<-Requesting cancelling Currently, the wiki lists enemy counts for each level in tables located in that level's article. This is all well and good, but the problem arises when infinitely respawning ones (like piped ones) are included. As seen here, this is awkwardly written as

  • "[number] (not including the infinite [enemy] spawning from [number] [method]),"

and why shouldn't it include them? That method of writing is ungainly, misleading, and bloats the table's width unnecessarily. Therefore, I propose the alternate writing of

  • "[number] + (∞ x [number]),"

with the "x [number]" and parentheses being removed if there is only one case. So in the linked example, it would be "6 + ∞," which says the same thing without contradicting itself with a lengthy diatribe.
(Also I had to restrain myself from using * rather than x because that's how I'm used to writing multiplication in equations. Thanks, higher-level math classes defaulting to "X" as a variable! But the asterisk could be used too, anyway.)

Proposer: Doc von Schmeltwick (talk)
Deadline: September 30, 2024, 23:59 GMT

Support

  1. Doc von Schmeltwick (talk) - Per
  2. Altendo (talk) - This doesn't sound like a bad idea, although I do think there should be an asterisk like "*" instead which leads to a note saying "not including the infinite [enemy] spawning from [number] [method]", as enemies can spawn in different ways, and showing how they spawn could still be useful. If we just show "∞ x [number]", it wouldn't show how Goombas are spawned in (the linked page doesn't specify how they are spawned in otherwise). But I do like the idea of shortening the "count" section of tables.

#ThePowerPlayer (talk) Per Altendo. This formatting is much better, but I also think some note of where the infinite enemy spawner(s) originate from should be preserved.
#Super Mario RPG (talk) Per all.

Oppose

  1. Hewer (talk) I don't see the benefit of changing this. The current wording is straightforward and succinct, I'd expect the reader to understand "6 (not including the infinite Goombas spawning from one Warp Pipe)" easily. Changing it to "6 + ∞" just makes it less clear for no reason, I'd definitely be confused if I saw that and didn't know this specific context. The fact that the other support votes have also brought up how doing this risks losing the specific information completely (and suggested a more long-winded solution that seems to contradict the proposal) compels me to oppose this more.
  2. Waluigi Time (talk) Per Hewer.
  3. FanOfYoshi (talk) Per all.
  4. Axii (talk) Per Hewer
  5. SolemnStormcloud (talk) Per all.
  6. EvieMaybe (talk) we don't need to throw a mathematical equation at people
  7. Sparks (talk) Per all.
  8. ThePowerPlayer (talk) I realized that this only makes sense if you have it explained to you like in the proposal description, which defeats the purpose.
  9. Arend (talk) I feel that "[number] (+ [number] infinite spawn points)" would be less awkward to write than what we currently do and more understandable fir most people than what is proposed here
  10. Killer Moth (talk) Per all.

Comments

@Hewer - "succinct" would generally imply "short, sweet, and to-the-point," of which the current method is the exact opposite. I'm fine with including an asterisk-note next to the infinity, but the current one is much too bloated, outright admits to stating false information, and since the tables are center-aligned with that horizontal-bloat, it makes it look incredibly awkward. Doc von Schmeltwick (talk) 12:41, September 17, 2024 (EDT)

I guess we just have totally opposing opinions on this one, because I don't personally find ten words of explanation to be "much too bloated", would rather "state false information" (not really what's happening because it's immediately clarified and the only way not to state any "false" info would be to just put "∞" which helps no one) than obscure the meaning of what we're trying to say, and I don't at all think the somewhat wider tables look "incredibly awkward". This is a case where I feel giving more explanation than "6 + ∞" is necessary for the sake of conveying clear information, so I'd rather prioritise that over having a thin table (which I still don't really see why that's so desirable). Hewer (talk · contributions · edit count) 03:19, September 18, 2024 (EDT)

If this proposal passes, I think that a dedicated template should be made; something like {{infinite respawn|5|3}} that would produce "5 + (∞ × 3)". Or at the very least, use an actual "×" symbol rather than "x". Jdtendo(T|C) 12:08, September 19, 2024 (EDT)

I dislike the idea of hiding details in easily missable hover text and don't really see the benefit of using it. It just makes it more convoluted. Hewer (talk · contributions · edit count) 11:12, September 20, 2024 (EDT)

I'll refrain from voting because I have a visceral reaction to anything that resembles a math formula, and I want as little as possible for personal preference to seep into my vote. That's not to say I don't understand what's being proposed, in fact it makes perfect sense if you're aiming strictly for concision, but you'd need to take into account how accessibly that information is communicated--you'd need to establish that "infinity symbol" stands for infinite enemy spawning point, which is not immediately clear. At that point, you'd go for a relatively lengthy explanation nonetheless. Though, I agree that the phrasing in that page you linked doesn't sound inclusive. I think something like "5 individual, 3 infinite spawning points" works better if we're going down this path.
If the proposal passes, I'd like to see it implemented in the manner Jdtendo suggests above.
EDIT: I'm aware there's already plenty of math on this wiki that has potential to confound people, but in that case, not only is its succinctness a better way to explain how the game's scoring system works (as opposed to paragraphs-long descriptions), but it's taken straight out of the game as well. I'd say, use math formulas only when you're sure prose would be of less service to its intended audience: people looking up how many enemies are in a level aren't necessarily interested in complex gameplay dynamics. -- KOOPA CON CARNE 13:12, September 19, 2024 (EDT), edited 14:55, September 19, 2024 (EDT)

I'd personally prefer if this was notated with ω instead of ∞, something like "3ω+5", but that would probably be too confusing to anyone not already familiar with transfinite ordinal notation. jan Misali (talk · contributions) 10:01, September 21, 2024 (EDT)

This should be written "ω⋅3+5" because 3⋅ω = ω; multiplication on transfinite ordinal numbers is not commutative. Jdtendo(T|C) 12:40, September 21, 2024 (EDT)

Maybe just have a table for finite enemies and a table for infinite enemies? There's horizontal space for both. Salmancer (talk) 11:33, September 21, 2024 (EDT)

That just needlessly splits information, which I again don't see the benefit of (and I still don't really see how there's a problem here that needs fixing anyway). Hewer (talk · contributions · edit count) 21:26, September 21, 2024 (EDT)

Figure out how to handle {{classic}} and {{classic-link}} templates when discussing Mario Kart Tour classic courses

This wiki has two templates used to format classic courses in the Mario Kart series: {{classic}} and {{classic-link}}. These templates convert text like "3DS Shy Guy Bazaar" into a format that closer resembles the one seen in games, with the prefix being written as such, a prefix, and not part of the courses name. So "3DS Shy Guy Bazaar" becomes "3DS Shy Guy Bazaar". However, there's an exception this wiki seems to have regarding this template: classic courses in Mario Kart Tour.

This is because the game does not structure the title of courses in such a way: instead it writes the prefix as large as the rest of the name, so it's written as "3DS Shy Guy Bazaar". However, I feel this creates a lot of inconsistency and confusion here on this wiki. For example, the page for a course like 3DS Rock Rock Mountain, a course featured as a classic in and out of Tour structures fellow course names both ways, with and without the template, simply because of the game the classic course appears in. To make things more confusing, when a Tour section on a course's page discusses classic courses outside of Tour, it uses the template, as seen in a few course pages. Additionally, page titles for courses that are only classics in Tour still use a smaller font for the page name, such as GBA Lakeside Park. Finally, some courses in Tour don't even adhere to this rule that has been enforced before, such as Wii Maple Treeway.

(I cannot find the edit log, however I was informed by a moderator here that it is a rule that is enforced a while back)

So this proposal is asking for one thing: an enforcement to be decided on.

The options are simple:

  • Use the templates for all references to classic courses.
  • Not use the template when referring to classic courses in Tour.

RMX courses will not be affected by this since the "RMX" is established to be part of the course's name.

Proposer: YoYo (talk)
Deadline: October 2, 2024, 23:59 GMT

Use the templates for all classic course links

  1. YoYo (talk) per my proposal, I think that the template formats them in a way that distinguishes the prefix from course name, and I think consistency is important here.

Do not use the templates for Mario Kart Tour classic course links

Comments

New features

None at the moment.

Removals

None at the moment.

Changes

Add film and television ratings to Template:Ratings

Regarding ratings on the games we cover on this wiki, it's usually done very well and even shows off obscure rating companies hardly anyone talks about. It's educational and shows how the world rates a Super Mario game. However, when it comes to television shows and movies, they do not get the same treatment. Television shows don't even have ratings in their infobox. And while the movies do, they not only list just the MPAA, which for people who live in the United Kingdom or other countries, is not representative of the majority of the world, it's just the text, "PG". Sure, most people know it means "Parental Guidance," but imagine if we included more ratings. It's not super easy to find ratings for films and television shows in general, other than IMDB and there are no sources for proof of these ratings. When it comes to the Canadian Home Video Rating System, I can hardly find what rating was applied to that particular movie/TV show and I remember not being lucky for searching any other ratings for other movies (personal experience, but I remember searching on one of these websites and the site was rather buggy or didn't have the film/show in question).

The better solution is to add film and television ratings to the rating template so we can provide a wide variety of ratings for movies and television shows. In this case, users from around the world can view how movies are rated in almost every country. As for what ratings we add, it's a bit tricky. Because there is a lot, I would need some help here. Regardless, I got some EFIGS ratings in question. If you have more ratings, please let me know and I'll add it to the proposal These are split up into film and television.

Film
Television

My list so far is not comprehensive, but my idea is to add these ratings (and potentially others) to the template and make the infoboxes look much prettier and more visually educational. I have nothing else to say, so that's about it.

Proposer: TheUndescribableGhost (talk)
Deadline: October 1, 2024, 23:59 GMT

Support

  1. TheUndescribableGhost (talk) Rated PR for per proposal.
  2. Technetium (talk) Never noticed ratings were missing from TV and movie coverage until now. It feels obvious ratings should be included like they are with games. Per proposal.
  3. FanOfRosalina2007 (talk) This is something I never noticed, but I completely agree. I'm happy that there are observant people in this world! Per proposal.
  4. Arend (talk) Per all (fun fact: the Dutch rating system for movies and television, Kijkwijzer, is being utilized by NICAM, which happens to also rate games in Europe using PEGI. In fact, PEGI's ratings appear to be based on those of Kijkwijzer)
  5. ThePowerPlayer (talk) Per all.
  6. Nintendo101 (talk) Per proposal.
  7. Sparks (talk) Per all.
  8. Mari0fan100 (talk) Per all, especially since movies like The Super Mario Bros. Movie have classification ratings.

Oppose

Comments

Wait, couldn't this just be a talk page proposal on the template itself? It would affect many pages, yes, but this is specifically about editing a template… I'm honestly not so sure. Technetium (talk) 15:52, September 24, 2024 (EDT)

Miscellaneous

None at the moment.

Retrieved from "https://www.mariowiki.com/index.php?title=MarioWiki:Proposals&oldid=4375957"