MarioWiki:Proposals/Archive/39

Change the MarioWiki:Signature rules
DON'T CHANGE 1-14


 * See: Draft

I'm proposing a change to the current Signature policy, the changes help reading and reduce the distracting signature does. The following are the rules that got changed, all other rules are unchanged..

First of any thing: Reduce the height of the signatures, The current signature is awfully very tall (See this for example: User:Dashbot/Sandbox). I'm proposing this for multiple reasons, the strongest reason is that signatures higher than 20px in height disrupt the normal spacing between rows of text. Adding ugly unnecessary spacing. This applies for text and images, thus you cannot use any html tags that increase the text size, including but not limited to,   and. The second reason I'm proposing this is that the bigger the signature is, the much more it would be disruptive catching the eye out of the message itself.

Second: You want to use image, as you wish.. but don't use mainspace images, simple! Just use any external or any personal image. That is because the unnecessary linking in the file page.

Third: Use whichever font you want, as long as it is not higher than normal font. It must be easily readable, also.

Fourth: A minor change, you are now required to link to your talk page, instead of requiring you to link to your userpage. 98% of the time I click on a signature is to visit the talk page. You still can have links to your userpage, contributions, etc

Fifth: Another minor change, You are no longer allowed to link to real articles directly.. Most of you guys are already not doing that, just adding that for the record. If you really must link to a real article, use an external link.

Sixth: No External Links such as advertising or any other websites are allowed, Use your userpage for such things. Like the current system, you are allowed for maximum of five word links.

Last and most importantly: Don't make your signature very disruptive.

You can use disruptive, long, anything signature as raw code in other user's talk pages, ONLY if they say okay. If this passes, there will be a week-to-month time until get issued.

Proposer: Deadline: April 5, 2014, 23:59 GMT.

Support

 * 1) We are an encyclopedia, we don't host fancy signatures. Signature should only be used for personality identifications, However, you can still have some good designs, if you adhere to those rules.

Oppose

 * 1) I'm fine with everything except the height rule; it seems okay as it is and you would hardly be able to see the pictures of Rosalina in my signature if you made the height requirement tighter.
 * 2) I don't think this would be great, many people will receive a sigfix warning. Per Epic Rosalina.
 * 3) I think the rules are fine the way they are.
 * 4) - While I am somewhat irritated by how spacing gets screwed up by sigs, I just shrug it off as something that can't be helped. Making images (and text) no taller than 12pt font is too draconian, and given how long the old dimensions have been established for, it's a bit late to try and change them now. Besides, we're an encyclopedia: messy talk pages aren't the end of the world as long as the mainspace and policy pages are solid. And on that note, the proposed MW:SIG draft is way too bulky; even if some things get changed to the policy down the road, the page should stay nice and compact like it is now.
 * 5) Awful. The rules are good as they are. Also, why not use mainspace images?
 * 6) Per Why Bother.
 * 7) Per all, it would be a hassle to get everyone to fix their signatures quickly.
 * 8) I strongly disagree with the second rule. I like the appearance of my signature very much, and I don't want to waste potential personal image slots and possible go over it just because of that rule. And using external links is not the best idea because you can't resize them. In all, this proposal creates more problems than it solves, I don't really hate the spacing and such. I just kind of ignore it.
 * 9) I think the current rules are fine and I don't see any problems with the spacing.
 * 10) I personally thought they were too strict as they are at one point. Per all.
 * 11) This crap is WAYYY freaking stringent for my tastes. Per all.
 * 12) No no no, absolutely not. There's no reason we can't have these. Per all.
 * 13) &mdash; Per Ghost Jam's comments and Walkazo's vote. The overall impact of this proposal is too extensive and the current policy page is neater and concise. While some of the individual ideas might have merit, they should be discussed in the Wiki Collaborations board on the forum so that there is more time to make them into workable policies.
 * 14) Per Super Mario Bros.

Comments
I agree with parts, but I see no reason for why mainspace images can't be used.

I agree that our current signature policy could probably stand a to be reviewed in some parts, and I do like some of your suggestions. However, this isn't like moving an article or banning something everyone is sick of, this is a site wide policy that a large section of our userbase takes advantage of. I feel that the proposals section is the wrong venue for this, you're not going to get the level of discussion really needed for a change of this scale here. More likely, it's going to fail because it only has a week get it's point across (and this is a fairly involved point) and proposals function less like discussions and more like "yes or no" affairs. My suggestion? Move this to the General Discussion forums (perhaps even the Wiki Collaborations sub-forum), get a discussion rolling. Once it's been narrowed down what people like, don't like and the compromises therein, bring it back to proposals as "yes or no" type of thing. --
 * Actually, writing guideline proposals last for two weeks, however, seeing as they can only be rewritten within the first three days and there are probably a few points that need to be ironed out and as Ghost Jam said the discussion for that probably wouldn't happen within that timeframe it would probably be best to discuss then propose.
 * Even at two weeks, I'd put money on this snowballing to the "nope" side.

I don't see why we can't use Mainspace Images, i don't see anything wrong with them.
 * Look at the file usage for File:Booboo.gif, you can still normally use an external link by using something like  http://www.mariowiki.com/images/a/ad/Booboo.gif -- 04:59, 22 March 2014 (EDT)

@Ghost Jam: That's a pretty good idea, I think.. When this proposal reaches the deadline, We will have four weeks to discuss and settle this.. @Epic Rosalina: If you used another image, maybe this, this, if cropped, or this. It would appear better. @Walkazo: The draft can be changed anytime. While it can be too draconian as you said, the talk pages are pretty disrupting, catching my eye out of the main message. The spacing looks ugly, I can't just throw this idea out myself.
 * -- 04:59, 22 March 2014 (EDT)

Pie for Everyone (revisit)
VETOED BY THE ADMINISTRATORS Nah, too much trouble. If you want pie, make it yourself. Any flavour you want: go crazy, it's your pie. Or, if you want cake, make that instead - we won't stop you. And if you don't want pie or cake, then that's fine too. Freedom is delicious, and this way, everyone wins.

Roughly seven years ago, I came to this very proposal page with an idea. Well, a hope, really. A hope for a better tomorrow. A hope for a more complete wiki. A hope for a happier editor. A hope....for pie.

Now, the idea was (and still is) simple. Basically, a pie button would be coded into the top bar that would send a signal to one of our sysops (the original proposal had Wayoshi being the baker of these pies, but I feel that we have sufficiently talented staff now that the work can be evenly divided with no issues), who would then prepare and deliver a piece of warm pie.

