MarioWiki:Proposals

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
Image used as a banner for the Proposals page
Current time:
Thursday, June 6th, 13:09 GMT
Proposals can be new features (such as an extension), the removal of previously-added features that have tired out, or new policies that must be approved via consensus before any action is taken.
  • "Vote" periods last for one week.
  • Any user can support or oppose, but must have a strong reason for doing so (not, e.g., "I like this idea!").
  • All proposals must be approved by a majority of voters, including proposals with more than two options.
  • For past proposals, see the proposal archive and the talk page proposal archive.

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

How to

Rules

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

Basic proposal and support/oppose format

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

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

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

All proposals dealing with a single article or a specific group of articles are held on the talk page of one of the articles in question. Proposals dealing with massive amounts of splits, merges or deletions across the wiki should still be held on this page.

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

Rules

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

List of ongoing talk page proposals

Unimplemented proposals

Proposals

Split Mario Kart Tour character variants into list articles, Tails777 (ended May 4, 2022)
Classify the Just Dance series as a guest appearance, Spectrogram (ended April 27, 2023)
Establish a standard for long course listings in articles for characters/enemies/items/etc., Koopa con Carne (ended June 8, 2023)
Add tabbers to race/battle course articles, GuntherBB (ended November 18, 2023)
Remove elemental creatures categories from various Super Mario RPG enemies, Swallow (ended January 11, 2024)
Merge Super Mario Bros. (film) subjects with their game counterparts, JanMisali (ended April 18, 2024)
Remove profiles and certain other content related to the Super Mario Bros. Encyclopedia from the wiki, Koopa con Carne (ended April 30, 2024)
Break alphabetical order in enemy lists to list enemy variants below their base form, EvieMaybe (ended May 21, 2024)
Consider "humorous" and other related terms as frequently misused in MarioWiki:Good writing, DrippingYellow (ended May 28, 2024)
  • ^Note: Requires action from admins.

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)
Add product IDs in game infoboxes, Windy (ended March 18, 2023)
Split Special Shot into separate articles by game, Technetium (ended September 30, 2023)
Convert the lists of episode appearances for television series characters into categories, Camwoodstock (ended November 22, 2023)
Split the Jungle Buddies from Animal Friends, DrippingYellow (ended December 22, 2023)
Make bestiary list pages for the Minion Quest and Bowser Jr.'s Journey modes, Doc von Schmeltwick (ended January 11, 2024)
Split Mario's Time Machine (Nintendo Entertainment System), or the Super Nintendo Entertainment version along with both console versions of Mario is Missing!, LinkTheLefty (ended April 11, 2024)
Remove non-Super Mario content from Super Smash Bros. series challenges articles, BMfan08 (ended May 3, 2024)
Split Cheep Blimp (Paper Mario: The Thousand-Year Door) and Zeeppelin from the blimp page, Doc von Schmeltwick (ended May 28, 2024)

List of talk page proposals

Writing guidelines

None at the moment.

New features

None at the moment.

Removals

None at the moment.

Changes

Prohibit Converting Between GIF, JPEG, and PNG Formats

Introduction

Converting between image formats is pointless and unconstructive maintenance. Why? Quality doesn't improve at all. There's also some misunderstandings how each image format works. JPEG to PNG preserves the JPEG artifacting (known as lossy compression). GIF to PNG keeps all the same pixels just to have a smaller file format because PNG compression is better than GIF compression (yes, there is a compression algorithm to GIF), which means improper colors are preserved because GIF is limited to 256 colors.

What this proposal applies to

PNG is the best format out there for web images but requires care to be wielded properly. It makes things harder to identify what needs replacing if improperly used. JPEG to PNG directly is improper use in general. This is especially true if it just to apply transparency that JPEG isn't capable of doing, which could fall under violation of a proposal prohibiting bad/fan transparency. The image that is in need of transparency should have a version that is officially applied by Nintendo, such as a press kit release. If it doesn't exist, don't convert to PNG (or edit the clean image if it is found to exist but not transparent). The file size will just be bloated at that point without affecting the quality at all.

What this proposal doesn't apply to

This doesn't apply to sprite rips or custom 3D model renders because the aliasing makes it super easy to apply so there is no potential for bad transparency. If there is a mistake, it can be corrected without affecting the overall image.

This doesn't apply to replacing images if a clean version of that image exists or can exist. I replace screenshots and sprites often, especially if they are in the wrong format or improperly taken. You can see my images to see just how they compare to the image I was targeting to replace at the time.

If the image is found to be released in PSD or a similar format and it doesn't have transparency with all exposed layers, it might be possible to apply the transparency without it violating the bad transparency proposal.

Sometimes images are in the BMP format or some other raw format. That is OK to convert to PNG. No quality loss there.

