The bulk update request #6370 has been rejected.

remove implication squirrelflight_(warriors) (3) -> warriors_(book_series) (2310)
create implication squirrelstar_(warriors) (142) -> warriors_(book_series) (2310)

Reason: This character has a new name, so her tag should reflect that going forwards. https://warriors.fandom.com/wiki/Squirrelstar

Part 2:

alias squirrelflight_(warriors) -> squirrelstar_(warriors)

EDIT: The bulk update request #6370 (forum #389041) has been rejected by @Nimphia.

aww love that for her

The bulk update request #6371 is active.

remove alias brambleclaw_(warriors) (95) -> bramblestar_(warriors) (15)
remove implication bramblestar_(warriors) (15) -> warriors_(book_series) (2310)

Reason: Brambleclaw stepped down from leadership so his name is no longer Bramblestar, it's Brambleclaw again

Part 2:
imply brambleclaw_(warriors) -> warriors_(book_series)
alias bramblestar_(warriors) -> brambleclaw_(warriors)

EDIT: The bulk update request #6371 (forum #389044) has been approved by @slyroon.

Haven't read the books since I was a kid, but good for her she deserved it.

Out of curiosity, hiw does e6 deal with the multiple characters who end up with the same leader name? Or has that not come up yet lol

oopsitripped said:
Out of curiosity, hiw does e6 deal with the multiple characters who end up with the same leader name? Or has that not come up yet lol

There may be more but the major example is the two Tigerstars (formerly Tigerclaw) and Tigerheart) ). So far e6 just hasn't updated tigerheart_(warriors)'s tag yet. I think we should probably just use the same clan/arc suffixes as the warriors wiki does?

Similar issue with the two Pouncetails, two Frecklewishes, and surely more

cloudpie said:
There may be more but the major example is the two Tigerstars (formerly Tigerclaw) and Tigerheart) ). So far e6 just hasn't updated tigerheart_(warriors)'s tag yet. I think we should probably just use the same clan/arc suffixes as the warriors wiki does?

Similar issue with the two Pouncetails, two Frecklewishes, and surely more

Funnily I actually just swapped a Frecklewish tag earlier

See, on one hand I get WHY the name should be updated, on the other hand I feel that it would be a massive spoiler for anyone who's looking at art but isn't up to date on the story. If the pictures are of a time while she was still named Squirrelflight then I feel the name should stay as-is on those pictures.

calydor said:
See, on one hand I get WHY the name should be updated, on the other hand I feel that it would be a massive spoiler for anyone who's looking at art but isn't up to date on the story. If the pictures are of a time while she was still named Squirrelflight then I feel the name should stay as-is on those pictures.

To be fair, it's one of those spoilers that's near impossible to avoid, given the wiki updated her page and everyone's using her new name on social media and such

Plus it's not even really a "latest book spoiler" since the plot point was set up at the end of Shadow (a book that is almost a year old). Really the only spoiler here is that she doesn't tragically die before getting her lives, lol

calydor said:
See, on one hand I get WHY the name should be updated, on the other hand I feel that it would be a massive spoiler for anyone who's looking at art but isn't up to date on the story. If the pictures are of a time while she was still named Squirrelflight then I feel the name should stay as-is on those pictures.

i'd argue that there are quiet amount of characters here that are too spoiler-y and important for the end to be revealed here (probably fitting spoiler example: chara or asriel dreemur from undertale that gets revealed at the end of the game or final evolution of starter pokemon you got exposed to on e6 before playing the game yourself to find out).

dsco said:
To be fair, it's one of those spoilers that's near impossible to avoid, given the wiki updated her page and everyone's using her new name on social media and such

Plus it's not even really a "latest book spoiler" since the plot point was set up at the end of Shadow (a book that is almost a year old). Really the only spoiler here is that she doesn't tragically die before getting her lives, lol

Which is itself a problem.

Some years ago I watched the first two seasons of a show, then put it aside for some time until I got around to watching season three. By then I only remembered the story in very broad strokes and so went to look up the show's wiki for a refresher.

I was so confused. There was a character I didn't remember -at all-. And another character I vaguely remembered who wasn't mentioned -at all-. And slowly I realized that the latter's actions were attributed to the former.

Turned out it was a massive plot point in season three that the character came out as trans, which is perfectly fine - but when it's possible for people to actually go back and experience them pre-coming out I feel the waters get very murky on whether their old name should be corrected everywhere or not. The first two seasons don't get retconned and re-released with their new identity, after all. At the time the character was female, by season three episode ... two or so the character is no longer female, and I feel any mention of actions in seasons one and two should be mentioned by how viewers will experience those seasons.

