staff
236
edits
Content:Characters: Difference between revisions
Jump to navigation
Jump to search
→Choosing the parent guise: guidance on mecha/vehicles/orgs
(→lovers: do not add on account of characters simply having sex) |
(→Choosing the parent guise: guidance on mecha/vehicles/orgs) |
||
| Line 88: | Line 88: | ||
===Choosing the parent guise=== | ===Choosing the parent guise=== | ||
{{eyecatch|Note|Always pick the '''first''' of those rules that you can fit your case into. This is not a majority vote among rules; it is an '''absolute order of precedence'''. You | {{eyecatch|Note|'''Always''' pick the '''first''' of those rules that you can fit your case into. This is '''not a majority vote''' among rules; it is an '''absolute order of precedence'''. You find the first rule that fits your case, '''stop there''', and '''apply that rule and no others'''. Please remember that mods have the final say and may overturn those rules if they deem necessary.}} | ||
# If a guise can be identified as '''clearly''' the most important one, it'll be set as the main one. This '''does not''' include maybes such as "X looks a teeny tiny bit more relevant than Y"; there must be a ''compelling'' difference in plot role. | {{eyecatch|ATTENTION|Only '''character-type''' characters can be ranked by importance; the first rule therefore '''cannot''' be applied to '''mecha, vehicles, or organizations'''. For those three character types, skip the first rule and start with the second one.}} | ||
# If a guise can be identified as '''clearly''' the most important one, it'll be set as the main one. This '''does not''' include maybes such as "X looks a teeny tiny bit more relevant than Y"; there must be a ''compelling'' difference in plot role. If your character is a mecha, vehicle, or organization, however, please refer to the "ATTENTION" box above. | |||
# That failing, if a guise can be identified as '''clearly''' the "true" or original version of the character, it will be the main one. Just as before, this '''does not''' include maybes; there must be ''compelling'' evidence pointing at one guise as being the original one. | # That failing, if a guise can be identified as '''clearly''' the "true" or original version of the character, it will be the main one. Just as before, this '''does not''' include maybes; there must be ''compelling'' evidence pointing at one guise as being the original one. | ||
## This rule applies in a special way to mecha and vehicles. The '''original''' guise in the mecha/vehicle "evolutionary tree", so to speak, is to be set as the parent. Therefore, '''upgrades''' of existing models as well as '''variant or custom''' models will be the children. See examples below for help. | |||
## For organizations, the original version is simply the one that was created first, in in-universe chronology. Newer versions of the organization must necessarily be created from the older ones. | |||
# That failing, whoever appears first, in chronological release order of the relevant episodes, and in order of appearance if on the same episode, will be the main guise. | # That failing, whoever appears first, in chronological release order of the relevant episodes, and in order of appearance if on the same episode, will be the main guise. | ||
# We are yet to see a case that can't be handled that way, such as two guises being introduced in two unrelated episodes released on the same day. Should such a case ever appear, set the character that gets added first as the main guise and report the child guise to the mods; the mods will figure it out. If such a case shows up and the characters are set the other way around, ''do not'' attempt to reverse the relation; simply report it and mention that they are reversed according to this point; it may be that the case has been reviewed previously and that a mod has intentionally set the state of affairs to be the way you found it. | # We are yet to see a case that can't be handled that way, such as two guises being introduced in two unrelated episodes released on the same day. Should such a case ever appear, set the character that gets added first as the main guise and report the child guise to the mods; the mods will figure it out. If such a case shows up and the characters are set the other way around, ''do not'' attempt to reverse the relation; simply report it and mention that they are reversed according to this point; it may be that the case has been reviewed previously and that a mod has intentionally set the state of affairs to be the way you found it. | ||
Examples for mecha/vehicles: | |||
* The [https://anidb.net/ch87549 Gundam Barbatos Lupus Rex] is an upgrade of its parent, the [https://anidb.net/ch84083 Gundam Barbatos Lupus], and the Barbatos Lupus itself is an upgrade of its parent, the [https://anidb.net/ch76364 Gundam Barbatos]. | |||
* The [https://anidb.net/ch86402 Gundam Vidar] is a customization of its parent, the [https://anidb.net/ch86162 Gundam Kimaris Trooper], itself a ground combat variant of the [https://anidb.net/ch77828 Gundam Kimaris], which is oriented for space combat. Meanwhile, the [https://anidb.net/ch101745 Gundam Kimaris Vidar] is a retrofit of its parent, the Gundam Vidar, making it more space-oriented. While the Kimaris Vidar was built to be closer to the Kimaris, it is still a child of the Vidar, and only a great-grandchild of the Kimaris, because that is how the unit's versions were designed over the in-universe chronology. | |||
==Character Relations== | ==Character Relations== | ||