As the title says, why does hybrid tag imply mimic dragon? Shouldn't it be the other way around?
And speaking of, why does hybrid imply fan character? As the wiki says: fan character "is a character that is based off of a franchise, series, or other copyright but is not a canon character." This implication makes it, so that, if there's e.g. a cat-fox hybrid, then it's automatically a fan character (and a mimic_dragon as well, for some reason), which, I think, shouldn't be the case.

Curiously enough, looking up the implications for hybrid → mimic_dragon and hybrid → fan_character pulls up topic #3655 and topic #18824 as sources. Odd, considering those are both several years ago and neither topic actually includes a hybrid implication.

The bulk update request #113 has been rejected.

remove implication hybrid (145643) -> fan_character (128277)
remove implication hybrid (145643) -> mimic_dragon (49)

Reason: Something odd happened...

EDIT: The bulk update request #113 (forum #293053) has failed: Implication for hybrid not found

EDIT: The bulk update request #113 (forum #293053) has been rejected by @KiraNoot.

So all thoses posts need to be corrected : mimic_dragon fan_character hybrid

We're working on it, this will be fixed with database magic soonish.

The automoderator must have gone wonky again or something.

seryam said:
As the title says, why does hybrid tag imply mimic dragon? Shouldn't it be the other way around?

Reversing the implication wouldn't be accurate either since mimic dragons aren't supposed to be hybrids. They're like dragonifications of the original animal, instead of a mix X animal with dragon.

Also, mimic dragons probably won't be fan characters so reversing that implication would be silly too.

lafcadio said:
Curiously enough, looking up the implications for hybrid → mimic_dragon and hybrid → fan_character pulls up topic #3655 and topic #18824 as sources. Odd, considering those are both several years ago and neither topic actually includes a hybrid implication.

As far as I can tell, in the time between those getting proposed vs. approved, the predicates dragonchu and bird_dragon got aliased to hybrid. So then hybrid received the implications.

clawstripe said:
The automoderator must have gone wonky again or something.

I got an instant pot the other day :D Neat kitchen tool! It has an awesome feature that detects if there's anything even close to "burning" going on on the bottom of the pot, and shuts everything down if that's the case. I had incorrectly added cooked rice to the pot, and nothing was sticking to the bottom, nothing was burning. It was just thicc. I just wanted the pot to run for about 5 minutes to soften the carrots.

It refused, despite adding 4 cups more liquid, scooping rice out, etc etc etc. It was just really set on the idea that it was burning, and that it wasn't going to run for more than 30 seconds.

This is basically what happened. A very useful feature, popping up at the wrong moment and getting in everyone's face, and the next thing you know -- mimic dragons everywhere.

Please be careful of suspiciously located treasure chests while we sort this out.

So a bunch of things went wrong here, but the take away here is that accepting aliases behaved in an unexpected way that created a mess. There isn't a trivial way to undo this because the result wasn't the direct action of any specific input or alias/implication approval, but instead a side effect, so there wasn't sufficient undo information stored to roll back the action. Work is being done to prevent transitive retargeting of aliases and implications during BUR, as well as provide moderators with forewarning if these retargetings may take place. Removing these retargeting actions would break aliases and implications, so a warning will have to do.

The bad news, yes, those 6 pages of posts need to be manually reviewed. Some of the older posts that haven't been touched in a while might be able to be reverted easily, but the newer ones are more suspect.

The bulk update request #113 (forum #293053) has failed: Implication for hybrid not found

The bulk update request #113 (forum #293053) has been rejected by @KiraNoot.

kiranoot said:
The bad news, yes, those 6 pages of posts need to be manually reviewed. Some of the older posts that haven't been touched in a while might be able to be reverted easily, but the newer ones are more suspect.

I'm working on it. Cleaning these up is relatively simple, just need to check which tags get added to the tag history. Edit: And finished.

As for the mimic_dragon tag itself: doesn't look like a hybrid to me. If it needs to be aliased anywhere, I'd suggest mimicry.

genjar said:
I'm working on it. Cleaning these up is relatively simple, just need to check which tags get added to the tag history. Edit: And finished.

As for the mimic_dragon tag itself: doesn't look like a hybrid to me. If it needs to be aliased anywhere, I'd suggest mimicry.

Wow, you should be like, staff or something.

kaworu said:
...the predicates dragonchu and bird_dragon got aliased to hybrid.

Wait, why was bird_dragon aliased away to hybtid? They were never meant to be hybrids, never intended to be hybrids, and never were hybrids. They are merely a subclass of small dragon that mimics certain varieties of birds. They are not a mix of birds and dragons. Furthermore, aliasing away bird_dragon makes it harder to search for these specific creatures as they're now drowned out by all those hybrids.