So it is for titles like this. Imagine a ... story set in the military, with the protagonist striving and failing over and over to reach the rank of I dunno, corporal. The whole point of the story is to see if he ever makes it. Except ... the fandom constantly refers to him as corporal rather than recruit because by the final episode he gets the promotion he so dearly wants. Is that fair to new viewers/readers who weren't following it at the time of release?

calydor said:
Which is itself a problem.

Some years ago I watched the first two seasons of a show, then put it aside for some time until I got around to watching season three. By then I only remembered the story in very broad strokes and so went to look up the show's wiki for a refresher.

I was so confused. There was a character I didn't remember -at all-. And another character I vaguely remembered who wasn't mentioned -at all-. And slowly I realized that the latter's actions were attributed to the former.

Turned out it was a massive plot point in season three that the character came out as trans, which is perfectly fine - but when it's possible for people to actually go back and experience them pre-coming out I feel the waters get very murky on whether their old name should be corrected everywhere or not. The first two seasons don't get retconned and re-released with their new identity, after all. At the time the character was female, by season three episode ... two or so the character is no longer female, and I feel any mention of actions in seasons one and two should be mentioned by how viewers will experience those seasons.

So it is for titles like this. Imagine a ... story set in the military, with the protagonist striving and failing over and over to reach the rank of I dunno, corporal. The whole point of the story is to see if he ever makes it. Except ... the fandom constantly refers to him as corporal rather than recruit because by the final episode he gets the promotion he so dearly wants. Is that fair to new viewers/readers who weren't following it at the time of release?

Right, but does e621 make tags less accurate because of potential spoilers? No, because what counts as a spoiler is subjective. I personally don't think a character name change from a plot point that was set up a year ago in a series where name changes are normal is a spoiler. You may disagree, but it's not e621's job to determine what is and is not a spoiler.

Also, we really don't need another princess_twilight_sparkle_(mlp), especially given that 90% of the time, unless an artist is giving leaders a unique feature, Squirrelflight and Squirrelstar are going to look visually identical.

Hell, you could argue that Fireheart -> Firestar is a spoiler for people who haven't read arc one... Despite that series being 20 years old. Or that Bramblestar's name is a spoiler for The Last Hope, even though the book immediately following it is literally titled "Bramblestar's Storm".

dsco said:
Also, we really don't need another princess_twilight_sparkle_(mlp), especially given that 90% of the time, unless an artist is giving leaders a unique feature, Squirrelflight and Squirrelstar are going to look visually identical.

honestly though, that alias to twilight_sparkle_(mlp) definitely should have been an implication, to me I agree that the change in character design was enough to have a separate character tag, but not enough to have a fully separate character tag (kinda like young_link). I'm pretty sure the only reason it was aliased after the discussion was pretty mixed, was to satisfy people doing data statistics on tag population of character tags. which like, fine, I guess, but an implication would have solved that and also not nuked the tag.

Haven't kept up with the warriors series, but i'm not so sure I like this situation where the direction of the alias can keep flipping based on new developments of the series.

snpthecat said:
Haven't kept up with the warriors series, but i'm not so sure I like this situation where the direction of the alias can keep flipping based on new developments of the series.

This isn't a regular occurrence, don't worry.

snpthecat said:
Haven't kept up with the warriors series, but i'm not so sure I like this situation where the direction of the alias can keep flipping based on new developments of the series.

This is the first time ever that a leader has changed their name back to their warrior name, iirc. Names (now almost) always go in one direcrion

Bumping because we still have two tags for this character and I don't think "spoilers" is generally a reason we consider

cloudpie said:
This is the first time ever that a leader has changed their name back to their warrior name, iirc. Names (now almost) always go in one direcrion

Rowanclaw has as well but he's not a popular character lol

The bulk update request #6370 (forum #389041) has been rejected by @Nimphia.

Rejecting because I realized I can do this in one step with an alias request

wandering_spaniel said:
The bulk update request #6371 is active.

remove alias brambleclaw_(warriors) (95) -> bramblestar_(warriors) (15)
remove implication bramblestar_(warriors) (15) -> warriors_(book_series) (2310)

Reason: Brambleclaw stepped down from leadership so his name is no longer Bramblestar, it's Brambleclaw again

Part 2:
imply brambleclaw_(warriors) -> warriors_(book_series)
alias bramblestar_(warriors) -> brambleclaw_(warriors)

Aaand bumping this one too since the Squirrelstar alias was approved

The bulk update request #6371 (forum #389044) has been approved by @slyroon.

The bulk update request #9533 is active.

create implication brambleclaw_(warriors) (95) -> warriors_(book_series) (2310)
create alias bramblestar_(warriors) (15) -> brambleclaw_(warriors) (95)

Reason: followup

EDIT: The bulk update request #9533 (forum #422767) has been approved by @slyroon.

The bulk update request #9533 (forum #422767) has been approved by @slyroon.