MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
Tags: Mobile edit Advanced mobile edit
 
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.
''None at the moment.''
#Users then vote and discuss on the issue during that week. The "deadline" for the proposal is one week from posting at:
##Monday to Thursday: 17:00 (5pm)
##Friday and Saturday: 20:00 (8pm)
##Sunday: 15:00 (3pm)
#Every vote should have a reason accompanying it.
#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.
#"<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.
#There are two topics that cannot be decided on through a proposal: the first is sysop promotions and demotions, which are decided by [[MarioWiki:Bureaucrats|Bureaucrats]].  Secondly, no proposals calling for the creation of Banjo, Conker or Sonic series articles are allowed (several proposals supporting them have failed in recent history).


The times are in EDT, and are set so that the user is more likely to be online at those times (after work/school, weekend nights).  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 a minute later, the deadline is a day plus 15 hours (Sunday), as opposed to a day minus 4 hours.
==New features==
===Create articles for Glohm enemies or merge them with their normal counterparts===
{{early notice|November 28}}
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.


__TOC__
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:


<center><span style="font-size:200%">CURRENTLY: '''{{LOCALTIME}}, {{LOCALDAY}} {{LOCALMONTHNAME}} {{LOCALYEAR}} (EDT)'''</span></center>
1. '''Glohm enemies get their own articles.''' They get their own dedicated pages.


==New Features==
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.
''None at the moment.


==Removals==
Let's see what happens!
=== Trouble Center ===
*Too sporadically used: basically on average once a month
*Most of the uses are incorrect &ndash; user or syntax related instead of articles
*The troubles are rarely solved
*Users usually ask directly on user talk and get a faster solution that way, because watchlist notification < user talk notification


'''Proposer''': {{User|Wayoshi}} <br>
'''Proposer''': {{User|Sparks}}<br>
'''Deadline''': October 11, 2008, 20:00
'''Deadline''': December 5, 2024, 23:59 GMT


==== Put it to Rest ====  
====Create new articles for Glohm enemies====
#{{User|Wayoshi}} &ndash; hope the bulleted list helps convince others
#{{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|Stooben Rooben}} - I've been thinking about this for a long time. I hardly see anyone ever use it, and when they do, their trouble(s) are never answered. Most people ask a Sysop or experienced member on his/her talk page more commonly, as Wayoshi said. People are more apt to get a fast response that way, than with a dead trouble center. I for one never used it; I always asked someone else for help, as many others have done with me.
#{{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|Iggykoopa}} Per all
#{{User|Tails777}} They are stronger variants with different stats to their originals, no different from every example Camwoodstock gave. Per proposal.
#{{User|Super-Yoshi}} - Per St00by. Holy crap I also agree with Wayoshi :O (for the first time :O)
#{{User|DryBonesBandit}} Per all.
#{{User|Princess Grapes Butterfly}} Per all. It hasn't been used in months.
#{{User|Zootalo}} The Shiny Paper versions of enemies from Paper Jam have their own articles as well; this is no different. Per all.
#{{user|Time Q}}: Per Wayo. We've [[MarioWiki:Proposals/Archive 1#Trouble Center|had this before]], and decided to try a comeback. There was no comeback, so I think it's finally time to bury it.
#{{User|Nightwicked Bowser}} Probably best for overall consistancy with a game like this one.
#{{User|Palkia47}} - Its useless. As already stated, its hardly used anymore; and when any user puts a question up; it's hardly answered.
#{{User|Technetium}} Per all.
#{{user|Phailure}} Per all, it definetly is easier to use user talk.
#{{User|Cheat-master30}} Given that some of them have specific differences in attack patterns, it seems like they should probably get unique articles.
#{{User|Mateus 23}} Per all.
#[[User: Booster|Booster]] - I sometimes forget that it even exists. Anyways, it's been pretty useless for over a year.
#{{user|InfectedShroom}} - Ay. Let's be rid of it.
#{{User|The Gravitator}} - I barely knew it existed until this proposal. 0_o
#{{User|1337Yoshi}} - Per all. In the year I've been here, I've never seen it used. Of course, once we do delete it, someone's gonna think of a use for it, but... :P
#{{User|Stumpers}} - Let's delete it, but we should make it clear to new users that they can ask for help on the Main Page talk if they don't know any users to ask.
#{{User|Luigi001}} Per all. It's nothing but a waste of space. No one uses it, so it's time to let it go.
#{{User|RAP}} Per all who shall tear it down! (not really though, XD)
#{{User|Walkazo}} - Per all. If people need help but don't know who to ask specifically, the Main Page talk and/or [[MarioWiki_talk:FAQ]] should be enough to take care of them.
#{{User|Dom}} - Per all. I looked at it once ages ago and noticed its lack of action and accuracy, so yeah.
#{{User|Tucayo}} - Per Stooben Rooben
#{{User|tanokki}} -I used It ''once'' , the last time I bothered looking almost ''all'' from when I first joined were still there,and finally no ones used It.We gave it a chance worked for a while and crashed.Per all.
#{{User|Yoshikart}}Per 1337. It's never been f***ing used.  


