MarioWiki:Proposals

Writing guidelines
None at the moment.

New features
None at the moment.

Removals
None at the moment.

Impose stricter policies for renaming files
I think the wiki should have stricter policies for renaming files, and I will give reasons why. Before I start, I need to explain that I start the file renaming craze. In August 2018, I saw some bad file names on the Donkey Kong Country page (e.g. KrashKlash.PNG) and felt it did not describe the article clearly enough. I moved the file name to File:Krash DKC.png. While it doesn't specifically mention "sprite" in the title, it still gives us a rough idea of what the subject is about. My file renaming led to Porplemontage adding in an extra rule on the image use policy.

Some months later, there has been a file renaming craze. Without getting into specifics here, this has not only led to correcting poorly named files. This has also led to minor things like "WW" being changed to Wario World simply because another game, Wario's Woods, has the same abbreviation. However, Wild Swing-Ding is obviously not in Wario's Woods, for others who know the game well enough.

Let's talk about the dashes/hyphens. Now I'm aware a recent rule has allowed them in subject name, but why should we move a file like File:CharacterSelect-SSBMelee.png if it already describes the subject clearly enough? A hyphen or space, it won't describe the file name any more or less. I have seen a lot of file names with parentheses (ex. File:Home-Run Contest (Super Smash Bros. Melee).jpg). Now for me, this isn't the most ideal way to name a file, but it still describes the article nonetheless. Sometimes it helps me not take a closer glance at the file name. For example, File:Yoshi Artwork - Mario Party 6.png. If the file were named it would not separate the game name from the character and subject. This are other files that I believe should not be renamed. Again, we should only rename if it is evident that the image could use with a better name or is not described clearly enough.

Another issue is the category, Category:Pages with broken file links. There's already 4,300+ pages in here, and if we keep renaming files unnecessarily, then it would only get larger and larger. I admit that I am guilty for adding to the list, since I have renamed/replaced many many images, but ultimately, does the average user want to be changing the file names on their userpage constantly? Only administrators can edit user pages as well, so users cannot fix the names of renamed images on their user pages.

Another thing is if I were quickly searching for a picture of, let's say, Rambi the Rhino. If all the images were named DKC Rambi or DKC2 Rambi, then it would be harder to find images on Rambi alone. Users could search on Rambi's article for images, but at least there's some diversity in file naming options. In my opinion, the diversity in file names corresponds to the inclusive nature of that Super Mario Wiki has.

File names are ultimately the backend to the wiki. It does not affect what the wiki is mainly about, providing content on the Mario, Yoshi, Wario, and my favorite series of them all, the Donkey Kong series. The file is displayed the same whether it has a hyphen, a space, or even all the words lumped together (the lattermost option can be convenient in some cases, for instance, so that a user does not have to alternate between the Shift key and spacebar; i personally like the visibility for filenames, but I am just noting the option is there). The average reader will not notice the difference to a file name at all. If 50 files are being moved every hour, the poor administrators are being put to work deleting all the redirects, when we could be focusing on more important issues, such as Category:Rewrite requested, Category:Image requested, or anything other under the maintenance category.

I think we could discuss some suggested naming standards to add to the image use policy. For example, I like the naming standard where it lists the subject, the game name/abbreviation, and then the type of image. The subject's name first because the image is about the character, the location, the item, etc. first and foremost. The game name or abbreviate shows the game that the character is in. Lastly, the type describes if the image is either artwork, sprite, screenshot, logo, etc. For example, Rambi DKC sprite.png. For the "type" part of the filename, i like to make it lowercase, since the 'type' is comparable to an identifier of an article. Words such as screenshot, sprite, and logo are common noun, so if I made them lowercase, it's quicker to distinguish the proper noun (like the game, character names) from the common noun (like the word 'sprite' or 'screenshot').

For screenshots, I tend to name based on whatever the context is about. For example, in Mario Kart Wii, if Luigi is racing in Wario's Gold Mine, during the part where he encounters many Swoopers, I would name it like a sentence, e.g. "Luigi and Swoopers in Wario's Gold Mine MKWii.png". Keep in mind this is only an example and a suggestion on one of many possible ways I would clearly describe the file in shortest terms possible. For screenshots such as the start of World 1-1 in the 1985 Super Mario Bros. there would be less options for clearly naming the file as it's only Mario (or Luigi in 2P mode). For a file like this, I would name it "World 1-1 SMB1 start.png".

In short, the proposal is to more strictly regulate on when users can rename files, such as only if the extension is uppercase, or if the subject is not described clearly enough or has redundancy (e.g. "3293 mario 1.jpg" could be more accurately renamed to 'Mario in Castle Courtyard SM64.jpg'). All the examples for naming that I gave are suggestions, and I'd love to hear the community's input on this proposal.

Proposer: Deadline: November 1, 2019, 23:59 GMT

Support

 * 1) - I am the person who made the proposal.
 * 2) My thoughts exactly.
 * 3) - As someone with several gripes about the current file renaming craze (it floods the recent changes, breaks userpage files like crazy, and unnecessarily renames files), I have one word: Yes.
 * 4) - Tbh I don't really mind what kind of name a file has, as long as the name tells me what the file is about, then it's okay. If a file name uses the full name of the game instead of an abbreviated version, then no need to change the name, it still tells us what the file is about. If the file name is something like "File:9375073dk.PNG", then yeah, it needs to be changed cause it tells us basically nothing about what the file is about.

