User talk:99.129.228.221: Difference between revisions
(Created page with "==Shortening enemy names== Hey there, regarding your recent edits on the boss articles, they're not bad, but I must warn you that it's not a very good idea to focus so much on...") |
(Forgot about the Scornet Maestro.) |
||
| Line 6: | Line 6: | ||
The best approach is to write the full name ''sometimes''. This not only keeps the vision of the documentation fresh, in that it should be objective documentation of the "Armored Mawdad" enemy, but it still keeps reading light and approachable by having all other instances just say "Mawdad". As a general rule, it's especially important to keep the full name in text that can be read in a vacuum. Like, if a reader shows up just to read some fighting strategy, they'll jump straight to the strategy section and start reading there. If they only read "Mawdad", that won't be very correct and will come off a bit casual and awkward, but if the section starts with "Armored Mawdad" and then shortens it from there on, everything becomes clear. | The best approach is to write the full name ''sometimes''. This not only keeps the vision of the documentation fresh, in that it should be objective documentation of the "Armored Mawdad" enemy, but it still keeps reading light and approachable by having all other instances just say "Mawdad". As a general rule, it's especially important to keep the full name in text that can be read in a vacuum. Like, if a reader shows up just to read some fighting strategy, they'll jump straight to the strategy section and start reading there. If they only read "Mawdad", that won't be very correct and will come off a bit casual and awkward, but if the section starts with "Armored Mawdad" and then shortens it from there on, everything becomes clear. | ||
To note is that it's also dangerous to just blindly remove a word from the name, as was the case with the Vehemoth Phosbat. At best, some readers will be a bit tripped up by reading "Phosbat", but at worst, some readers (especially newcomers to the series) will interpret a sentence completely wrong, because they assume it's referring to the children Phosbat. Also, citations from text that comes directly from the games or another source cannot be changed, though I can't remember if you ever did that, so it's fine. | To note is that it's also dangerous to just blindly remove a word from the name, as was the case with the Vehemoth Phosbat. At best, some readers will be a bit tripped up by reading "Phosbat", but at worst, some readers (especially newcomers to the series) will interpret a sentence completely wrong, because they assume it's referring to the children Phosbat. In addition, something like the Scornet Maestro also comes off as very silly, since just calling a creature "Maestro" is like calling a famous person by their job. It's especially awkward for an insect, right? Also, citations from text that comes directly from the games or another source cannot be changed, though I can't remember if you ever did that, so it's fine. | ||
So, in conclusion, please do not remove every instance of the first word. Moderation is key, as they say. — '''{''[[User:Espyo|Espyo]]''<sup>[[User talk:Espyo|T]]</sup>}''' 14:39, September 17, 2021 (EDT) | So, in conclusion, please do not remove every instance of the first word. Moderation is key, as they say. — '''{''[[User:Espyo|Espyo]]''<sup>[[User talk:Espyo|T]]</sup>}''' 14:39, September 17, 2021 (EDT) | ||
Revision as of 14:42, September 17, 2021
Shortening enemy names
Hey there, regarding your recent edits on the boss articles, they're not bad, but I must warn you that it's not a very good idea to focus so much on shortening the names of the enemies.
For starters, it makes the article more awkward to read. The creature's name is "Armored Mawdad" (for instance). It's not the case that its name is "Mawdad", and "Armored" just happens to be flavor text. For some enemies it's not very important, but for others it's an important differentiator, like Caustic Dweevil vs. Munge Dweevil. That said, it is true that the first word of the names tends to just be an adjective, and explaining some behavior or something still works fine if you just say "Mawdad". But again: since that's not the "real" name of the creature, it's not fair to only call it "Mawdad". It makes it sound as if the article is calling it by a nickname, like a high-school friend.
The best approach is to write the full name sometimes. This not only keeps the vision of the documentation fresh, in that it should be objective documentation of the "Armored Mawdad" enemy, but it still keeps reading light and approachable by having all other instances just say "Mawdad". As a general rule, it's especially important to keep the full name in text that can be read in a vacuum. Like, if a reader shows up just to read some fighting strategy, they'll jump straight to the strategy section and start reading there. If they only read "Mawdad", that won't be very correct and will come off a bit casual and awkward, but if the section starts with "Armored Mawdad" and then shortens it from there on, everything becomes clear.
To note is that it's also dangerous to just blindly remove a word from the name, as was the case with the Vehemoth Phosbat. At best, some readers will be a bit tripped up by reading "Phosbat", but at worst, some readers (especially newcomers to the series) will interpret a sentence completely wrong, because they assume it's referring to the children Phosbat. In addition, something like the Scornet Maestro also comes off as very silly, since just calling a creature "Maestro" is like calling a famous person by their job. It's especially awkward for an insect, right? Also, citations from text that comes directly from the games or another source cannot be changed, though I can't remember if you ever did that, so it's fine.
So, in conclusion, please do not remove every instance of the first word. Moderation is key, as they say. — {EspyoT} 14:39, September 17, 2021 (EDT)