==== Keep it Running ====
====Include Glohm enemy coverage on their normal counterparts' articles without creating new articles for them====
#{{User|Magitroopa}} - Really bad idea. It's like you don't care about newbies.
 
==== Comments ====
{{User:Magitroopa/sig}}: Even though all of the above is true, It's still pretty useful.
:Like I said in my post, new users should post concerns on [[Talk:Main Page|this page]] or alert one of the sysops - that's what we're here for. {{User|Stumpers}}
::Or if you need help with something else, you can always contact [[Special:Listusers/Sysop|one of us]]. {{User|Stooben Rooben}}
:::We even mention that on the welcome template, so we actually do care about new users. {{User|Stumpers}}
::::Yeah. Like everyone said, people rarely respond to to the trouble center. We're HELPING newbies. {{User|1337Yoshi}}
 
==Splits & Merges==
===Merge Goomba with bellhop goomba===
I feel we should merge bellhop goombas with regular goombas Because they are just goombas in bellhop suits also They are the same thing just differnt looks.
 
'''Proposer''': {{User|Iggykoopa}}<br>
'''Deadline''': October 11, 2008, 20:00
====Merge====
#{{user|Iggykoopa}} Per what i said.
#{{user|Phailure}} Per Iggy. There's not really any basic proof they're any different, so merge it is. EDIT:See below proposal. :P
#{{user|Cumoriasiome}} they sould merge, as the bellhop goomba page even says there is no difference besides looks.
 
====Keep Separate====
#{{User|Super-Yoshi}} No, they are considered a sub-species of Goomba's.
#{{User|Stooben Rooben}} - Per S-Y. Plus, they are officially named.
#{{User|Princess Grapes Butterfly}} Per S-Y! No just no. There '''not''' Goomba there a sub-species like S-Y said.
#{{User|Palkia47}} - Per S-Y. They're different from regular Goombas and are a different species (but, rather called "sub-species"; as said by PGB above). While they '''act''' like a Goomba; and '''attack''' like a Goomba; they are '''not the''' regular Goomba.
#{{User|Walkazo}} - Per all. Plus, this would requie merging [[Rhinestone Goomba]]s, and perhaps other obscure ''[[Hotel Mario]]'' sub-species that have slipped my mind...
#{{User|Stumpers}} - I'm not sure why they should be merged and not [[Pirate Goomba]]s, so it makes me worried that this is either about limiting ''[[Hotel Mario]]'' content or will lead to limiting content rather than merging alternately dressed Goombas.
#[[User: Booster|Booster]] - Per all. Bellhop Goomba is a Bellhop Goomba.
#{{User|Grandy02}} - They are officially named and look different from the ordinary Goombas. They might act like the normal Goombas, but a lot of enemies have similar patterns.
#{{User|InfectedShroom}} - Per All.
#{{User|1337Yoshi}} - Per all.
#{{User|Mateus 23}} - Per all.
#{{User|Dom}} WTFudge!? per all.
#{{User|Ameboid}} - Keep itself at his place. Otherwise we would have a Goomba page longer than Mario. Also many Koopa or whatever sub-species are kept seperate. So let's do it here, too.


====Comments====
====Comments====
Think about it guys we merged Pumpkin Heads with goombas and there way differnt so we should merge bellhop goombas because they are not any differnt from regular goombas. - {{User|Iggykoopa}}
{{@|Zootalo}} The Paper Jam shiny enemies are not split, but the Sticker Star ones are. {{Unsigned|Nightwicked Bowser}}
:Pumpkin heads weren't officially-named though. {{User|Stooben Rooben}}
::Per St00by. If it isn't official, then they don't have an article about it. And just a tip, try to outline your proposal with more details instead of just two simple sentences. For Example, St00by's proposal has many details and whatnot in it. {{unsigned|Super-Yoshi}}