Exceptions

However, if the PNG is seen to be too large for upload, even after compression optimization (10MB max at this time for each file), exceptions can be made to allow PNG to JPEG conversion. At that point, the JPEG will be of lower space requirements but the lower space requirements means lossy compression took place.

Conclusion

In short, keep the original format and don't convert directly. Do things properly. If this proposal passes, MarioWiki:Image use policy needs to be amended to reflect the change. This applies to future uploading only. If it can be spotted that an image already uploaded is in violation of this policy change, deal with it on a case by case basis as things are discovered. No need to massively go through each an every image uploaded all at once.

Proposer: Wildgoosespeeder (talk)
Deadline: January 30, 2017, 23:59 GMT

Support

  1. Wildgoosespeeder (talk) Per proposal
  2. Alex95 (talk) - Per Wildgoosespeeder
  3. Toadette the Achiever (talk) It took me two whole days to read and fully digest what this proposal means to the quality of images, considering how complicated it is, but after some thought, I've decided to support. It helps to have near pixel-perfect image conversions that don't affect the format (because affecting the format of an image is actually harder than it sounds). I also appreciate the fact that you're planning to update the written policy on images since, again, considering how complicated it is, this proposal, should it pass, is better written than unwritten. So long as you know exactly what you're proposing, well, per proposal!
  4. Marshal Dan Troop (talk) Per proposal.

Oppose

Comments

Anything unclear? --Wildgoosespeeder (talk) (Stats - Contribs) 22:45, 22 January 2017 (EST)

I think {{image-quality}} suffices to tell other editors that the image in question has JPEG artifacts or GIF 256-color limits. There are benefits of keeping things in a single format when the image size is small. When I created the list of Star Pieces in Paper Mario, I first used the screenshots from a 100% Paper Mario run on the Internet, which were similar to JPG, then replaced them with GIFs from the Star Piece guide on RPGClassics and finally retook them myself for successively higher quality. Since things were done in PNG at first, this saved the work of replacing all the images two times, with the additional benefit of preserving all the older versions for historical reference. --A gossip-loving Toad (Talk) 00:42, 23 January 2017 (EST)