As one might expect, there were issues with this idea. Some people liked it (in fact, the proposal passed 12 to 10), others didn't (I recall at least one administrator at the time having a bit of a fit over the whole thing). And I understand. Change is a hard thing to swallow sometimes (unlike pie) and we are a bit of an argumentative bunch. Not to mention that there are some legitimate concerns with this plan. It'll be hard to code, hard to coordinate and could get fairly expensive fairly quickly. On the other hand, if executed with the level of precision and expertise we've developed over the last seven years, I believe that it's well within our current abilities. In fact, this may be something we can eventually take to NIWA and help other wikis grow. So, I bring this proposal back here today because we are a much different MarioWiki than in 2007. We've grown, in more ways than one and I think it's time to reconsider.

The actual division of labor of the idea will be discussed among the administrative staff come the passing of the proposal, but the basics read as follows:


 * A single editor may only make use of the pie button once every 72 hours, due to time constraints on part of the administrative staff.
 * Each piece of pie will cost $3 American. This is to cover basic delivery services. This price may need to be adjusted as the project fleshes itself out.
 * Third point to help make proposal look less like I just suddenly decided to do it at 3am and am basically bull$*@!ing it as I go.
 * Flavors of pie can be decided upon (via community input) at a later date, but the current plans are for cherry, blueberry, freedom and Randy Savage.

I encourage discussion and am more than willing to answer any design related questions the community might have. All I ask is that we keep it civil and work towards a better, pie filled tomorrow.

Proposer: Deadline: April 8, 2014, 23:59 GMT

Delicious Pie

 * 1) as the proposer.
 * 2) IT'S PIE DAY, PIE DAY, GOTTA GET DOWN ON PIE DAY.
 * 3) I'd per YoshiKong but due to an intense hatred of that song I'll per the proposal.
 * 4) &mdash; Ghost Jam has clearly come up with a workable system that will be extremely beneficial to the community. My only concern is where we will get the money to start the program, but I assume we can either borrow some from the MarioWiki's ad revenue or take out a loan. The Super Mario Wiki has always prided itself on being one of the premier Mario resources on the Internet, and implementing this project will solidify our status once and for all. The "Pie for Everyone" feature will increase editor productivity and community morale, (eventually) increase the Super Mario Wiki's revenue, and allow us to expand our appeal. I urge everybody that cares for the future success of the wiki to support this proposal.
 * 5) Let them eat pie.
 * 6) I support because I feel this will bring Randomyoshi back.
 * 7) Pie is a great idea, we shouldn't keep the users from their pie. Pie for everyone!
 * 8) - I have regretted opposing the first pie proposal every day of my life. Never again. Pie for everyone, forever!
 * 9) - Pie is superior to all other desserts.
 * 10) PIEPIEPIEPIEPIEPIEPIEPIEIPEIPIEIPIE
 * 11) Give me pie or give me death.
 * 12) I retired a while ago, then I heard the the pie button was returning... PIE FORE EVRYONE!!!!!!!!!!!!!!1
 * 13) You convinced me SMB. BUT IT MUST BE CHOCOLATE PIE, OR I WONT HAVE ANY.
 * 14) Let them eat pie.
 * 15) Pie will keep productivity up, and people can edit longer without having to worry about fainting from hunger. Plus it's pie. What more could you ask for?
 * 16) I do have a particular craving for chocolate cream pie...
 * 17) - The flaws of the original proposal have been vastly improved upon. This will definitely bring both a greater sense of democracy and also a greater sense of echantment with the MarioWiki administrative staff.
 * 18) I. Think a pie dilevery service would be yummy and delicious!!!
 * 19) Per all, pie for all.

No Pie for You

 * 1) - No delicious fruit pie = no per.
 * 2) If the members of the administration are responsible for making and delivering the pies, then the flavors of pie to be offered should be determined via an administrative consensus and not via community input. The only way I can see that changing is if we accept minimum monetary donations of $20 for every pie flavor that is not currently offered.
 * 3) Cake is better.
 * 4) Per Mario!
 * 5) Pie gives me indigestion
 * 6) Per Mario and Glowsquid-o.
 * 7) Don't like pie,
 * 8) I didn't have pie for my birthday on 5 March, I had CAKE! I WANT CAKE! I WANT CAKE!
 * 9) Per all.
 * 10) I've never eated pie *-*
 * 11) Per Mario, chocolate cake FTW.

Comments
Additionally, as this has proven to be something of a hot button issue, I'm further suggesting that, should this proposal fail, the overturn rule (point #7) be extended for this topic alone from four weeks to a full year. That will basically give everyone a year to discuss and then reconvene on April 1st. --

I think there should be a rota for which admin delivers the pies.
 * Definitely workable. --

@Glowsquid The proposed list of flavors includes a few fruits. However, if you're suggesting we replace baked pies with those little packaged fruit pies.....that would certainly be cheaper and easier to deliver, but I'm not sure how the community would react to that. Anyone else have an opinion? --
 * It depends if you use real fruits or not. 13:34, 1 April 2014 (EDT)
 * I'll support if you can hook everyone up with a free sample first. -- 13:49, 1 April 2014 (EDT)
 * Free samples require $2 for shipping and handling.
 * This is a scam! 14:11, 1 April 2014 (EDT)
 * The admin team does scam, we are 100% truthful the entire time.
 * So wait, why is everyone trusting scammers to bake the pies? How do we know they won't poison them or something? -- 14:53, 1 April 2014 (EDT)
 * Oops, looks my random miss out a word thing happened again :/. Besides why we would poison you?
 * Hey, if you guys want to handle the production and distribution of pies, be our guests, though I should mention that transferring responsibility also incurs a monetary fee. It's less work for us.
 * Is this proposal an April Fool's Joke? Today is April 1st and I don't find it likely to order pie from a wiki. In fact, pies in the face have been used a lot in comedy. SeanWheeler (talk) 17:35, 1 April 2014 (EDT)
 * It'd be passing a lot better if it was an April Fool's joke.

@YK It's do a hop. 17:43, 1 April 2014 (EDT)


 * Aye? Dafaq you talkin bout Willis?! 07:17, 2 April 2014 (EDT)

Now how long will this take until it moves to the BJAODN?
 * Aw, don't ruin the fun! 09:17, 2 April 2014 (EDT)

YoshiKong, why have you voted twice?
 * Because he wants to! There's no rule against it, after all. 14:33, 2 April 2014 (EDT)
 * Rules, schmoolz, I don't give a hoot about 'em. 14:36, 2 April 2014 (EDT)
 * Really, I don't either. Sometimes. 08:30, 3 April 2014 (EDT)

@Bluetoad63: Forget the cake: the cake is a lie. 12:48, 5 April 2014 (EDT)
 * It's still delicious just thinking about it. :) 14:28, 5 April 2014 (EDT)
 * That's what I'm counting on. 15:34, 5 April 2014 (EDT)
 * But i like cake! WHAAAA-*shot* 11:13, 8 April 2014 (EDT)