As far as I know, you can't remove the "Protection" of the Bellhop Goombas, unlike the Pumpkin head. Just throwing that out. {{User|Blitzwing}}
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)
:Oh well that was kinda embarrasing, not signing my comment just like that :o. And Per Blitz {{User|Super-Yoshi}}
: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}}
::Hey Grapes, whos this '''Y-S''' guy? he sounds pretty neat. I wanna meet him :D {{User|Super-Yoshi}}
:::'''ROFL...''' {{User|Stooben Rooben}}


Oh crud I didn't notice that till nao. (ROFL...LOL) XD Sry 'bout that I'll fix it. {{User|Princess Grapes Butterfly}}
===Create a template to crop images on-the-fly without having to tamper with the base file's dimensions===
:lol np {{User|Super-Yoshi}}
So {{user|Wildgoosespeeder}} shared this nifty template that TCRF has: [[tcrf:Template:CSS image crop]], which allows images to be displayed in mainspace at a cut-out size from how they are on the image files themselves. This has two utilities: one is shrinking to a relevant entity in group textures such as {{file link|M&SatL2012OG Wii audience.png|this one}}, and the other is to avoid blank space without having to crop the raw graphic parameters - thus allowing best-of-both-worlds for the previous proposal I attempted (and failed), as it satisfies the OCD itch of avoiding bad and/or inconsistent crops on the base files without taking up unnecessary space where the images are actually used. It also removes a lot of unnecessary work actually cropping/uncropping images since you don't have to save them to a machine/web address to upload a new version - you can just put in the parameters you want and go from there.


::Okay I fixed it. :p {{User|Princess Grapes Butterfly}}
'''Proposer''': {{User|Doc von Schmeltwick}}<br>
'''Deadline''': December 11, 2024, 23:59 GMT


Iggykoopa Wait so your tellling me bellhop goombas are a sub species when they act the same and are just goombas in hotel outfits. But the pumpkin heads are not a sub species well there are no simularets beetween goombas and pupkin heads also one hit for bellhop goombas and goombas while it takes two for pumpkin heads
====C-S-Yes====
#{{User|Doc von Schmeltwick}} - Goes without saying I think this is a good idea.
#{{user|Super Mario RPG}} Sounds like a reasonable compromise.
#{{User|Jdtendo}} It's better to crop an existing image programmatically than having to upload a cropped version for a specific use case.
#{{User|Ahemtoday}} Per proposal.
#{{User|Pseudo}} Seems useful.


Um exscuse me, but umm pumpkin heads '''are''' Goombas. If you star spin them, the pumkin breaks revealing a regular Goomba. (See [[Talk:Pumpkin Head]]) {{User|Princess Grapes Butterfly}}
====No new template====


Iggykoopa, instead of putting your name before your message, please put this at the end of your message: ''<nowiki>{{User|Iggykoopa}}</nowiki>''. Also please post new comments at the bottom. Thanks! {{user|Time Q}}
====Comments on CSS image crop====
This appears to be similar to [[Template:Squared icon|a template I have made]] in order to crop images to perfectly squared off icons for uses on pages such as [[Pipe Frame]] (e.g. displaying Mii Racing Suit icons in the same table as other character icons); however, the version you're presenting seems to include more options. I'm not gonna vote yet, but so far I don't see the harm to have this other template too. {{User:Arend/sig}} 06:42, November 27, 2024 (EST)


Iggy, just to clarify, "sub-species" is just a fan word used to describe an enemy or species that is obviously a modification of another species.  For example, Paragoombas are obviously the developers referencing back to Goombas and Paratroopas.  Honestly, we use it way too much, and as I can tell from your confusion, it really is misleading.  "Associated Enemies" would be a better, albeit vaguer, term. {{User|Stumpers}}
==Removals==
''None at the moment.''


Wait so your telling me the bellhop goombas are sub sprcies when on the page you say there is no difference but the pumpkin head goombas are not just becayuse they were never named {{User|Iggykoopa}}
==Changes==
 
===Tag images of bind-posing models for reuploading===
Um please sigh your comments. Thanks! {{User|Princess Grapes Butterfly}}
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:


