MarioWiki:Proposals
|
|
Monday, December 2nd, 20:28 GMT |
|
|
Proposals can be new features, the removal of previously-added features that have tired out, or new policies that must be approved via consensus before any action is taken.
|
A proposal section works like a discussion page: comments are brought up and replied to using indents (colons, such as : or ::::) and all edits are signed using the code {{User|User name}}.
How to
If someone has an idea about improving the wiki or managing its community, but feel that they need community approval before acting upon that idea, they may make a proposal about it. They must have a strong argument supporting their idea and be willing to discuss it in detail with other users, who will then vote on whether or not they think the idea should be implemented. Proposals should include links to all relevant pages and writing guidelines. Proposals must include a link to the draft page. Any pages that would be largely affected by the proposal should be marked with {{proposal notice}}.
Rules
- Only autoconfirmed users may create or vote on proposals. Anyone is free to comment on proposals (provided that the page's protection level allows them to edit).
- Proposals conclude at the end of the day (23:59) two weeks after voting starts (all times GMT).
- For example, if a proposal is added at any time on Monday, August 1, 2011, the voting starts immediately and the deadline is two weeks later on Monday, August 15, at 23:59 GMT.
- Users may vote for more than one option, but they may not vote for every option available.
- Every vote should have a strong, sensible reason accompanying it. Agreeing with a previously mentioned reason given by another user is accepted (including "per" votes), but tangential comments, heavy sarcasm, and other misleading or irrelevant quips are just as invalid as providing no reason at all.
- Users who feel that certain votes were cast in bad faith or which truly have no merit can address the votes in the comments section. Users can ask a voter to clarify their position, point out mistakes or flaws in their arguments, or call for the outright removal of the vote if it lacks sufficient reasoning. Users may not remove or alter the content of anyone else's votes. Voters can remove or rewrite their own vote(s) at any time, but the final decision to remove another user's vote lies solely with the wiki staff.
- Users can also use the comments section to bring up any concerns or mistakes in regards to the proposal itself. In such cases, it's important the proposer addresses any concerns raised as soon as possible. Even if the supporting side might be winning by a wide margin, that should be no reason for such questions to be left unanswered. They may point out any missing details that might have been overlooked by the proposer, so it's a good idea as the proposer to check them frequently to achieve the most accurate outcome possible.
- If a user makes a vote and is subsequently blocked for any amount of time, their vote is removed. However, if the block ends before the proposal ends, then the user in question holds the right to re-cast their vote. If a proposer is blocked, their vote is removed and "(blocked)" is added next to their name in the "Proposer:" line of the proposal, which runs until its deadline as normal. If the proposal passes, it falls to the supporters of the idea to enact any changes in a timely manner.
- Proposals cannot contradict an already ongoing proposal or overturn the decision of a previous proposal that concluded less than four weeks (28 days) ago.
- If one week before a proposal's initial deadline, the first place option is ahead of the second place option by eight or more votes and the first place option has at least 80% approval, then the proposal concludes early. Wiki staff may tag a proposal with "Do not close early" at any time to prevent an early close, if needed.
- Tag the proposal with {{early notice}} if it is on track for an early close. Use {{proposal check|early=yes}} to perform the check.
- Any proposal where none of the options have at least four votes will be extended for another week. If after three extensions, no options have at least four votes, the proposal will be listed as "NO QUORUM." The original proposer then has the option to relist said proposal to generate more discussion.
- If a proposal reaches its deadline and there is a tie for first place, then the proposal is extended for another week.
- If a proposal reaches its deadline and the first place option is ahead of the second place option by three or more votes, then the first place option must have over 50% approval to win. If the margin is only one or two votes, then the first place option must have at least 60% approval to win. If the required approval threshold is not met, then the proposal is extended for another week.
- Use {{proposal check}} to automate this calculation; see the template page for usage instructions and examples.
- Proposals can be extended a maximum of three times. If a consensus has not been reached by the fourth deadline, then the proposal fails and cannot be re-proposed until at least four weeks after the last deadline.
- All proposals are archived. The original proposer must take action accordingly if the outcome of the proposal dictates it. If it requires the help of an administrator, the proposer can ask for that help.
- After a proposal passes, it is added to the appropriate list of "unimplemented proposals" below and is removed once it has been sufficiently implemented.
- If the wiki staff deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to cancel it at any time.
- Proposals can only be rewritten or canceled by their proposer within the first four days of their creation. However, proposers can request that their proposal be canceled by a staff member at any time, provided they have a valid reason for it. Please note that canceled proposals must also be archived.
- Unless there is major disagreement about whether certain content should be included, there should not be proposals about creating, expanding, rewriting, or otherwise fixing up pages. To organize efforts about improving articles on neglected or completely missing subjects, try setting up a collaboration thread on the forums.
- Proposals cannot be made about promotions and demotions. Staff changes are discussed internally and handled by the bureaucrats.
- No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
- Proposals must have a status quo option (e.g. Oppose, Do nothing) unless the status quo itself violates policy.
Basic proposal and support/oppose format
This is an example of what your proposal must look like, if you want it to be acknowledged. If you are inexperienced or unsure how to set up this format, simply copy the following and paste it into the fitting section. Then replace the [subject] - variables with information to customize your proposal, so it says what you wish. If you insert the information, be sure to replace the whole variable including the squared brackets, so "[insert info here]" becomes "This is the inserted information", not "[This is the inserted information]". Proposals presenting multiple alternative courses of action can have more than two voting options, but what each voting section is supporting must be clearly defined. Such options should also be kept to a minimum, and if something comes up in the comments, the proposal can be amended as necessary.
===[insert a title for your proposal here]===
[describe what issue this proposal is about and what changes you think should be made to improve how the wiki handles that issue]
'''Proposer''': {{User|[enter your username here]}}<br>
'''Deadline''': [insert a deadline here, 14 days after the proposal was created, at 23:59 GMT, in the format: "December 2, 2024, 23:59 GMT"]
====Support====
#{{User|[enter your username here]}} [make a statement indicating that you support your proposal]
====Oppose====
====Comments====
Users will now be able to vote on your proposal, until the set deadline is reached. Remember, you are a user as well, so you can vote on your own proposal just like the others.
To support, or oppose, just insert "#{{User|[add your username here]}}" at the bottom of the section of your choice. Just don't forget to add a valid reason for your vote behind that tag if you are voting on another user's proposal. If you are voting on your own proposal, you can just say "Per my proposal".
Talk page proposals
Proposals concerning a single page or a limited group of pages are held on the most relevant talk page regarding the matter. All of the above proposal rules also apply to talk page proposals. Place {{TPP}} under the section's header, and once the proposal is over, replace the template with {{settled TPP}}. Proposals dealing with a large amount of splits, merges, or deletions across the wiki should still be held on this page.
All active talk page proposals must be listed below in chronological order (new proposals go at the bottom) using {{TPP discuss}}. Include a brief description of the proposal while also mentioning any pages affected by it, a link to the talk page housing the discussion, and the deadline. If the proposal involves a page that is not yet made, use {{fake link}} to communicate its title in the description. Linking to pages not directly involved in the talk page proposal is not recommended, as it clutters the list with unnecessary links.
List of ongoing talk page proposals
- Merge False Character and the Fighting Polygon/Wireframe/Alloy/Mii Teams to List of Super Smash Bros. series bosses (discuss) Deadline: December 2, 2024, 23:59 GMT
- Move Kolorado's father to Richard (discuss) Deadline: December 11, 2024, 23:59 GMT
- Move Mysterious Cloud to either Hat cloud or Cap cloud (discuss) Deadline: December 14, 2024, 23:59 GMT
- Split and trim the Vine article (discuss) Deadline: December 14, 2024, 23:59 GMT
- Move Bomb (species) to Bomb (Final Fantasy) (discuss) Deadline: December 14, 2024, 23:59 GMT
- Split the Yoshi's Island teeter-totter from Seesaw (discuss) Deadline: December 16, 2024, 23:59 GMT
Unimplemented proposals
Proposals
| Break alphabetical order in enemy lists to list enemy variants below their base form, EvieMaybe (ended May 21, 2024) |
| Standardize sectioning for Super Mario series game articles, Nintendo101 (ended July 3, 2024) |
- ^ NOTE: Not yet integrated for the Super Mario Maker titles, Super Mario Run, and Super Mario Bros. Wonder.
| Create new sections for gallery pages to cover "unused/pre-release/prototype/etc." graphics separate from the ones that appear in the finalized games, Doc von Schmeltwick (ended September 2, 2024) |
| Add film and television ratings to Template:Ratings, TheUndescribableGhost (ended October 1, 2024) |
| Use the classic and classic-link templates when discussing classic courses in Mario Kart Tour, YoYo (ended October 2, 2024) |
| Split articles for the alternate-named reskins from All Night Nippon: Super Mario Bros., Doc von Schmeltwick (ended October 3, 2024) |
| Clarify coverage of the Super Smash Bros. series, Doc von Schmeltwick (ended October 17, 2024) |
| Remove all subpage and redirect links from all navigational templates, JanMisali (ended October 31, 2024) |
| Prioritize MESEN/NEStopia palette for NES sprites and screenshots, Doc von Schmeltwick (ended November 3, 2024) |
| Stop considering reused voice clips as references (usually), Waluigi Time (ended November 8, 2024) |
| Allow English names from closed captions, Koopa con Carne (ended November 12, 2024) |
- ^ NOTE: A number of names coming from closed captions are listed here.
| Split off the Mario Kart Tour template(s), MightyMario (ended November 24, 2024) |
Talk page proposals
| Split all the clothing, Doc von Schmeltwick (ended September 12, 2021) |
| Split machine parts, Robo-Rabbit, and flag from Super Duel Mode, Doc von Schmeltwick (ended September 30, 2022) |
| Make bestiary list pages for the Minion Quest and Bowser Jr.'s Journey modes, Doc von Schmeltwick (ended January 11, 2024) |
| Allow separate articles for Diddy Kong Pilot (2003)'s subjects, Doc von Schmeltwick (ended August 3, 2024) |
| Split Banana Peel from Banana, Doc von Schmeltwick (ended September 18, 2024) |
| Merge Spiked Thwomp with Thwomp, Blinker (ended November 2, 2024) |
| Create articles for specified special buildings in Super Mario Run, Salmancer (ended November 15, 2024) |
| Expand and rename List of characters by game to List of characters by first appearance, Hewer (ended November 20, 2024) |
| Create articles for "Ashita ni Nattara" and "Banana Tengoku" or list them in List of Donkey Kong Country (television series) songs, Starluxe (ended November 23, 2024) |
| Determine how to handle the Tattle Log images from Paper Mario: The Thousand-Year Door (Nintendo Switch), Technetium (ended November 30, 2024) |
Writing guidelines
None at the moment.
New features
None at the moment.
Removals
None at the moment.
Changes
Allow colorful tables again
Recently, there's been an update to follow Help:Table that standardizes all the colorful tables into boring, white-and-gray ones. I personally don't like this: not only is it removing a bit of charm from the site, the colored boxes are legitimately helpful at a glance and make it easier to distinguish individual sections in these large chunks of data.
Take Rock-Candy Mines, a world from New Super Mario Bros. U and New Super Luigi U. Here are two versions of the level lists:
| Level Number | Level Name | Description |
|---|---|---|
| Rock-Candy Mines-1 | Fuzzy Clifftop | This is a clifftop level that features Yoshi, Fruits and Fuzzies. |
| Rock-Candy Mines-2 | Porcupuffer Falls | Another cliff level over the water, where Porcupuffers attack. Many Urchins can be found, too. |
Rock-Candy Mines- Tower
|
Grinding-Stone Tower | The sixth and final tower where Boom Boom is the boss, the final instance he is fought. The main enemies in this tower are Grrrols. |
| Rock-Candy Mines-3 | Waddlewing's Nest | This level features Chain Chomps, Waddlewings and tilting stands. |
| Level Number | Level Name | Description |
|---|---|---|
| Rock-Candy Mines-1 | Mount Fuzzy | An overworld level with some Fuzzies. |
| Rock-Candy Mines-2 | Porcupuffer Cavern | An underground level with low water level and a Porcupuffer. |
| Rock-Candy Mines-Tower
|
Smashing-Stone Tower | A tower full of blocks destroyable only by Grrrols. |
| Rock-Candy Mines-3 | Spike's Seesaws | A level with tilting platforms attacked by Spikes. |
| Level number | Level name | Description |
|---|---|---|
| Rock-Candy Mines-1 | Fuzzy Clifftop | This is a clifftop level that features Yoshi, Fruits and Fuzzies. |
| Rock-Candy Mines-2 | Porcupuffer Falls | Another cliff level over the water, where Porcupuffers attack. Many Urchins can be found, too. |
| Rock-Candy Mines-Tower
|
Grinding-Stone Tower | The sixth and final tower where Boom Boom is the boss, the final instance he is fought. The main enemies in this tower are Grrrols. |
| Rock-Candy Mines-3 | Waddlewing's Nest | This level features Chain Chomps, Waddlewings and tilting stands. |
| Level Number | Level Name | Description |
|---|---|---|
| Rock-Candy Mines-1 | Mount Fuzzy | An overworld level with some Fuzzies. |
| Rock-Candy Mines-2 | Porcupuffer Cavern | An underground level with low water level and a Porcupuffer. |
| Rock-Candy Mines-Tower
|
Smashing-Stone Tower | A tower full of blocks destroyable only by Grrrols. |
| Rock-Candy Mines-3 | Spike's Seesaws | A level with tilting platforms attacked by Spikes. |
The only concern I can see is that black-on-blue text might be a bit hard to read, but we can change the text color to white, like some articles already do. It's a lot easier to tell with the colored header. If someone is just scrolling through the article to find the levels, the blue and green will catch their eye and they can easily know which game is which. The specific blue and green are distinctly featured on the games' logos and boxes:
The standardization of the templates also really harms articles like Super Mario World 2: Yoshi's Island: compare the colored navbox revision to the current, and it looks more inconsistent because the levels section is still using a unique format and color. Also compare Pi'illo, an item list: colored revision vs. standardized revision. I don't mind that the colors aren't official wiki standard because they're not arbitrary: they clearly correspond to the area, and lists for this game use the same colors for the same areas. Even so, it's still useful to have different colors because you can scroll through the article and easily know when one list ends and another begins.
Some lists are also heavily dependent on color to distinguish areas with colors specifically used in-game, such as List of ? Blocks in Paper Mario: The Origami King or List of ? Blocks in Paper Mario: Color Splash. Standardizing these would make them much less usable. I don't care if we need to make the colors specifically approved or consistent on a per-game basis, I just want them back. Scrooge200 (talk) 
20:51, July 1, 2024 (EDT)
Proposer: Scrooge200 (talk)
Deadline: July 9, 2024, 23:59 GMT
Support: Allow colors
- Scrooge200 (talk) Per proposal.
- DrBaskerville (talk) Per proposal. Not only is it more aesthetically pleasing, but it is also easier to read. I do, however, agree we should look into somehow standardizing colors, like what we do with MarioWiki:Proposals/Archive.
- Camwoodstock (talk) Per proposal. Just because they weren't standardized heavily isn't a very good reason to default to "plain ol' gray". In addition, while this is admittedly an "us" issue, we do find it annoying how similar the two grays actually are when we're scrolling quickly--the higher contrast provided by the colors helps to quell that issue.
- Pseudo (talk) Per proposal, and per all.
- Tails777 (talk) I am a very simple man; I enjoy colorful things. But in all seriousness, I feel it helps make sections stand out and could make them easier to identify when reading. Per proposal.
- Meester Tweester (talk) Per proposal.
- Nintendo101 (talk) Fun and look nice. It's also nice to give users some breathing room with what they want to try integrating into the articles they work on.
- Ahemtoday (talk) Per proposal.
- RetroNintendo2008 (talk) Per all.
- Arend (talk) TBH I always found it odd why only the Donkey Kong games get to have the colored tables... is it a remnant of the DK Wiki? In any case, it'd be nice to have some color (not sure if everything should have similar standardized colors or if it should be a case-by-case basis though)
- FanOfRosalina2007 (talk) Per all. This makes the tables easier to read, and it's also easier to find specific sections. I do think we should standardize the colors, though. Order above all.
- LadySophie17 (talk) Per all. I am not sure what caused this recent trend of table bleaching, but it drained all appeal from them. I don't think we need to standardize colors for specific purposes, either. Just give each game or topic a color that is fitting for that particular case. Not everything needs to be set to rigorous standards, live a little.
- Technetium (talk) Per all.
- Yook Bab-imba (talk) We should embrace colors in the Mario wiki. I think the DKC games are some of our best looking articles, the tables playing a huge part. I do think some consistency is needed, though (a light yellow row next to a dark purple row with white text for example is just garish).
Oppose: Prioritize gray
- Super Mario RPG (talk) Colors are based on arbitrary choice and not by official merit. I think there can be a system where there are exceptions to allow for certain colored tables on a case by case basis, but allowing it in absolutely every single case is overdoing it.
Comments
@Super Mario RPG: Chestnut Valley, List_of_hidden_Toads_in_Paper_Mario:_The_Origami_King#Blue_streamer, Not-Bottomless_Hole#Blue_Streamer, List_of_Collectible_Treasures_in_Paper_Mario:_The_Origami_King#Blue_streamer, List_of_?_Blocks_in_Paper_Mario:_The_Origami_King#Blue_streamer all use the exact same colors. And it's because this is a blue streamer area in game, so it makes logical sense; I will usually color pick directly from sprites to get the right color codes. I don't really see where the "arbitrary" part is coming from. Scrooge200 (talk) 21:14, July 1, 2024 (EDT)
To be fair, even the older revisions didn't acknowledge the color styling of the former table format, so that part wasn't erased to begin with. It's just the design, and colors work with the wikitable class as well (see here, for example). Super Mario RPG (talk) 21:50, July 1, 2024 (EDT)
I think I'd like a little standardization, just so we don't end up with complete chaos. Maybe standardize alternating-color cells of the same color as the header? And as for the colors themselves — outside of when they're used to separate levels, which is by necessity a case-by-case basis — maybe we could do something similar to or based on the standardized navbox color schemes?
The preceding unsigned comment was added by Ahemtoday (talk).
- @Ahemtoday Yeah, perhaps something like the navboxes could work. The problem with the proposal title is that it's misleading in a certain sense since there already has been one custom styling for the wikitables -- "dk" , which is for Donkey Kong content. I think what it's trying to get at is allowing more standardized wikitable options, and this way there would be less likelihood of conflict if, let's say, someone else were to overhaul an entire page and how it looks. I still think colors should be reserved in specialized circumstances. Super Mario RPG (talk) 16:34, July 2, 2024 (EDT)
Move Super Princess Peach enemies to their full names
Or, to be specific, move:
- G. R. P-Troopa to "Glad Red Paratroopa"
- G. Torpedo Ted to "Glad Torpedo Ted"
- Glad P. Plant to "Glad Piranha Plant"
- M. M-Spike Top to "Mad Mecha-Spike Top"
- M. Red P-Goomba to "Mad Red Paragoomba"
- Mad G. P-Troopa to "Mad Green Paratroopa"
- Sad N. Plant to "Sad Nipper Plant"
- C. A. F. H. Bro to "Calm Amazing Flyin' Hammer Brother"
- C. Chain Chomp to "Calm Chain Chomp"
- C. Fishing Boo to "Calm Fishing Boo"
- C. V. Plant to "Calm Volcano Plant"
- A. F. H. Bro to... nothing in particular, actually, they're already included on the same page as the SMW one. More on that later.
We have a few reasons for wanting this, and a few justifications, but for the sake of putting everything out on the table, I'll start with our immediate emotional feelings.
In Super Princess Peach, a lot of returning enemies with existing official names are given "emotional" variants. When English names are said in full, these are exclusively referred to as "Glad", "Mad", "Sad", or "Calm" versions of the original enemies. Additionally, to my understanding, the Japanese version of the game universally modifies names for emotional variants by appending 喜(Ki), 怒(Do), 哀(Ai), and 楽(Raku) respectively to preexisting official names for all enemies which have them. With this in mind, we feel it is, if nothing else, a bit silly to present these enemies as if we don't know what their names are supposed to be abbreviating.
That being said, of course, we're aware of the reasons why. Despite this feeling, we would have begrudgingly respected the former name of friend of the wiki Bombshell Bill Blaster had she not decided to change it, and we were certainly in support of keeping The O. P. L. W. T. E. E. W. R. F. A. K. E. B. I. Happens faithful to the source material. There are many cases like this, where something awkward needs to be the name of a page because, well, that's just what it's called.
But this bothers us anyway, and I think that hinges on the contention that these names are definitive official names for unique enemies.
Super Princess Peach presents these names in exactly one context, which is the in-game glossary section. In Japanese, none of the names are abbreviated, and all names of returning enemies are shared with previous official names for those enemies, with the variants having the relevant emotion appended. Meanwhile, in English, a number of emotional variant enemy names (and A. F. H. Bro, but we'll get to him later) are abbreviated when the addition of the extra words would make them excessively long. While the names are able to scroll to display more, the display column for their names in-game is quite small, and none of the abbreviated names are longer than 15 characters. This implies that, regardless of how the localizers may have wanted to change these names, they had a hard character limit.
The Naming policy actually has something that I think expresses our feelings here. It's for name changes, but given that these are all variants of preexisting enemies, I think it applies. Quote: "...the newer name will replace the older one with certain exceptions. Exceptions include naming errors, translation errors, and use of aliases/nicknames ... It is up to the users to find and determine what the naming errors, translation errors, and use of aliases/nicknames are. When mentioning subjects whose names have changed overtime, the newest name generally takes greater priority, except in the context of older media where they went by previous names, in which case those are used instead."
So, if we're in a situation where an enemy is agreed to be a variant of a preexisting enemy (the pages of these enemies will generally confidently state this, because it's obviously the case), and that enemy uses a variant of the same name as that preexisting enemy in Japanese, but then is shortened in English in a manner that would have been impossible to not do... Isn't that just a forced translation error? Or at the very least, some kind of alias? Can we really consider these to be official English names for these enemies if it was physically impossible to translate them in accordance with the Japanese naming scheme? And furthermore, when we can see that literally every name in the game that wouldn't have been over 15 characters was translated that way?
Personally, I think this is a pretty compelling explanation of why we feel this should be an exception to the usual rules, so I wanted to raise it. With all this in mind, it feels sort of disingenuously literal to take an alias that the localizers had no choice but to use and which doesn't reflect the Japanese name at all as more official than a name which actually describes all of the properties of the enemy as depicted in the game. But it's up to you guys.
Though, I will say, if we're going to take the stance that the literal in-game name is all that matters... Why are A. F. H. Bros still using their old name from 1991? Super Princess Peach was their last in-game appearance, and therefore has the most modern official English name.
Proposer: Exiled.Serenity (talk)
Deadline: July 10, 2024, 23:59 GMT
Support
- Exiled.Serenity (talk) Proposer.
- DrBaskerville (talk) Though Pseudo makes compelling points, I don't see how there could be anything else but the names the pages all already say are "presumably" their actual names. If necessary, we can add the conjuncture disclaimer at the top of the articles. The main reason I support this change is because the abbreviations do not make it immediately obvious to someone who is browsing all Paratroopa variants (something I was actually doing recently) what "G. R. P-Troopa" is. This is true for all of the enemies and their base species. Moving them to the full names makes it clear what they are without having to click on the page.
Oppose
- Pseudo (talk) These names are simply not these enemies' official names. We can certainly read between the lines regarding their names and come to reasonable conclusions about what they stand for and why their names are abbreviated, and this is currently done on all of these articles by mentioning what each title is presumably short for. Despite that, the unabbreviated names aren’t actually used in the game itself nor in any other extant official material, so I’m not comfortable moving these pages unless a source can be found explicitly backing up the enemies' full names (and, for the record, I am not staunchly opposed to moving Amazing Flyin' Hammer Brother to A. F. H. Bro despite its strangeness, since it's the more common name in recent sources, though I'm not really certain I'd support it, either, but it's a conversation for another day and another proposal anyway).
- FanOfYoshi (talk) Per Pseudo.
- Hewer (talk) I'd rather we didn't move official names to unofficial ones because we don't like the official names. There is plenty of precedent now for using shortened names if they're what official sources use, but in all of those cases, the long names were at least also official names - here, they're not.
- JanMisali (talk) Per all. Using the official in-game names takes priority over using "full names".
- Nintendo101 (talk) Those are their names.
- TheUndescribableGhost (talk) Per all, especially given ongoing Daisy proposal.
- YoYo (talk) per all.
Comments
To clarify the end of my vote regarding Amazing Flyin' Hammer Brother, it was brought up a while ago on Talk:Volcano Lotus that the English version of the Mario Portal’s Super Mario World page surprisingly refers to this enemy as an A. F. H. Bro despite the original game using the full name in the end credits. While there has been understandable concern about citogenesis on the Mario Portal, this still can be taken to suggest that A. F. H. Bro became the main official name starting with Super Princess Peach, especially since this enemy’s article wasn’t moved on this wiki at the time for the Mario Portal localizers to cross-reference. Pseudo (talk) (contributions) 
01:15, July 3, 2024 (EDT)
Abstaining for now, but the very reason why we haven't moved these Super Princess Peach enemies to the full name is also the exact same reason why hadn't moved B. Bill Blaster to Bombshell Bill Blaster for so long until the Nintendo Switch remake of TTYD. There simply hasn't been an official record of these enemies' full names. This is due to character limitations, of course, but it should be noted that the original GCN version of TTYD still never even referred to the B. Bill Blaster by its full name in the Tattle, which should be exempt from character limitations, as can be seen with H. S. Goomba; it was only until the Nintendo Switch remake when the full name of Bombshell Bill Blaster has finally been used, hence we finally moved that article then. But the full names for all these Super Princess Peach enemies have still never been in use before in an official sense (at least Amazing Flyin' Hammer Brother's full name had been implemented in its debut game's cast roll). 
rend (talk) (edits) 05:47, July 3, 2024 (EDT)
- Not just in TTYD, but also in the first Paper Mario they're also called B. Bill Blasters in the tattle.
Nightwicked Bowser 
06:27, July 3, 2024 (EDT) - The tattle log thing is the exact reason why I'm fine with B. Bill Blasters. They had ample opportunity to give a full name, and didn't. In TTYD, they even make something of a joke out of it. Plus, I think it isn't truly unbelievable that they could be, like, "Buff Bill Blasters" or whatever. Meanwhile, Super Princess Peach had nowhere to clarify this, and all of the abbreviated enemies save AFH Bro are variants of enemies that do have official names in the exact same menu. Therefore, I don't think it's reasonable to treat these aliases as official names in this one specific case. Exiled.Serenity (talk) 20:29, July 3, 2024 (EDT)
Wanted to add a couple comments since it's been a day:
- I think that DrBaskerville raised a significant point here that I overlooked. Insisting that these literal names are official is fine if you already know what they're supposed to be short for, as we all do, but if you're just a random person browsing variants of Goomba then "M. Red P-Goomba" tells you absolutely nothing. Frankly, it looks like it could just be some guy's real name.
- I think a lot of the opposition votes aren't contending with our central point here. To be clear: We don't think that the official names should be discounted. We simply think that these should not be considered official names, because they are obvious nicknames describing variants of enemies which themselves have official names in the exact same menu. I don't think there's any real reason to take these names as definitive or official, because they're mistranslations, aliases, and nicknames all at once and there's nothing in the game which goes against this.
Exiled.Serenity (talk) 20:59, July 3, 2024 (EDT)
- "We don't think that the official names should be discounted. We simply think that these should not be considered official names" ...What? That is discounting the official names. If no official sources back up a name, then it's simply not an official name, no matter how much you think it ought to be. And even if we did have a source for these full names, see the proposals I linked to in my vote - do you disagree with the recent Baby DK rename, for instance? If a shortened name is used significantly more often than a full name, the shortened one is what should take priority. In this case, we've got a usage of the shortened names vs. no usage of the longer names. Hewer (talk · contributions · edit count) 04:48, July 4, 2024 (EDT)
Miscellaneous
None at the moment.