To address opposing votes, I hereby suggest the Vommack Amendment to the Pie for Everyone Act: Vommack (talk) 17:51, 5 April 2014 (EDT)
 * Any flavor of pie may be ordered; however, pies not currently listed as an available pie will be considered a "custom pie" and extra money will be charged, depending on availability of supplies, etc.
 * The Administrator Bakery will be expanded to allow for the baking of cakes. All restrictions relating to ordering of pies extends to the ordering of cakes. Cake may or may not be a lie.
 * Does it adhere to current government regulations? 17:52, 5 April 2014 (EDT)
 * Which regulations are you referring to? Vommack (talk) 17:54, 5 April 2014 (EDT)
 * Wiki Manual, Section B, Paragraph 19, Subheader 4. 11:14, 8 April 2014 (EDT)
 * Why yes, yes it does, Mr. Toad.--Vommack (talk) 15:27, 8 April 2014 (EDT)

I am so confused. What do you mean by administrators delivering pie? This may sound stupid, but I don't really understand. Could someone please explain? 20:05, 8 April 2014 (EDT)
 * Explanation: seven days ago was April 1, seven years ago was fun times, and pie is awesome. -

Create an "Regional Differences" Page
SECTIONS ONLY 1-6

As far as I know, some games series like Mario Party, Mario Kart and sports spin-offs have some/lots of regional differences in all the world. An example is myself: Ashley in Japan is 8, but in USA she is 15. Also, the majority of the Mario games released on hand-held consoles have differences. Sawaru Meifo in Wario (WarioWare Touched!) has LOTS of differences between all the releases: The american one is totally different from the Japanese's one. I suggest to these pages be called like: List of (name of the game) Regional differences.

Proposer: Deadline: April 13, 2014, 23:59 GMT

Support

 * 1) Per proposal

Oppose

 * 1) Per Walkazo in the comments.
 * 2) Per Walkazo.
 * 3) Per Walkazo.
 * 4) Per all.
 * 5) - Per me (in the comments). Make the pages someday, but keep the priority on getting the info down in the sections for now.
 * 6) Per Walkazo.

Comments
I honestly think it would be better if we merged it with the article itself, unless the regional differences is very substantial or something. 13:16, 6 April 2014 (EDT)
 * We already have a policy for version differences, including regional differences (a broader scope is better, since more info can be covered). The policy only talks about the creation of sections for now; I suppose it could be expanded to have another class of ex-subpages, but perhaps not until we have more information of the sort built up: right now, I feel like we'd only have a few pages, and most of them would be small. -
 * Yes. Games that has lots of differences (e.i WarioWare games) should have an subpage like Quotes. Games with only a few of differences (e.i Super Princess Peach) should have only a section. What about?
 * Eventually, that would be ideal, but again, I feel like we should try to build up the information first and then start making subpages, rather than adding provisions for a whole new subpage class now, only for it to be sparsely populated for the longest time. You cite the WarioWare series as having tonnes of differences, but none of those pages even have sections yet. It would be best to make a Wiki Collab to try and generate more interest in making sections, with the goal being to make enough coverage to move a handful of those sections onto subpages. -

Create separate articles for Standard Kart and Standard Bike
CREATE 10-0

Looking back at my last proposal of splitting the Pipe Frame and Gold Standard from Kart, I was thinking we should give the Standard Karts and Standard Bike their own articles. The Kart and Bike articles can cover Karts and Bikes as a whole. This is how I think it can be laid out: I feel this should be done for consistency sakes, as all other karts have their own article and the Standards should be no different. I know most of the info is just covered in Kart and Bike, but those can cover the vehicles as a whole instead.
 * The Standard Kart page would cover the information and stats of the Standard Karts from Mario Kart DS, Mario Kart Wii, Mario Kart 7 and the upcoming Mario Kart 8.
 * The Kart page can simply cover Karts as a whole, not necessarily the stats of each one. We can also add pictures of karts from the various MK titles much like how the Double Dash!! section does.
 * The Standard Bike page would, like the Standard Kart, list the stats of said bikes from Mario Kart Wii and Mario Kart 8 while the Bike article covers bikes as a whole, such as showing pictures of each bike from Mario Kart Wii and bike part from Mario Kart 8.

Proposer: Deadline: April 14, 2014, 23:59 GMT

Support

 * 1) Per me
 * 2) Per...you? (Tails777)
 * 3) The standards are their own parts/karts, so they should get a different article rather than being lumped into the generic kart article.
 * 4) They are 2 different vehicles; per all.
 * 5) Per proposal
 * 6) Per All.
 * 7) The term "Kart" is a umbrella term for all the 4-wheeled, car-like vehicles used in Mario Kart games. It shouldn't exclusively mean the go-karts. Sure, the article should definitely cover the karts used in the first few Mario Kart games, but it should stop covering just the go-kart-like karts post Mario Kart Double Dash. This applies to "bike" as well. The term "Bike" should apply to ALL bikes, not just the Standard Bikes.
 * 8) Having seen an example of the proposed end result, per Tails777.
 * 9) Per all.
 * 10) - Per all.

Comments
Shouldn't this be a TPP? 20:06, 8 April 2014 (EDT)
 * It could be, but it covers 2 different topics so I put it here.

It seems unnecessarily fiddly to break down Kart just to copy and paste the same information to another article, not really seeing the benefit here. And just going off the information currently up in Bike, we'd be breaking it down into a stub to create another stub, when the current host article seems to serve the purpose well enough. I'm not going to vote until someone explains to me what the end goal really is here, what is the actual benefit of breaking these two articles down further. --
 * The goal is to basically move the stats and information on the general Standard parts into their own article while the Kart and Bike articles cover the 2 vehicles as a whole. The current kart page covers the Karts from all games (looking at the Double Dash!! as it has a picture of all the karts in the game) while covering the information about a single kart/part. Why keep the information on the Standard in the generic kart article when we can have a separate article for said part like all the other karts/parts have?
 * @Ghost Jam, short articles are NOT stubs. I'd rather have short articles organized nicely w/o padding than large articles that a large, bloated, and are padded out on this wiki. 22:30, 10 April 2014 (EDT)