Ok just to set the record straghit i do not want to merge rhinestone goombas with regular goombas and the reason being they are much faster then regular goombas also they act differnt. {{User|Iggykoopa}}
{{tem|image-quality|Bind-posing model; should be replaced with a rendered game model}}


To your point Princess Grapes Butterfly  think of this if you hit a winged goomba does it become a regular goomba yes but does that mean they should be merged no so by that logic we should un merge pumpkin head goombas and regualr goombas.{{User|Iggykoopa}}
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.
:Please try to use more full stops in your comments so they are easier to read, Iggykoopa. Thanks. {{User|Stooben Rooben}}


Uh they are merge. {{User|Princess Grapes Butterfly}}
'''Proposer''': {{User|GuntherBayBeee}}<br>
:What? {{User|Stooben Rooben}}
'''Deadline''': November 29, 2024, 23:59 GMT
The Pumpkins Heads. {{User|Princess Grapes Butterfly}}
:Ah. I thought you were referring to Bellhop Goombas. {{User|Stooben Rooben}}
::No. :D {{User|Princess Grapes Butterfly}}


===Spliting goombas and pumpkin Head goombas.===  
====Support====
I feel we sould unmerge goombas and pumpkin head goombas because they are differnt from regular goombas For two reasons first they look differnt and they are stronger and second on the whole if you star spin them they become regular goombas that is true but think of this if you hit a winged goomba it becomes a regular goomba but do we merge it with regular goombas no.
#{{User|GuntherBayBeee}} Per proposal
<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>


'''Proposer''': {{User|Iggykoopa}}<br>
====Oppose====
'''Deadline''': October 12, 2008, 15:00
#{{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|EvieMaybe}} this seems better handled on a case-by-case basis rather than a full sweep
====Unmerge====
#{{User|Waluigi Time}} Per all.
#{{user|Iggykoopa}} Per what i said.
#{{User|Hewer}} Per all, a hard rule isn't necessary here.
 
#{{User|ThePowerPlayer}} Per all.
====Stay merged====
#{{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|Stumpers}} - We merged them because Nintendo themselves never separated Pumpkin Heads from Goombas - that was our own speculative decision. However, the other Goombas have specifically been given official names, and we feel that we should respect Nintendo's decision by giving separate articles to subjects with different names except when two subjects are way too similar (ie two enemies that always work together, for example)
#{{User|Mario}} Tag them if they're bad quality, not because they're t-posed.
#{{User|Stooben Rooben}} - Per Stumpers. They were never officially named, thus they were merged. Pumpkin Goomba is not a Pumpkin Goomba &ndash; it is just a Goomba.
#{{User|Super-Yoshi}} - Look, they were named officially, if you didn't read the page, or our comments on your other proposal. Also Per Stumpers.
#{{User|Princess Grapes Butterfly}} Per all! They're just Goombas with '''head''' '''armor'''! It doesn't change there species.
#{{User|Dom}} - Per Stumpers. (he always makes good points)
#{{User|1337Yoshi}} - Per Stumpers. I mean, we don't have an article for SMG's helmeted Goombas, now, do we?
#{{User|Mateus 23}} - Per Stumpers and Princess Grapes.


====Comments====
====Comments====
Like i said if you jump on a winged goomba they become regular goombas but do we merge them no so with that logic we should not merge regular goombas and pumpkin head goombas. Iggykoopa
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)
 
But think of this those fish things you Call ????  Have there own page when one is just a blurp with a sharkfin also there are some you merged even with the fact that they have names like pat-the-bats. Iggykoopa
 
Ok but on that point they never called them goombas so they should just be called pumpkin head goombas Iggykoopa
 
Heres just a tip Iggy, get some facts about what your going to write a proposal about, create it in a proffesionally looking way (eg: using full stops, adding puncuation, grammer, etc.) so we can get more detail on what your implying too. You should get to know what your going to propose about before writing a proposal. Nothing personal, just a tip. Lol I just noticed, everyone whos opposing starts with an "S". And Btw Iggykoopa, {{User|Time Q}} asked for you to follow the proposal rules, and use ''<nowiki>{{User|Iggykoopa}}</nowiki>'' instead of signing it with just ''Iggykoopa''. So I ask nicely to sign it with the proper format, please. Thanks. {{User|Super-Yoshi}}
 