Oppose

 * 1) - See comment.
 * 2) - Per Alex95 primarily - this seems more strict than would reasonably be necessary, and as indicated by Trig, even if he does somewhat agree with the sentiment I think it still would've been much more preferable to discuss this at length with him prior to immediately going for a shift in policy.
 * 3) - I had to think long and hard about if I should make a statement here. Besides the comments I left, I want to be explicitly clear that we need a better system in place, in my opinion. However, this basically provides no real plan or structure to do so, and only really brings up the topic for people to be mindful of. I try my hardest to keep the impact of what I do as minimal as possible on both the Recent Changes page, and on the moderation staff's part. Until a formal plan that explicitly lists what actions will be taken to have a better naming scheme is made, I will be against the proposal.
 * 4) Per all. I see no reason to change anything at all.

Comments
Pretty sure the actual in-place rule is "don't rename files that are already named accurately," which has recently been broken to hell and back, thus annoying ME to hell and back. Anyways, I think that putting the game abbreviation before the subject makes infinitely more sense, as it's easier to find things in a licensing-based image category that way. Doc von Schmeltwick (talk) 01:11, October 25, 2019 (EDT)
 * If that's one of the rules, this proposal should help make the rule stricter and more enforced. Results May Vary (talk) 01:13, October 25, 2019 (EDT)

Well it's very very clear that this was targetted to me, or at least a majority of it is. I'm not necessarily upset about this, but I am somewhat disturbed by the fact that if I'm the main issue to you (the collective) here, that none of you would at least try to come to me about it? Hyphens were the only thing that were really ever brought up to me and even then a heavy majority of that conversation was more about what I was doing and not really asking why. There's nothing stopping me from explaining why I choose to rename a file except that virtually nobody consults me on it. I have a talk page too, y'know. If something isn't working out, like hyphens or WW being split to Wario's Woods/Wario World (which I still deem as a valid change), I would be delighted to work it out and reach a consensus. Please don't assume I won't try and work with you.

That's fine or whatever, I guess.

I'm close to supporting this, which may or may or not surprise you, with some exceptions in regards to Doc and I leaning more towards the Game-Object-Type format, and the disuse of parentheses in pages. I'm not sure if I would even stop there, either, as I think it would be better to rewrite/recreate the Image Use Policy to have a much clearer standard for the initial naming files, before addressing the rename of files as a new section.

To quote RMV, "Another thing is if I were quickly searching for a picture of, let's say, Rambi the Rhino. If all the images were named DKC Rambi or DKC2 Rambi, then it would be harder to find images on Rambi alone. Users could search on Rambi's article for images, but at least there's some diversity in file naming options. In my opinion, the diversity in file names corresponds to the inclusive nature of that Super Mario Wiki has." This statement is a part of why I have increased the general size of files I rename, because a lot of files have been along the lines of Mario1 or Waluigi3, which is not very descriptive.

EDIT (addition): Another interesting comment from TheDarkStar is "breaks userpage files like crazy". I actually do sometimes make talk page comments about the files I change if I know offhand that the user is active. I can do this at a higher frequency if so requested of me.

In short, my biggest intent is that I should be able to look at a file name and know what is in the image and what game the image is from without seeing the picture.

I think overall if this had a little more structure to what would be changed, I would be happy to both help create a standard and to sign on said standard. As of now, however, this seems more of a concept than an action. Trig - 10:46, October 25, 2019 (EDT)
 * Pretty sure I've said it multiple times in edit summaries, and a few times amidst other complaints on your talk page. Anyways, when a subject that has appeared in a zillion games has a generic image title, that's one thing, but ones that appeared only once ages ago don't need that kind of specificity, and you've been treating them with equal importance. Doc von Schmeltwick (talk) 12:17, October 25, 2019 (EDT)
 * I talked to Trig about this already, actually. 12:21, October 25, 2019 (EDT)