--
 * @Tails777 I follow the reasoning and the logic, and in principle I believe I agree. What's bothering me is the creation of stub or fluff articles. Can you guarantee that there is enough information available to make this worth the trouble? If yes, then I guess I'm behind it.
 * @Baby Luigi The line between "this article is short" and "this article is a stub" is pretty thin and has been something editors have argued about since the start of this wiki. A bloated article is just as bad as a sparse one, both can be dealt with by stepping in before it happens.
 * I've written down here what the Standard Kart article would look like, basically a draft of it.
 * Ok, you've got my support. --


 * Actually, there's a pretty notable difference between a stub and a short article. A stub is an article that lacks sufficient information. Most stubs are short articles, yes, but not all short articles are stubs. They're short because that's all that can be said about them without having to pad the articles out. An article about the level that does not have any further information other than basic information would definitely be classified as a stub because it lacks sufficient information to get an understanding of the subject. Sufficiency and completeness is the key, not the length of the article. 23:07, 10 April 2014 (EDT)
 * Correction, all stubs are short articles (and/or sections, although we see far less of that on MarioWiki than, as an example, Bulbapedia), which is why we have more peer review for short articles and subjects that lack more than passing information. Additionally, you're thinking too hard about the precise words I'm using here. I'm not insinuating that any and all short articles are stubs, rather that they are more prone to becoming stubs, either at creation or due to over specialization. It's not about padding an article (in fact, if you have to pad an article to reach a point where people aren't going to start slapping "fix this" templates on it, it either needs to be merged into another article or dropped), it's about proving that a subject is worth having a separate article. You prove this by supplying context and showing relevance. If that can be done in a few sentences, well done, but that can't be and shouldn't be blanket applied to everything.


 * As we are very quickly moving off subject, I'm going to ask that we end this here and move it to either the forums or talk pages. --

The Fate of WFC Glitches
KEEP 1-13

I know it's a bit early, but might as well clear the air now. As we all know, support for Nintendo WFC is ending May 20. That means no more online features for basically every game on the Wii and DSi. The question is, what are we going to do about glitches that we have listed on glitch lists of a certain game that happen only in wi-fi? No one will be able to do a glitch for themselves anymore, nor could anyone add any glitches, so I'm not totally sure if we should keep them all, or delete them on May 20.

Proposer: Deadline: April 19, 2014, 23:59 GMT

Delete them

 * 1) I honestly don't see much of a point in keeping them.

Keep them

 * 1) – Once a glitch, always a glitch.
 * 2) Seriously? This is like Wikipedia deleting a page on Windows XP because support has been dropped. There is absolutely no reason to delete these glitches.
 * 3) There are modders who are working to set up their own servers in Mario Kart Wii so it won't be 100% eliminated. There's absolutely no reason to delete history of them, though they may be questionable if they lack evidence we cannot acquire.
 * 4) Per All.
 * 5) It's not an uncommon practice for encyclopedias to keep a historical record of otherwise outdated information, so I don't see keeping them as a problem. The only issues I see arising are the provability moving forward, as mentioned by Baby Luigi above. But we'll cross that bridge when/if we come to it.
 * 6) - Per all. If anything, preserving this info is becoming more important now that the official sources are being taken away. You don't burn your history books.
 * 7) - Per all.
 * 8) Per all.
 * 9) - Per YoshiKong and Vommack.
 * 10) Per all. Maybe we could move them to their own section on the page though.
 * 11) Per all.
 * 12) Per all
 * 13) Per all, especially Walkazo.

Comments
Since it seems that many are in agreement to keep them listed, it might be a good idea to further our coverage a tad. Make sure we have images or videos of our soon to be inaccessible glitches (perhaps suggesting same to the rest of NIWA as a courtesy). We have a rare opportunity in knowing in advance that sources are about to vanish, best to document what we can while we can. --

Disambiguation minimum
DELETED BY THE PROPOSER

I have noticed many of the orphaned pages on the wiki are disambiguation. These pages have only two pages on them, and those pages have links to each other already, making the disambig page useless. What I think is that disambiguation pages should have at least three instead of two page links in order to be made and as for the ones that have less, they should either have another page link added or be deleted.

Proposer: Deadline: April 30, 2014, 23:59 GMT

Support-Change limit

 * 1) Per my own proposal.

Oppose-Keep it as it is

 * 1) Per Vommack's comment. There needs to be a default term for people to be linked to. Removing these could potentially make it harder for people to navigate the wiki.
 * 2) Per Yoshi. Which makes it per me in a way, I suppose.
 * 3) If I look up 'Luma', what would it go to? Species, or character? This is why we need those pages.
 * 4) Per all. If a term has two equally prominent uses, a disambig page is the only way to go. There is nothing wrong with disambiguation pages being orphaned: they're for helping searches, after all, just like redirects.
 * 5) System works fine and as intended as is.

Comments
And what would you default to if you searched for a term with two meanings?--Vommack (talk) 16:53, 23 April 2014 (EDT)
 * I see your point. Now, how do we make them un-orphaned if the two pages already have links to each other? 17:33, 23 April 2014 (EDT)
 * I'd say they don't necessarily have to be. While there shouldn't be normal pages lying around in the orphanage, some disambiguation pages will inevitably end up there. There's not really anywhere to link to them, but they need to stay for the sake of navigation.--Vommack (talk) 17:40, 23 April 2014 (EDT)
 * Basically what we're saying is that these pages don't need to be un-orphaned, they have a use in the search bar. - 17:56, 23 April 2014 (EDT)

It's unsurprising that a disambiguation page would be orphaned as well. Orphaned pages are pages that no other page links to. Due to the nature and use of a disambiguation page, it makes sense that nothing would link directly to them. Adding more to the page itself won't solve that, although I'm sure linking back could be jury-rigged into existing articles (IE: "To read more about [TOPIC], see here: [LINK TO DISAMBIGUATION PAGE FOR TOPIC].). I don't see it as a necessity, however.--
 * Names with more than two meanings often/usually link to the disambig page in the articleabout (rather than listing everything there), but if there's only one other meaning, it makes more sense to link directly to the other article: cutting out the middle man, and all. -
 * Figured we already did it, just couldn't think of any examples off the top of my head. :D -
 * Try things like Yoshi and Luma, and everyone should get the point. Searching Luma will put you on the disamxhjdujbc page, whereas the Yoshi page sends you to the disamxhjdujbc page. - 21:30, 23 April 2014 (EDT)

Course, Courts and Tracks
DON'T CHANGE 2-8

I've noticed a bit of an incorrection ( or so I think ) with things such as Mario Kart courses, which should be called tracks, as in 'Racing Track'. 'Course' should refer to 'Golf Course', because we do say that Golf areas are courses, not racing areas. Therefore I propose that pages, articles and sections with an incorrect reafearal to 'Course' s should be moved or changed to 'Tracks'.

Proposer: Deadline: April 26, 2014, 23:59 GMT

Support - Change to 'Tracks'

 * 1) per proposal
 * 2) per proposal

Oppose - Keep as 'Courses'

 * 1) I've seen a number of articles that use "course" and "track" interchangeably. People know what is meant regardless of the word used. To go through and change one to the other is just nitpicking and doesn't really affect the accuracy of any particular article.
 * 2) Per Mario4Ever. This wouldn't really have any constructive effect.
 * 3) Per Mario4Ever. An Track is a Course.Even in Golf Games, you can call, for example: "Peach's Golf Course" as "Peach's Golf track". We understand that in the same way.
 * 4) "Course" can mean the track on which a race is run. Per Mario4Ever.
 * 5) - The official game manuals call them "courses" (at least the MK Wii and MK:DD ones do - it's even a header in the Table of Contents for the latter one).
 * 6) - Per Walkazo.
 * 7) The two words can be synonyms. Per all.
 * 8) They are the same thing!

