MarioWiki:Proposals

Current time: Saturday, December 21st, 13:58 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.

If you would like to get feedback on an idea before formally proposing it here, you may do so on the proposals talk. For talk page proposals, you can discuss the changes on the talk page itself before creating the TPP there.

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 formatting

Below is an example of what your proposal must look like. If you are unsure how to set up this format, simply copy the following and paste it into the fitting section. When updating the bracketed variables with actual information, be sure to replace the whole variable including the square brackets, so "[insert info here]" becomes "This is the inserted information" and not "[This is the inserted information]". Proposals presenting multiple alternative courses of action can have more than two voting options, but the objective(s) of each voting option 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|{{subst:REVISIONUSER}}}}<br>
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT

====[option title (e.g. Support, Option 1)]: [brief summary of option]====
#{{User|{{subst:REVISIONUSER}}}} [make a statement indicating that you support your proposal]

====[option title (e.g. Oppose, Option 2)]: [brief summary of option]====

====Comments ([brief proposal title])====

Autoconfirmed users will now be able to vote on your proposal. Remember that you can vote on your own proposal just like the others.

To vote for an option, just insert #{{User|[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 simply say "Per 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

• Move Shadow (character) to Shadow (Sonic the Hedgehog) (discuss) Deadline: December 23, 2024, 23:59 GMT
• Move "Rare Ltd." to "Rareware" or "Rare" (discuss) Deadline: December 25, 2024, 23:59 GMT
• Make changes to List of Smash Taunt characters (discuss) Deadline: December 27, 2024, 23:59 GMT
• Tighten Category:Deceased characters (discuss) Deadline: December 27, 2024, 23:59 GMT
• Merge Cascading Stone, vanishing platform, and moon platform with Falling Platform (discuss) Deadline: December 28, 2024, 23:59 GMT
• Add to-do tasks on the Main Page (discuss) Deadline: January 1, 2025, 23:59 GMT
• Rename the NES Template (discuss) Deadline: January 4, 2025, 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)

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)

Split major RPG appearances of recurring locations, EvieMaybe (ended December 16, 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)

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)

Determine how to handle the Tattle Log images from Paper Mario: The Thousand-Year Door (Nintendo Switch), Technetium (ended November 30, 2024)

Merge False Character and Fighting Polygon/Wireframe/Alloy/Mii Teams into List of Super Smash Bros. series bosses, Doc von Schmeltwick (ended December 2, 2024)

Writing guidelines

None at the moment.

New features

None at the moment.

Removals

None at the moment.

Changes

Consistent formatting for the Other Languages section

Alright, so since this is starting to get really annoying, I'm going to put this proposal here. Here are two inconsistent ways that the meaning of names in the "Names In Other Languages" section are listed on the wiki:

1. "name" (meaning)
2. name ("meaning")

Now, almost all the pages on the wiki already have Option 1 for their formatting, but for some reason some other users think that they should all be changed to look like Option 2, even though Option 1 already works just fine and there's no point in putting asterisks between one single word if it's already in between paragraphs. But, what do you guys think, which way of displaying the Other Names section do you think would be better?

Proposer: Annalisa10 (talk) (banned)
Deadline: February 7, 2024, 23:59 GMT

Change all Other Languages sections to Option 2

1. Super Mario RPG (talk) I prefer this option so that this way, both languages are formatted and appropriately in a distinct manner from one another.
2. Koopa con Carne (talk) Per my vote in this proposal and my general distaste for the “we’ve always done it this way, which automatically makes it the right way” argument.
3. PnnyCrygr (talk) Per All. I think, this second option is a more academic style than the first. I like the fact that the foreign name is italicized to make sense that it is foreign.
4. Yook Bab-imba (talk) How I've always formatted it, and my preferred style.
5. PhGuy12 (talk) Per all.

Comments

So, for clarification, what vote is the oppose part of the proposal? Mario^-HOHO! (Talk / Stalk) 22:07, January 30, 2024 (EST)

