MarioWiki:Proposals: Difference between revisions
From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
Mukumukuluma (talk | contribs) |
(→Changes: Archive proposal "Decide how to handle the "latest portrayal" section in infoboxes") |
||
| Line 1: | Line 1: | ||
{{/Header}} | |||
{ | |||
This | ==Writing guidelines== | ||
===Change how "infinitely respawning" enemies are counted in level enemy tables=== | |||
Currently, the wiki lists enemy counts for each level in tables located in that level's article. This is all well and good, but the problem arises when infinitely respawning ones (like piped ones) are included. As seen [[World 6-B (New Super Mario Bros.)|here]], this is awkwardly written as | |||
*"[number] (not including the infinite [enemy] spawning from [number] [method])," | |||
and why shouldn't it include them? That method of writing is ungainly, misleading, and bloats the table's width unnecessarily. Therefore, I propose the alternate writing of | |||
*"[number] + (∞ x [number])," | |||
with the "x [number]" and parentheses being removed if there is only one case. So in the linked example, it would be "6 + ∞," which says the same thing without contradicting itself with a lengthy diatribe. | |||
<br>(Also I had to restrain myself from using * rather than x because that's how I'm used to writing multiplication in equations. Thanks, higher-level math classes defaulting to "X" as a variable! But the asterisk could be used too, anyway.) | |||
'''Proposer''': {{User|Doc von Schmeltwick}}<br> | |||
'''Deadline''': September 30, 2024, 23:59 GMT | |||
====Support==== | |||
#{{User|Doc von Schmeltwick}} - Per | |||
#{{User|Altendo}} - This doesn't sound like a bad idea, although I do think there should be an asterisk like "*" instead which leads to a note saying "not including the infinite [enemy] spawning from [number] [method]", as enemies can spawn in different ways, and showing how they spawn could still be useful. If we just show "∞ x [number]", it wouldn't show how Goombas are spawned in (the linked page doesn't specify how they are spawned in otherwise). But I do like the idea of shortening the "count" section of tables. | |||
<s>#{{User|ThePowerPlayer}} Per Altendo. This formatting is much better, but I also think some note of where the infinite enemy spawner(s) originate from should be preserved.</s><br> | |||
<s>#{{User|Super Mario RPG}} Per all.</s> | |||
====Oppose==== | |||
#{{User|Hewer}} I don't see the benefit of changing this. The current wording is straightforward and succinct, I'd expect the reader to understand "6 (not including the infinite Goombas spawning from one Warp Pipe)" easily. Changing it to "6 + ∞" just makes it less clear for no reason, I'd definitely be confused if I saw that and didn't know this specific context. The fact that the other support votes have also brought up how doing this risks losing the specific information completely (and suggested a more long-winded solution that seems to contradict the proposal) compels me to oppose this more. | |||
#{{User|Waluigi Time}} Per Hewer. | |||
#{{User|FanOfYoshi}} Per all. | |||
#{{User|Axii}} Per Hewer | |||
#{{User|SolemnStormcloud}} Per all. | |||
#{{User|EvieMaybe}} we don't need to throw a mathematical equation at people | |||
#{{User|Sparks}} Per all. | |||
#{{User|ThePowerPlayer}} I realized that this only makes sense if you have it explained to you like in the proposal description, which defeats the purpose. | |||
#{{User|Arend}} I feel that "[number] (+ [number] infinite spawn points)" would be less awkward to write than what we currently do ''and'' more understandable fir most people than what is proposed here | |||
#{{User| | |||
#{{User| | |||
#{{User| | |||
#{{User| | |||
#{{User| | |||
#{{User| | |||
#{{User| | |||
#{{User| | |||
====Comments==== | ====Comments==== | ||
I | {{@|Hewer}} - "succinct" would generally imply "short, sweet, and to-the-point," of which the current method is the exact opposite. I'm fine with including an asterisk-note next to the infinity, but the current one is much too bloated, outright admits to stating false information, and since the tables are center-aligned with that horizontal-bloat, it makes it look incredibly awkward. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 12:41, September 17, 2024 (EDT) | ||
: | :I guess we just have totally opposing opinions on this one, because I don't personally find ten words of explanation to be "much too bloated", would rather "state false information" (not really what's happening because it's immediately clarified and the only way not to state any "false" info would be to just put "∞" which helps no one) than obscure the meaning of what we're trying to say, and I don't at all think the somewhat wider tables look "incredibly awkward". This is a case where I feel giving more explanation than "6 + ∞" is necessary for the sake of conveying clear information, so I'd rather prioritise that over having a thin table (which I still don't really see why that's so desirable). {{User:Hewer/sig}} 03:19, September 18, 2024 (EDT) | ||
I | |||
If this proposal passes, I think that a dedicated template should be made; something like <code><nowiki>{{infinite respawn|5|3}}</nowiki></code> that would produce "{{hover|5 + (∞ × 3)|5 (not including the 3 infinite spawning points)}}". Or at the very least, use an actual "×" symbol rather than "x". {{User:Jdtendo/sig}} 12:08, September 19, 2024 (EDT) | |||
:I dislike the idea of hiding details in easily missable hover text and don't really see the benefit of using it. It just makes it more convoluted. {{User:Hewer/sig}} 11:12, September 20, 2024 (EDT) | |||
I'll refrain from voting because I have a visceral reaction to anything that resembles a math formula, and I want as little as possible for personal preference to seep into my vote. That's not to say I don't understand what's being proposed, in fact it makes perfect sense if you're aiming strictly for concision, but you'd need to take into account how accessibly that information is communicated--you'd need to establish that "infinity symbol" stands for infinite enemy spawning point, which is not immediately clear. At that point, you'd go for a relatively lengthy explanation nonetheless. Though, I agree that the phrasing in that page you linked doesn't sound inclusive. I think something like "5 individual, 3 infinite spawning points" works better if we're going down this path.<br>If the proposal passes, I'd like to see it implemented in the manner Jdtendo suggests above.<br>EDIT: I'm aware there's [[Mario Kart Tour race points system#Bonus-points boost|already plenty of math on this wiki that has potential to confound people]], but in that case, not only is its succinctness a better way to explain how the game's scoring system works (as opposed to paragraphs-long descriptions), but it's taken straight out of the game as well. I'd say, use math formulas only when you're sure prose would be of less service to its intended audience: people looking up how many enemies are in a level aren't necessarily interested in complex gameplay dynamics. {{User:Koopa con Carne/Sig}} 13:12, September 19, 2024 (EDT), edited 14:55, September 19, 2024 (EDT) | |||
' | I'd personally prefer if this was notated with ω instead of ∞, something like "{{hover|3ω+5|3 infinite spawn points and 5 others}}", but that would probably be too confusing to anyone not already familiar with transfinite ordinal notation. {{User:JanMisali/sig}} 10:01, September 21, 2024 (EDT) | ||
:This should be written "ω⋅3+5" because 3⋅ω = ω; {{wp|Ordinal arithmetic#Multiplication|multiplication on transfinite ordinal numbers}} is not commutative. {{User:Jdtendo/sig}} 12:40, September 21, 2024 (EDT) | |||
Maybe just have a table for finite enemies and a table for infinite enemies? There's horizontal space for both. [[User:Salmancer|Salmancer]] ([[User talk:Salmancer|talk]]) 11:33, September 21, 2024 (EDT) | |||
:That just needlessly splits information, which I again don't see the benefit of (and I still don't really see how there's a problem here that needs fixing anyway). {{User:Hewer/sig}} 21:26, September 21, 2024 (EDT) | |||
== | ==New features== | ||
''None at the moment.'' | |||
==Removals== | ==Removals== | ||
| Line 159: | Line 55: | ||
==Miscellaneous== | ==Miscellaneous== | ||
''None at the moment.'' | |||
Latest revision as of 11:47, September 22, 2024
|
|
Sunday, September 22nd, 18:06 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
Rules
- If users have an idea about improving the wiki or managing its community, but feel that they need community approval before acting upon that idea, they may make a proposal about it. They must have a strong argument supporting their idea and be willing to discuss it in detail with the other users, who will then vote about whether or not they think the idea should be used. Proposals should include links to all relevant pages and writing guidelines. Proposals must include a link to the draft page. Any pages that would be largely affected by the proposal should be marked with {{proposal notice}}.
- Only registered, autoconfirmed users can create, comment in, or vote on proposals and talk page proposals. Users may vote for more than one option, but they may not vote for every option available.
- Proposals end at the end of the day (23:59) one week after voting starts, except for writing guidelines and talk page proposals, which run for two weeks (all times GMT).
- For example, if a proposal is added at any time on Monday, August 1, 2011, the voting starts immediately and the deadline is one week later on Monday, August 8, at 23:59 GMT.
- 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 administrators.
- Users can also use the comments section to bring up any concerns or mistakes in regards to the proposal itself. In such cases, it's important the proposer addresses any concerns raised as soon as possible. Even if the supporting side might be winning by a wide margin, that should be no reason for such questions to be left unanswered. They may point out any missing details that might have been overlooked by the proposer, so it's a good idea as the proposer to check them frequently to achieve the most accurate outcome possible.
- If a user makes a vote and is subsequently blocked for any amount of time, their vote is removed. However, if the block ends before the proposal ends, then the user in question holds the right to re-cast their vote. If a proposer is blocked, their vote is removed and "(banned)" is added next to their name in the "Proposer:" line of the proposal, which runs until its deadline as normal. If the proposal passes, it falls to the supporters of the idea to enact any changes in a timely manner.
- No proposal can overturn the decision of a previous proposal that is less than 4 weeks (28 days) old.
- 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% support to win. If the margin is only one or two votes, then the first place option must have at least 60% support to win. If the required support threshold is not met, then the proposal is extended for another week.
- Use the {{proposal check}} tool to automate this calculation; see the template page for usage instructions and examples.
- Proposals can only be extended up to three times. If a consensus has not been reached by the fourth deadline, then the proposal fails and can only be re-proposed after four weeks (at the earliest).
- 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.
- If the administrators deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to remove it at any time.
- Proposals can only be rewritten or canceled by their proposer within the first three days of their creation (six days for writing guidelines and talk page proposals). However, proposers can request that their proposal be canceled by an administrator 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. Users can only be promoted and demoted by the will of the administration.
- 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, 7 days after the proposal was created (14 for writing guidelines and talk page proposals), at 23:59 GMT, in the format: "September 22, 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. Proposals dealing with a large amount of splits, merges, or deletions across the wiki should still be held on this page.
- For a list of all settled talk page proposals, see MarioWiki:Proposals/TPP archive and Category:Settled talk page proposals.
Rules
- All active talk page proposals must be listed below in chronological order (new proposals go at the bottom) using {{TPP discuss}}. Include a brief description of the proposal while also mentioning any pages affected by it, a link to the talk page housing the discussion, and the deadline. If the proposal involves a page that is not yet made, use {{fake link}} to communicate its title in the description. Linking to pages not directly involved in the talk page proposal is not recommended, as it clutters the list with unnecessary links. Place {{TPP}} under the section's header, and once the proposal is over, replace the template with {{settled TPP}}.
- All rules for talk page proposals are the same as mainspace proposals (see the "How to" section above), with the exceptions made by Rules 3 and 4 as follows:
- Voting in talk page proposals will be open for two weeks, not one (all times GMT).
- For example, if a proposal is added at any time on Monday, August 1, 2011, it ends two weeks later on Monday, August 15, 2011, at 23:59 GMT.
- The talk page proposal must pertain to the subject page of the talk page it is posted on.
- When a talk page proposal passes, it should be removed from this list and included in the list under the "Unimplemented proposals" section until the proposed changes have been enacted.
List of ongoing talk page proposals
- Consider the "Blurp" and "Deep Cheep" in the Super Mario Maker games an alternate design of Cheep Cheep with the former twos' designs as a cameo rather than a full appearance of the former two, in line with the game's own classification (discuss) Deadline: September 25, 2024, 23:59 GMT
- Add English to {{foreign names}} and retitle to {{international names}} (discuss) Deadline: September 26, 2024, 23:59 GMT
- Allow usage of {{Release}} as a generic "flag list" template (discuss) Deadline: September 27, 2024, 23:59 GMT
- Prune "sports" games from Black Shy Guy in line with White Shy Guy and Red Boo (discuss) Deadline: September 28, 2024, 23:59 GMT
- Merge Preying Mantas with Jellyfish (discuss) Deadline: September 28, 2024, 23:59 GMT
- Create article(s) for the SM64DS character rooms (discuss) Deadline: September 30, 2024, 23:59 GMT
- Create an article for the Peach doll from Super Mario RPG: Legend of the Seven Stars (discuss) Deadline: September 30, 2024, 23:59 GMT
- Remove the remaining non-Super Mario "stage gimmicks and hazards" from Super Smash Bros. (discuss) Deadline: October 1, 2024, 23:59 GMT
- Remove non-Super Mario "stage cameos" from Super Smash Bros. (discuss) Deadline: October 1, 2024, 23:59 GMT
- Rename {{Manga infobox}} to {{Publication infobox}} (discuss) Deadline: October 4, 2024, 23:59 GMT
- Merge Play Nintendo secret message puzzles (discuss) Deadline: October 4, 2024, 23:59 GMT
- Merge categories for Donkey Kong Country remakes with their base game's categories (discuss) Deadline: October 5, 2024, 23:59 GMT
Unimplemented proposals
Proposals
| Establish a standard for long course listings in articles for characters/enemies/items/etc., Koopa con Carne (ended June 8, 2023) |
| 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 New Super Mario Bros. games, the Super Mario Maker games, Super Mario Run, or Super Mario Bros. Wonder
| Expand use of "rawsize" gallery class, Doc von Schmeltwick (ended July 19, 2024) |
| Do not use t-posing models as infobox images, Nightwicked Bowser (ended September 1, 2024) |
| 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) |
| Tag sections regarding the unofficially named planets/area in Super Mario Galaxy games with "Conjecture" and "Dev data" templates, GuntherBayBeee (ended September 10, 2024) |
| Rename the remaining baseball teams to their current titles, GuntherBayBeee (ended September 19, 2024) |
| Add WikiLove extension, Super Mario RPG (ended September 20, 2024) |
| Only add in the current voice actor in the "latest portrayal" section in infoboxes, Altendo (ended September 21, 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 Bowser's Flame from Fire Breath, Doc von Schmeltwick (ended September 18, 2024) |
| Split Banana Peel from Banana, Doc von Schmeltwick (ended September 18, 2024) |
| Split truck article into cargo truck and pickup truck articles, Doc von Schmeltwick (ended September 21, 2024) |
| Split Donkey Kong template into separate arcade and Game Boy templates, Doc von Schmeltwick (ended September 21, 2024) |
| Merge Crocodile Isle (Donkey Kong 64) with Crocodile Isle, Doc von Schmeltwick (ended September 21, 2024) |
Writing guidelines
Change how "infinitely respawning" enemies are counted in level enemy tables
Currently, the wiki lists enemy counts for each level in tables located in that level's article. This is all well and good, but the problem arises when infinitely respawning ones (like piped ones) are included. As seen here, this is awkwardly written as
- "[number] (not including the infinite [enemy] spawning from [number] [method]),"
and why shouldn't it include them? That method of writing is ungainly, misleading, and bloats the table's width unnecessarily. Therefore, I propose the alternate writing of
- "[number] + (∞ x [number]),"
with the "x [number]" and parentheses being removed if there is only one case. So in the linked example, it would be "6 + ∞," which says the same thing without contradicting itself with a lengthy diatribe.
(Also I had to restrain myself from using * rather than x because that's how I'm used to writing multiplication in equations. Thanks, higher-level math classes defaulting to "X" as a variable! But the asterisk could be used too, anyway.)
Proposer: Doc von Schmeltwick (talk)
Deadline: September 30, 2024, 23:59 GMT
Support
- Doc von Schmeltwick (talk) - Per
- Altendo (talk) - This doesn't sound like a bad idea, although I do think there should be an asterisk like "*" instead which leads to a note saying "not including the infinite [enemy] spawning from [number] [method]", as enemies can spawn in different ways, and showing how they spawn could still be useful. If we just show "∞ x [number]", it wouldn't show how Goombas are spawned in (the linked page doesn't specify how they are spawned in otherwise). But I do like the idea of shortening the "count" section of tables.
#ThePowerPlayer (talk) Per Altendo. This formatting is much better, but I also think some note of where the infinite enemy spawner(s) originate from should be preserved.
#Super Mario RPG (talk) Per all.
Oppose
- Hewer (talk) I don't see the benefit of changing this. The current wording is straightforward and succinct, I'd expect the reader to understand "6 (not including the infinite Goombas spawning from one Warp Pipe)" easily. Changing it to "6 + ∞" just makes it less clear for no reason, I'd definitely be confused if I saw that and didn't know this specific context. The fact that the other support votes have also brought up how doing this risks losing the specific information completely (and suggested a more long-winded solution that seems to contradict the proposal) compels me to oppose this more.
- Waluigi Time (talk) Per Hewer.
- FanOfYoshi (talk) Per all.
- Axii (talk) Per Hewer
- SolemnStormcloud (talk) Per all.
- EvieMaybe (talk) we don't need to throw a mathematical equation at people
- Sparks (talk) Per all.
- ThePowerPlayer (talk) I realized that this only makes sense if you have it explained to you like in the proposal description, which defeats the purpose.
- Arend (talk) I feel that "[number] (+ [number] infinite spawn points)" would be less awkward to write than what we currently do and more understandable fir most people than what is proposed here
Comments
@Hewer - "succinct" would generally imply "short, sweet, and to-the-point," of which the current method is the exact opposite. I'm fine with including an asterisk-note next to the infinity, but the current one is much too bloated, outright admits to stating false information, and since the tables are center-aligned with that horizontal-bloat, it makes it look incredibly awkward. Doc von Schmeltwick (talk) 12:41, September 17, 2024 (EDT)
- I guess we just have totally opposing opinions on this one, because I don't personally find ten words of explanation to be "much too bloated", would rather "state false information" (not really what's happening because it's immediately clarified and the only way not to state any "false" info would be to just put "∞" which helps no one) than obscure the meaning of what we're trying to say, and I don't at all think the somewhat wider tables look "incredibly awkward". This is a case where I feel giving more explanation than "6 + ∞" is necessary for the sake of conveying clear information, so I'd rather prioritise that over having a thin table (which I still don't really see why that's so desirable). Hewer (talk · contributions · edit count) 03:19, September 18, 2024 (EDT)
If this proposal passes, I think that a dedicated template should be made; something like {{infinite respawn|5|3}} that would produce "5 + (∞ × 3)". Or at the very least, use an actual "×" symbol rather than "x". Jdtendo(T|C) 12:08, September 19, 2024 (EDT)
- I dislike the idea of hiding details in easily missable hover text and don't really see the benefit of using it. It just makes it more convoluted. Hewer (talk · contributions · edit count) 11:12, September 20, 2024 (EDT)
I'll refrain from voting because I have a visceral reaction to anything that resembles a math formula, and I want as little as possible for personal preference to seep into my vote. That's not to say I don't understand what's being proposed, in fact it makes perfect sense if you're aiming strictly for concision, but you'd need to take into account how accessibly that information is communicated--you'd need to establish that "infinity symbol" stands for infinite enemy spawning point, which is not immediately clear. At that point, you'd go for a relatively lengthy explanation nonetheless. Though, I agree that the phrasing in that page you linked doesn't sound inclusive. I think something like "5 individual, 3 infinite spawning points" works better if we're going down this path.
If the proposal passes, I'd like to see it implemented in the manner Jdtendo suggests above.
EDIT: I'm aware there's already plenty of math on this wiki that has potential to confound people, but in that case, not only is its succinctness a better way to explain how the game's scoring system works (as opposed to paragraphs-long descriptions), but it's taken straight out of the game as well. I'd say, use math formulas only when you're sure prose would be of less service to its intended audience: people looking up how many enemies are in a level aren't necessarily interested in complex gameplay dynamics. -- KOOPA CON CARNE 13:12, September 19, 2024 (EDT), edited 14:55, September 19, 2024 (EDT)
I'd personally prefer if this was notated with ω instead of ∞, something like "3ω+5", but that would probably be too confusing to anyone not already familiar with transfinite ordinal notation. jan Misali (talk · contributions) 10:01, September 21, 2024 (EDT)
- This should be written "ω⋅3+5" because 3⋅ω = ω; multiplication on transfinite ordinal numbers is not commutative. Jdtendo(T|C) 12:40, September 21, 2024 (EDT)
Maybe just have a table for finite enemies and a table for infinite enemies? There's horizontal space for both. Salmancer (talk) 11:33, September 21, 2024 (EDT)
- That just needlessly splits information, which I again don't see the benefit of (and I still don't really see how there's a problem here that needs fixing anyway). Hewer (talk · contributions · edit count) 21:26, September 21, 2024 (EDT)
New features
None at the moment.
Removals
None at the moment.
Changes
None at the moment.
Miscellaneous
None at the moment.
