The bulk update request #5369 is pending approval.

create implication majin_android_21 (591) -> android_21 (84)
create implication android_21 (84) -> dragon_ball_fighterz (637)

Reason: Apparently a transformative state. Wacha all think?

I don't know Dragonball all that well, but if majin_android_21 and android_21 are separate forms, one shouldn't implicate the other. Or if they're the same, they should be aliased.

i'd say we could instead alias the android_21 into android_21_(human) or say the base android_21 is a disambiguation. i don't think implicating it is a good idea.

Somewhat related, see topic #32252 (implications for Cell's various transformative forms).

benjiboyo said:
i'd say we could instead alias the android_21 into android_21_(human) or say the base android_21 is a disambiguation. i don't think implicating it is a good idea.

I'm not sure how I feel about "(human)" when she's like not _actually_ a human. maybe something like "(base_form)"... is the human-looking forn even her base form though? the db wiki seems to that the majin-looking form is her "true" form but the human form looks more like her template, Vomi.

I guess the majin-looking form isn't technically a majin either and majin_android_21 is a fan created term as far as I can tell, so...

hmm... I think if we want it to be consistent with the rest of our naming schemes for tags like this we should just use android_21_(human_form) and android_21_(majin_form)