MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
 
Line 1: Line 1:
<center>[[File:Proposals.png]]</center>
{{/Header}}
<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), removals of previously added features that have tired out, or new policies that must be approved via [[Wikipedia:Wikipedia:Consensus|consensus]] before any action is taken.
*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]].
*All proposals must pass by a majority, including proposals with more than two options.
|}
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>.


This page observes the [[MarioWiki:No-Signature Policy|No-Signature Policy]].
==Writing guidelines==
===Add identifiers to near-identical titles===
Current MarioWiki writing guidelines state that articles with shared titles recieve an identifier to disambiguate between them (see: [[Mark (Mario Tennis series)|Mark (''Mario Tennis'' series)]] and [[Mark (NES Open Tournament Golf)|Mark (''NES Open Tournament Golf'')]]). However, this currently relies on the articles sharing an identical, character-by-character name. This means [[Color coin]] (''Super Mario Run'') and [[Colored coin]] (''Wario Land 3'') do not recieve identifiers, despite sharing functionally identical titles. Other sets of articles with the same dilemma include [[Secret Course 1]] (''Super Mario Land 2: 6 Golden Coins'') and [[Secret Course 01]] (''Super Mario Run''), [[Spyguy]] (''Mario vs. Donkey Kong 2: March of the Minis'') and [[Spy Guy]] (''Paper Mario''), and [[Rollin' Down the River]] (''Yoshi's Woolly World'') and [[Rolling Down the River]] (''The Super Mario Bros. Super Show!'').  


<h2 style="color:black">How To</h2>
This proposal aims to amend [[MarioWiki:Naming]] to consider near-identical titles like these as "shared titles", and thus qualify for recieving an identifier according to the established criteria. This is already applied in some articles, but this proposal aims to formalize it as part of the naming rules.
<h3 style="color:black">Rules</h3>
#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 [[MarioWiki:Writing Guideline|Writing Guideline]] proposals ''must'' include a link to the draft page.
#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.
#Every vote should have a reason accompanying it. Agreeing with or seconding a previously mentioned reason given by another user is accepted.
#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 at any time, but the final decision to remove another user's vote lies solely with the [[MarioWiki:Administrators|administrators]].
#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.
#No proposal can overturn the decision of a previous proposal that is less than '''4 weeks''' ('''28 days''') old.
#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 that end up in a tie will be extended for another week. Proposals with more than two options must also be extended another week if any single option does not have a majority support: i.e. more than half of all votes cast must be for a single option, rather than one option simply having more votes than the other options.
#If a proposal has more than ten votes, it can only pass or fail by a margin of '''three''' votes. In other words, one option must have 50% + 3 of all votes cast. This means that if a basic two-option proposal reaches the deadline and the total number of votes for each option differ by two or less votes, the deadline will be extended for another week. Proposals with more than two options require more precise counting of votes to determine if an extension is necessary.
#Proposals can only be extended up to three times. If a consensus has not been reached by the fourth deadline, the proposal fails and can only be re-proposed after four weeks, at the earliest.
#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.
#Proposals can only be rewritten or deleted by their proposer within the first three days of their creation. However, proposers can request that their proposal be deleted by an [[MarioWiki:Administrators|administrator]] at any time, provided they have a valid reason for it. Please note that cancelled proposals must also be archived.
#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.
#There should not be proposals about creating articles on an underrepresented or completely absent subject, unless there is major disagreement about whether the content should be included. To organize efforts about completing articles on missing subjects, try setting up a [[ForumBoard:57|collaboration thread on the forums]].
#Proposals cannot be made about promotions and demotions. Users can only be promoted and demoted by the will of the [[MarioWiki:Administrators|administration]].
#No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.


<h3 style="color:black">Basic Proposal and Support/Oppose Format</h3>
Note that this proposal only covers names that are '''semantically identical''', and only differ in formatting or minor word choices. [[Buzzar]] and [[Buzzer]] have extremely similar names, but they aren't semantically identical. [[Balloon Boo]] and [[Boo Balloon]] are extremely similar as well, but the word order sets them apart.
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 <u>replace the whole variable including the squared brackets</u>, 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.
-----
<nowiki>===[insert a title for your Proposal here]===</nowiki><br>
<nowiki>[describe what issue this Proposal is about and what changes you think should be made to improve how the Wiki handles that issue]</nowiki>


<nowiki>'''Proposer''': {{User|[enter your username here]}}<br></nowiki><br>
'''Edit:''' Per Hewer's question and my comment below, I'd like to point out MarioWiki already does this sometimes. Pairs of near-identical names with identifiers include [[Family Basic (microgame)]] and [[Family BASIC]] (as ruled by [[Talk:Family_Basic_(microgame)#Moving_the_page|a proposal]]), [[Hot Air Balloon (Donkey Kong franchise)|Hot Air Balloon (''Donkey Kong'' franchise)]] and [[Hot-air balloon]], [[Finish line (object)]] and [[Finish Line (microgame)]], and [[Avalanche (obstacle)]] and both [[Avalanche! (Dance Dance Revolution: Mario Mix)|Avalanche! (''Dance Dance Revolution: Mario Mix'')]] and [[Avalanche! (Mario Party 4)|Avalanche! (''Mario Party 4'')]]. If this proposal doesn't pass, all of these would get their identifiers removed.
<nowiki>'''Deadline''': [insert a deadline here, 7 days after the proposal was created, at 23:59 GMT. (14 days for </nowiki>[[MarioWiki:Writing Guideline|Writing Guidelines]] and [[#Talk Page Proposals|Talk Page Proposals]])


<nowiki>====Support====</nowiki><br>
'''Proposer''': {{User|EvieMaybe}}<br>
<nowiki>#{{User|[enter your username here]}} [make a statement indicating that you support your proposal]</nowiki>
'''Deadline''': November 26, 2024, 23:59 GMT


<nowiki>====Oppose====</nowiki>
====Support====
#{{User|EvieMaybe}} per.
#{{User|Super Mario RPG}} Per proposal.


<nowiki>====Comments====</nowiki>
====Oppose====
-----
#{{User|Altendo}} I don't see a need for this. If the names are similar, tophats containing the other pages can be placed on the pages with similar names. Identifiers are used to identify subjects with ''identical names'', not similar names.
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.
#{{User|Hewer}} Per Altendo, this is what [[Template:Distinguish]] is for. We have to use identifiers for identical titles because the wiki can't have multiple pages with the same title, but that limitation doesn't exist if the titles are just similar. This would make the titles longer than they need to be, and I could also see this leading to disagreements about what's similar enough to count, if the examples are anything to go by. Easier to stick to the objectivity of only giving identical names identifiers. The proposal also doesn't specify what the "some articles" are where this has already been done, but I'm assuming they should be changed.
#{{User|Ray Trace}} Per Hewer.
#{{User|Dine2017}} Per Hewer & I'd like to see the use of identifier kept to a minimum because it simplifies typing (URL, wikicode, etc.)
#{{User|SeanWheeler}} Per Hewer. No need to extend the title just because of a couple letter difference. The identifiers are there for identical titles because it's impossible for wikipages to have the same name.
#{{User|ThePowerPlayer}} Per Hewer. Making this change would only cause more confusion, not less.


To support, or oppose, just insert "<nowiki>#{{User|[add your username here]}}</nowiki> 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".
====Comments====
I'm not sure why this is a problem in the first place, can you please elaborate? --{{User:Waluigi Time/sig}} 12:13, November 11, 2024 (EST)
:i just find it a bit unreasonable to expect people to remember the difference between two names that are identical in all but formatting, or essentially irrelevant word choice differences (in the case of Color coin and Colored coin, which have also been). this is especially true while editing; i had to verify whether Secret Course 1 was the SML2 one or the SMR one when writing the [[Secret exit]] article. without resorting to a literal, robotic interpretation of the rules, all of the articles i mentioned have functionally "the same name" as their pair, and there is precedent for adding identifiers to article names like these. [[Family Basic (microgame)]] recieved a differentiatior because a mere capitalization difference from [[Family BASIC]] [[Talk:Family_Basic_(microgame)#Moving_the_page|was deemed unreasonable]]. folks in the MarioWiki Discord server agreed with me when i asked if i should rename [[Hot Air Balloon (Donkey Kong franchise)]] (previously just "Hot Air Balloon", with no hyphen and Air capitalized) to differentiate it from [[Hot-air balloon]]. [[Avalanche (obstacle)]] has an identifier to separate it from [[Avalanche! (Dance Dance Revolution: Mario Mix)]] and [[Avalanche! (Mario Party 4)]], even though both of them have exclamation marks. [[Finish line (object)]] and [[Finish Line (microgame)]] get identifiers, even though they're capitalized differently. this is something we already do, the aim here is just to formalize it. [[User:EvieMaybe|EvieMaybe]] ([[User talk:EvieMaybe|talk]]) 14:51, November 11, 2024 (EST)
::This proposal passing wouldn't mean you no longer have to check whether it's Secret Course 1 or 01, it'd just mean you now have to type an unnecessary identifier and pipe link it as well. I'd say it's different for finish line and Family BASIC where the only difference between titles is casing, as the search function on the wiki is case insensitive (and also, that proposal made [[Family Basic]] a redirect to [[Family BASIC]], so an identifier is still needed to distinguish from that). But in the other cases, we don't need the identifier. {{User:Hewer/sig}} 15:49, November 11, 2024 (EST)


__TOC__<!--
==New features==
===Create articles for Glohm enemies or merge them with their normal counterparts===
I'm currently contributing to ''[[Mario & Luigi: Brothership]]'' content, and I'm currently creating articles for enemies in the game. It has been brought to my attention that [[Glohm]] enemies are basically stronger versions of preexisting enemies, although they have unique characteristics.


<center><span style="font-size:200%">CURRENTLY: '''{{#time: H:i, d M Y}} (GMT)'''</span></center>
This proposal aims to determine whether or not Glohm enemies get their own articles. So, there are two choices for when Glohm enemy coverage eventually occurs:


1. '''Glohm enemies get their own articles.''' They get their own dedicated pages.


2. '''Glohm enemy coverage is limited to the articles for their normal counterparts.''' This means all Glohm related information for them is explained for the normal versions of the enemies.


<br>
Let's see what happens!
-->


<h2 style="color:black">Talk Page Proposals</h2>
'''Proposer''': {{User|Sparks}}<br>
All proposals dealing with a single article or a specific group of articles are held on the talk page of one of the articles in question. Proposals dealing with massive amounts of splits, merges or deletions across the Wiki should still be held on this page.
'''Deadline''': December 5, 2024, 23:59 GMT


:''For a list of all settled Talk Page Proposals, see [[:Category:Settled Talk Page Proposals|here]].''
====Create new articles for Glohm enemies====
#{{User|Sparks}} My preferred choice. Sure it could get repetitive and redundant, but it's worth it to document the abilities of these Glohm enemies.
#{{User|Camwoodstock}} We give articles to [[Elite Dry Bones|other stronger]] [[Shy Guy R|RPG enemy]] [[Antasma X|and boss variants]], so why should Brothership be any different?
#{{User|Tails777}} They are stronger variants with different stats to their originals, no different from every example Camwoodstock gave. Per proposal.
#{{User|DryBonesBandit}} Per all.
#{{User|Zootalo}} The Shiny Paper versions of enemies from Paper Jam have their own articles as well; this is no different. Per all.
#{{User|Nightwicked Bowser}} Probably best for overall consistancy with a game like this one.
#{{User|Technetium}} Per all.
#{{User|Cheat-master30}} Given that some of them have specific differences in attack patterns, it seems like they should probably get unique articles.


<h3 style="color:black">Rules</h3>
====Include Glohm enemy coverage on their normal counterparts' articles without creating new articles for them====
#All active talk page proposals must be listed below in chronological order (new proposals go at the bottom). All pages affected must be mentioned in the ''brief'' description, with the talk page housing the discussion linked to directly via "({{fakelink|Discuss}})". If the proposal involved a page that is not yet made, use {{tem|fakelink}} to communicate its title. The '''Deadline''' must also be included in the entry. Linking to pages not directly involved in the talk page proposal is not recommended, as it clutters the list with unnecessary links. Place {{tem|TPP}} under the section's header, and once the proposal is over, replace the template with {{tem|SettledTPP}}.
#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:
#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.
#Talk page proposals may be closed by the proposer at any time if both the support ''and'' the oppose sides each have fewer than five votes.
#The talk page proposal '''must''' pertain to the article it is posted on.


===List of Talk Page Proposals===
====Comments====
*Remove info about ''Super Mario 64''/''Super Mario 64 DS'' item from [[Cape Feather]] and put somewhere more relevant. ([[Talk:Cape Feather#Put Super Mario 64 (DS) info somewhere else|Discuss]]) '''Deadline''' November 24, 2012 23:59 GMT
{{@|Zootalo}} The Paper Jam shiny enemies are not split, but the Sticker Star ones are. {{Unsigned|Nightwicked Bowser}}
*Merge [[Sticker Star]] with [[List of Implied Locations]]. ([[Talk:Sticker Star|Discuss]]) '''Deadline''' December 3rd, 2012 23:59 GMT


==Writing Guidelines==
Kinda torn to be honest. I voted yes because some of them have specific differences from their regular counterparts (Glohm Floopfly Rs and Glohm Soreboars always explode once defeated for example), but then we've got the weird situation of trying to figure out what exactly you'd include on a page for the enemies without these things, like the Glohm Palookas (which as far as I know, look and act almost identically to their standard counterparts). --[[User:Cheat-master30|Cheat-master30]] ([[User talk:Cheat-master30|talk]]) 22:30, November 23, 2024 (EST)
''None at the moment.''
:In fairness, this could also be said about many other stronger variants of enemies. The only real difference between a Goomba and Gloomba are the color schemes, in a similar way to how the only difference between a Palooka and a Glohm Palooka is the darker coloration and Glohmy aura. It's kinda just a natural thing for most stronger variants (not all mind you, but most). {{User:Tails777/sig}}
 
==New Features==
''None at the moment.''


==Removals==
==Removals==
Line 88: Line 68:


==Changes==
==Changes==
===Allow Support Reasoning on Featured Article Nominations===
===Tag images of bind-posing models for reuploading===
It's been two years since [[MarioWiki:Proposals/Archive/69#Do not use t-posing models as infobox images|the previous proposal]] had passed. Now let's talk about tagging images of bind-posing models for reuploading. Take [https://www.models-resource.com/resources/big_icons/4/3950.png?updated=1673644745 this image] for example. As you can see, this image is a bind-posing model. Once this proposal passes, we'll be able to tag every bind-posing model with this:


This is kind of a... er... wierd rule, On Featured Article nominations, nobody other than the creator can put a reason for supporting.
{{tem|image-quality|Bind-posing model; should be replaced with a rendered game model}}


I have heard some users say that sometimes they actually want to write a support vote, but can't because of the rules.
That way, if a bind-posing model is reuploaded as a rendered game model that serves as a replacement, we'll be able to reuse it as an infobox image.


I am proposing to allow, but not require, reasoning for supporting a Featured Article nomination. However, votes that say "Per *insert user*" will be removed.
'''Proposer''': {{User|GuntherBayBeee}}<br>
 
'''Deadline''': November 29, 2024, 23:59 GMT
'''Proposer:''' {{User|Yoshi K}}<br>
'''Deadline:''' November 22, 2012 23:59 GMT


====Support====
====Support====
#{{User|Yoshi K}} It's my proposal.
#{{User|GuntherBayBeee}} Per proposal
#{{User|Electrical Bowser jr.}} I've often thought the exact same thing.
<s>#{{User|ThePowerPlayer}} Like I said in the other proposal, T-poses are generally not how characters are supposed to look. If [[MarioWiki:Proposals/Archive/70#Prioritize MESEN/NEStopia palette for NES sprites and screenshots|this]] is any indication, the wiki should favor game accuracy in images.</s>


====Oppose====
====Oppose====
#{{User|YoshiKong}} Comments should only be left in the oppose section, so as to give a reason why users don't agree with the FA nomination and give suggestions to improve the article. I believe that it is logical to leave the support section clean, rather than allow a flood of supporting comments. This can eliminate the possibility of users middle-fencing (see [[MarioWiki:Featured Articles/A1/Super Smash Bros.|this nomination archive]]) for a good example. Most of the users there have supported the nomination, but still suggested improvements for the article. We should either support a nomination or oppose it, not both. Removing supporting comments is logical as it allows all the attention to go to what the oppose have to say. I think we should just stick to the rule we already have and only allow a supporting comment for the nominator.
#{{User|Nintendo101}} I think it is great when users replace images of bind-posed (or "t-posed") models with organically rendered ones. It is a practice I personally encourage and welcome. However, I do think there [[:File:PiantissimoUnmasked.png|can be educational and illustrative purposes to bind-posed models]], and I think a blanket rule would put unnecessary pressure on the users of this site to render models when a bind-posed one can be more than serviceable, and may even discourage the cataloging of 3D assets in the future if a user cannot render them. Rendering models is a very time-consuming process, and I think it is healthier to just allow users to replace the bind-posed images we have ''if'' they can. Not require them to. Perfection is the enemy of the good.
#{{User|Mario4Ever}} Including support reasons in Featured Article nominations is redundant. With FAs, there are established standards they must meet before they can be featured, and it stands to reason that users who nominate articles for featured status believe they meet those standards, and any supporters afterward also hold that view (or some variation which falls under one or more of the established standards). The process is the same with every FA. Proposals, by contrast, allow for greater variety regarding users' reasons for supporting them because proposals cover a wide range of topics, so there is no list of standards to which the proposer must ensure the topic of his or her proposal adheres before the proposal can be made. Every proposal must be formatted a certain way, but each type of proposal is dealt with a little differently depending on its specific type.
#{{User|EvieMaybe}} this seems better handled on a case-by-case basis rather than a full sweep
#{{User|Bop1996}} As flawed as our current FA nomination system is, this wouldn't fix the flaws. Per Mario4Ever.
#{{User|Waluigi Time}} Per all.
#{{User|BabyLuigiOnFire}} There is a reason we removed support votes. Per all.
#{{User|Hewer}} Per all, a hard rule isn't necessary here.
#{{User|Creeper}} &ndash; per all
#{{User|ThePowerPlayer}} Per all.
#{{user|Coincollector}} As Mario4Ever said, in a nutshell, we already have the reasonings [[MarioWiki:Featured Articles#Featured Article Standards|here]].
#{{User|Camwoodstock}} Per all, especially Nintendo101. Given there ''are'' scenarios where bind-posed/T-posed models are actually more illustrative than properly rigged alternatives, we should probably handle these on a case-by-case basis.
#{{User|Mario}} Tag them if they're bad quality, not because they're t-posed.


====Comments====
====Comments====
I would support it but <s>then I took an arrow to the knee</s> why should "per" votes be removed? They are as equally legitimate as the same user restating the other user's reason. {{User|Zero777}}
Wording should be changed to "bind pose" since not all characters are T-posed, especially non-bipeds ([https://www.models-resource.com/resources/big_icons/4/3950.png?updated=1673644745 like Yoshi from Super Smash Bros. Melee or Brawl], Wiggler, Buzzy Beetles, Piranha Plants, and more) and A-pose exists as a default pose too. In addition, models technically aren't "t-posing", they're modeled this way before animations and a rig are applied to them, the wording makes them look like they're animating when they're not. {{User:Ray Trace/sig}} 20:36, November 15, 2024 (EST)
 
Does this proposal advocate replacing these ripped models with ones that are posed from a screenshot or posed in a 3d program with ripped animation files? Not all models are ripped with animations, so it's a bit of a task to undertake if you really want models with animations AND a rig (let's not get started in lighting, which is a separate skillset that's demanded from renderers; not many people get the lighting very good, no offense!); a chunk of models tend to not have a rig, much less an animation. Additionally, some t-posed models are great to use when comparing models or viewing models ''as they are''. [[:File:MLNPC.png]] is an example where it's easy to compare the proportions of Mario, PC Luigi, and NPC Luigi. Sure, you can probably put them all in a orthographic lineup in the same keyframe of a shared animation, but due to the arms, legs, spine, and head all straightened out, it's better to illustrate in T-pose imo. {{User:Mario/sig}} 21:00, November 15, 2024 (EST)


==Miscellaneous==
==Miscellaneous==
=== Create articles for non-Mario attractions ===
''None at the moment.''
For the sake of resolving the discussion [[Talk:Nintendo Land#Articles for all atractions|here]], I'm reaching a decision through a proposal. It has been discussed that we shouldn't create articles for the [[Nintendo Land#Minigames|Minigames]] in ''Nintendo Land'' that don't relate to the ''Mario'' series. But our [[MarioWiki:Coverage#Crossovers|coverage policy]] says that we cover ''all'' information in a crossover that mixes ''Mario'' with another series, but it is limited to the information from the crossover and we can't talk about additional info from the other series. We currently cover only four of the twelve minigames, [[Octopus Dance|one of them]] not being directly related to ''Mario''. I see this as illogical as we shouldn't leave a game half covered and rely on other NIWA sites for further info on the uncovered minigames (one of them isn't even covered by a NIWA site). And then we fully cover crossovers like the [[Super Smash Bros. (series)|''Super Smash Bros.'' series]] and the [[Mario & Sonic (series)|''Mario & Sonic'' series]]. As discussed on the talk page, we don't fully cover ''[[Captain Rainbow]]'' but the policy says we can, so why not ''Nintendo Land''?
 
'''Proposer:''' {{User|YoshiKong}}<br>
'''Deadline:''' November 24, 2012 23:59 GMT
 
====Support====
#{{User|YoshiKong}} Per my arguments above.
#{{User|Electrical Bowser jr.}} Per Yo-YoKong.
#{{User|Walkazo}} - I agree this should count as a full crossover, like ''SSB'', ''Itadaki Street DS'' or ''Mario Hoops 3-on-3'', and so, all the minigames should get pages, including the stuff that's not directly part of the ''Mario''-derived content in the game.
#{{User|The Forgotten Beast}} - Per all.
#{{User|Mario4Ever}} Per Walkazo.
#{{User|JORDAN DEBONO}} I'm very undecided, but I suppose the MarioWiki coverage allows us to make these articles. SO LONG as external hyperlinks to the articles in other NIWA wikis remain, I guess I'll support this.
#{{User|ThatPeskyKoopaling}} Per all.
#{{User|Byllant}} - Why didn't anyone bothered to move my support vote when this proposal was moved here? anyway I started this, I supported this.
#{{User|Sonic98}} If we put all the information regarding the crossover seems sensible to create pages for the mini-games that do not belong to the Mario series, even if it could encompass all these mini games on a single page.
 
====Oppose====
# {{User|1337star}} Going against the curve here in opposing. Unlike ''Super Smash Bros.'', ''Mario & Sonic'', or even ''Captain Rainbow'' to an extent (in the hypothetical case that our coverage of that game would be expanded), as far as I'm aware, the attractions of Nintendo Land don't interact with each other. They could essentially be their own games, they're just all on the same disc. While I could see making a page for, say, the monitor host thingy whose name I forget, making pages for non-''Mario'' minigames just because they appear in the same collection as ''Mario'' minigames seems to be pushing our coverage policy. Now, if someone can prove to me that the games do interact in some meaningful way, I'm all for supporting this, but otherwise that's my position.
# {{User|Glowsquid}} per 1337star.
# {{User|Marshal Dan Troop}} Per all.
# {{User|Creeper}} per 1337star
 
====Comments====
@Electrical Bowser jr. Thanks for the vote, but providing a reason is mandatory. {{User|YoshiKong}} 21:46, 17 November 2012 (EST)
 
In response to some of the [[Talk:Nintendo_Land#Articles_for_all_atractions|arguments against full coverage]], unlike ''[[NBA Street V3]]'' and ''[[SSX on Tour]]'', the ''Mario'' influence on ''[[Nintendo Land]]'' is huge, just like all the undisputed crossovers (''[[Mario & Sonic (series)|Mario & Sonic]]'', ''[[Super Smash Bros. (series)|SSB]]'', ''[[Fortune Street]]'' and ''[[Itadaki Street DS]]'', ''[[Mario Kart Arcade GP|Mario Kart Arcade GP]] 1'' and ''[[Mario Kart Arcade GP 2|2]]'', ''[[Wario Blast: Featuring Bomberman!]]'', ''[[Mario Hoops 3-on-3]]'' and ''[[Mario Sports Mix]]'', plus the slightly different case of the ''[[Game_%26_Watch#Game_.26_Watch_Gallery_series|Game & Watch Gallery]]'' series (they're ports of non-''Mario'' games, but with "modern" ''Mario'' versions)). Leaving out the non-''Mario'' stuff would make the coverage of any of these games seem patchy, whereas for ''NBA Street V3'' and ''SSX on Tour'', it's clear we're only bothering with the little slices of ''Mario'' and not the other 95% of the games that are completely unrelated to our series: as I said [[forum:17310.msg718029#msg718029|in this forum post]], these games are more like "guest appearances" than full-on crossovers (same with ''Densetsu no Stafy 3'', which we haven't even made a page for yet). ''[[Captain Rainbow]]'' is more of a crossover than a "guest appearance" given how Birdo's a major character and how there's other series represented in the game, but giving it full coverage would be difficult given the Japan-only nature of the game. Plus, most of the main characters, as well as the plot and setting, are original to the game and factor in much more heavily than the original content in other crossovers (''SSBB'' is the only one that really comes close), which sets it a bit apart from the more standard crossovers - including ''Nintendo Land''. And to be thorough, we also give single-article coverage only to ''[[Tetris DS]]'' and ''[[Art Style: PiCTOBiTS]]'' (and now ''[[Pushmo]]'' too), but given the simple puzzle-game nature of these titles, single articles is all we really ''need'' to cover them. '''The point is,''' ''Nintendo Land'' is much more like the other accepted crossovers than the "guest appearance" games that are only given partial coverage, so as the proposal says, it should get full coverage. - {{User|Walkazo}}
 
:Awesome. I'm glad that the decision the proposal will make is off to a good start. Also I'm just wondering, what's the limit we can go for creating articles for guest appearances? I would like to get the article ''Densetsu no Stafy 3'' created eventually, but how notable does the guest appearance have to be to get their own article? Like for example, we have a heap of [[List of Mario references in video games|''Mario'' references]] in the game ''The Legend of Zelda: Link's Awakening''. Like ''Stafy 3'', could that game also get an article? {{User|YoshiKong}} 22:18, 17 November 2012 (EST)
::What sets ''Stafy 3'' apart from games that merely "reference" ''Mario'' is the fact that Wario's role is fairly important, and not just a cameo that could be totally erased from the game with no effect on its plot or gameplay. Wario's not playable like the ''Mario'' characters in ''NBA Street V3'' and ''SSX on Tour'', but [[Wario#Densetsu no Stafy 3|as his article explains]], he helps the player complete various levels, gives them treasures and teaches them how to use one of Starfy's moves. Wario's not a major part of the game, so it's not a full crossover, but if you take him out, there ''would'' be an effect on the game, so he's more than just a cameo. And unlike something like Mario refereeing in ''Mike Tyson's Punch-Out!!'', Wario isn't just a face slapped on what cold easily be a generic role: it's Wario being Wario in ''Stafy 3''. Of course, speaking of ''Punch-Out!!'', the Wii game might be eligible for an article given how [[Donkey Kong#Punch-Out!!|Donkey Kong's featured]] as a bonus opponent: that's less involved than Wario is with ''Stafy 3'', but it's still heftier than your run-of-the-mill cameo. I think the best thing to do would be to make Proposals (like this one) before expanding content for ''Punch-Out!!'' Wii, ''Densetsu no Stafy 3'', or any other intermediate "guest appearance" game: when you're dealing with grey areas like this, case-by-case is always the way to go. - {{User|Walkazo}}
 
[[File:WL4-Densetsu no Starfy 3 Flaming Wario.png|frame|''[[starfywiki:Densetsu no Starfy 3|Densetsu no Starfy 3]]''<br> Cameo or not, Wario doesn't care what you call him. He's on fire!!]]
:::Okay, but is doesn't have to be a grey area. MW:Coverage could get updated to mention such articles. At present, the policy says that we organize information based on importance. How you defined importance above may be a topic to elaborate on in the policy. And if we were to allow ''Densetsu no Stafy 3'' as a complete article some time in future, then it may be good to update the "Cameo" section when necessary (changing the part where it says that info about the game that isn't related to the cameo appearance is not allowed). But you also said Wario was more than a cameo in ''Stafy 3''. If he's not exactly a cameo, then what should it be defined as in the policy? Oh, and here's an image to liven up a chunk of text :D {{User|YoshiKong}} 02:53, 18 November 2012 (EST)
 
 
=== Put the page of Boos Rush in a different page of the Boost Mode ===
Page of the Boos Rush relates to a challenge test mode so it should not be in the page of the Boost Mode but it should be seen in a page made ​​on purpose for that mode.
 
====Support====
#{{User|Sonic98}} Per my arguments above.
 
====Oppose====

Latest revision as of 19:12, November 24, 2024

Image used as a banner for the Proposals page
Current time:
Monday, November 25th, 06:27 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.
  • Voting periods last for two weeks, but can close early or be extended (see below).
  • Any autoconfirmed user can support or oppose, but must have a strong reason for doing so.
  • 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 autoconfirmed users may create or vote on proposals and talk page proposals. While only autoconfirmed users can comment on proposals, anyone is free to comment on talk page proposals.
  3. Proposals end at the end of the day (23:59) two weeks after voting starts (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 two weeks later on Monday, August 15, at 23:59 GMT.
  4. Users may vote for more than one option, but they may not vote for every option available.
  5. 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.
  6. 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 wiki staff.
    • 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.
  7. 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.
  8. Proposals cannot contradict an already ongoing proposal or overturn the decision of a previous proposal that concluded less than four weeks (28 days) ago.
  9. If one week before a proposal's initial deadline, the first place option is ahead of the second place option by eight or more votes and the first place option has at least 80% approval, then the proposal concludes early. Wiki staff may tag a proposal with "Do not close early" at any time to prevent an early close, if needed.
    • Use {{proposal check|early=yes}} to automate this calculation; see the template page for usage instructions and examples.
  10. 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.
  11. If a proposal reaches its deadline and there is a tie for first place, then the proposal is extended for another week.
  12. 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% approval to win. If the margin is only one or two votes, then the first place option must have at least 60% approval to win. If the required approval threshold is not met, then the proposal is extended for another week.
    • Use {{proposal check}} to automate this calculation; see the template page for usage instructions and examples.
  13. Proposals can be extended a maximum of three times. If a consensus has not been reached by the fourth deadline, then the proposal fails and cannot be re-proposed until at least four weeks after the last deadline.
  14. 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.
  15. After a proposal or talk page proposal passes, it is added to the corresponding list of "unimplemented proposals" below and is removed once it has been sufficiently implemented.
  16. If the wiki staff deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to cancel it at any time.
  17. Proposals can only be rewritten or canceled by their proposer within the first four days of their creation. However, proposers can request that their proposal be canceled by a staff member at any time, provided they have a valid reason for it. Please note that canceled proposals must also be archived.
  18. 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.
  19. Proposals cannot be made about promotions and demotions. Staff changes are discussed internally and handled by the bureaucrats.
  20. No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
  21. 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, 14 days after the proposal was created, at 23:59 GMT, in the format: "November 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. Place {{TPP}} under the section's header, and once the proposal is over, replace the template with {{settled TPP}}. Proposals dealing with a large amount of splits, merges, or deletions across the wiki should still be held on this page.

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.

List of ongoing talk page proposals

Unimplemented proposals

Proposals

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 Super Mario Maker titles, Super Mario Run, and Super Mario Bros. Wonder.
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)
Add film and television ratings to Template:Ratings, TheUndescribableGhost (ended October 1, 2024)
Use the classic and classic-link templates when discussing classic courses in Mario Kart Tour, YoYo (ended October 2, 2024)
Split articles for the alternate-named reskins from All Night Nippon: Super Mario Bros., Doc von Schmeltwick (ended October 3, 2024)
Clarify coverage of the Super Smash Bros. series, Doc von Schmeltwick (ended October 17, 2024)
Remove all subpage and redirect links from all navigational templates, JanMisali (ended October 31, 2024)
Prioritize MESEN/NEStopia palette for NES sprites and screenshots, Doc von Schmeltwick (ended November 3, 2024)
Stop considering reused voice clips as references (usually), Waluigi Time (ended November 8, 2024)
Allow English names from closed captions, Koopa con Carne (ended November 12, 2024)
^ NOTE: A number of names coming from closed captions are listed here.
Split off the Mario Kart Tour template(s), MightyMario (ended November 24, 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 Banana Peel from Banana, Doc von Schmeltwick (ended September 18, 2024)
Merge Spiked Thwomp with Thwomp, Blinker (ended November 2, 2024)
Create articles for specified special buildings in Super Mario Run, Salmancer (ended November 15, 2024)
Expand and rename List of characters by game to List of characters by first appearance, Hewer (ended November 20, 2024)
Create articles for "Ashita ni Nattara" and "Banana Tengoku" or list them in List of Donkey Kong Country (television series) songs, Starluxe (ended November 23, 2024)

Writing guidelines

Add identifiers to near-identical titles

Current MarioWiki writing guidelines state that articles with shared titles recieve an identifier to disambiguate between them (see: Mark (Mario Tennis series) and Mark (NES Open Tournament Golf)). However, this currently relies on the articles sharing an identical, character-by-character name. This means Color coin (Super Mario Run) and Colored coin (Wario Land 3) do not recieve identifiers, despite sharing functionally identical titles. Other sets of articles with the same dilemma include Secret Course 1 (Super Mario Land 2: 6 Golden Coins) and Secret Course 01 (Super Mario Run), Spyguy (Mario vs. Donkey Kong 2: March of the Minis) and Spy Guy (Paper Mario), and Rollin' Down the River (Yoshi's Woolly World) and Rolling Down the River (The Super Mario Bros. Super Show!).

This proposal aims to amend MarioWiki:Naming to consider near-identical titles like these as "shared titles", and thus qualify for recieving an identifier according to the established criteria. This is already applied in some articles, but this proposal aims to formalize it as part of the naming rules.

Note that this proposal only covers names that are semantically identical, and only differ in formatting or minor word choices. Buzzar and Buzzer have extremely similar names, but they aren't semantically identical. Balloon Boo and Boo Balloon are extremely similar as well, but the word order sets them apart.

Edit: Per Hewer's question and my comment below, I'd like to point out MarioWiki already does this sometimes. Pairs of near-identical names with identifiers include Family Basic (microgame) and Family BASIC (as ruled by a proposal), Hot Air Balloon (Donkey Kong franchise) and Hot-air balloon, Finish line (object) and Finish Line (microgame), and Avalanche (obstacle) and both Avalanche! (Dance Dance Revolution: Mario Mix) and Avalanche! (Mario Party 4). If this proposal doesn't pass, all of these would get their identifiers removed.

Proposer: EvieMaybe (talk)
Deadline: November 26, 2024, 23:59 GMT

Support

  1. EvieMaybe (talk) per.
  2. Super Mario RPG (talk) Per proposal.

Oppose

  1. Altendo (talk) I don't see a need for this. If the names are similar, tophats containing the other pages can be placed on the pages with similar names. Identifiers are used to identify subjects with identical names, not similar names.
  2. Hewer (talk) Per Altendo, this is what Template:Distinguish is for. We have to use identifiers for identical titles because the wiki can't have multiple pages with the same title, but that limitation doesn't exist if the titles are just similar. This would make the titles longer than they need to be, and I could also see this leading to disagreements about what's similar enough to count, if the examples are anything to go by. Easier to stick to the objectivity of only giving identical names identifiers. The proposal also doesn't specify what the "some articles" are where this has already been done, but I'm assuming they should be changed.
  3. Ray Trace (talk) Per Hewer.
  4. Dine2017 (talk) Per Hewer & I'd like to see the use of identifier kept to a minimum because it simplifies typing (URL, wikicode, etc.)
  5. SeanWheeler (talk) Per Hewer. No need to extend the title just because of a couple letter difference. The identifiers are there for identical titles because it's impossible for wikipages to have the same name.
  6. ThePowerPlayer (talk) Per Hewer. Making this change would only cause more confusion, not less.

Comments

I'm not sure why this is a problem in the first place, can you please elaborate? --Waluigi's head icon in Mario Kart 8 Deluxe. Too Bad! Waluigi Time! 12:13, November 11, 2024 (EST)

i just find it a bit unreasonable to expect people to remember the difference between two names that are identical in all but formatting, or essentially irrelevant word choice differences (in the case of Color coin and Colored coin, which have also been). this is especially true while editing; i had to verify whether Secret Course 1 was the SML2 one or the SMR one when writing the Secret exit article. without resorting to a literal, robotic interpretation of the rules, all of the articles i mentioned have functionally "the same name" as their pair, and there is precedent for adding identifiers to article names like these. Family Basic (microgame) recieved a differentiatior because a mere capitalization difference from Family BASIC was deemed unreasonable. folks in the MarioWiki Discord server agreed with me when i asked if i should rename Hot Air Balloon (Donkey Kong franchise) (previously just "Hot Air Balloon", with no hyphen and Air capitalized) to differentiate it from Hot-air balloon. Avalanche (obstacle) has an identifier to separate it from Avalanche! (Dance Dance Revolution: Mario Mix) and Avalanche! (Mario Party 4), even though both of them have exclamation marks. Finish line (object) and Finish Line (microgame) get identifiers, even though they're capitalized differently. this is something we already do, the aim here is just to formalize it. EvieMaybe (talk) 14:51, November 11, 2024 (EST)
This proposal passing wouldn't mean you no longer have to check whether it's Secret Course 1 or 01, it'd just mean you now have to type an unnecessary identifier and pipe link it as well. I'd say it's different for finish line and Family BASIC where the only difference between titles is casing, as the search function on the wiki is case insensitive (and also, that proposal made Family Basic a redirect to Family BASIC, so an identifier is still needed to distinguish from that). But in the other cases, we don't need the identifier. Hewer (talk · contributions · edit count) 15:49, November 11, 2024 (EST)

New features

Create articles for Glohm enemies or merge them with their normal counterparts

I'm currently contributing to Mario & Luigi: Brothership content, and I'm currently creating articles for enemies in the game. It has been brought to my attention that Glohm enemies are basically stronger versions of preexisting enemies, although they have unique characteristics.

This proposal aims to determine whether or not Glohm enemies get their own articles. So, there are two choices for when Glohm enemy coverage eventually occurs:

1. Glohm enemies get their own articles. They get their own dedicated pages.

2. Glohm enemy coverage is limited to the articles for their normal counterparts. This means all Glohm related information for them is explained for the normal versions of the enemies.

Let's see what happens!

Proposer: Sparks (talk)
Deadline: December 5, 2024, 23:59 GMT

Create new articles for Glohm enemies

  1. Sparks (talk) My preferred choice. Sure it could get repetitive and redundant, but it's worth it to document the abilities of these Glohm enemies.
  2. Camwoodstock (talk) We give articles to other stronger RPG enemy and boss variants, so why should Brothership be any different?
  3. Tails777 (talk) They are stronger variants with different stats to their originals, no different from every example Camwoodstock gave. Per proposal.
  4. DryBonesBandit (talk) Per all.
  5. Zootalo (talk) The Shiny Paper versions of enemies from Paper Jam have their own articles as well; this is no different. Per all.
  6. Nightwicked Bowser (talk) Probably best for overall consistancy with a game like this one.
  7. Technetium (talk) Per all.
  8. Cheat-master30 (talk) Given that some of them have specific differences in attack patterns, it seems like they should probably get unique articles.

Include Glohm enemy coverage on their normal counterparts' articles without creating new articles for them

Comments

@Zootalo The Paper Jam shiny enemies are not split, but the Sticker Star ones are.
The preceding unsigned comment was added by Nightwicked Bowser (talk).

Kinda torn to be honest. I voted yes because some of them have specific differences from their regular counterparts (Glohm Floopfly Rs and Glohm Soreboars always explode once defeated for example), but then we've got the weird situation of trying to figure out what exactly you'd include on a page for the enemies without these things, like the Glohm Palookas (which as far as I know, look and act almost identically to their standard counterparts). --Cheat-master30 (talk) 22:30, November 23, 2024 (EST)

In fairness, this could also be said about many other stronger variants of enemies. The only real difference between a Goomba and Gloomba are the color schemes, in a similar way to how the only difference between a Palooka and a Glohm Palooka is the darker coloration and Glohmy aura. It's kinda just a natural thing for most stronger variants (not all mind you, but most). Sprite of Yoshi's stock icon from Super Smash Bros. Ultimate Tails777 Talk to me!Sprite of Daisy's stock icon from Super Smash Bros. Ultimate

Removals

None at the moment.

Changes

Tag images of bind-posing models for reuploading

It's been two years since the previous proposal had passed. Now let's talk about tagging images of bind-posing models for reuploading. Take this image for example. As you can see, this image is a bind-posing model. Once this proposal passes, we'll be able to tag every bind-posing model with this:

{{image-quality|Bind-posing model; should be replaced with a rendered game model}}

That way, if a bind-posing model is reuploaded as a rendered game model that serves as a replacement, we'll be able to reuse it as an infobox image.

Proposer: GuntherBayBeee (talk)
Deadline: November 29, 2024, 23:59 GMT

Support

  1. GuntherBayBeee (talk) Per proposal

#ThePowerPlayer (talk) Like I said in the other proposal, T-poses are generally not how characters are supposed to look. If this is any indication, the wiki should favor game accuracy in images.

Oppose

  1. Nintendo101 (talk) I think it is great when users replace images of bind-posed (or "t-posed") models with organically rendered ones. It is a practice I personally encourage and welcome. However, I do think there can be educational and illustrative purposes to bind-posed models, and I think a blanket rule would put unnecessary pressure on the users of this site to render models when a bind-posed one can be more than serviceable, and may even discourage the cataloging of 3D assets in the future if a user cannot render them. Rendering models is a very time-consuming process, and I think it is healthier to just allow users to replace the bind-posed images we have if they can. Not require them to. Perfection is the enemy of the good.
  2. EvieMaybe (talk) this seems better handled on a case-by-case basis rather than a full sweep
  3. Waluigi Time (talk) Per all.
  4. Hewer (talk) Per all, a hard rule isn't necessary here.
  5. ThePowerPlayer (talk) Per all.
  6. Camwoodstock (talk) Per all, especially Nintendo101. Given there are scenarios where bind-posed/T-posed models are actually more illustrative than properly rigged alternatives, we should probably handle these on a case-by-case basis.
  7. Mario (talk) Tag them if they're bad quality, not because they're t-posed.

Comments

Wording should be changed to "bind pose" since not all characters are T-posed, especially non-bipeds (like Yoshi from Super Smash Bros. Melee or Brawl, Wiggler, Buzzy Beetles, Piranha Plants, and more) and A-pose exists as a default pose too. In addition, models technically aren't "t-posing", they're modeled this way before animations and a rig are applied to them, the wording makes them look like they're animating when they're not. BabyLuigiFire.pngRay Trace(T|C) 20:36, November 15, 2024 (EST)

Does this proposal advocate replacing these ripped models with ones that are posed from a screenshot or posed in a 3d program with ripped animation files? Not all models are ripped with animations, so it's a bit of a task to undertake if you really want models with animations AND a rig (let's not get started in lighting, which is a separate skillset that's demanded from renderers; not many people get the lighting very good, no offense!); a chunk of models tend to not have a rig, much less an animation. Additionally, some t-posed models are great to use when comparing models or viewing models as they are. File:MLNPC.png is an example where it's easy to compare the proportions of Mario, PC Luigi, and NPC Luigi. Sure, you can probably put them all in a orthographic lineup in the same keyframe of a shared animation, but due to the arms, legs, spine, and head all straightened out, it's better to illustrate in T-pose imo. Icon showing how many lives Mario has left. From Super Mario 64 DS. It's me, Mario! (Talk / Stalk) 21:00, November 15, 2024 (EST)

Miscellaneous

None at the moment.

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