Comments
Meh, the proposal is a bit vague for my liking. What exactly constitutes as an "incorrect" referral to "course" anyway? I'd like some more clarity on that. 11:42, 19 April 2014 (EDT)

This is like making a proposal to change capitals to lower case in subsection titles. There's no point in making it universal, and the effort we have to concentrate to enact such minor changes is not very productive. Courses have been nomenclature for a while; its being correct or not isn't really clear-cut since it can be used interchangeably. 12:19, 19 April 2014 (EDT)
 * So basically your saying that this isn't important enough, do it yourself? And 'incorrect' refers to any Mario Kart reference to course that should actually be called tracks. If you oppose, just oppose, that's why it's here. - 16:45, 19 April 2014 (EDT)
 * You made the proposal today, and since this isn't a Writing Guideline or Talk Page Proposal, the deadline is in a week, not two, so I fixed it for you.
 * My saying that this is way too trivial to warrant a proposal. 20:26, 19 April 2014 (EDT)

This isn't something that requires input from the entire community, it's a minor editorial dispute at best. Might be better to bring this up on individual talk pages or on the general discussion forums. I have no opinion on the subject itself. --
 * Yeah, didn't really know where to put this, this was the only place I could think of. I wouldn't describe this a nitpicky, more if just getting a bit of order to pages, but anyway if this doesn't really makes anyone else a slight bit confused/annoyed, there isn't a real propose to keep this up, but we could just wait and see. - 05:16, 20 April 2014 (EDT)
 * While it might've been better as a discussion in the Wiki Collabs forum board, seeing as the term is used on large numbers of pages (including templates and categories), it's not a minor change being suggested here, so the Proposals isn't a bad place to go with the issue: it's certainly better than trying to host it on one or more talk pages. - 19:43, 21 April 2014 (EDT)

The two words can be synonmyms. I honestly don't think it makes the biggest difference. 18:30, 22 April 2014 (EDT)

McDonalds
DON'T CREATE 1-6

Nintendo has had a couple of licenses with McDonalds for about 20 years, but there is no official page/pages about these licenses on the wikipedia. I propose that a page be made on the Happy Meal Lines.

Proposer: Deadline: April 29, 2014, 23:59 GMT

Support - Create Page/Pages

 * 1) per my proposal

Oppose - Don't do anything!

 * 1) Firstly, they are listed here. Second, unlike the K'NEX sets, there really aren't enough of these to justify creating an entire new page on them.
 * 2) Per Vommack.
 * 3) Seriously, we don't need a page on cheap merchandise that doesn't have any real purpose or function aside from being thrown in the garbage by parents. Also, per Vommack.
 * 4) Per Vommack and Ninelevendo.
 * 5) Per Vommack. Feel free to add to the articles mentioned if you have new information, though.
 * 6) Per all.

Comments
If you have enough info, go ahead and create it. There is no need for a proposal in tgis case.

This should be a TPP.--Vommack (talk) 14:18, 22 April 2014 (EDT)

This doesn't need a proposal. If the merchandise is official and real, then go add it to the merchandise page. 14:51, 22 April 2014 (EDT)
 * It's actually already on this page. He's saying it warrants an entire new article.--Vommack (talk) 15:04, 22 April 2014 (EDT)

Merge 9-Volt and 18-Volt
DON'T MERGE 1-8

So, first of all: These two guys from yhe WarioWare series should be considered as only one charactwr, and have only one page for they, much like it does in Kat and Ana, Me and Red, Dribble and Spitz... Considering that 18-Volt's page is little, I think that this should be merged with 9-Volt.

Proposer: Deadline: May 1, 2014, 23:59 GMT

Support

 * 1) Per proposal.

Oppose

 * 1) I feel that 18-Volt has more that can be said about him. More of 18-Volt's personality has been shown. Now I've only played 2 WarioWare games and I've seen more about both Red and 18-Volt than I have about Spitz in total, but even with the one game I've played that 18-Volt has been in, I still see he's shown more about himself. Plus his article isn't that short, pretty big if you ask me.
 * 2) Red is practically always seen with you, whereas 18-Volt is a bit like Wario in the sense of characters.
 * 3) Per Tails and Nin.
 * 4) 18 Volt's not particularly short for a WarioWare character page so I have no idea why you.re saying that. Anyway, 9-Volt and 18-Volt aren't an ensemble the way Ashley & red or Kat & Ana are; they're shown acting separately plenty of time (most notably D.I.Y and D.I.Y Showcase where the two have separate stages).
 * 5) - Per all.
 * 6) - Per standard procedure. As was mentioned in the comments, this should be a TTP.
 * 7) - Per Glowsquid.
 * 8) Per all.

Comments
This should be a TTP on 18-Volt's page.

Move Rosalina to Princess Rosalina
DELETED BY THE PROPOSER

So, I know that lots of users had proposed that, but once again I will propose it: Move Rosalina's page to "Princess Rosalina". I would say that because she is a princess, and I'm not saying this because of her crown or even her dress. Her Super Mario Galaxy's bio states:"Not much is known about Rosalina, the lonely princess who wanders the cosmos in the Comet Observatory, a giant starship that travels the celestial expanse. She is a great friend of the Luma, taking them in and caring for them as if they were her children. But there is a sadness behind her eyes. What has she lost out among the stars?"

Also her Mario Kart 8's bio (that is shared with Pink Gold Peach bio)states:"Baby Rosalina and Pink Gold Peach. Hit the road as a bouncing baby princess or a metallic mystery woman!"

Proposer: Deadline: May 8, 2014, 23:59 GMT

Support

 * 1) Per proposal.

Oppose

 * 1) Per standard procedure. As was mentioned in the comments, this should be a TTP.
 * 2) Per the supernatural jelly.

Comments
This should be a talk page proposal 11:57, 1 May 2014 (EDT)

Change the design of Species infoboxes
DON'T CHANGE 1-7

So, I've been checking out some other NIWA wikis an I noticed that many of them have more informative and organized species templates than this wiki's. I thought of this design that, besides separating the informations by type, it also avoids irregularity.

Just some notes. In the draft I linked above, the right one is for species that appear as enemies and don't live in a single land (like Goombas and Pokeys). The left one is for other species (mostly friendly NPCs) that are shown to be a population of one or more determined areas (like the Flip-Flop Folk and Pi'illos). In this infobox, the headers would not show up if there is not any info under them. I'm also trying to come up with a better word than Location. If anyone's got any ideas, we can change it if the proposal passes.

Proposer: Deadline: May 10, 2014, 23:59 GMT

Change it

 * 1) - Per my proposal.

Don't change it

 * 1) Per Mario in the comments.
 * 2) Also Per Mario.
 * 3) Per all.
 * 4) - Per myself and Mario in the comments.
 * 5) I'm surprised people perred me because I thought it's just a little nitpick. Oh well, I'm not liking the new design. Per myself and 'kazo.
 * 6) } &mdash; Per all.
 * 7) Per Walkazo and Mario (that pun by the way) in the comments.