Ok first of all super-Yoshi Dont tell me what i should and should not do i made this proposal and to say i do not know what im talking about well screw you. Also Think of this your whole thing on nintendo never named them is funny because why should that matter i mean because think about it bellhop goombas were never in a nintendo game There for there not nintendo charecters. {{User|Iggykoopa}}
:Bellhop Goombas were in Hotel Mario, a NINTENDO game. And your banned now. Come say "Screw you" to my face next time, k? Ill deal with it. {{User|Super-Yoshi}}
::Aww man, I was about to chastize him (have I ever mentioned how I hate Edit Conflicts?)... Anyway, Nintendo didn't actually make ''[[Hotel Mario]]'', but it's still a ''Mario'' game and everything in it is as official as Mario himself. And in response to Iggy's other arguments: we have an article for [[????]] because that's what the Blurp with a sharkfin on it's back is called in ''[[Mario & Luigi: Superstar Saga]]'', whereas "Pumpkin Goomba" was pure conjecture. And as for [[Pat the Bat]]s, it doesn't matter how silly the name is, it's still their name; they're still valid enemies. - {{User|Walkazo}}
 
The Pumpkin heads can have their protections removed and be turned into normal Goombas, you might say the same about the Para-Goombas, but they appeared in a dozen of games, and they have an ''actual'' name. --[[User:Blitzwing|Blitzwing]] 06:47, 6 October 2008 (EDT)
:Now wait just a minute. If you remove a Bellhop Goomba's uniform, it turns into a noral Goomba. So why are we voting to NOT merge Goomba and Bellhop Goomba? {{User|Phailure}}
::The Bellhop Goombas uniform can't be removed ingame (Man that sound perverted), duuuurrrrrrrr. --[[User:Blitzwing|Blitzwing]] 07:46, 8 October 2008 (EDT)
:::Touche. But still, why merge Pumpkin Heads and not Bellhop Goombas? {{User|Phailure}}
 
See Knife quote in [[Talk:Pumpkin Head]]s {{User|Princess Grapes Butterfly}}


=== Goombas ===
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)
I say we should split the Goomba article into two articles: Goomba and Goomba (SMW). The SMW Goombas appeared in more than one game (Seriously, I've seen round ones in Super Mario Galaxy), they have differend Japanese names and they look different, unlike the Bellhop Goomba proposal (see below) and I hope this is not like Arend's disaster Rosalina proposal.
 
'''Proposer''': {{User|Yoshikart}} <br>
'''Deadline''': October 15, 2008, 17:00
 
==== Split ====
#{{User|Yoshikart}} This is my proposal.
#{{User|Stumpers}} - I'm not sure that they were in ''Super Mario Galaxy'' not having played the whole game, but yes, ''Super Mario World'' did feature "Round Goombas" rather than "Goombas" in the Japanese version.  Just as we separate Kamek from Magikoopa (he is known only as Magikoopa in Japan), maybe it's time that we also pay attention to how Nintendo of Japan names separate subjects.
#{{User|Walkazo}} - Per all.
#{{User|Stooben Rooben}} - Per all. Since they are officially named, I have no objections.
#{{User|InfectedShroom}} - Per all. I wondered why I couldn't find info on those guys... :P
#{{User|Blitzwing}} - Per All. btw, There's indeed a different species of Goomba in Galaxy, but they're not round, just smaller and with a duller skin.
#{{User|Ameboid}} - Per all. The thing about the Goombas in SMG is indeed correct.
 
==== Keep Together ====
 
====Comments====
Ain't and round Goomba basicly a Goomba or a sub species. (I'm sorta confused.) {{User|Princess Grapes Butterfly}}
:'''To the supporters''': Do these have an official name? {{User|Stooben Rooben}}
::They do in Japan (as both Yoshikart and Stumpers mentioned): "Kuribon", which should be enough to allow the split. While we're on the subject, another enemy I know that clearly is not the same species as its name-sake is ''[[Mario & Luigi: Superstar Saga]]'' [[Boomerang Bros.]]; but as far as I know, the Japanese names are the same as well, so it's more problematic. - {{User|Walkazo}}
:::Thanks. {{User|Stooben Rooben}}
 
 
Say, if this proposal pass, would the page be called '''Kuribon''' or '''Goomba (SMW)'''? {{User|Blitzwing}}
 
[[Image:RoundGoomba.png|50px]] <- Is this what your talking 'bout. Anyway doesn't '''Kuribon''' means Little Chestnut people. {{User|Princess Grapes Butterfly}}
 
