Talk:Prohibited Command: Difference between revisions
m (→Official name) |
(→This article is too broad: new section) |
||
Line 7: | Line 7: | ||
The ''M&LSS+BM'' electronic instructional manual calls this status effect '''Prohibited Command''' (“Prohibited Command: The character is unable to choose a certain Command Block for a certain period of time.”) Should this page be moved now that it has an official name? {{User:Scrooge200/sig}} 20:59, August 22, 2019 (EDT) | The ''M&LSS+BM'' electronic instructional manual calls this status effect '''Prohibited Command''' (“Prohibited Command: The character is unable to choose a certain Command Block for a certain period of time.”) Should this page be moved now that it has an official name? {{User:Scrooge200/sig}} 20:59, August 22, 2019 (EDT) | ||
:It should, though "No Skills" should be kept as a redirect because it has quite a history of being used. Also, be sure to talk to Porplemontage about doing a text replacement to change every instance of a link to "No Skills" to point to "Prohibited Command" instead. {{User:Toadette the Achiever/sig}} 21:08, August 22, 2019 (EDT) | :It should, though "No Skills" should be kept as a redirect because it has quite a history of being used. Also, be sure to talk to Porplemontage about doing a text replacement to change every instance of a link to "No Skills" to point to "Prohibited Command" instead. {{User:Toadette the Achiever/sig}} 21:08, August 22, 2019 (EDT) | ||
== This article is too broad == | |||
I think this article's scope is too large. This specifically involves the concept of Prohibited Command being a "status ailment", as per the intro, even though [[Thunder Sass]] is on this page. It's not that Mario is being prevented from using Command Blocks while fighting Thunder Sass by any kind of effect. They aren't being stolen or magically sealed, nor did Mario drop his Command Blocks. It's that Mario agreed that he can't use attacks in that fight, and this is reflected mechanically by not having Command Blocks appear. | |||
I think the quick and easy fix is moving Thunder Sass to a separate paragraph and noting how it's odd compared to every other example on this page. [[User:Salmancer|Salmancer]] ([[User talk:Salmancer|talk]]) 00:39, August 6, 2024 (EDT) |
Latest revision as of 23:39, August 5, 2024
Is the name of this official? Also I see it's too minor despite its lengthy information, because it's not actually an status ailment or something relevant that happens very often in the gameplay, actually are special moves that very few enemies can perform - and apparently they're never mentioned in any way. ¢oincoll€ctor
It is named in Super Paper Mario (you can see it after touching a Tech Cursya), and this is relevant because it's a status ailment in multiple games. There should be information about this. Technickal 09:42, 20 November 2011 (EST)
Official name[edit]
The M&LSS+BM electronic instructional manual calls this status effect Prohibited Command (“Prohibited Command: The character is unable to choose a certain Command Block for a certain period of time.”) Should this page be moved now that it has an official name? Scrooge200 (talk) 20:59, August 22, 2019 (EDT)
- It should, though "No Skills" should be kept as a redirect because it has quite a history of being used. Also, be sure to talk to Porplemontage about doing a text replacement to change every instance of a link to "No Skills" to point to "Prohibited Command" instead. (T|C) 21:08, August 22, 2019 (EDT)
This article is too broad[edit]
I think this article's scope is too large. This specifically involves the concept of Prohibited Command being a "status ailment", as per the intro, even though Thunder Sass is on this page. It's not that Mario is being prevented from using Command Blocks while fighting Thunder Sass by any kind of effect. They aren't being stolen or magically sealed, nor did Mario drop his Command Blocks. It's that Mario agreed that he can't use attacks in that fight, and this is reflected mechanically by not having Command Blocks appear.
I think the quick and easy fix is moving Thunder Sass to a separate paragraph and noting how it's odd compared to every other example on this page. Salmancer (talk) 00:39, August 6, 2024 (EDT)