First of all, we don't need to be strict about how we name things. Game-type-subject is a suggestion, not a requirement. As long as the image says what it needs to, the file name is fine. However, there can be multiple images with the same subject, such as File:MP9 Mario.png and File:Mario MP9.png, so renaming them to be clearer is perfectly acceptable as well. The same holds true for images of subjects with both an artwork and a sprite image on the wiki, renaming the file to be distinct is helpful. But again, it's not a requirement, and it's up to the editor if they want to fix it. As for files with certain punctuation, I believe the reasoning is not everyone has access to the same marks. You can see this in page redirects that use a different apostrophe, so renaming the file to remove hyphens, dashes, parenthesis, etc. when the file's subject doesn't use them itself is also helpful, and I actually recommend it happens. For broken file links, things happen and time moves on. Images get deleted, moved, or replaced for a variety of reasons. There are 199,923 pages, 27,883 users with most having userpages, and 115,370 images as of this proposal. That's a total of 343,176 pages of some type of content to look through, so I perfectly understand not wanting to look through everything and keeping it to just mainspace. "Luigi and Swoopers in Wario's Gold Mine MKWii.png" - The Image use policy actually recommends against long names. Short and sweet is better. To conclude, Trig's filename movement has been, I'll say, 92% helpful so far. There are a few points where I move file names back (not to mention personal images and 'Shroom images), but I have had no problem with his file changes otherwise. 11:40, October 25, 2019 (EDT)
 * Look, the whole point of the proposal is for all of us to chill out about renaming too many filenames and let them be, so that we don't rename too many files. The proposal is not just about Trig but about all of us moving filenames. It's out of control. Results May Vary (talk) 15:07, October 25, 2019 (EDT)
 * Then, instead of going straight to a proposal that can be seen as trying to force people's hands, perhaps an actual discussion with the people in question would probably help smooth things out, especially if you're worried about flooding Recent Changes or something similar. And in any case, trying to get people to 'chill out' by arguing for stricter rule enforcement tends to have the opposite of the desired effect, at least in my experience. -- 15:23, October 25, 2019 (EDT)
 * Alex95, The subject-game-type format for filenames was only me recommending a suggested format for naming a file. I know the proposal was long but if Trig's name scheme wants to be suggested in image use policy as well, then I'm ok with that. I'm not trying to dictate the wiki with my filenames. I can see why there's confusion, so I'm trying my best to explain myself. Results May Vary (talk) 15:33, October 25, 2019 (EDT)
 * For the most part, a majority of the file names have been to get them to work with our policy. They're only following rules, though I did add an amendment earlier to keep punctuation in the subject's name. If there's any major problem, an admin will say something to the mover. 16:39, October 25, 2019 (EDT)
 * I was talking about dashes between words, for example: File:Mario-amiibo-yoshi.png. moving a filename like this solely to remove the dashes are the main problems in my opinion Results May Vary (talk) 16:43, October 25, 2019 (EDT)
 * I don't see why they should stay, either. It's far easier to just hit the space key, and the dashes don't really add to the file name. Sure, removing them doesn't really change much, but they aren't all that necessary, either. 16:49, October 25, 2019 (EDT)

I agree with the sentiment that images that already have clear titles shouldn't be renamed, and renaming titles specifically to remove things like dashes and hyphens is going overboard. That being said, this seems like something that needs a long discussion and probably shouldn't have been immediately rushed to the proposal stage. For that reason, I am remaining neutral. -- 16:32, October 25, 2019 (EDT)

Split articles/keep articles split if they have notable name and appearance changes. Merge articles if they have the same name and not enough changes from the original.
Currently, the wiki does not have a clear set guideline on how similar entites with different names or slightly different entities with the same name should be handled. If this proposal goes through I believe it will friendlier for new and exisiting wiki users as it allows content to be searched outside Mario Wiki and covered more cleanly.

I propose that articles covering similar should be split in the following conditions.


 * If there is a name change. This should be the most important factor in deciding an article split, as search engines such as Google rely on the name the most.
 * It is considered a different entity by the game itself in addition to the name change. Direct replacements such as Power Star to Grand Star can be covered in the original article. Moves used by different characters count.
 * If there are design differences in addition to the above, such as with Daisy Blossom and Goombo.
 * If the same name is shared, but there are significant differences to the point where a seperate article is needed to cover them all. Examples like Mario and Sonic games from Wii to DS count.

Articles possibily affected include: Daisy Blossom, Daisy Bomber, Daisy Parasol, Azure Roller, Cyber Slick, Goombo and the ports of games with the same name such as Captain Toad: Treasure Tracker and Luigi's Mansion.

Proposer: Deadline: October 27, 2019, 23:59 GMT

Support

 * 1) Not only do I think pages such as Azure Roller and Daisy Blossom should be split from Roller and Peach Blossom because they have different names and look different, they also don't appear in every game and share every single detail. Azure Roller appears in different CPU controller karts and time trials, and Daisy Blossom is all flowers and daisies and the background and frames are completely different, and also doesn't appear in games before Super Smash Bros. Ultimate. There is also the issue of how search engines such as Google cannot easily link Daisy Blossom to Peach Blossom and a user searching up the move will not get relevant results unless it's on a seperate page. There are a lot of people searching up wheels such as Retro Off Road and Cyber Slick. For games such as Captain Toad Treasure Tracker and Donkey Kong Country: Tropical Freeze with the same name and a lack of drastic sweeping changes, I think they should be merged and exclusive content covered in the article itself, then it would be friendlier if Switch owners are looking for the content.

Oppose

 * 1) The statement that there's no policy on splitting pages with the same name (prior to any editing) is downright false; policy and consensus have stated that if something has gameplay differences, it's splitting time. Azure Roller being merged to Roller doesn't even need a proposal, just a talk page discussion. Finally, this all seems like a knee-jerk reaction to the Daisy Bomber page being converted back to a redirect, seeing as it happened just yesterday.
 * 2) Per DarkStar and my principle towards opposing proposals that are purely reactive and/or prioritize forcing through a user's personal opinion over all else. In support of the later, it's evident that the proposal's claim (at least prior to any editing) of the wiki lacking "a guideline on how similar entites with different names or slightly different entities with the same name should be handled" is poorly researched to the point of being blatantly false - for starters, we have this proposal regarding ports, and with regards to slightly different entities and games bearing the same name, we have this section on the "Naming" page of our writing guidelines and the "New Article" guideline on titling pages for ported games, which I believe may have served as a basis for the aforementioned proposal.
 * 3) per the above, but it really seems too subjective/non-concrete to me. I think it would create more inconsistency over less due to not being able to tell alternates in-page and alternates new-page. - 11:23, October 20, 2019 (EDT)
 * 4) This proposal is extremely vague and your list doesn't even come close to how many articles this would affect, and is also confusing since it doesn't even mention which articles would be split and which ones would be merged if this passed. You're painting with far too broad of a brush here, matters like this should only be settled on a case-by-case basis. Also, like I told you before, having a different name alone is not an instant reason to split articles (on the other side of the coin, having the same name is also not an instant reason to merge articles) and would unnecessarily undo countless proposals over the years. I get that you really want Daisy Blossom to be split for whatever reason, but this is going way too far.
 * 5) As much as I'm actually extremely uneasy about merging Roller and Azure Roller, this proposal is just too vague to even consider supporting. Per all.
 * 6) To make my point clear, I do love echo fighters. However, that doesn't affect that fact that echo fighters are officially clones, and that point should be made clear as the proposer seems to think that the wiki has a bias against echos when it doesn't, as the only reason that they're treated differently is because of what they are officially considered. As a wiki we do not have any bias towards different characters, and reason why we would treat some differently is due to something official. On the other side though, this proposal seems to be made out of spite without much thought. Per all.
 * 7) Per everyone. Way too vague for my support.
 * 8) - First point, name alone is not enough, otherwise Super Thwomp and Star Thwomp would be separate. Second point, I don't even understand, this is obviously going to get a new page. Third point, if all of those three points align (which is not the case for Daisy Blossom), then yes, different name + different game play attributes = new page. Fourth point, we already do this. The Mario Kart pieces should be a different, better put-together proposal.
 * 9) Per all.
 * 10) Per all.
 * 11) Per all.
 * 12) Per all. There's absolutely no reason to split the same ability performed by a different character (the ability itself having an aethistic change).

