Dealing with copyright-specific Pokemon NPC character tags

Posted under Tags

BUR #41318 has been rejected.

Show

mass update ace_trainer_(female)_(pokemon_bw) -> -ace_trainer_(female)_(pokemon_bw) ace_trainer_(female)_(pokemon)
mass update ace_trainer_(female)_(pokemon_colosseum) -> -ace_trainer_(female)_(pokemon_colosseum) ace_trainer_(female)_(pokemon)
mass update ace_trainer_(female)_(pokemon_dppt) -> -ace_trainer_(female)_(pokemon_dppt) ace_trainer_(female)_(pokemon)
mass update ace_trainer_(female)_(pokemon_frlg) -> -ace_trainer_(female)_(pokemon_frlg) ace_trainer_(female)_(pokemon)
mass update ace_trainer_(female)_(pokemon_gsc) -> -ace_trainer_(female)_(pokemon_gsc) ace_trainer_(female)_(pokemon)
mass update ace_trainer_(female)_(pokemon_hgss) -> -ace_trainer_(female)_(pokemon_hgss) ace_trainer_(female)_(pokemon)
mass update ace_trainer_(female)_(pokemon_lgpe) -> -ace_trainer_(female)_(pokemon_lgpe) ace_trainer_(female)_(pokemon)
mass update ace_trainer_(female)_(pokemon_oras) -> -ace_trainer_(female)_(pokemon_oras) ace_trainer_(female)_(pokemon)
mass update ace_trainer_(female)_(pokemon_rgby) -> -ace_trainer_(female)_(pokemon_rgby) ace_trainer_(female)_(pokemon)
mass update ace_trainer_(female)_(pokemon_rse) -> -ace_trainer_(female)_(pokemon_rse) ace_trainer_(female)_(pokemon)
mass update ace_trainer_(female)_(pokemon_sm) -> -ace_trainer_(female)_(pokemon_sm) ace_trainer_(female)_(pokemon)
mass update ace_trainer_(female)_(pokemon_xy) -> -ace_trainer_(female)_(pokemon_xy) ace_trainer_(female)_(pokemon)
mass update ace_trainer_(male)_(pokemon_bw) -> -ace_trainer_(male)_(pokemon_bw) ace_trainer_(male)_(pokemon)
mass update ace_trainer_(male)_(pokemon_dppt) -> -ace_trainer_(male)_(pokemon_dppt) ace_trainer_(male)_(pokemon)
mass update ace_trainer_(male)_(pokemon_frlg) -> -ace_trainer_(male)_(pokemon_frlg) ace_trainer_(male)_(pokemon)
mass update ace_trainer_(male)_(pokemon_gsc) -> -ace_trainer_(male)_(pokemon_gsc) ace_trainer_(male)_(pokemon)
mass update ace_trainer_(male)_(pokemon_hgss) -> -ace_trainer_(male)_(pokemon_hgss) ace_trainer_(male)_(pokemon)
mass update ace_trainer_(male)_(pokemon_lgpe) -> -ace_trainer_(male)_(pokemon_lgpe) ace_trainer_(male)_(pokemon)
mass update ace_trainer_(male)_(pokemon_oras) -> -ace_trainer_(male)_(pokemon_oras) ace_trainer_(male)_(pokemon)
mass update ace_trainer_(male)_(pokemon_rgby) -> -ace_trainer_(male)_(pokemon_rgby) ace_trainer_(male)_(pokemon)
mass update ace_trainer_(male)_(pokemon_rse) -> -ace_trainer_(male)_(pokemon_rse) ace_trainer_(male)_(pokemon)
mass update ace_trainer_(male)_(pokemon_sm) -> -ace_trainer_(male)_(pokemon_sm) ace_trainer_(male)_(pokemon)
mass update ace_trainer_(male)_(pokemon_xy) -> -ace_trainer_(male)_(pokemon_xy) ace_trainer_(male)_(pokemon)
deprecate ace_trainer_(female)_(pokemon_bw)
deprecate ace_trainer_(female)_(pokemon_colosseum)
deprecate ace_trainer_(female)_(pokemon_dppt)
deprecate ace_trainer_(female)_(pokemon_frlg)
deprecate ace_trainer_(female)_(pokemon_gsc)
deprecate ace_trainer_(female)_(pokemon_hgss)
deprecate ace_trainer_(female)_(pokemon_lgpe)
deprecate ace_trainer_(female)_(pokemon_oras)
deprecate ace_trainer_(female)_(pokemon_rgby)
deprecate ace_trainer_(female)_(pokemon_rse)
deprecate ace_trainer_(female)_(pokemon_sm)
deprecate ace_trainer_(female)_(pokemon_xy)
deprecate ace_trainer_(male)_(pokemon_bw)
deprecate ace_trainer_(male)_(pokemon_dppt)
deprecate ace_trainer_(male)_(pokemon_frlg)
deprecate ace_trainer_(male)_(pokemon_gsc)
deprecate ace_trainer_(male)_(pokemon_hgss)
deprecate ace_trainer_(male)_(pokemon_lgpe)
deprecate ace_trainer_(male)_(pokemon_oras)
deprecate ace_trainer_(male)_(pokemon_rgby)
deprecate ace_trainer_(male)_(pokemon_rse)
deprecate ace_trainer_(male)_(pokemon_sm)
deprecate ace_trainer_(male)_(pokemon_xy)