Comments
Infoboxes in general could probably benefit from some work: making blank sections not show up would be a plus, but I think our current row-by-row approach is good (it just needs to be set-up so that the rows always alternate colours, but if it can be done for nav templates, I'm sure infoboxes can be automated like that too). Having sub-headers just adds unnecessary area (extra lines, and more blank space), and the location stuff seems more like speculating or otherwise interpreting the info, rather than just presenting hard facts at a glance. The "related" and "subspecies" also shouldn't be collapsed by default, I think, since having long lists that need collapsing is the exception, not the rule. -

As 'kazo said earlier, I don't like the way the "location" aspect is handled. The article content itself is already adequate to give readers a clue where enemies are typically located. And we have Goombas, which occur nearly everywhere. 14:28, 3 May 2014 (EDT)

The "Type" part is also quite ridiculous. This isn't Pokemon...--Vommack (talk) 19:09, 8 May 2014 (EDT)
 * I suppose it's not very effective. http://forum.mariowiki.com/Smileys/default/dk.gif 16:57, 9 May 2014 (EDT)
 * This change doesn't affect this user.... Why do you want to change it anyway? We can have our own, unique species box. -  17:04, 9 May 2014 (EDT)

Change Page Names for Mario Kart Courses
DON'T CHANGE 1-5

Recently, due to the release of Mario Kart 8, I have been looking over and creating links for retro courses (courses that originate in one Mario Kart game and are brought back in another) and courses based off of another stage in a Mario game. Here are some page names: As you can see, all these names are differently formatted, and I only pulled 6 examples. My proposal is to create a uniform page name for all race courses to keep it consistent and spare confusion. All race courses from Mario Kart will have the same format; even new courses from Mario Kart 8 like Water Park: This would be Course (Game abbreviation). Here are what the previous examples would look like: Here are the abbreviations that would be used if this proposal is passed: This would avoid confusion and keep everything orderly.
 * Tick-Tock Clock (race course) - First appeared in Mario Kart DS; Retro course in Mario Kart 8
 * Dry Dry Desert (course) - First appeared in Mario Kart: Double Dash!!; Retro course in Mario Kart 8
 * Moo Moo Meadows - First appeared in Mario Kart Wii; Retro course in Mario Kart 8
 * DK Jungle (Mario Kart) - First appeared in Mario Kart 7; Retro course in Mario Kart 8
 * Sherbet Land (GCN) - First appeared in Mario Kart: Double Dash!!; Retro course in Mario Kart 8
 * Water Park - First appeared in Mario Kart 8 (New course)
 * - First appeared in Mario Kart DS; Retro course in Mario Kart 8
 * - First appeared in Mario Kart: Double Dash!!; Retro course in Mario Kart 8
 * - First appeared in Mario Kart Wii; Retro course in Mario Kart 8
 * - First appeared in Mario Kart 7; Retro course in Mario Kart 8
 * - First appeared in Mario Kart: Double Dash!!; Retro course in Mario Kart 8
 * - First appeared in Mario Kart 8 (New course)

Proposer: Deadline: May 24, 2014 at 23:59 GMT.

Support

 * 1) Per proposal and it would make everything a lot more organized.

Oppose

 * 1) - Identifiers (in brackets) are only for cases where multiple things share one name, which isn't always the case with Mario Kart courses, hence some don't have anything. Other times, a name's only used for a course once, but is used for other things elsewhere, which is why things like "(course)" are used for some titles. As for the course names that are recurring in the series, the official policy (see the last bullet of Point 2) is that the identifier is the console abbreviation, which matches retro course names and also avoids inconsistencies in the game abbreviations (everyone calls it "SNES", but different folks might want to use "MKDD" or even "MK:DD!!" instead of "MK:DD"). I think it's better for the courses to be consistent with the overall naming policy, rather than get their own specific set of rules.
 * 2) Per Walkazo.
 * 3) Per Walkazo.
 * 4) Per Walkazo, although I think we could do with establishing a standard on (course) vs. (race course), looking at the first two examples in that list.
 * 5) Per Walkazo, and per Porplemontage in the comments section.

Comments
I don't think a proposal is necessary. The naming policy's section on shared titles already says that for Mario Kart games, console abbreviations are used to be consistent with the retro course naming convention, so this is something we'd end up doing automatically.

Can you use instead of having these red links? 08:36, 18 May 2014 (EDT)
 * I'm not really sure how to do that, but if you want to, you can change it. 10:45, 18 May 2014 (EDT)

@Vommak: That is the whole reason why I satrted this proposal, and I just grew that idea, so if this doesn't pass, I still want there to be uniformity like you said. 16:49, 18 May 2014 (EDT)


 * That is an example of 1-bullet here. In general, course is good. But Super Mario 64 identifies maps as courses, so Tick Tock Clock and Tick-Tock Clock (race course) are both courses. Which is why "race course" is used to differentiate one from the other. Also see my comments here about console abbreviations making the article relevant to multiple games. -- 17:18, 18 May 2014 (EDT)

Separating confirmed and possible generic-looking character appearances
INCLUDE SEPARATELY 13-0

This proposal is based on discussions on Toad's talk page, where expressed concern about the page covering games where it is only assumed that THE Toad is involved, but not confirmed. Assumptions are best avoided on a fact-based wiki like ours, but assuming things like the briefly playable Toad in Mario & Luigi: Superstar Saga is THE Toad isn't unreasonable, and outright removing the information is likely to make it look there's gaps in our coverage, confusing or even frustrating readers. Furthermore, moving the info to the overal species page would be less than ideal when we're talking about specific Toad individuals, and making new articles for every not-THE-Toad character is also far less efficient than simply leaving the information on the perfectly good page we have for our established recurring specific Toad individual (whom everyone assumes is all the unnamed Toads anyway).

Fortunately, we are allowed to make interpretations as long as they are "straightforward and logical [...] and explicitly stated to be "implied"", so as long as we're clear about what's confirmed and what's not, it's perfectly within current regulations to leave that info on the Toad character page. It just needs to be reorganized a bit, and for that I propose the creation of a Possible appearances section, which would come after History and start out with a brief discussion about the confusion over appearances and then cover all the unconfirmed stuff in fully fleshed-out sections with headers (just like History; as opposed to using a table, although could still be used in addition to some text to link to the species page depending on the exact situation). For Toad, this would mean moving a number of sections from History to the new section, and merging any extra info found in the current "Confusion with appearances" section.

And the reason why this is a mainspace Proposal and not a TPP is because Toad isn't the only generic-looking character with confused appearance history: numerous other characters like Kamek or Yoshi could potentially benefit from "Possible appearances" sections. So rather than just proposing this new organization for Toad's page, I'm seeking approval for the system as a whole as a way to deal with this sort of appearance ambiguity, past, present and future.

