The bulk update request #10987 is pending approval.

create implication destiny_(video_game) (1147) -> bungie (177)
create implication destiny_2 (560) -> bungie (177)
create implication marathon (9) -> bungie (177)

Reason: A relatively simple one, this is a BUR to add an implication for the Bungie tag for some series that they currently own the rights to that have a tag on e621.

This includes Destiny 1 and 2 as well as Marathon.

More info:
https://en.wikipedia.org/wiki/Marathon_Trilogy
https://en.wikipedia.org/wiki/Destiny_(video_game)
https://en.wikipedia.org/wiki/Destiny_2

marathon needs a disambiguator. the tag's been removed from nearly twice as many posts than it's got active.

also does destiny 2 really need a separate tag from destiny?

The bulk update request #10988 is pending approval.

Reason: A (not-so) relatively simple expansion of topic #56525 to include major characters and species. Part 1!

The bulk update request #10989 is pending approval.

Reason: A (not-so) relatively simple expansion of topic #56525 to include major characters and species. Part 2!

I tried my best to "group up" the BURs into segments that made sense, and did everything as best as I can.

pleaseletmein said:
also does destiny 2 really need a separate tag from destiny?

Realistically, I would say no, since they are quite close in proximity in terms of the timeline.

bird-tm said:
create alias exo (273) -> exo_(destiny) (18)
...
create alias war_beast (22) -> war_beast_(destiny) (0)
...
create alias eris_morn (6) -> eris_morn_(destiny) (0)
...
create alias zavala (7) -> zavala_(destiny) (0)
...
create alias cayde-6 (40) -> cayde-6_(destiny) (0)
...
create alias ikora_rey (3) -> ikora_rey_(destiny) (0)
...
create alias lord_shaxx (5) -> lord_shaxx_(destiny) (0)
...
create alias tess_everis (2) -> tess_everis_(destiny) (0)
...
create alias banshee-44 (2) -> banshee-44_(destiny) (0)

These are either unnecessary or bad. If the name is largely unambiguous, they don't need and shouldn't have a suffix. If they need a suffix, that means they're ambiguous and should be disambiguated instead of aliased to a specific one.

Also characters shouldn't imply species, since they can be depicted as alternate_species.

watsit said:
These are either unnecessary or bad. If the name is largely unambiguous, they don't need and shouldn't have a suffix. If they need a suffix, that means they're ambiguous and should be disambiguated instead of aliased to a specific one.

Also characters shouldn't imply species, since they can be depicted as alternate_species.

The base tag Exo is already defined as the Exo from Destiny, and widely used as such, so I can understand that. However, I felt it would be safe to do so, given that it's a (fairly) common Sci-Fi thing to see.
War beast IS a species from Destiny 2, and therefore should have the suffix. Everything else that I've aliased as such are actual characters from the game.

EDIT: Also, I should have mentioned before, anything that isn't already a specific character tag in those two BURs (For example, hive_wizard and goblin_(destiny)) are specifically species tags. For the tags that ARE character names, all I did was attempt to make it a bit easier to understand, since for most of them, there were two (or even three) tags for the same thing. The only exceptions to this are Hunter, Warlock, and Titan, but that's because they are specifically the different subsets of Guardian.