I'm just writing here because I'm stuck in the middle about this. Keeping the first option would mean that we don't have to go and change the formatting of most "Names in other languages" sections (which would obviously take an incredibly long time), but on the other hand, option 2's formatting style is clearer to read. I will vote later once I decide. -- FanOfRosalina2007 (talk · edits) 22:10, January 30, 2024 (EST)

I'm more of a "who cares?". It's like hand wringing over if a date in a citation should have parentheses or not. I don't see the point in adopting italics or not. Either way works in this case. Just keep it consistent in one table. But across the wiki? Meh. Mario^-HOHO! (Talk / Stalk) 22:16, January 30, 2024 (EST)

I'm in the exact same camp. I don't see a problem with either option, so I'm hesitant about having to choose which one we should use. If the proposer won't include a "Do nothing" option here for whatever reason, I would rather abstain from voting. rend (talk) (edits) 08:37, January 31, 2024 (EST)

There is, however, a conventional and consistent way to format these things. Doing nothing would just give way to pointless edit wars with users who refuse to acknowledge that. -- KOOPA CON CARNE 08:41, January 31, 2024 (EST)

I'm also far less motivated to vote given that this proposal about a naming style was made way too soon after the creator's block expired, which the block was from edit warring and general hostility to other users on the Wow Bud (history) page over naming style. That this proposal includes taking swipes at users that disputed the edits on that page does not help convince me that this proposal was made in good faith. Please maintain your conduct. Mario^-HOHO! (Talk / Stalk) 22:26, January 30, 2024 (EST)

Oh, I didn't know that. I'll still consider this, but I may leave it up to everyone else. -- FanOfRosalina2007 (talk · edits) 23:31, January 30, 2024 (EST)

...honestly, the fact that this proposal is a follow-up from an edit war that the proposer was responsible for and got blocked for, and being made directly after the block had ended and being made just because they disagreed on a certain thing that made them edit war (and also seems to be a response to a previous proposal they disagreed with and didn't know about until the edit war was escalating)... makes me want to choose a side even less than I already do now (and I didn't want to choose a side to begin with). Where's the "I'm fine with either way" option? rend (talk) (edits) 08:48, January 31, 2024 (EST)

Aren't proposals with multiple/either-or answers required to have a "do nothing" option, anyways? ~Camwoodstock (talk) 11:25, January 31, 2024 (EST)

Yep, rule 18 says "Proposals must have a status quo option (e.g. Oppose, Do nothing) unless the status quo itself violates policy." There definitely has to be a "do nothing" option here. MegaBowser64 (talk) 13:34, January 31, 2024 (EST)

Okay, what should we do about this then? If the proposal setup breaks the rules, then I'm not voting until it's fixed (and honestly, I might not vote anyway, as I never edit the "Names in other languages" sections). A proposal that is set up simply because someone's upset about not getting what they want through an edit war is not something I want to get involved in. -- FanOfRosalina2007 (talk · edits) 20:02, January 31, 2024 (EST)

Isn't settling disputes like that the whole point of a proposal? Hewer (talk · contributions · edit count) 12:24, February 1, 2024 (EST)

Yeah, no harm really in them creating a proposal about the matter. However, they're basically asking "should we carry out my idea in x form or y form" without even giving an option for anyone that disagrees with the idea. Would it be acceptable for a user other than the proposer to create a "do nothing" option, on the grounds that the proposal in its current form goes against the rules? MegaBowser64 (talk) 13:33, February 1, 2024 (EST)

Proposals are intended to settle disputes but in good faith like "we disagree on this, let's hash out with the community to see which one of us has a stronger stance". The timing of this proposal from the user's history and rhetoric in the proposal don't work in the user's favor, and I really don't want proposals to be a kind of combative medium where you fight "enemies" to "win". Sure, discussions get heated and anxiety inducing and super frustrating. But you really shouldn't be trying to attack users while writing a proposal on heels of a disagreement, it casts perception of good faith in doubt imo. Mario^-HOHO! (Talk / Stalk) 16:28, February 1, 2024 (EST)

