Topic: [REJECTED] Tag alias: barbie_wire -> barbie_(helluva_boss)

Posted under Tag Alias and Implication Suggestions

Watsit

Privileged

atomicblaze21 said:
Fair enough, but it should still have the IP suffix at the end just like the rest of the Helluva Boss character tags. In that case, it would be better to update the existing tag of barbie_(helluva_boss) to barbie_wire_(helluva_boss) and then apply this alias to the new tag.

There's no need for a suffix if the name is unique enough. There are cases where an IP has some characters with a suffix and some without, depending on the given name being unambiguous.

atomicBlaze21

Member

watsit said:
There's no need for a suffix if the name is unique enough. There are cases where an IP has some characters with a suffix and some without, depending on the given name being unambiguous.

There are plenty of characters in Helluva Boss that have unambiguous names if it weren't for character tags for certain versions of the character.

For example, loona_(helluva_boss) and loona_(aeridiccore) are the same Loona, yet the second one just denotes a specific popular 3D model. In this case, Loona needs a specific IP suffix for artwork that doesn't utilize this model. Whether or not these sub-character tags are necessary is another discussion entirely though, but it brings me to my next point.

For Barbie Wire, we have barbie_(helluva_boss) and barbie_(valorlynz). Both are the same actual character, but with the latter being a specific 3D model. Under the current paradigm that is established elsewhere, it would make sense to update both of these tags to change "barbie" to "barbie_wire", while keeping their individual suffixes.

Watsit

Privileged

atomicblaze21 said:
For Barbie Wire, we have barbie_(helluva_boss) and barbie_(valorlynz). Both are the same actual character, but with the latter being a specific 3D model.

This is actually a problem, since there's multiple characters named Barbie, so a barbie_(non-ip-suffix) is ambiguous despite the suffix.

And this tagging 3D models is not something I'm on board with, because of the issues it creates (like this). Using this logic, no character or species could ever be non-suffixed since anyone can make a 3D model of any character or species, which would require suffixing all of them. This also lets people get around the hybrid name restrictions; we can't tag vaporunny, but we can have all the vaporunny_(modeller_name) tags for each model anyone can make despite them not depicting a distinct character. Every 3D post would have a character tag for each model alongside the actual tag for the character, doubling up character tags just for being a 3D image instead of 2D.

atomicBlaze21

Member

watsit said:
This is actually a problem, since there's multiple characters named Barbie, so a barbie_(non-ip-suffix) is ambiguous despite the suffix.

And this tagging 3D models is not something I'm on board with, because of the issues it creates (like this). Using this logic, no character or species could ever be non-suffixed since anyone can make a 3D model of any character or species, which would require suffixing all of them. This also lets people get around the hybrid name restrictions; we can't tag vaporunny, but we can have all the vaporunny_(modeller_name) tags for each model anyone can make despite them not depicting a distinct character. Every 3D post would have a character tag for each model alongside the actual tag for the character, doubling up character tags just for being a 3D image instead of 2D.

I decided to make a separate forum post on the topic of character tags, I just wanted this implication because someone added the barbie_wire tag when the barbie_(helluva_boss) tag was already in more widespread use. I figured I would just request an alias to avoid the eventual need to disambiguate between the two.

  • 1