Posted under Tags
The bulk update request #13700 has been approved by @evazion.
create alias hero-chan_(hanauna) -> arihara_yuuna_(hanauna)
She has a name, and she's appeared in hanauna's original works enough times with no connection to her origin as a genderswap of Roto.
I've updated her wiki page with the other two Pixiv tags the artist is using to describe her: 有原優奈 (her name, as in the alias) and 魔法少女ゆーしゃちゃん (Magical Girl Hero-chan).
I've also put together a wiki page for and flushed out the other "see also" tag from the Roto entry (Heroine (dq3)) proposed in topic #18888.
Speaking of Roto, the character's name is ambiguous with other tags started with "roto*", like Rotom and its many forms. I'll do this on a separate thread if anyone agrees.
VR-Man said:
Speaking of Roto, the character's name is ambiguous with other tags started with "roto*", like Rotom and its many forms. I'll do this on a separate thread if anyone agrees.
Go ahead.
VR-Man said:
Speaking of Roto, the character's name is ambiguous with other tags started with "roto*", like Rotom and its many forms. I'll do this on a separate thread if anyone agrees.
Maybe it should be moved to Roto (DQ3)? I like the idea of keeping a tag to catch both variants of the character. After flushing things out, it turns out in practice it's about 50-50 male and female instances, so it's not like one or the other would be the "main" version.
Should the assorted Dragon Quest tags attached to her be purged too? She's clearly an OC at this point.
Hillside_Moose said:
Should the assorted Dragon Quest tags attached to her be purged too? She's clearly an OC at this point.
It probably makes sense to keep the tag for the older posts like post #3253228 or post #2613018 where it's obvious that it's a genderswap. The alternative is to retroactively tag it as cosplay, but that doesn't feel right.
I don't even think cosplay would count, since it's loosely based on Roto's costume than an exact match (post #5865373 vs post #2013102).
The bulk update request #13700 (forum #227750) has been approved by @evazion.