So...couldn't anyone just add the status quo option in for the proposer? I'm pretty sure I've seen that happen before. Sometimes, you know, it slips your mind, or you have other things going on where proposal developments don't have your attention. LinkTheLefty (talk) 06:06, February 2, 2024 (EST)

I still feel like assuming bad faith in this case is a bit of a stretch when they didn't really "attack" anyone in the proposal, just pointed out the disagreement (and also didn't even vote in the proposal anyway). Hewer (talk · contributions · edit count) 10:22, February 2, 2024 (EST)

@LinkTheLefty yeah, I think it would be fine to add the status quo option, stuff like that has been done before. I'd be all for voting for that option when it gets added. MegaBowser64 (talk) 14:30, February 2, 2024 (EST)

I'm just gonna say it again: a "Do Nothing" option would just give way to more pointless edit wars. That concern is also what guided much of the opposition in a previous proposal that sought to loosen restrictions for British English spellings in wiki text. Regarding the subject of the current proposal, there is a conventional, widespread way to format words depending on their nature and purpose: foreign words should be in italics to make it clear they're foreign, and words that are being separated from the rest of the others for an explanatory purpose should be in quotation marks. Regardless of that, the idea that articles can be consistent only within themselves and not across the entire wiki is a questionable point of view to have; having an ambiguous outlook for a medium that's supposed to be encyclopedic is anything but encyclopedic. In the words of 7feetunder (concerning the aforementioned proposal on British English spelling): "how do we decide who's right and who's wrong if we don't have a preference? If the answer is 'first come, first serve', the worst solution ever to anything on a wiki, then no thanks". Let's settle on one formatting option or another. -- KOOPA CON CARNE 15:06, February 2, 2024 (EST)

Provide more context as to Mario entities' roles in Minecraft

In Minecraft's Super Mario Mashup, which gets (relatively) full coverage here, many familiar Mario entities get appearances replacing traditional Minecraft mobs and items, and their respective pages reflect that. The problem is, they are relegated to what amounts to a footnote of a section and do not provide any further context as to what they replace, which is unhelpful if you do not know what the original thing does in vanilla Minecraft. For example, Template:Quote2 Tells us nothing about how they actually act. What this proposal aims to do is, for example, make this one say Template:Quote2 This should clear up any confusion readers may have on the subject.

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

Support