Gendered character tags for the trainer classes which can be either male or female aren't replacable with another search in the same way the above are, and so I think there's some merit in keeping them. In line with the above, however, I propose we de-copyright them by merging the same gender tags together.

I'm going to go against the grain and say all these characters shouldn't be grouped together under the same chartag. Visually speaking, they are all different characters, it doesn't make any sense to me to group them just because they share the same name. As someone who's only tangentially interested in pokemon, this system looks like it was designed by a bureaucrat instead of an actual user of this site.

Look at the lineup in post #1699925. They all look different. If they were named characters we wouldn't be grouping them under the same chartag.
If we're doing this because "we've always done it this way", then this might be a good time to stop.

I know nothing about these NPCs, and with the current status quo I can't just look at the tags to figure out which character is which, instead I have to go on a hunt by combining game tags with character tags until I find the right character. This seems like a pointless waste of effort and it makes me feel like we're just shooting ourselves in the foot when I compare it to other copyrights.

Updated by nonamethanks

If lass (pokemon) won't have its category changed to general, maybe add an implication. Other than that, I think each one should be a separate character tag.

Most other character classes are general tags I think, as other people within the same class can look quite different—as they're different people!

LQ said:

If lass (pokemon) won't have its category changed to general, maybe add an implication. Other than that, I think each one should be a separate character tag.

Most other character classes are general tags I think, as other people within the same class can look quite different—as they're different people!

This is what's actually happening here, these are class/job/profession tags, not character tags. We should not be grouping vastly different designs under them and pretending it's a good system.

This is not like May (Pokemon) where the same character appears in multiple games. post #8897175 and post #5037595 are different characters, they should not be under the same chartag.

Updated by nonamethanks

nonamethanks said:

BUR #42242 has been rejected.

mass update lass_(pokemon) -lass_(pokemon_*) -> -lass_(pokemon)
deprecate lass_(pokemon)

My proposal. I'll cleanup the search first, since there's a bunch of posts not tagged with the correct character. The rest of the NPC tags haven't been split yet, so I'm ignoring them, but if they ever are we can deprecate them too.

Since we're not touching the player character tags, I have no objections to this. They are seperate characters, after all.

zetsubousensei said:

What would done about fan Lass designs for speculative/fan-made regions?

Same thing we did with similar cases, make a chartag for unofficial ones, something like lass (pokemon) (unofficial). It's not like you can search for them properly now anyway, you already have to filter out another dozen characters and original is too broad.

Another question is about images like post #1215162 or post #1212582 where the text/pose indicates the character is meant to be a Lass but it isn't cosplay.

This is a good question. For other copyrights, for references that aren't cosplays we often have dedicated gentags, for example jonathan_joestar's_pose, but it's not that simple with pokemon because of things like specific pokemon species or poke balls or other contextual info associated with a character.
It would be a good argument for keeping the umbrella tag, though we'd still want the subtags because we want users to be able to search for individual characters with a single chartag (like every other copyright).

Updated by nonamethanks

I agree that we shouldn't treat all lass_(pokemon) trainers as a single character.
Each version has a unique design and personality specific to their game.

We already apply this logic elsewhere. We recognize that the various Ninas in the Breath of Fire series are different characters (nina_(breath_of_fire_i), nina_(breath_of_fire_ii), etc.).
If we merged them, we'd also have to merge every generic NPC. For example, instead of a specific bandit_(tales_of_destiny_2), we'd have a single bandit_(tales_of) tag, even though the "Bandit" in Tales of Graces is a man and the one in Destiny 2 is a woman. It's inconsistent.

