Merging Overwatch 1 and Overwatch 2 into Overwatch

BUR #36185 has been rejected.

remove implication overwatch_1 -> overwatch
remove implication overwatch_2 -> overwatch
create alias overwatch_1 -> overwatch
create alias overwatch_2 -> overwatch

With the somewhat milquetoast state of Overwatch 2 (the cancellation of PvE and the big lore drops), there isn't really a point to keep these two separate anymore.
Unlike big entries in an ongoing franchise like for example Call of Duty: Modern Warfare 2 and Call of Duty: Black Ops where each installment has completely different characters and settings, Overwatch 2 is just a small timeskip with some new added heroes in the same setting.

Also, because the boundary between the two is so vague, we have a bunch of posts in this weird limbo where they have neither of the two tags.
overwatch -overwatch_1 -overwatch_2

Even if the upcoming Overwatch Spotlight on February 12 is going to helidrop truckloads of new lore and heroes, for all intents and purposes, Overwatch 2 is still just Overwatch.

forum #329700

evazion said:

We made this mistake with Overwatch when Overwatch 2 was first announced. We split the Overwatch tag up into Overwatch 1 and Overwatch 2, but there turned out to be no significant difference between Overwatch 1 and 2. So now every Overwatch post gets multiple copyright tags, even though nobody actually searches for Overwatch 1 or Overwatch 2. All the search traffic is just for Overwatch, because that's what the game is called and nobody really cares about the distinction between the two.

Overwatch 2 introduced new default skins for every character which are different from the Overwatch 1 default skins. Currently the only way to identify them is to use "character overwatch_1" and "character overwatch_2". Alternatively, we could create tags for the default skins, the way unlockable skins are already tagged, i.e. character_(overwatch_1) and character_(overwatch_2).

Beyond that I don't think there's a reason to distinguish between overwatch_1 and overwatch_2.

Are there any cases of OW1 skins interacting with characters introduced in OW2? That could be a point in the BUR's favor.

post #5796873 dual_persona of ow1 and 2 design

usefulness of ow1 and 2 split is pretty limited imo but if there's a post it's good for it's that one(?)

The alternate OW2 default skins are a good point, so I will start tagging them as skins and make a BUR for them over at topic #28063.
Overwatch 2 was announced during Blizzcon 2019 on the first of November.
Substract a day for margin which results that of the 16494 Overwatch posts on Danbooru, only 4781 can possibly contain anything Overwatch 2 related, so it shouldn't be too hard to get through them.
Those tags should be useful regardless of whether this merge BUR passes or fails.

The old OW1 skins are called "Classic" in-game, and the new default skins are called "Overwatch 2" A for effort
But because the OW2 default skins are a very small subset, I don't really see the point to create a new tag for the old OW1 skins.

If people are searching for Mei, my proposal would be:
Mei_(overwatch) for any depiction
Mei_(overwatch_2) for her new skin
Mei_(overwatch) -official_alternate_costume for her default.

Regarding post #5796873 and similar posts;
Because the passage of time is a requirement, those should easily be handled with the time paradox tag, which at the moment only has 1 page worth of Overwatch content. A significant chunk of which is currently taken up by Captain Amari + Pharah

Yeah the characters should just have (ow1) and (ow2) qualifiers or at least one of the two, just like the skins do in-game

CS2 and CSGO got merged

However I would merge them all into OW2 not into OW (I initially voted meh); might as well make the tag the only game that exists

LQ said:

Yeah the characters should just have (ow1) and (ow2) qualifiers or at least one of the two, just like the skins do in-game

CS2 and CSGO got merged

CSGO was renamed into CS2, like, officially, while OW2 replaced OW1. That's different.

BUR #36753 has been approved by @evazion.

deprecate overwatch_1
deprecate overwatch_2

I'll deprecate these tags first so that any necessary OW2 skin tags can be created before the tags are aliased away.

I think not all characters necessarily need tags for their default OW2 skin. Sometimes the differences are minor or aren't always reflected in fanart. Our tagging is also very haphazard, so the Overwatch 1/Overwatch 2 tags aren't always a good indicator of which skin it is.

See https://overwatch.fandom.com/wiki/Heroes_skins for a good comparison of OW1/OW2 default skins.