1. Doc von Schmeltwick (talk) - HI GUYS (V)
2. Ray Trace (talk) I've played zero Minecraft and I'm not interested in clicking external wiki links to get information. Context like this should be filled in; you don't need to get into too much detail but a general overview is nice. I've also went out of my way to detail what stats are in playable character pages in the wiki (eg Paratroopa is classified as a technique character, which means that her shots are accurate).
3. GuntherBB (talk) Per Doc von Schmeltwick.
4. Waluigi Time (talk) It feels very incomplete to say something appears in a game and then not elaborate any further on its actual role. Sure, it's just a cosmetic change, but I don't think it's horribly out of scope to expand these a little. Regardless of the outcome we at least need to get Minecraft Wiki links in all those sections, though.
5. FanOfRosalina2007 (talk) Per all. More context is needed in these sections, especially because not everyone who either browses the wiki or is a user on the wiki plays Minecraft (I don't play Minecraft at all). Those people would need more detail as to what the characters do in Minecraft. Besides, this is a Super Mario wiki; we need to cover everything that's Super Mario related in order to keep the wiki up to date.
6. Hooded Pitohui (talk) Per proposal and per Waluigi Time. A brief overview of what the role of these Mario-skinned enemies and objects serve in the game is nice to have. I do think the point Camwoodstock has brought up regarding the versatility of Minecraft's elements is a good point and worth considering, but I feel it's entirely possible to keep these descriptions brief. For, say, Spider Eyes, we simply describe them as an item used in various crafting recipes that are dropped by Spiders. That's enough to know, broadly, where they appear and what they do; more in-depth coverage and explanation of mechanics can be saved for another site to cover. Likewise, for blocks with a Mario skin, we simply leave it at something like "Wood planks can be obtained in the overworld or by crafting, and may be placed in the world as a building material or decoration or be used in crafting."
7. Ninja Squid (talk) Not adding at least an overview of how they work feels incomplete and ridiculous honestly. Per all.

#Swallow (talk) Per all. It's not like we'd be giving Minecraft full coverage.

Oppose

1. Super Mario RPG (talk) - While it's true that the first option does not talk of much, there is little relevance to Super Mario other than what the skins and contents are replaced with. This was one of the main reasons why I wanted to direct people to minecraft.wiki, so that they can read more than just what the Super Mario content replaces. What's described in the second example are not attributes exclusive to the Super Mario Mash-up Pack, except for Tarantox's eyes.
2. SolemnStormcloud (talk) Per Super Mario RPG.
3. Koopa con Carne (talk) If you want info on how each NPC in Minecraft works, you go to a website that has it. If you're leery to go there, c'est la vie, not our business. A sentence-long overview of what the game itself is about is fine on Mario Wiki's Minecraft article, but further details don't belong here. Those Mario-themed skins don't affect gameplay in any way, so there's nothing worth noting here in that particular regard either; best one can do is link to the relevant NPC's Minecraft Wiki page from the character that inspired its appearance in the Mario texture pack.
4. Camwoodstock (talk) Per KCC in particular--we feel like it's probably just more conductive to link to, say, the Minecraft Wiki article for Spider Eyes when mentioning Tantrox's Eyes replace them, than to try and give a brief overview, for one key reason--Minecraft blocks, items, and to a lesser extent even mobs are (usually) incredibly versatile and variable in their use-cases. What we mean by that is that a lot of things in Minecraft are multi-purpose and can be used for a wide variety of different things, especially the older ones. Bringing it back to Tantrox's eyes, Spider Eyes are used in no fewer than 3 crafting recipes themselves and technically count as a food item (and apparently can be used to breed the upcoming Armadillos??? were we just meant to find this out because of this proposal??? what is mojang game design nowadays), and one of those items it crafts is... The Fermented Spider Eye, which gets used in 4 more potion recipes. That's about 4 distinct uses for this one item and 4 uses for an item we'd likely have no other place to mention--even if we forcibly limited the sections to be one sentence per relevant (e.g. all the uses for Spider Eyes are one sentence and all the uses for Fermented Spider Eyes are another sentence), this has the potential to kill a section's pacing stone-cold dead. (Case in point, look at how long this vote is... Oops. ;P) In comparison, a quick link is all the reader needs to learn more if they're just that curious or otherwise aren't familiar with Minecraft; for those who are, then they just need the thing's name, which is presumably provided by the link itself.
5. MegaBowser64 (talk) Per all.
6. DrippingYellow (talk) Per all, the Mario series content in Minecraft is just limited to the texture pack, skins, and add-on map. There's really no point in going into any further detail for mobs or items. I would even go as far as to say that claiming that Minecraft objects are "replaced" by Mario objects is misleading, as again, the only thing that changes for them is the texture. They're still named "Spider", "Spider Eyes", "Zombie", etc., and they still make their original Minecraft sounds.
7. Cadrega86 (talk) per Koopa con Carne and DrippingYellow.
8. PnnyCrygr (talk) A something like "Minecraft Wiki article: (link)" right below the section header would fit better than a paragraph that literally and redundantly recaps the behavior of a Minecraft mob.
9. Hewer (talk) Per all, but in particular, DrippingYellow brings up a good point - these aren't appearances of the Mario entities so much as design cameos.
10. Shy Guy on Wheels (talk) Per all. We'll essentially just be covering how Minecraft works but in Mario terminology, and I don't believe that has a place on this wiki.
11. Nintenboi1 (talk) Per all.
12. Killer Moth (talk) Per all. All the Mario content in Minecraft are just skins and retextures.

Comments

@Camwoodstock "this has the potential to kill a section's pacing stone-cold dead" - The Minecraft appearances get their own sections anyway though. I don't think that "In the Super Mario Mash-up in Minecraft, pandas are replaced by Shiverians." has any pacing to kill in the first place. Hewer (talk · contributions · edit count) 12:20, February 4, 2024 (EST)

In addition, this is not the level of coverage I was thinking about anyway. I want something a little bit more than "Scuttlebugs replace Spiders" but not to the extent that "spiders can be used as crafting items to spawn a bullshit item or this other bullshit item and they can drop legs that you can make a weapon out of". My sentence here also demonstrates my utter lack of Minecraft knowledge and I have zero desire to hop across external websites just to look up very generic information that can easily be corrected with a little bit more context. Ray Trace^(T|C) 17:34, February 4, 2024 (EST)

Yes, in some articles, like Shiverians, there is a Minecraft section... But that that's kind of the exception, not the norm. In fact, it currently looks like there is no norm or standard whatsoever. The closest we have is the list on the Minecraft article itself, but not only is that list incomplete, but just a few examples we saw from articles linked on that: In the example we gave for Tarantox (in which we'll likely have to go over the 8 uses for his eyes alone--we didn't even touch on the minutia of the mob itself), Tarantox doesn't have a Minecraft section; it's just in his article opener. Also, because Tarantox is the Cave Spider, we'd likely have to mirror a good portion of that information to Scuttlebug as well, since they replace ordinary spiders and those also drop Spider Eyes--and Minecraft is only mentioned in an "Other appearances" section for Scuttlebugs and shares this section with other games, not a bespoke header of its own; either that needs to get split, or else it will indeed clog that section with the minutia of Minecraft Spider Information. What about Spider Jockeys, just at all--do they go on the article for Scuttlebugs or Dry Bones, and what do we discuss on those articles about Spider Jockeys? What about Nabbit, who lacks any mention of Minecraft on his article because he replaces the Killer Bunny (an otherwise-removed mob only summonable via commands)? Buzzy Beetles lack a section, but replace Endermites, which are used. What about blocks and items? Do we explain how to acquire froglights in the Snake Block article? Do we discuss the Trident in Fauster's article? And then there's the Totem of Undying replacement, which we genuinely aren't even sure where you'd put that short of the Minecraft article itself.
We think what it boils down to is that, since our coverage of Minecraft as it is is already rather dodgy and inconsistent, whole-sale inserting these descriptions without any consideration of where to actually put them is a very poorly thought-out idea (at least in our opinion, natch.) This is the Mario Wiki--we need to consider what information pertaining to Minecraft is actually relevant to the Mario franchise and what is best suited for another wiki, because otherwise, this could get out of hand very fast, and lead to plenty of confusion down the road; and in our humble opinion, a simple acknowledgement of what's what is all that's relevant, as any details about Minecraft's gameplay are better suited for a different wiki.
We guess what we've been trying to say is that we would like to see some clear limit of where the coverage ends be defined, because Minecraft is big, and if unchecked, you get the aforementioned issue with Spider eyes where suddenly what's supposed to be just a sentence could reasonably become much, much larger. ~Camwoodstock (talk) 18:50, February 4, 2024 (EST)

For the record, each subject should have a dedicated Minecraft section in their history based on current organization. The inconsistency is mostly due to changes in policy and Minecraft's coverage status over time that haven't really been kept up with. While it's unfortunate and something that should be fixed ASAP, it's not really relevant to this proposal. (Also, I'm fairly certain the aim of this proposal isn't to cover literally everything in Minecraft, but to be more descriptive when we say "this appears in the game". The Trident and Totem examples are moot.) -- Too Bad! Waluigi Time! 18:59, February 4, 2024 (EST)

We had a feeling at least some of what we were seeing was just kind of the consequence of coverage priority shifting about, so it's good to know we're not going completely nuts more than we usually are on that regard. Still, it does kind of leave us with a lot of questions seeing as, even after that gets resolved, we're not quite sure where exactly the line is drawn for descriptiveness; as we mentioned, that count range from anywhere to simply listing what a Mario thing is replacing to literally just a full description of the Minecraft mob, and we're honestly a little hesitant to support when there doesn't really seem to be a cleanly defined line for how descriptive we should be aside from kinda "feeling" it based on the provided example--which works fine for mobs, but doesn't quite work good for items or blocks. ~Camwoodstock (talk) 19:06, February 4, 2024 (EST)

This certainly is an interesting proposal. On the one hand, a little more context on how the (Mariofied) mobs act would be nice, so expanding the info a little bit with a short, one-sentence summary would be appreciated... but on the other hand, since the mobs aren't necessarily Mario-related and don't have additional behavioral differences in the Mario Mash-Up pack, it doesn't really make a lot of sense to talk more about regular Minecraft mobs on a Mario wiki, and simply linking to the Minecraft wiki would also solve the issue. I do get Ray Trace's concern though, and since it would make sense to link to the Minecraft wiki anyway, regardless of the proposal's outcome; really, it's boiling down to whether we should add a bit more context on what the Minecraft mobs do on each of our pages, or if it's too irrelevant for this wiki. rend (talk) (edits) 17:07, February 4, 2024 (EST)

Maybe a "if it can be neatly summarized" should've been a key qualifying part. Linking to the wiki shouldn't be a crutch to being opaque about information. If something like a Scuttlebug can be like "Replaces spiders. They make webs and scare Steve." go for it. I kind of doubt ALL replaced assets in Minecraft are so incredibly complex affairs that we have to link to a wiki to satisfactorily cover all bases. Mario^-HOHO! (Talk / Stalk) 23:27, February 7, 2024 (EST)

Rename Category:Twitter images and Category:Twitter media files to Category:X images and Category:X media files respectively

This proposal is simple. Twitter has been renamed to "X" several months back, and people have become increasingly adjusted to the change over time. On Wikipedia, it even says that "Twitter" is both the former and the colloquial name.

Proposer: Super Mario RPG (talk)
Deadline: February 14, 2024, 23:59 GMT

Support

1. Super Mario RPG (talk) As proposer.
2. Somethingone (talk) I don't see why not. Most recent name, becomes current page name.
3. PnnyCrygr (talk) Prefer the old name, but this is really inevitable when websites now use the new name
4. Swallow (talk) Per Twitter's Organization XIII treatment (though it was dumb as hell)
5. Arend (talk) Reluctantly supporting this (since I prefer the old name and still call it Twitter to this day), but it would only be fair because of a similar proposal of renaming the Wikia template to Fandom, which I also supported.
6. ThePowerPlayer (talk) I'm also reluctant to support this, but it sounds like the right change.
7. FanOfRosalina2007 (talk) I'm used to the name Twitter as well, but times change, and so must we. Per all.
8. Mushroom Head (talk) Per all.

Rename {{promo-photo}} and Category:Promotional photos to {{photo}} and Category:Photos respectively

Now that this proposal has passed, which broadens the scope of Template:Promo-photo to cover more than just promotional photographs, the name of the template and its corresponding category should be updated accordingly.

Proposer: ThePowerPlayer (talk)
Deadline: February 15, 2024, 23:59 GMT

Support

1. ThePowerPlayer (talk) Per proposal.
2. Mario (talk) Sure
3. FanOfRosalina2007 (talk) Yes, let's keep this consistent. Per proposal.
4. Hewer (talk) Kinda thought this would be an obvious enough choice to not need a proposal but per proposal.

Miscellaneous

None at the moment.