There has been much debate over the use of that tag. I think it's best to just prohibit future uploads from converting the images so that way new debates if the tag should be placed on those images don't get started and existing debates can get resolved ASAP (any affected images that currently occupy Category:Quality requested). --Wildgoosespeeder (talk) (Stats - Contribs) 01:10, 23 January 2017 (EST)
What if someone takes a screenshot from a YouTube video, like a Nintendo ad? I would save it as PNG to avoid another layer of compression, but the result would still be PNG with lossy compression. (Correct me if I'm wrong.) --A gossip-loving Toad (Talk) 09:54, 23 January 2017 (EST)
Even though the content is definitely heavily lossy compressed, compressing it as JPEG would cause further losses in quality, furthermore it can be subsequently replaced with a proper PNG screenshot without renaming. If no uncompressed or at least high bitrate lossy compressed source video can be found I would therefore say that in this case it is fine saving as PNG, stating that the source is a video and possibly including a link to the actual video.--Mister Wu (talk) 10:41, 23 January 2017 (EST)
I don't think those kinds of images apply to the proposal. This is more for artwork, screenshots, or other images obtained by means through someone else rather than through the submitter's own doing, like if the image they find through a Google Image Search is in the JPEG or GIF format and they submit it as a PNG instead. In general, I find that kind of practice plagiarism, unless the source is specified and there is no way for the submitter to replicate the result. --Wildgoosespeeder (talk) (Stats - Contribs) 15:41, 23 January 2017 (EST)

If I wanted to make a jpg transparent (make it a png), would this be allowed based on your proposal? --Andymii (talk) 23:46, 27 January 2017 (EST)

That's already covered by the proposal. --Wildgoosespeeder (talk) (Stats - Contribs) 15:47, 28 January 2017 (EST)
What if the image is a scan (like most of the pre-internet artworks)? What's wrong with making them transparent so they don't have fuzzy backgrounds? I feel it would be better if each case was taken upon individually, instead of having a sweeping rule that may in fact get in the way for certain cases. --Andymii (talk) 12:59, 29 January 2017 (EST)
This is a matter of image format and understanding what format is best for what situation and understanding that converting between formats doesn't increase quality. PNG doesn't mean higher quality. PNG means that it will preserve an image in whatever state it is in 100% accurately. BMPs are ideal for PNG because no degradation occurred. JPEG uses encodings that estimate what a color is at certain pixels, divided into blocks, which is why it is regarded as a lower quality lossy format that degrades an image. There is nothing wrong with JPEGs if that is all that is available at this time. It's also better for photographs or other images that are complex with colors and patterns, which can often compress better than PNG. JPEG is a tradeoff of lower space requirements for images that can get away with quality loss, which visually, could be undetectable. [1]
This is also a matter of patience and making things easier to track what needs a high quality replacement at some point, if at all. High quality versions of images will eventually come. Just a month or two ago, Shokora (talk) (formerly YoshiKong (talk)) found BMPs of Super Mario World artwork that MarioWiki hosted JPEG versions of instead. The JPEGs were replaced with the BMPs (converted to PNG). That's something we don't have to worry about anymore. --Wildgoosespeeder (talk) (Stats - Contribs) 18:35, 29 January 2017 (EST)
How come that if something doesn't increase quality it must be forbidden? It is true that PNG encodes a photo worse than JPG, but it encodes better than GIF a pixel artwork < 256 color, such as early images on Nintendo's website before PNG came. --A gossip-loving Toad (Talk) 21:30, 29 January 2017 (EST)
  1. We should focus on constructive edits. Converting wastes time and makes things more confusing in the long run and problems can go unnoticed for years. At least if we forbid conversion, we can track JPEG and GIF by extension instead of by visually scanning the image for imperfections if it was converted to PNG and tagging them with {{image-quality}}, thus keeping Category:Quality requested more manageable. The extension is like a MediaWiki maintenance category in disguise. Just have to use Special:Export (formerly could use Special:MIMESearch) and remove the PNGs from the list of possible JPEGs and GIFs that should see a replacement.
  2. PNG isn't encoding. It's the result of reducing data redundancy without affecting the image's pixel data. JPEG goes about compression much differently, which leads to detail loss.
  3. I am kind of iffy converting those GIFs to PNG because GIF has an inferior algorithm compared to PNG but there could be a better version floating around where the colors aren't limited to 256 colors.
I hope this clears things up. --Wildgoosespeeder (talk) (Stats - Contribs) 22:14, 29 January 2017 (EST)

I mostly agree with your proposal, however, I disagree with this:

Exceptions

However, if the PNG is seen to be too large for upload, even after compression optimization (10MB max at this time for each file), exceptions can be made to allow PNG to JPEG conversion. At that point, the JPEG will be of lower space requirements but the lower space requirements means lossy compression took place.

I would truthfully rather have no image at all for a given subject in cases like this if the alternative is an image with lossy compression. 3D Player 2010 16:41, 30 January 2017 (EST)

Changing the Super Mario Wiki Logo!

This is the logo of Super Mario Wiki.

It's time for the wiki to get a facelift and receive a brand new logo. The matter was brought up on the forums recently and I've been discussing it with several users, including Porplemontage. I presented a proposed design for the logo, and after a few adjustments I can now present it here:

This new logo is simple. Rather than displaying a piece of Mario himself, it shows the iconic mushroom. The mushroom is a symbol of the Mushroom Kingdom as a whole, similarly to how the wiki covers the entire franchise as a whole, even when Mario isn't the focus of a game. The current logo (seen at the top left of the page) is very dated, featuring artwork and screenshots from games that came out almost a decade ago. The proposed design is unique in that it won't become dated in a few years by each game that comes out.

What do you think? Should we change the logo to this new design, or keep the current logo?

Proposer: Eldritchdraaks (talk)
Deadline: February 1, 2017, 23:59 GMT

  1. Eldritchdraaks (talk) Per proposal
  2. Alex95 (talk) I'm honestly going to miss the old one, but I agree, it's long overdue for a change.
  3. Glowsquid (talk) I like it!
  4. Owencrazyboy9 (talk) The design looks really good and everything Eldritchdraaks said about it symboling the Mushroom Kingdom instead of just Mario is really accurate. In other words, I like it enough for it to be the new logo. Per all.
  5. Yoshi the Space Station Manager (talk) Per all.
  6. Baby Luigi (talk) Preferably should be drawn with vectors, though
  7. Jazama (talk) Per all
  8. A51 Trooper (talk) Per all
  9. TheFlameChomp (talk) Per all
  10. Mister Wu (talk) Since Mario's cap is not proposed as alternative logo, voting this one. Surely, a logo that doesn't become outdate is better.
  11. The Pyro Guy (talk) Per all.
  12. Bazooka Mario (talk) Goody. Though I wish it was a little less generic.
  13. Toadette the Achiever (talk) While the current logo is at least somewhat generic, the artwork of Mario and the game screenshots are from around a decade ago, which might not be as appealing to readers. Having a logo with a good enough genericness would give that logo a much longer life span. And yes, we as a wiki also provide details about the Yoshi and Wario series, so having a simple Mushroom would be good enough, since Yoshi and Wario are too connected to Mario to have their own wikis. However, I do agree with Baby Luigi's comment about converting the image to vector scale, but we can always cross that bridge if and when we come to it.
  14. Marshal Dan Troop (talk) That is a good looking logo.
  15. The Koopa Bro. (talk) Per All. While I Do Agree That It's A Bit Generic, It's Also Easily Recognisable.
  16. Tucayo (talk) - Per all.
  17. Niiue (talk) I'm gonna miss the old one. Per all.
  18. Luigi 64DD (talk) No real reason not to. Per all.
  19. Infinite8 (talk) The Super Mushroom represents the Mario franchise, like the emblem used to represent the Mario universe in the Smash Bros series. And also this is the perfect time to switch to the new logo to coincide the "new Nintendo", with their brand logo changed from "grey logo on white" to "white logo on red". Per all.
  20. Andymii (talk) The new logo isn't very unique or clever, so I'm hesitant to support it. However, it's definitely better than what we have now, so I guess it's okay.
  21. Lakituthequick (talk) Per proposed.
  22. Mr Squid (talk) Per all.

  1. Tails777 (talk) At the risk of sounding picky, I kinda like the current logo better. I have nothing against the one shown, but it's a matter taste and I just like the current one. If I need a reason why I like the current one, I like the screenshots behind Mario and the logo itself. While they are kinda hard to see, they do show a bit of the various games in the series overall.

Comments

The original file IS drawn with vector... mostly. It's x1500px.--EldritchdraaksSig1.pngEldritchdraaksSig2.png 22:45, 25 January 2017 (EST)

Barely related, but how does everyone feel about naming this Wiki Mushroom Kingdom Wiki? Not something that is going to be changed any time soon or even through a proposal to make the change, but I think it is worth discussing just as a hypothetical. --Wildgoosespeeder (talk) (Stats - Contribs) 20:56, 27 January 2017 (EST)

Too close to The Mushroom Kingdom. Hello, I'm Time Turner. 21:04, 27 January 2017 (EST)
The series is called "Mario" after all, so it makes sense to be named after that. BabyLuigiFire.png Ray Trace(T|C) 21:05, 27 January 2017 (EST)
But we cover a lot of non-Mario things, such as Luigi's Mansion, WarioWare, Donkey Kong Country (series), Super Smash Bros., Mario & Sonic (series), Captain Toad: Treasure Tracker, and Yoshi (series) just to name a few examples. I already feel that we shouldn't cover some of those on another talk page. --Wildgoosespeeder (talk) (Stats - Contribs) 15:34, 28 January 2017 (EST)

Along with the new logo, can this wiki change its wiki skin to Vector (with the search bar on the top right) as default? The new logo skin wouldn't fit in with the MonoBook skin. The Zelda Wiki, Smash Wiki and Nintendo Wiki all have the Vector skin as default. Infinite8 21:45, 27 January 2017 (EST)

One change at a time! Isn't it possible to have it's size reduced or create a smaller one, though? ...Eh, I'd likely keep my setting to MonoBook anyway. Alex95sig1.pngAlex95sig2.png 22:10, 27 January 2017 (EST)

One thing about the SVG version placed here last night is that while a PNG of 150px is 23KB, the vector is 342KB, which is significant. I would then use the PNG instead.
You can also use a PNG of 300px instead to accommodate for high density screen users (51KB), or both and have it be switched as needed by CSS.
Lakituthequick.png Lakituthequick 09:52, 28 January 2017 (UTC)

If filesize is a concern, the SVG can just be scaled down to the desired x150px and uploaded as that, right? – Shokora (talk · edits) 08:18, 28 January 2017 (EST)
That's not how SVG works. SVG grows in size as the complexity of the image increases, not the resolution. Lakituthequick.png Lakituthequick 13:29, 28 January 2017 (UTC)
Ah, gotcha. In that case, I think we're better off uploading a PNG at the appropriate 150px size for use in the CSS, and keeping the full SVG available for potential use elsewhere. – Shokora (talk · edits) 08:37, 28 January 2017 (EST)
This isn't about png or svg, it's about the logo design. I've already discussed the png vs svg with Steve.--EldritchdraaksSig1.pngEldritchdraaksSig2.png 12:32, 28 January 2017 (EST)
The format is good to think about though. What was the outcome of your discussion? Can't seem to find it on his talk. Lakituthequick.png Lakituthequick 21:44, 28 January 2017 (UTC)
It's a private discussion. The proposal isn't about the format; it's not something up for discussion here, and will be decided by Steve himself.--EldritchdraaksSig1.pngEldritchdraaksSig2.png 17:31, 28 January 2017 (EST)

Oh yeah, if this proposal passes, we need to change {{mariowiki-image}}. --Wildgoosespeeder (talk) (Stats - Contribs) 15:38, 28 January 2017 (EST)

Miscellaneous

None at the moment.

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