Comments
We already split subjects with different names and appearances, such as with Goombo. Regardless, arguably Daisy's special moves are different than other variants, as Daisy is labelled as an echo fighter, contrary to other examples of variants which are often treated as their own separate thing. Due to that there is less ground to split Daisy's special moves when they are literally part of a official clone of a character. Regardless, the "and if there are less than four variants" thing is unnecessary, as really if a thing should be split than it should be split, merging stuff just because there is a lot of things would just be confusing and would pad out articles for no reason. 09:24, October 20, 2019 (EDT)

There are more differences between Daisy's moves and Peach's moves than Goombos and Goombas. I believe Daisy still have a seperate Movelist page in the game than Peach has. In New Super Mario Bros U Deluxe, Blue Toad and Yellow Toad were similar enough to be merged and not seperately selectable in game, and literally call the same model. They have seperate pages on the wiki. Echo Fighters are more like how you copy a file and it still takes up extra space on your harddrive, rather than creating a file shortcut. The original Japanese meaning even references how derivative numbers are still different numbers despite being copied from. -- memoryman3 09:30, October 20, 2019 (EDT)
 * There isn't more difference though. If anything, that just comes off as biased. As for Blue and Yellow Toad, you can actually select either of them. The reason that they are in the same slot and thus cannot play as both Blue and Yellow Toad is because Toadette took the slot the Blue Toad had. They have separate pages on the wiki simply due to their previous appearances regardless. If you copy a file it is still the same file, and the comparison has nothing to do with wether or not Daisy's move should be split.  09:40, October 20, 2019 (EDT)


 * Even if you could select Blue and Yellow Toad in different slots, the only difference between them is the color of their mushroom cap. No gameplay differences and no design differences other than that, Nintendo explictly kept them as similar as possible. They are still seperate pages. Like Peach and Daisy's moves the game appearances are a bit different. As for the copying thing, if the file is changed a bit, for all intents and purposes it is a different file. For Blue Toad and Yellow Toad I would probably keep them split for the search engine reasons.--MK8DX_Daisy_Icon.png memoryman3 09:46, October 20, 2019 (EDT)

I have updated the proposal to more clearly reflect what I mean, and how this could be applied wiki wide. This is not reactive. -- memoryman3 10:29, October 20, 2019 (EDT)

Been following the matter on the talk page, and this is rather poor form to say the least. -- 10:32, October 20, 2019 (EDT)

Generally poor form to make a proposal when you've been unanimously opposed on the talk page beforehand. 10:37, October 20, 2019 (EDT)

Explain how Daisy's moves don't deserve their own pages when they have been given their own pages ingame, plus content such as the identical Mario Kart wheels, Goombo, and the two Toads allowed to have their own pages with even less differences? That does not make any sense to me. We can very easily merge Goombo with Goomba as it is just the Super Mario Land variant of a Goomba with an appearance change. -- memoryman3 10:40, October 20, 2019 (EDT)
 * Explanation.


 * Azure Roller doesn't need a proposal, just a quick discussion.
 * Daisy's specials are practically identical to Peach's save for visual effects.
 * The Toads are separate characters, not the same toad in different hats.
 * That is my explanation. 10:44, October 20, 2019 (EDT)

In addition, Goombo and Goomba have different Japanese and English names, were explicitly described as relatives, and variants of existing enemies already have precedents for splitting. Try again. -- 10:46, October 20, 2019 (EDT)