The bulk update request #36753 (forum #335494) has been approved by @evazion.

This bulk update request is pending automatic rejection in 5 days.

mock said:

Overwatch 2 introduced new default skins for every character which are different from the Overwatch 1 default skins. Currently the only way to identify them is to use "character overwatch_1" and "character overwatch_2". Alternatively, we could create tags for the default skins, the way unlockable skins are already tagged, i.e. character_(overwatch_1) and character_(overwatch_2).

Beyond that I don't think there's a reason to distinguish between overwatch_1 and overwatch_2.

Precisely.

This bulk update request has been rejected because it was not approved within 45 days.

The bulk update request #36185 (forum #333280) has been rejected by @DanbooruBot.

mock said in forum #333286:

Beyond that I don't think there's a reason to distinguish between overwatch_1 and overwatch_2.

It seems like the devs heard us.

I read somewhere that the in-game default skins that vary between OW1 and OW2 are being renamed as well; guess we'll find out today or in five days. "Classic" for OW1, and maybe "Valorous" for "OW2", but that might be a translation from Chinese.

D.Va has been processed and now has the following tags for her default costumes:
Launch outfit: D.Va (Legacy) (Overwatch)
Current default: D.Va (Default) (Overwatch)

These are technically placeholder names because the official names of those costumes are Overwatch 1 and Overwatch 2 which would have resulted in:

d.va_(overwatch_1)_(overwatch)
d.va_(overwatch_2)_(overwatch)

which even for a silly person like me, would just be too silly.

But as mentioned above by LQ, there is a chance these might get other names.
So we'll just wait for a bit because the new patch should go live in less than 24 hours, at which point we can whip up a BUR with the proper alias and an implication to D.Va (Overwatch).

Speaking of which, I would like to use this opportunity to update the costume tags to our current conventions regarding costume tags, because these tags are very old. For reference, Overwatch released in May 2016, while the first generation of Hololive debuted in May-June 2018.

This would also help with searchability because some of the Overwatch costume tags rely heavily on lore and don't have a common base name.
Some examples being Dr. Ziegler (Overwatch) for Mercy and Sophomore Kamori for Kiriko.

But let's first tackle D.Va for now.

BUR #54631 is pending approval.

These are all the costume tags that currently imply D.Va (Overwatch) with the exception of:
D.Va (Gremlin) Not really a costume but an alternate form
D.Va The Destroyer Not really sure what to do with this one because it's related to Heroes Of The Storm RIP
Feel free to throw in some suggestions.

GabrielWB said in forum #417748:

Speaking of which, I would like to use this opportunity to update the costume tags to our current conventions regarding costume tags, because these tags are very old. For reference, Overwatch released in May 2016, while the first generation of Hololive debuted in May-June 2018.

This would also help with searchability because some of the Overwatch costume tags rely heavily on lore and don't have a common base name.
Some examples being Dr. Ziegler (Overwatch) for Mercy and Sophomore Kamori for Kiriko.

Overwatch is currently using our current conventions regarding costume tags. As discussed in topic #18788, Overwatch, alongside League and Apex, currently use the convntion that they do because that's how their skins are named, skinname_charname, or at least viewed to be the case. The last time something like this was attempted was in topic #23039 with Apex.

Just like in that last topic, the argument you should be making is one that explains that Overwatch does not have the same naming convention as League, because that gives it legitimacy, not forced uniformity.

The skins should maintain the qualifiers at the end though, right? If we had to keep the final qualifier on Marina (Splatoon 2 One Year Anniversary) (Splatoon) I don'r see why D.va's costags shouldn't end in the overwatch qualifier.

Ylimegirl said in forum #417842:

The skins should maintain the qualifiers at the end though, right? If we had to keep the final qualifier on Marina (Splatoon 2 One Year Anniversary) (Splatoon) I don'r see why D.va's costags shouldn't end in the overwatch qualifier.

I don't disagree with you on this, but I will just point out that this sort of copytag qualifier dropping does also happen with League and Apex. Compare Ahri (League of Legends) with K/DA Ahri, and Wraith (Apex Legends) and Acid Wraith. So if we do it for Overwatch, we have to do it for those two too.