Proposer: Deadline: May 31, 2014, 23:59 GMT

Support

 * 1) - Per proposal and the Toad talk page. Keep the information on likely yet unconfirmed appearances on the character page, but move it to a new "Possible appearances" section, rather than leaving it in the regular History.
 * 2) Per Walkazo
 * 3) Per proposal. THE Toad character is always just an ambiguous thing: I've heard somewhere that the playable Toad in Mario Kart and whatnot is actually never intended to be a standalone character but localizations characterize and singularize this one Toad. Same with Yoshi and Kamek. I think making a "Possible Appearances" section would clear up some of the cloudy mess that are in this characters and possibly resolve any conflict regarding if this Toad that appears is THE Toad or not.
 * 4) The Possible Apperances section would help heaps. The Blue Toad from 3D Land or SMB2 is a prime example.
 * 5) Per proposal.
 * 6) Per all.
 * 7) Per all.
 * 8) If only Nintendo would bother to give these kinds of people a less generic appearance. Sounds like a plan, though, 'kazo.
 * 9) Per all.
 * 10) Per all. Only concern is that this might open up articles to certain degrees of unreasonable yet difficult to refute fantheories. Even as I type that, I can't think of any specific examples off hand, but it's something to keep in mind while building these new sections.
 * 11) Per all.
 * 12) Per everyone.
 * 13) I agree with Ninelevendo and Walkazo.

List Mario Party Minigames in which a certain enemy appears
LIST THE MINIGAMES 4-0-1

I've been looking at the Mario Party: Island Tour subheading for the Goomba page, and yet it only states that they appear in various minigames. That was a real bummer to me, because I wanted to know what minigames Goombas appear in other than Git Along, Goomba!, Match Faker, Starring Artist, and Tap Dash.

The only reason why this is a Writing Guideline Proposal and not a TPP is because the Goomba isn't the only page with this problem. This is the same reason why I proposed this in the first place. Pages such as Koopa Troopa and Shy Guy have the same coincidence. Therefore, I would like to propose that, for enemies that appear in excessive minigames for just one game in the Mario Party series, either a list is made for all minigames in which the enemy appears in with a lot of detail as to the role of the enemy, or simply state that "it appeared in various minigames".

Should the proposal pass on one option, users may take action accordingly, but must ask for permission to do so.

Proposer: Deadline: May 31, 2014, 23:59 GMT.

List the minigames the enemy appears in with detail

 * 1) In my opinion, the whole purpose of the wiki's Mario Party subheadings is to list exactly which enemies appear in certain minigames, since these pages themselves don't provide that info. Per the proposal.
 * 2) Just as long as it doesn't unfeature articles in the future, I won't mind more comprehensive coverage on Mario Party minigames, just so the details aren't excessive.
 * 3) Even though I don't see why we need this proposal, it's the right thing to do.
 * 4) Per Mario.

Make No Standard

 * NO, they would both be pointless and confusing, it looks fine the way it is.

Comments
The way I'm interpreting it, you want a literal list of minigame appearances? 21:14, 24 May 2014 (EDT)


 * Yes, exactly the way you mentioned it, but still feel free to make suggestions. Stonehill (talk) 21:31, 24 May 2014 (EDT)
 * The way Chain Chomp does it is pretty much a list of appearances, but with more detail. What do you think about it? 21:37, 24 May 2014 (EDT)


 * Okay, I understand. Let me reword the proposal. Stonehill (talk) 22:21, 24 May 2014 (EDT)

Okay, I'm settled: I don't believe this has to be a standard. It's just that people aren't willing to document every appearance for each enemy for every minigame. I fear that, enacted or not, this proposal won't change much, so maybe it's not needed, and you can start adding information right away. 01:57, 25 May 2014 (EDT)
 * I don't know that it's an unwillingness so much as it's a big job that no one has really taken the initiative to tackle yet. Or that it might not be obvious that it needs to be done, given that Chain Chomp is currently the only article that does it to any volume. In either case, I agree with a twist on the notion of it not needing to be a standard. It should be standard to look into if adding a section detailing appearances is feasible, given either the abundance or lack of appearances. The "not be a standard" part happens on either end of the spectrum. I think Stonehill's proposal is a decent way to explain this middle ground. Not (currently) going to submit a formal vote, as I don't see an option that really covers this middle ground, the voting options are currently "yes, yes kinda and no". -- [[Image:Shyghost.PNG]]Chris[[Image:Shyghost.PNG]] 06:44, 25 May 2014 (EDT)


 * Okay, I see where you're headed. Anyways, I'm creating test pages for the enemies to make it look as detailed as the Chain Chomp one. Once I'm finished, you can view them here, here, and here. Maybe then, you can understand the direction I'm going. Stonehill (talk) 15:47, 25 May 2014 (EDT)
 * "No one has really taken initiative to tackle yet" is basically an euphemism for "not now, I don't feel like it, I don't have the time" a.k.a. not willing. Look, I'm not willing either, I'll straight up say it. But again, you can do what I did to Chain Chomp, and nobody is going to bat an eyelid. 16:45, 26 May 2014 (EDT)
 * Why didn't you just DIY instead of making a proposal? People later on will copy you. - 16:58, 26 May 2014 (EDT)
 * Precedents aren't that powerful. 17:34, 26 May 2014 (EDT)
 * I prefer to assume the best of our userbase when making assertions about why this or that hasn't been done. All evidence suggests that this hasn't happened due to a lack understanding that it needs to be looked into for articles, rather than a mass shrug from editors. I agree that, at this point, we can safely skip the proposal and just add the sections, then go from there. -- [[Image:Shyghost.PNG]]Chris[[Image:Shyghost.PNG]] 22:16, 26 May 2014 (EDT)

I'm confused, do you want to do it like: Goomba appears in this game, this game, this game, this game, and this game, or did you want to do a bullet point list? -- 17:47, 26 May 2014 (EDT)
 * Correct me if I'm wrong, but I think it's like Goombas also appeared in Mario Party: Island Tour in five minigames; Goomba Tower Takedown you get the point. - 18:00, 26 May 2014 (EDT)


 * I see.... Stonehill (talk) 19:14, 28 May 2014 (EDT)

Create mother articles for Mario Kart tires & gliders
CREATE 9-0

Looking back at a nearly 2-month-old proposal by, I noticed that there's no mother articles for tires or gliders. Therefore, I propose that we create the said articles, so that they have a little info, as well as direct links and photos of the tire and glider customization from 7 and 8.

Proposer: Deadline: June 12, 2014, 23:59 GMT.

Support

 * 1) Per proposal.
 * 2) Per proposal.
 * 3) Does this really warrant a proposal?
 * 4) I think it will be useful! Good idea!
 * 5) This is a great idea! I have been thinking about doing this for a while, but never got around to it, but now it is in a proposal, we can actually do it! It would also keep all the parts much more organized. Per proposal.
 * 6) We have kart articles, so we should have tire and glider articles.
 * 7) Ditto.
 * 8) I agree with Mario7's comment.
 * 9) Per proposal.