Yes, but Daisy's moves arguably fall under the Goombo and Goomba variants. Daisy's moves, whilst behaving the same as Peach's moves, have differences including visual effects. Visuals are still a difference worth noting. If Daisy's moves looked a bit different and had the same name it would make sense to keep them merged. However the naming being different means that in order for the move to be properly represented across the web, it needs to be split into a new article. If you type Daisy Blossom into Google you don't get relevant images easily, unlike with Peach Blossom. Additionally. Daisy Blossom does not appear in any other Smash game other than Ultimate. They are also technically seperate moves, such as how Blue Toad and Yellow Toad are seperate characters. Daisy is not a Peach costume, she is unlocked seperately. It is the same thing for Azure Roller and normal Roller. Different unlock times, different appearances, different names, different wheels. A split makes sense even though the function is the same. -- memoryman3 10:50, October 20, 2019 (EDT)
 * It makes no sense to make a duplicate page just to note the difference in visuals. 10:59, October 20, 2019 (EDT)
 * The pages will not be duplicate pages however. Daisy Blossom's past edits had notable changes such as new images, new descriptions, and how it relates to Daisy's past instead of Peach's past. Daisy Parasol would show Daisy's 8 different parasol designs and how she uses it in her entrance animation and not her taunts and victory animations. The articles would also not be cluttered with references to previous games, like how Cyber Slicks and Azure Rollers don't reference Mario Kart 7. I plan to also revamp the Peach special pages along with this. --MK8DX_Daisy_Icon.png memoryman3 11:04, October 20, 2019 (EDT)


 * Have to second DarkStar here: The matter regarding the Final Smash will probably change when sufficient proof of differences beyond the visuals and character references (which are tied to the visual appearance, if I recall correctly) is put forth on the Talk Page where things were initially being discussed the day prior to this proposal. The same should apply for the rest of the special moves in question as well, I'd imagine. Much more pertinent is the fact that how we handle enemies and how we handle fighting moves are two entirely different baskets of eggs, and using the splitting of similar-but-differentiated enemy variants as a basis for splitting move variants that have not been sufficiently differentiated doesn't strike me as a particularly sound argument. -- 11:13, October 20, 2019 (EDT)

How so, it's literally the same thing. Goomba and Goombo have no differences beyond visuals and character references. Exact same thing with Blue Toad and Yellow Toad. You can easily merge Goombo with Goomba and no one would bat an eye. I have already put many arguments as to why Daisy's moves have merits to be seperated, and to be honest none of the reasons against it strike me as compelling or more substantial than "Daisy's just Peach in orange", and how in general there's an bias against Daisy in the wiki due to her fans. I've already provided external reasons such as search engines not correctly referencing Daisy Blossom and visual differences being important. When people are looking for Daisy Blossom, I'm pretty sure they DON'T want pictures of Peach's trophies -- memoryman3 11:22, October 20, 2019 (EDT)
 * If Daisy Blossom getting "proper web representation" is your main concern here, SmashWiki already covers it on its own page. And no, that's not a good reason to split, the "X wiki does it so we should do" argument has been shot down many, many times over the years. I don't know how many times we have to tell you that every single one of Daisy's moves is functionally identical to Peach's, the only differences are visuals which aren't enough to warrant a separate page. I'd also like to point out that, with the exception of her Final Smash, not even SmashWiki splits Daisy's moves and specifically mentions that there's no difference between them, and this is the same wiki that explains specific amounts of frame and knockback trajectories. Ultimate has been out for almost a year, if SmashWiki hasn't found any differences between Peach and Daisy's moves that actually affect gameplay, there aren't any. -- 11:36, October 20, 2019 (EDT)

Gameplay is not an argument. In fact I would say that basing it only on gameplay is unfair, when there are visual differences that affect areas such as Google Images. Or how an end user is looking for a specific variant. In that case we can say that there's no difference at all between Blue Toad and Yellow Toad and that they don't deserve seperate articles. But we split them, because when someone is looking for Blue Toad or a specific variant of a wheel, they are looking for information on that Toad or wheel specifically. Merging Daisy's named moves benefits absolutely no one except the people who REALLY dislike clone characters in fighting games and think they should be erased. -- memoryman3 11:58, October 20, 2019 (EDT)


 * I noticed you curiously skipped over my suggestion that you first prove there are more than visual-based and character-reference differences, and WT's rebuttal seems to indicate why, but in any case, I'll add that your statement on Goomba and Goombo is a circular argument - as stated previously, they also have different names and a statement from a notable source (Nintendo Power) that indicates they're related but not exactly the same. And again, splitting/merging enemies and attacks aren't handled with the same exact policies - and to boot, there have been numerous cases of pages for heavily similar enemies being split upon the basis of a different Japanese name. Furthermore, Blue Toad and Yellow Toad are very visibly two distinct characters that have both clearly appeared separately from each other, and are thus treated separately regardless of whether or not they serve the same gameplay function. As you just said in contradiction to your earlier point, gameplay is not an argument, and once we humor that notion and remove it from the equation, there are only visual-based differences to distinguish Daisy Blossom and Peach Blossom - thus no split.


 * In fact, you seem to be using only gameplay roles as the basis for suggesting that the aforementioned articles should be merged, with the implication that if Daisy Blossom isn't going to be split, then neither should those. This is a poorly constructed line of logic, per what I've just stated above: they're established as different characters by official material, with enough differentiation between them that is established by more than visuals. E.G. Goomba and Goombo are split on the basis of being similar-yet-distinct creatures with different names that exist in different locations, as has been established with many other regional variants (Beanbean Kingdom says hi), and Yellow and Blue Toad are split per being two different Toads that we see literally standing next to each other through the various cutscenes of the New Super Mario Bros. games they appear in, as has been established by viewing said scenes for at least five seconds. Therefore they deserve articles, contrary to what your opinion on that is.


 * In addition, you're trying to use an amendment to wiki policy to enact some arbitrary form of "one true wayism" that conflates multiple wide and distinct established proposals, guidelines and precedents and blatantly flies in the face of them for the sake of trying to obtain a desired result on a small subset of articles and correct some perceived "innate bias" against a given character. The problem with this is, even assuming said bias existed, this would be categorical overcorrecting in the other direction: the existence of said bias being invoked as the basis for this is dubious to begin with per a simple application of Hanlon's Razor (i.e. it's infinitely more believable that the page isn't split due to policy than due to some imagined character-based bias), and overall the wiki has done pretty well in regards to ironing out character favoritism and its opposite. In addition, the correction of supposed bias in scenarios like this is very often a flimsy cover to enforce a more "preferable" one; nothing is being done with Daisy's special moves that wouldn't have been done with any other moves of the same nature, and attributing this to a desire for clone characters to be """erased""" is patently nonsensical and without merit, not least because (if I recall correctly) Daisy was among one of the more popularly desired characters for Smash, as was the case with many other newcomers and Echo Fighters.


 * Finally, even ignoring that the stated "web search engine optimization" motive is evidently an ad hoc explanation trying to cover for the other less substantiated ones rebutted above, it would likely be far from high on the list of this wiki's priorities, well below maintaining a standard of encyclopedic integrity. And last I checked, I highly doubt that standard is worth sacrificing on the altar of Google results. -- 12:12, October 20, 2019 (EDT)

