MarioWiki:Proposals

List of Talk Page Proposals

 * Merge Koopasta with Koopasta Dish. (Discuss) Deadline: September 21, 2015, 23:59 GMT
 * Resize the Costume Mario costumes. (Discuss) Deadline: September 30, 2015, 23:59 GMT
 * Revamp the images on the Trick page. (Discuss) Deadline: October 2, 2015, 23:59 GMT

Writing Guidelines
None at the moment.

New features
None at the moment.

Removals
None at the moment.

Add "bugs and" or "and bugs" to "List of glitches in"
First, my reasoning is bugs and glitches are not the same. A bug is a minor glitch (like a short-lived audio glitch, which would be considered a bug according to this proposal), whereas a full-blown glitch is something that is longterm, causes a game to freeze, and so on and so forth. For example: this is what would be considered a bug, but this would be a full-blown glitch.

Proposer: Deadline: September 20, 2015, 23:59 GMT

Change

 * 1) per my own proposal.

Leave as is

 * 1) - Seems too similar and minor to bother changing all these titles, and mouthful "_ and _" names are less than ideal in general. The only reason we're stuck with "pre-release and unused" is because there's no nice umbrella term, but I feel like the broad meaning of "glitch", like how we currently use it, is more widespread and accepted than "beta" was, with a lot of (if not most) folks using it and "bug" interchangeably.
 * 2) Per Walkazo. Better off staying how they are.
 * 3) Per Walkazo, as well as Baby Luigi in the comments.
 * 4) I think it's totally fine to create a page called Bug and redirect it to Glitch, but beyond that, I feel the definitions here are a smidge pedantic, unlike the far more confusing "subspecies" and "beta".
 * 5) Walky said it better, but I don't see the point. Bugs and glitches are already near synonyms and I doubt anyone's getting confused.

Comments
I'm on the edge with this, but your description is wrong. The term of a bug and glitches is not defined on how damaging of a scale they are (both can cause game-breaking things, it depends on what component of the game experiences that or that), but the processes that caused them. Glitches, I believe, are things that the game developers did not intend/over-looked that are performed by the player, while a bug is a problem in the coding of the software itself. But since we do use "pre-release and unused" for that, I don't see why we can't add "bugs" to the title description. However, most people say those two interchangeably, so I do think it's verging in pedantry. 16:52, 13 September 2015 (EDT)
 * I wasn't talking about the level of damage but the significance of a glitch. And while they are interchangeable, that is only in speaking. On the wiki, however, the two should have different meanings. RoyNSMBU.png Roy Koopa 16:57, 13 September 2015 (EDT)
 * It's still not dependent on the magnitude of the glitch. As I said, the term is defined more of processes that caused the error in the game rather than how significant they are, as both are fully capable of crashing the game or whatever, so it's really hard to define terms that way (like, a minor clip bug could cause the rest of the game to be unplayable, because you cannot advance due to it). And tell why they should? I have said why they should not; because it's for the convenience of searching for these articles and because it's used interchangeably in normal speak. Compared to beta elements, that is. I've also stated why we should, to be consistent with the pre-released and unused content article. 17:01, 13 September 2015 (EDT)
 * About the minor clip bug, that would call for a reset of the system/software. As for the convenience of searching bit, if someone doesn't know we only use the term "glitches" and looked up "List of bugs in," they would get nowhere. As you might be able to see, this proposal is more for the help of readers who have no intention of editing, anons who edit, and new users. RoyNSMBU.png Roy Koopa 17:12, 13 September 2015 (EDT)
 * Exactly, you've proved my point on why we don't define the terms solely because of how big and game-changing they are. There are far too many variables and parameters we have to define; saying the processes that caused this and this error is a better way to define "bug" and "glitch" rather than how significant it is, and "significant" is a pretty loose and relative term. Also, I think we need more redirects in general with the whole lists thing, like List of minigames articles needs more redirects. 17:16, 13 September 2015 (EDT)
 * What if I added an option to say "Redirect 'List of bugs in' to 'List of glitches in'"? RoyNSMBU.png Roy Koopa 17:20, 13 September 2015 (EDT)
 * Maybe? Maybe not. I don't know about this. 14:58, 14 September 2015 (EDT)
 * I don't think anyone would object if you created Bug as a redirect to Glitch although "bug" can mean other things. 15:08, 14 September 2015 (EDT)

I don't think there is a need to split the vote between "bugs and" and "and bugs". Just a simple support would suffice so determining outcomes would be simpler. 17:14, 13 September 2015 (EDT)
 * Do you mean have the voters post their opinion in the vote? RoyNSMBU.png Roy Koopa 17:15, 13 September 2015 (EDT)
 * I mean, you can merge your "bugs and" and "and bugs" choices into one support vote. They're pretty much the same thing, so there's no need to mull over the order of the elements. 17:23, 13 September 2015 (EDT)

@Walkazo Adding two syllables is not a mouthful imo. Six syllables (I counted) is though. Roy Koopa 17:28, 13 September 2015 (EDT)
 * You're not adding just syllables, but extra spaces and characters. It makes the title and links look more clunky. 18:11, 13 September 2015 (EDT)
 * ummmm...how does it make a link clunky? RoyNSMBU.png Roy Koopa 21:12, 13 September 2015 (EDT)
 * In the navigation templates mostly, so you mostly have to resort to piping there. And considering that it's not all that necessary, then I'm not sure if it's worth lengthening the name like that. 14:58, 14 September 2015 (EDT)

Miscellaneous
None at the moment.