Comments
@Stonehill In your proposal, could you add creating a page entitled ? I think this would also help with your idea and it would keep all parts on one page. 13:47, 5 June 2014 (EDT)

What Ninelevendo said. For the most part, a proposal isn't necessary to create and article, just make it if you think you can pull it off. If it doesn't work out, people will step in and it'll be handled. -- Chris 17:10, 5 June 2014 (EDT)

@Mario7 The problem with this is, the wiki may have had such a combined page, but it was probably removed or split.  At last, the rock fell.

Oh well...At least it's a step in the right direction!!!  At last, the rock fell.


 * Actuallu, I think a page called "Kart Parts" would be better. - 17:05, 6 June 2014 (EDT)


 * Actually, I'm not so sure about making that page. It doesn't really stand out to me, and if you want to make a proposal about it, it's fine, but you'd have to wait a month.  At last, the rock fell.

Hey guys...Sorry I'm so late about this...The test pages can be viewed here and here.

Write quotes with ambiguity in a more formal manner
DON'T CHANGE 1-14

That is to say, for example, a quote written like this:

He told me to follow you around this place.

Is instead written like this:

'' [ Bowser ] told me to follow you around [ World 1 ]. (said to Mario)''

Proposer: Deadline: June 12, 2014, 23:59 GMT

Oppose

 * 1) Why would you change quotes to incorrect and confusing quotes?
 * 2) Nope, in this way quotes lose all their fashion! Completely supporting Ninelevendo!
 * 3) I see your point, and while it is more formal to do that in some instances, the way they are done now are considered correct under the right circumstances, which they are.
 * 4) Per myself in the comments, we'll be supplying false quotes if we follow this.
 * 5) - Best to just leave listed quotes exactly as they were in the source material, otherwise it makes the information less authentic and useful, even if the changes are marked with square brackets (which is already done when using quotes in articles to back up statements and whatnot).
 * 6) - Per all, our current method serves our needs better.
 * 7) That's not what the quote is, and... it's kinda strange, so Per everyone.
 * 8) There would be a policy against this already. Per Ninelevendo, Mario7, Yoshi876, Walkazo, and Koopakoolklub.
 * 9) The links, while sometimes kind of dumb, clarify who or what the speaker is referring to, so it's NOT ambiguous as it is claimed here. Altering quotes just makes it more confusing, not less.
 * 10) - We are here to quote everything as is and we think it is defying a rule that everything must be taken from the original content and it is incorrect. That just makes everything fabricated. Per everyone.
 * 11) - This doesn't even make sense...?
 * 12) - Per me in the comments, as well as Ninelevendo, Walkazo, and Mario.
 * 13) - What the other saids. If a quote *really* can use context, I just put it in brackets before the quote proper, like [Upon seeing (something) or "[In reaction to _]".
 * 14) Per all.

Comments
What is this trying to accomplish exactly? And since when do we write You? - 01:53, 5 June 2014 (EDT)

I need this explaining, because it looks like you're changing the example quote to something different, which means that it is no longer a quote from that game.

In general this would only be needed in cases where the subject isn't clear, but we generally don't use quotes like that where quotes are needed, in fact I can't think of any off the top of my head. Can you provide me with a link to any articles where this is going to make a difference? -- Chris 03:41, 5 June 2014 (EDT)


 * I knew this would happen. :P But anyway, here are some examples of what I'm talking about:  RickTommy (talk) 04:19, 5 June 2014 (EDT)
 * My issue is that looking at that, you have changed some of the comments by removing "he's" and replacing them with "Bowser" or whatever, thus changing the quote and making it incorrect.
 * The thing is, that's the formal way of writing quotes with ambiguity - by changing pronouns to the name of the character they are referring to, and putting them in square brackets. RickTommy (talk) 04:24, 5 June 2014 (EDT)
 * The thing is though, that is how the quote is said so if we transcribe it like your way we'll be supplying false quotes.
 * Not precisely. A quote is still fundamentally correct if all that is changed is a "btw, context" to the reader, court documents and reporting outlets use this method, as clarity is more important than keeping a few He's and She's. That said, I wanted an example because I didn't think we had many articles that used quotes that would need and our current method of just linking indicators off to relevant articles seems to be working fine with less visual clutter. -- [[Image:Shyghost.PNG]]Chris[[Image:Shyghost.PNG]] 17:05, 5 June 2014 (EDT)

@RickTommy I have another solution for you. Try taking cues around the links of the quotes. They should tell you which context is which. Stonehill (talk) 20:31, 5 June 2014 (EDT)

I guess we should reproduce the quote as much as possible.. In case of the undefined subjects, we have one of the two options: If we have an article on that subject, we can use pipe-linking to remove any doubts about who exactly is that subject? [e.g: Bowser : "I hate him very much."]. There, we kept the quote and identified the subject.. Otherwise, If we don't have the subject as an article (I cannot think of use of that here), we can add something about who the character is talking about [e.g: Guy1 : "If I didn't return by 11:00, he is going to kill me for sure." (About his father)] or if that is not acceptable, we can use something like that. (i.e: "If I didn't return by 11:00, he is going to kill me for sure.) In all cases, we don't have any reason to change the quote.-- 07:27, 6 June 2014 (EDT)
 * I have a template in my sandbox that would assist with that if it was ever needed. That aside, I would agree with this proposal if the quote is in the article body text, rather than the actual quote/LLQuote template. 18:15, 10 June 2014 (EDT)

Formality is good, right up to the point where it starts interfering with communication. This is well past that point. In actual formal writing, e.g., a newspaper, I don't recall ever seeing any bracketed info that made it unclear what the person's exact words were. It's always something like the first part of the example sentence, replacing a pronoun with the name of the person it's referring to, when that context is removed. I've never seen anything as egregious as the last part of that sentence. If I'm reading the bracketed substitution, my guess would be that he said "here", not "this place". Even by the given example, this proposal would remove information, with no obvious benefit. Plus, we have an advantage over printed newspaper. Here, a reader can hover over a word and get an explanation if they so desire, which is exactly what the current method does in a concise, elegant way. To this request for an absurdly high level of formality, I can only echo the words attributed to Winston Churchill, when an editor mangled a sentence of his to remove a preposition from the end: "This is the type of arrant pedantry up with which I will not put!" --Steve470 (talk) 08:50, 11 June 2014 (EDT)

Yeah,besides the Wiki requires everything to come from its original source. That is defying a rule of the Wiki.That is not how we do things around here. We're here for keeping everything accurate as possible no matter what. Our wiki will continue till the end of time possibly and it keeps on growing and we're not complete as far as we are 95% complete but new games are being announced and are released each year. Our wiki will last till the final Mario game is released maybe.