That does not explain why the seperate wheel designs in Mario Kart are still covered seperately despite only having decal differences. I am not objecting to these but Daisy's is literally the only case of differently named moves being used on different characters, in a different list of games, being merged. I'm not arguing that every similar move and object should be merged. I'm arguing that they should stay seperate and Daisy's moves should be seperated too. The establishment of them being different is straight in game, where Daisy Bomber and Peach Bomber have their own pages. Smash in itself is not a traditional fighter either. -- memoryman3 12:23, October 20, 2019 (EDT)


 * Simple: Tires have separate articles because Mario Kart 7 and 8 established the trend of tire choice affecting vehicle performance. And if you didn't object to them, then why invoke them at all and go so far as to claim some of those instances don't deserve articles?


 * In addition, Daisy's likely seems to be the only case because she's the only Echo Fighter in Smash who's native to the Mario franchise - AKA the main reason her moves are covered on their own articles like all the other Mario characters; if other cases come up, they will receive the same treatment, and in fact I recall Dr. Mario used to receive the same treatment prior to determining that his moves were different enough from Mario's to warrant splitting coverage accordingly. Smash not being a traditional fighter has no bearing on this, and more to the point was never brought up by anyone else before you mentioned it. -- 12:30, October 20, 2019 (EDT)

That...still doesn't explain the wheels in Mario Kart. One user already explained merging the palette swapped wheels made them uneasy, despite them being identical in every other way. Also, I think being an Echo Fighter is not a good reason to merge the moves, when they are not exactly the same. Fighting game fans do have an inherent bias against clone characters and it ripples everywhere from message boards to tier lists. What benefit is there to keeping Daisy's moves merged, and do they outweigh the drawbacks, if there are even any? I agree though, I don't think I have made my point clear and this proposal is too vague. -- memoryman3 12:35, October 20, 2019 (EDT)
 * I know I said I'd support merging the recolor tires, but I'm starting to go back on that because of one reason, and that's the fact that they're Mario Kart 8 variants of tires that were previously introduced in Mario Kart 7, and merging them might be a bit messy. And no, this isn't the same thing as Daisy Blossom being introduced in Ultimate. Tires in Mario Kart have differing stats from game to game, and it would be awkward having a section talking about stats in Mario Kart 7 when that specific tire didn't even exist yet. Meanwhile, Peach Blossom has changed very little since its introduction in Brawl, and doesn't have any game-specific sections that would make Daisy Blossom's inclusion on the page feel awkward. Also, I don't think many users on this wiki hate clone characters. Personally, I welcome Echo Fighters because it gives a chance for more characters to get in the game. -- 12:43, October 20, 2019 (EDT)
 * Peach Blossom's operation has changed notably between game to game however. In Brawl, it spawned thirteen small peaches, and did not affect users airborne. In Smash 4, it affected users airborne in exchange for shorter range and sleeping time, it also got completely redrawn and summoned three large peaches. Ultimate's variant had significantly increased sleeping time and new aesthetics in the background. Peach Bomber has changed drastically between games (startup, distance, damage, effects and knockback) and had custom move variants that Daisy's version obviously lacks. Peach Parasol also got tweaked quite a bit. Of course, information such as the trophies do not relate to Daisy's variant at all. --MK8DX_Daisy_Icon.png memoryman3 12:51, October 20, 2019 (EDT)


 * And again with the circular arguing. On top of differences between MK7 and 8, the wheels are all distinct from each other and have a tangible effect on gameplay (i.e. changing the overall stats of the kart they're used on) that is not universally shared among each wheel type. The palettes of said wheels contribute absolutely nothing towards that, and thus are safe to merge. In short: tire choice affects vehicle performance, and the only way that doesn't explain it is if you didn't read it to begin with.


 * And again, not only is MarioWiki not the place to try to correct biases against particular characters presumed or otherwise (because Righting Great Wrongs™ is not our job period, and should not take priority over encyclopedic integrity), the bias you're citing against this specific clone character is a non-factor in the moves receiving their current coverage. That's why I've referred to it with the air of "alleged bias" - not because it literally doesn't exist, but because there's absolutely no tangible proof of its influence on the matter at hand. And with regards to the matter at hand, the discussion should have remained on the article's Talk Page, rather than used as a not-at-all-solid basis for enacting a vague policy change that steps on the toes of several well-established policies and guidelines before it. I will likely be making my cases there as well later on.


 * The merge is not done for the sake of some arbitrary benefit, but because it is in accordance with established policies, guidelines and precedents on covering such things, which dictates it is not substantially differentiated enough to warrant a split. (Clarifying Edit: Peach Blossom has had various changes between games, yes - but Daisy Blossom has not, as it is directly based on the version used with Ultimate, and there has yet to be any proof of difference between those two versions, making the changes to Peach Blossom between games irrelevant.) And as we've painstakingly outlined, the drawbacks of blatantly and selectively ignoring these policies, guidelines and precedents in favor of a poorly-justified split whose reasoning has been shown to be thoroughly unsound rebutted far outweighs any of the similarly-debated-and-rebutted imagined benefits. -- 12:57, October 20, 2019 (EDT)

That falls apart when you realise that quoted from the wiki itself, The only difference between the Roller and Azure Roller is the azure palette and the gray screw-like rims, surrounded by a yellow outline., Absolutely no stat differences whatsoever. Many wheels in Mario Kart have identical stats, yet they are seperated for consistency. By that precedent, all of Daisy's named specials should be seperated for encyclopedic intergity and a lack of bias. Arguing against it is essentially identical to arguing against WaluigiTime's point of keeping the wheels seperate.-- memoryman3 13:02, October 20, 2019 (EDT)

I wasn't going to comment further, but here's an Omega Tyrant-style deconstruction.

Currently, the wiki does not have a clear set guideline on how similar entites with different names or slightly different entities with the same name should be handled. No? Many discussions have decided by consensus that similar entities with different names should be merged. If this proposal goes through I believe it will friendlier for new and exisiting wiki users as it allows content to be searched outside Mario Wiki and covered more cleanly. You forget about the existing in-wiki search tool. ''If there is a name change. This should be the most important factor in deciding an article split, as search engines such as Google rely on the name the most.'' That's already a candidate for moving by policy. Also, why do search engines matter? The wiki is listed pretty high up on most searches, so it's kinda unnecessary. ''It is considered a different entity by the game itself in addition to the name change. Direct replacements such as Power Star to Grand Star can be covered in the original article. Moves used by different characters count.'' That's also normally a split, if it has gameplay differences. If there are design differences in addition to the above, such as with Daisy Blossom and Goombo. Goombo's been confirmed to be related to Goombas. They are not the same thing. ''If the same name is shared, but there are significant differences to the point where a seperate article is needed to cover them all. Examples like Mario and Sonic games from Wii to DS count.'' That's already a split too. 3/4 of this list is completely unnecessary, and the other quarter is dubious at best. 13:33, October 20, 2019 (EDT)

I agree about most of this propsal being vague. I want to delete it and make a talk page proposal on the relevant article. -- memoryman3 13:44, October 20, 2019 (EDT)


 * A lot of DarkStar's response is what I basically covered in my vote reason above, but it does bear repeating. In addition, note the context of your own statements.


 * It is considered a different entity by the game itself in addition to the name change. Direct replacements such as Power Star to Grand Star can be covered in the original article. Moves used by different characters count.


 * There is no name being changed - just the addition of a second Final Smash copied from a pre-existing one.


 * If there are design differences in addition to the above, such as with Daisy Blossom and Goombo.
 * If the same name is shared, but there are significant differences to the point where a seperate article is needed to cover them all. Examples like Mario and Sonic games from Wii to DS count.


 * Goombas and Goombos were established as different species when they were mentioned in Nintendo Power; if this had been untrue, a correction would have been made. Again, I point to the Beanbean Kingdom from Mario and Luigi: Superstar Saga for an established case of regional variants, particularly the Beanerang Bro - who, prior to the game's remake, was covered in a separate article from the Boomerang Bro for a significant amount of time, despite sharing its name and many aspects of its design.


 * You've also backpedaled to the "Daisy Blossom isn't being split because of bias!!!" argument, when not only have you failed to prove the existence of said bias's influence in any decisions related to the move's coverage, this entire proposal and the Talk Page discussion that spawned it clearly display a lack of forethought and basic research on your part in trying to push through a change you see as desirable, despite it being rightfully contested even before the proposal was made not less than 48 hours later - in other words, trying to enact your own bias via policy change while using the correction of a supposed pre-existing bias as plausible deniability, as was pointed out and made apparent earlier. The evidence of your bias is easily visible in your actions, priorities and responses, while the evidence that the bias you keep citing had any significant influence on the coverage of Daisy Blossom (or indeed, any influence at all) is visibly lacking.


 * As a point of order, there is far a more relevant precedent to this case - Doctor Finale vs. Mario Finale. While based off the latter like Daisy Blossom is to Peach Blossom, there are actual functional differences beyond the appearance, particularly with regards to knockback and damage. Daisy Blossom and Peach Blossom do not have even those differences, and so it is determined there is no need to split them. Final Smashes and Mario Kart tires are also very much "apples and oranges", and as is indicated in the many and varied rebuttals, trying to paint things of this nature with the same brush does infinitely more harm than good, especially when they are already handled on a case-by-case basis. And this is a case where a changed appearance and references to aspects of character design alone do not sufficient cause for a split make.


 * Your repeated attempts to conflate the standard established for the Mario Kart tires with the standard for Final Smashes is indicative of a "broad strokes" approach based on a generalization fallacy that further weakens your argument in light of all the other holes in your proposal. And in claiming that "arguing against it is essentially identical to arguing against WaluigiTime's point of keeping the wheels seperate", you acknowledge one of my previously made points while somehow simultaneously ignoring it: though not all of the tires affect kart stats, enough of them do so that it makes no sense to merge them solely based on stats anyway. It's also more than a bit disingenuous to lean on the notion of "if you're arguing against X you're also arguing against Y": If I was somehow arguing against keeping the wheels separate, what would it matter? I would cross that bridge when I come to it later. And considering I'm in agreement with him on that, this smacks of a manufactured dilemma (though I'm unsure if if would be a textbook "false dilemma", but I digress).


 * In addition to the note of the Doctor Finale above, the nature of Echo Fighters provides an official basis of sorts for this: while they are indeed regarded as different moves by the game, there is not enough of a difference between the Final Smashes to justify a separate article. This is far from suggesting they are literally the same thing, but while they are not, such is beside the point - different types of subjects receive different coverage, and the standard of coverage for the Smash Bros. moves we do cover suggest there is a lack of grounds for a split.


 * And with sufficient evidence of such grounds still yet to be provided, and readily available evidence of an ulterior motive that undermines the legitimacy of the proposal being overwhelming - along with many an established basis for both the current nature of the coverage and the reason that such changes would run counter to current policy and efficient coverage overall - there is no reason at all that this proposal should pass. There is certainly no reason that things should have been "escalated" to this point, either: a Talk Page proposal should have been the course of action taken, and yet said discussion was shoehorned into a suggested policy amendment seemingly before the former option was even considered. That - on top of everything else about the proposed change - indicates that the result of the TPP will likely be the same. -- 14:00, October 20, 2019 (EDT)

As for Star Thwomp and Super Thwomp, it is literally the same entity, but Prima gave it a different name. Peach's moves and Daisy's moves exist together as different entities with OBVIOUS VISUAL DIFFERENCES but function the same. 2 out of 3. That should be enough. -- memoryman3 17:12, October 20, 2019 (EDT)
 * It's not. Moves aren't entities, unlike with Star Thwomps. Both moves are the same. So really there is only still one argument for their split, which isn't enough. 17:15, October 20, 2019 (EDT)
 * So if Bowser and Donkey Kong got super moves which involved Bowser's fire breath and DK's barrel, but they had the exact same gameplay effect, would they be merged? --MK8DX_Daisy_Icon.png memoryman3 19:12, October 20, 2019 (EDT)
 * Actually, yes. 19:14, October 20, 2019 (EDT)
 * Fair point. However, there is no bias towards any variant on that page. Dry Bowser's Blazing Barrage is not merged with Bowser's Fire Breath in the table, despite being almost the same in every way. In the merged Peach/Daisy Blossom pages, there is a huge bias towards Peach's variant to the point where Daisy's is drowned out and can't be easily accessed outside the wiki, especially if the user is looking for assets. If we give equal spaces to them, it will look messy. It's a lose-lose situation. --MK8DX_Daisy_Icon.png memoryman3 19:20, October 20, 2019 (EDT)
 * "However, there is no bias towards any variant on that page" because all of them are variants of the same Powershot move in one game, which originated in that game, and have all their visual and animation differences noted. With Peach and Daisy Blossom, there's only two variants to compare: one of them has existed for several games, and the other is a variant of the first one based directly and heavily on its latest appearance. And they also only have visuals and animations to differentiate them - that's not bias, there's just legitimately not much else to cover, and certainly not enough to split. -- 19:25, October 20, 2019 (EDT)

YOU think that's not enough to warrant a split. What about if there are several roller wheels and they each got their own pages. despite having as you put it, only minor differences in the textures. The fact that Peach Blossom and Daisy Blossom only are two moves means that a split wouldn't look messy and unwarranted, because then the seperate content can be covered without making the page look cluttered. That is the point I want to get across, and seeing as how many other extremely similar cases are handled, I think there is a strong, strong personal bias. -- memoryman3 06:01, October 21, 2019 (EDT)
 * I keep telling you there is no friggin' personal bias, stop going in circles groundlessly claiming that there is, it's immeasurably aggravating. Also "vehicle parts" are not the same type of entity to shared moves. This isn't apples and oranges, this is celery stalks and durians. Doc von Schmeltwick (talk) 06:14, October 21, 2019 (EDT)
 * Yes, I think that's not enough to warrant a split - that's how opinions work. And I've backed up my opinion with actual relevant examples of naming and splitting policies being applied to such cases, as have several other people in their own dissenting opinions. This is including your constant circular argument of "but da wheels!!1!" and the repeated contesting that those scenario are exactly the same - despite the fact that I and others have repeatedly addressed them and explained how different types of subjects are and have been consistently handled with different types of coverage by the wiki (again, with actual citations of those examples). Your refusal to acknowledge that or other "inconvenient" facts are in no way evidence of any personal bias on our part, and to accuse others of bad faith at this point is both transparently sanctimonious and inflammatory. -- 06:27, October 21, 2019 (EDT)
 * Also, Doc, I understand this is aggravating, and a bit late in the process to give this kind of advice, but try not to get too heated. -- 06:37, October 21, 2019 (EDT)

Miscellaneous
None at the moment.