evazion said in forum #396842:
I'll just deprecate it for now until someone can some up with something better.
Since previous attempts at mob_x_character failed due to being seen as redundant with solo_focus, I propose a cleaner, atomic approach by separating Identity from Quantity.
The current reliance on solo_focus is insufficient; it essentially only covers "one girl + X boys" , leaving a massive gap for multiple_girls, multiple_boys, or any group interaction involving anonymous subjects. Furthermore, gender counts (1boy, 2boys, etc.) act as massive, unorganized "everything tags" that mix named characters with nameless extras.
The Proposal:
mob_character (Identity): A tag for a non-background character with an active role but no unique design (faceless, POV, generic anon, etc.).
Utility: It identifies a subject, not a relationship. It allows users to filter -mob_character to see only canon/OC content—something solo_focus cannot do. It differs from people/crowd because the mob_character has agency and interacts with the cast.
multiple_mobs (Quantity): Used when two or more such characters are present. This avoids numerical counter bloat and separates active group interactions from passive background noise.
We don't need mob_x_character. If we define the subjects properly (Character A + mob_character), the relationship is implied.
If the concern is that this will become a "bulk tag", we must realize that 1boy, 2boys, etc., are already that—just much messier versions. It's better to have a functional, filterable "trash can" than to have the trash mixed in with the named identities of our database.