Content:Characters: Difference between revisions

Character relations are supposed to be '''lower case''', as well as '''short''' and as '''neutral''' as possible. They are furthermore '''always''' supposed to be two-sided; the vice versa option should '''always''' be marked. If a relation is truly one-sided (e.g. character A considers character B a rival, but character B doesn't think that way, or maybe doesn't even know character A exists), the comment should specify it as "on character A's part only".

Family relations never end, even after one person dies. The question of whether someone who's related through marriage (e.g. your aunt who's your mother's brother's wife) continues to be a family member following a divorce or the death of their spouse has not yet been settled; for now, please assume all relations existing at the time of the end of the marriage will stay so, and new additions to the family will not have the relation. This is not yet settled policy and is subject to change at any time. Also, it should go without saying, but family relations are never one-sided.

As a final note, please note that couples are '''NOT''' valid family relations; please use the appropriate couple-centered relations instead. If, however, the relation is incestuous, both the couple relation and the regular family relation should evidently be added.

On its own, that relation is entirely self-explanatory. A comment might elaborate on the circumstances, reasons, means employed, and so on; some examples might include "stabbed in the jugular vein with a ballpoint pen" or "accidentally shot on the forehead". Clearly, this relation is never one-sided and never ends.

This relation type also requires a comment, as it always refers to an office, position, title, etc. You can be someone's successor as some company's CEO, as some country's king, as head of your clan, and so on; the comment should specify what role specifically one character succeeded the other in. Some reasonable examples might be "as family head", "as king", "as the King of England", or "as Nintendo's president". This relation is never one-sided, and it never ends.

This relation type implies an object of rivalry between the rivals, which needs to be specified; when two people compete, they compete for something, and there is a need of a comment to specify what they are competing for. You can be someone's rival in the fight for someone else's love, in trying to be the fastest racer in town, in your goal of being the very best, like no one ever was, and so on; additionally, rivalries might end following some sort of event, and they may be one-sided, in that only one side recognizes the other as a rival. Reasonable examples might be "for Sakura's love", "for Sakura's love, until Tarou fell in love with Yuri", "for Sakura's love, until Tarou died", "for Sakura's love, only on Keiichi's part", "for Sakura's love, only on Keiichi's part, until Tarou died", "as fellow racers", and so forth.

The "other" relation type '''always''' requires a comment, because otherwise people won't be able to understand what the relation is even supposed to cover. This may sound obvious, but "other"-type relations without a comment are very common, leading to much frustration when dealing with them. As such, please '''always''' describe the "other"-type relations you add, and try to elaborate on any you find. Since this relation type is a catchall for anything not covered by any other type, it may be one-sided, and it may end, or it may not. Please exercise common sense to its fullest when adding an "other"-type relation and do not add foolish relations over inane things.