Kama Fate untangling

Posted under Tags

BUR #42596 has been approved by @nonamethanks.

Show

Kama's a fun one to deal with because she has three distinct forms. Eventually want to work on implicating individual costumes to their respective ascensions, but for now I'm starting with what is hopefully the easiest--fixing her damn swimsuit tags. Umbrella tag serves no real purpose and each individual ascension is better implied to the actual corresponding ascension of her Assassin self.

BUR #42597 has been approved by @nonamethanks.

create implication kama_(mistake)_(first_ascension)_(fate) -> kama_(first_ascension)_(fate)
create implication kama_(mistake)_(second_ascension)_(fate) -> kama_(first_ascension)_(fate)
create implication kama_(mistake)_(third_ascension)_(fate) -> kama_(first_ascension)_(fate)
deprecate kama_(mistake)_(fate)
mass update kama_(mistake)_(*_ascension)_(fate) -> -kama_(mistake)_(fate)

Implying all of mistake's ascensions to her first ascension, since that's clearly the form this version of Kama is based on. And then deprecating the Mistake tag since that's all very different costumes with no connective link beyond all being her assassin first ascension age.

I wonder if we shouldn't just have kama (young) (fate), kama (teenager) (fate) (or something) and kama (adult) (fate). That way the original ascension costumes can get their own tags and be searchable.

Also I think there was a mistake that I just noticed (but didn't when approving ORZ): kama (swimsuit avenger) (third ascension) (fate) and kama (swimsuit avenger) (second ascension) (fate) are now implying kama (first ascension) (fate), but that doesn't seem right.

nonamethanks said:

I wonder if we shouldn't just have kama (young) (fate), kama (teenager) (fate) (or something) and kama (adult) (fate). That way the original ascension costumes can get their own tags and be searchable.

Also I think there was a mistake that I just noticed (but didn't when approving ORZ): kama (swimsuit avenger) (third ascension) (fate) and kama (swimsuit avenger) (second ascension) (fate) are now implying kama (first ascension) (fate), but that doesn't seem right.

Oh yeah that one's my bad. What I get for copypasting lines of a BUR.

BUR #44241 is pending approval.

Show

Alright, covering this aforementioned costume split thingie. Option 1, repurpose kama_(*_ascension)_(fate) tags to specifically refer to the Assassin ascensions and rename the sub-umbrellas to the other names in forum #364027. Pros: Fairly intuitive. Cons: Unofficial. as of the exact minute when im posting these BURs the favgroups are not fully populated. im working on it. i get impatient. ok they should all be like 95% complete, barring banned posts and human error

Updated by Ylimegirl

BUR #44242 is pending approval.

mass update favgroup:45247 -> kama_(assassin)_(first_ascension)_(fate)
mass update favgroup:45248 -> kama_(assassin)_(second_ascension)_(fate)
mass update favgroup:45249 -> kama_(assassin)_(third_ascension)_(fate)
create implication kama_(assassin)_(first_ascension)_(fate) -> kama_(first_ascension)_(fate)
create implication kama_(assassin)_(second_ascension)_(fate) -> kama_(second_ascension)_(fate)
create implication kama_(assassin)_(third_ascension)_(fate) -> kama_(third_ascension)_(fate)

Option 2, creating new tags qualified with (assassin) to refer to her as an Assassin-class servant. Pros: means you can search for kama_(assassin)_(*)_(fate) and get all of the outfits simultaneously (as opposed to the previous BUR, where kama_(*_ascension)_(fate) would give false positives for her swimsuit version), technically official, don't have to move around the existing tags, matches her swimsuit avenger version. Cons: Kinda clunky.

I'll let my votes speak for themselves on which one I'm partial to.

1