:I would call it "Goomba (SMW)" because of the fact many people don't know the Japanese name (Kuribon), so they compare their look. And, what do they look like? They look like little Goombas. Of course, there are some experts knowing the Jap. name but we simply redirect to 'Goomba (SMW)'. My opinion. - {{User|Ameboid}}
 
==Changes==
=== Userbox Page ===
Recently, I stopped by the userbox page and found it to be absolutly unacceptable. Users add new userboxes at will, and often don't care for things such as, I dunno, GRAMMAR? So, I'm prposing that we lock up the Userbox page or at least trim it down. If you want to make a new userbox so badly, don't place it on the main page.
 
'''Proposer''': {{User|Phailure}} <br>
'''Deadline''': October 15, 2008, 17:00
 
====Lock the page====
 
====Don't lock====
#{{User|Stumpers}} - <s>Right now I'm busy enough operating the rest of the Wiki, but maybe the other sysops aren't.  Regardless, I have to say, userboxes themselves are useless, so I don't see why a useless userbox would be a problem.  Plus, what are your criteria for determining whether a userbox is useless or useful?</s> Since other sysops are cool with trimming the page down, I no longer object. However, I'm keeping this vote here for everyone who "per'd" me.
#{{User|Princess Grapes Butterfly}} Per Stumpers. Anyways why lock just because if some userboxes seem useless. There just for user whom want them. You don't have to use the new ones that just pop up. The userboxes page is for every user to post a userbox (as long as there aproperate.)
#{{User|Palkia47}} - Per Stumpers. Userboxes are epic, and someone may want to create their own.
#{{User|Super-Yoshi}} - Per Stumpers and Grapes.
#{{User|M&SG}} - As long as the userbox is appropriate, I don't see the problem.  Besides, even if that article is locked, we'll still be able to make our own personal userboxes for our user page.
 
====Trim down====
#{{User|Phailure}} Per what I said.
#{{user|tanokki}} -Both sides have a good point we should have criteria for userboxes {ie:This user likes luigi. '''OK'''. This user is friends with [insert username here]. '''NO'''} It shouldn't be that hard delete some keep others and we really need to trim down the userbox section other [I had to remove my own cose the page had trouble loading].
#{{User|Stooben Rooben}} - That page has been chaotic for quite a few months now. Many of the userboxes on there aren't needed, as they are simply edited from other similar userboxes. Also, the "This user is friends with __" have absolutely no reason to be on there; these userboxes, if created, should be created only for users to give to their friends. (Just like I used to do.) The page takes ridiculously long to load due to the mass amounts of images and coding on it as well. It's a '''MarioWiki''' page, not a '''User''' page. It's a fine page for referring to how to make basic userboxes, (ex: This user is an advanced gamer), etcetera. These userboxes that say, "this user's favorite character is Mametchi/Luigi/Francis/whatever" are entirely unnecessary &ndash; there only needs to be one userbox for that "genre" of userboxes &ndash; '''This user's favorite character is ___'''. The userbox can be edited from there to the user's liking. Take my userbox tower for example: Most of the userboxes on there were created/edited by me, but I don't recall ever putting them in the [[MarioWiki:Userbox|userbox]] page.
#{{User|Phoenix Rider}} - This is definitely something that needs to be done. As Stooben said, '''one''' genre of userboxes that can be customized to the user's liking. Specific, one person/object/etc. userboxes should not be put of there.
#{{User|Blitzwing}} - Per Stooben. Took the words right out of my mouth.
 
====Comments====
Okay, I take that back. But if you had stopped by before I cleaned it up, you'd see how atrocious it's become. {{User|Phailure}}
:Rather than locking the page, what about just eliminating all of the excess userboxes? Take [[MarioWiki:Userbox#Characters|this]], [[MarioWiki:Userbox#Specific Games (A-Z)|this]], and [[MarioWiki:Userbox#Other|this]] for examples: they could easily be trimmed down to basic userboxes that could be edited to a user's liking. Also, if there was a "Trim Down" option on this proposal, I'd vote for it. {{User|Stooben Rooben}}
::Same here. The Sysops have enough things to do without having to worry about something as frivolous as Userboxes. Simply let the Users who care about Userboxes keep them tidy, and be done with it. - {{User|Walkazo}}
:::But that's the whole point. The page '''isn't''' kept tidy. It overloads the bandwidth with all the pictures and code, and most are used by maybe one or two people: the people that made them and decided to stick them on there. I have plenty of userboxes that I created myself without needing to put it on the Userbox page. {{User|Phoenix Rider}}
::::Walkazo: You've conivinced my to change my mind. Now that I think about it, sysops DO have better things to do :l Phoenix Rider: Ditto. Palkia47:True, but they still don't need to clog up the page.{{User|Phailure}}


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

Latest revision as of 12:42, November 28, 2024

Image used as a banner for the Proposals page
Current time:
Thursday, November 28th, 20:22 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

If someone has 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 other users, who will then vote on whether or not they think the idea should be implemented. 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}}.