Also, regular users like me are limited to two search tags. If we have to use both just to identify a single character (chartag + copytag), it becomes impossible to add any other tags to refine the search.
Keeping the existing, specific character tags is essential.

Should existing posts with general trainer class tags all be retagged? Looking at the lass tags for example, there is about 20-30 posts each under the game-specific ones and ober 400 for the general one

Currently I don't have a problem with splitting up the different designs into separate tags, I generally prefer specific designs to have their own character tags in other franchises after all, but recognize such a thing will add a ton of new tags across the board when you take into account how many trainer classes there are in Pokemon, the many different versions each have through the games, manga and anime and doubly so if we also split male and female down the line as they usually also have different designs within the same game. It will also mean every image will be tagged with both the specific character tag + corresponding copyright tag that both have the same acronyms. Again I personally don't mind this but I know others consider it bloat.

Anyways, I would prefer the specific character tag to be an implication over making the tag general or nuking/depreciating the group tag entirely. I'm sure it'd be useful for users to still have one tag that has all the different designs found under it.

Updated by pc88

BUR #43325 has been approved by @nonamethanks.

create implication lass_(pokemon_bdsp) -> lass_(pokemon)
create implication lass_(pokemon_bw) -> lass_(pokemon)
create implication lass_(pokemon_dppt) -> lass_(pokemon)
create implication lass_(pokemon_frlg) -> lass_(pokemon)
create implication lass_(pokemon_gsc) -> lass_(pokemon)
create implication lass_(pokemon_hgss) -> lass_(pokemon)
create implication lass_(pokemon_lgpe) -> lass_(pokemon)
create implication lass_(pokemon_oras) -> lass_(pokemon)
create implication lass_(pokemon_origins) -> lass_(pokemon)
create implication lass_(pokemon_rgby) -> lass_(pokemon)
create implication lass_(pokemon_rse) -> lass_(pokemon)
create implication lass_(pokemon_sm) -> lass_(pokemon)
create implication lass_(pokemon_swsh) -> lass_(pokemon)
create implication lass_(pokemon_xy) -> lass_(pokemon)

Changing to implication

BUR #43327 has been approved by @nonamethanks.

Show

create implication ace_trainer_(female)_(pokemon_bw) -> ace_trainer_(pokemon)
create implication ace_trainer_(female)_(pokemon_colosseum) -> ace_trainer_(pokemon)
create implication ace_trainer_(female)_(pokemon_dppt) -> ace_trainer_(pokemon)
create implication ace_trainer_(female)_(pokemon_frlg) -> ace_trainer_(pokemon)
create implication ace_trainer_(female)_(pokemon_gsc) -> ace_trainer_(pokemon)
create implication ace_trainer_(female)_(pokemon_hgss) -> ace_trainer_(pokemon)
create implication ace_trainer_(female)_(pokemon_lgpe) -> ace_trainer_(pokemon)
create implication ace_trainer_(female)_(pokemon_oras) -> ace_trainer_(pokemon)
create implication ace_trainer_(female)_(pokemon_rgby) -> ace_trainer_(pokemon)
create implication ace_trainer_(female)_(pokemon_rse) -> ace_trainer_(pokemon)
create implication ace_trainer_(female)_(pokemon_sm) -> ace_trainer_(pokemon)
create implication ace_trainer_(female)_(pokemon_xy) -> ace_trainer_(pokemon)
create implication ace_trainer_(male)_(pokemon_bw) -> ace_trainer_(pokemon)
create implication ace_trainer_(male)_(pokemon_dppt) -> ace_trainer_(pokemon)
create implication ace_trainer_(male)_(pokemon_frlg) -> ace_trainer_(pokemon)
create implication ace_trainer_(male)_(pokemon_gsc) -> ace_trainer_(pokemon)
create implication ace_trainer_(male)_(pokemon_hgss) -> ace_trainer_(pokemon)
create implication ace_trainer_(male)_(pokemon_lgpe) -> ace_trainer_(pokemon)
create implication ace_trainer_(male)_(pokemon_oras) -> ace_trainer_(pokemon)
create implication ace_trainer_(male)_(pokemon_rgby) -> ace_trainer_(pokemon)
create implication ace_trainer_(male)_(pokemon_rse) -> ace_trainer_(pokemon)
create implication ace_trainer_(male)_(pokemon_sm) -> ace_trainer_(pokemon)
create implication ace_trainer_(male)_(pokemon_xy) -> ace_trainer_(pokemon)

The equivalent for ace trainer.

1