The tag implication #51410 neck_expansion -> expansion is pending approval.

Reason: This seems like a fairly obvious missing one to me. There are more but neck_expansion already has a few posts associated with it and I might potentially add it to quite a few more TF-related images.
I've also added it to the expansion wiki page as an existing tag. Thanks!

Small bump (just in case anyone wants to vote, got buried a bit, will not bump again)

I still think we should avoid the 'expansion' tags in favor of 'growth'. e6 tries to distinguish expansion from growth by 'something that exists growing more' (expansion) and 'something that didn't exist growing new' (growth), but in common speech they mean nearly the same thing (or to me, "expansion" indicates something that stretches out from what it already has, like a balloon, rather than something becoming different, like a human neck becoming an elongated dragon neck), it's sometimes difficult or impossible to tell one from the other, the distinction can be ambiguous (particularly for multi-page sequences, where a character could start to grow a tail or wings on one page, then on the other, the tail or wings are already there and grow to full size), and many *_growth tags get used for things that preexisted and grow more.

I don't really see how this is relevant to this. The *_growth vs *_expansion debate is an interesting one. But this implication just aims to make the existing system a tiny bit more consistent with itself (a quick fix).

Switching to a completely different system to the current one takes way more work and discussion (and therefore time). It's also debatable whether there really is no worth in trying to differentiate growth and expansion (even if the current names are a bit confusing and the tagging gets more ambiguous).

If you then want to change all neck_expansion to neck_growth later, so be it. I just want want more internal consistency in the meantime. Seems weird to me to not do this based on some potential future change.

arandompersonishere said:
I don't really see how this is relevant to this.

Primarily because changing tags later becomes more of a problem when there's more aliases and implications associated with them. Changing neck_expansion/expansion later will be more difficult if there's already implications associated with them, as the implications will have to be removed first before they can be aliased/renamed. There's little point to adding an implication that would just need to be removed.

watsit said:
Primarily because changing tags later becomes more of a problem when there's more aliases and implications associated with them. Changing neck_expansion/expansion later will be more difficult if there's already implications associated with them, as the implications will have to be removed first before they can be aliased/renamed. There's little point to adding an implication that would just need to be removed.

I can't say I really see the problem. Changing the tag structure itself seems far more involved than just removing an implication to me. Or rather, removing these implications (there are many existing ones like it) seems like the smallest part of such a change. Yes, it will need to be done but again, it will need to be done for others as well and it's arguing from the position of a future change that has not been decided yet, as far as I can tell (if I'm wrong, please correct me, I'm quite new to this).

The alternative is to just continue with always manually adding the more general tag as well (because again, anything else is just not consistent with the current tagging structure IMO). Which is prone to error. Would be nice to have that part automated.

If you completely disagree with adding the more general tag, I'd like to know why (using the current tag structure) a neck_expansion is not a type of expansion. It is not the sort of exception to the rule like body_size_growth (or arguably muscle_growth but I'm not touching that right now) as far as I can tell. It fits with the existing other *_expansion tags since you are not growing a new neck.

EDIT: (hope this didn't sound aggressive, I'm just confused about this right now and it's hard to convey emotions in text)