Rules

  1. Only autoconfirmed users may create or vote on proposals. Anyone is free to comment on proposals (provided that the page's protection level allows them to edit).
  2. Proposals conclude 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.
  3. Users may vote for more than one option, but they may not vote for every option available.
  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 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.
  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 "(blocked)" 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. Proposals cannot contradict an already ongoing proposal or overturn the decision of a previous proposal that concluded less than four weeks (28 days) ago.
  8. 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.
    • Tag the proposal with {{early notice}} if it is on track for an early close. Use {{proposal check|early=yes}} to perform the check.
  9. 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.
  10. If a proposal reaches its deadline and there is a tie for first place, then the proposal is extended for another week.
  11. 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.
  12. 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.
  13. 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.
  14. After a proposal passes, it is added to the appropriate list of "unimplemented proposals" below and is removed once it has been sufficiently implemented.
  15. 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.
  16. 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.
  17. 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.
  18. Proposals cannot be made about promotions and demotions. Staff changes are discussed internally and handled by the bureaucrats.
  19. No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
  20. 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 28, 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. All of the above proposal rules also apply to talk page proposals. 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

  • Determine how to handle the Tattle Log images from Paper Mario: The Thousand-Year Door (Nintendo Switch) (discuss) Deadline: November 30, 2024, 23:59 GMT
  • Merge False Character and the Fighting Polygon/Wireframe/Alloy/Mii Teams to List of Super Smash Bros. series bosses (discuss) Deadline: December 2, 2024, 23:59 GMT
  • Move Kolorado's father to Richard (discuss) Deadline: December 11, 2024, 23:59 GMT

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

None at the moment.

New features

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

Based on the early vote, this proposal may be eligible to close one week early. Please use {{proposal check|early=yes}} on November 28 at 23:59 GMT and close the proposal if applicable.

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

Create a template to crop images on-the-fly without having to tamper with the base file's dimensions

So Wildgoosespeeder (talk) shared this nifty template that TCRF has: tcrf:Template:CSS image crop, which allows images to be displayed in mainspace at a cut-out size from how they are on the image files themselves. This has two utilities: one is shrinking to a relevant entity in group textures such as this oneMedia:M&SatL2012OG Wii audience.png, and the other is to avoid blank space without having to crop the raw graphic parameters - thus allowing best-of-both-worlds for the previous proposal I attempted (and failed), as it satisfies the OCD itch of avoiding bad and/or inconsistent crops on the base files without taking up unnecessary space where the images are actually used. It also removes a lot of unnecessary work actually cropping/uncropping images since you don't have to save them to a machine/web address to upload a new version - you can just put in the parameters you want and go from there.

Proposer: Doc von Schmeltwick (talk)
Deadline: December 11, 2024, 23:59 GMT

C-S-Yes

  1. Doc von Schmeltwick (talk) - Goes without saying I think this is a good idea.
  2. Super Mario RPG (talk) Sounds like a reasonable compromise.
  3. Jdtendo (talk) It's better to crop an existing image programmatically than having to upload a cropped version for a specific use case.
  4. Ahemtoday (talk) Per proposal.
  5. Pseudo (talk) Seems useful.

No new template

Comments on CSS image crop

This appears to be similar to a template I have made in order to crop images to perfectly squared off icons for uses on pages such as Pipe Frame (e.g. displaying Mii Racing Suit icons in the same table as other character icons); however, the version you're presenting seems to include more options. I'm not gonna vote yet, but so far I don't see the harm to have this other template too. ArendLogoTransparent.pngrend (talk) (edits) 06:42, November 27, 2024 (EST)

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=4446457"