Topic: Consistent league of legends character names BUR

Posted under Tag Alias and Implication Suggestions

The bulk update request #7454 is pending approval.

create alias veigar (994) -> veigar_(disambiguation) (0) # duplicate of has blocking transitive relationships, cannot be applied through bur
create alias renekton (853) -> renekton_(disambiguation) (0)
create alias soraka (1330) -> soraka_(disambiguation) (0) # duplicate of has blocking transitive relationships, cannot be applied through bur
create alias volibear (747) -> volibear_(disambiguation) (0) # duplicate of has blocking transitive relationships, cannot be applied through bur
create alias shyvana (143) -> shyvana_(disambiguation) (0)
create alias trundle (59) -> trundle_(disambiguation) (0)
create alias thresh (332) -> thresh_(disambiguation) (0)
create alias ziggs (3) -> ziggs_(disambiguation) (0)
create implication veigar_(lol) (0) -> league_of_legends (31281)
create implication renekton_(lol) (0) -> league_of_legends (31281)
create implication soraka_(lol) (0) -> league_of_legends (31281)
create implication volibear_(lol) (3) -> league_of_legends (31281)
create implication shyvana_(lol) (0) -> league_of_legends (31281)
create implication trundle_(lol) (13) -> league_of_legends (31281)
create implication thresh_(lol) (0) -> league_of_legends (31281)
create implication ziggs_(lol) (330) -> league_of_legends (31281)

Reason: The majority of League of legend characters are named with the suffix *_(lol), these (and maybe a few I missed) still uses only their name and not the new format.

The bulk update request #7455 is pending approval.

mass update veigar -> veigar_(lol)
mass update renekton -> renekton_(lol)
mass update soraka -> soraka_(lol)
mass update volibear -> volibear_(lol)
mass update shyvana -> shyvana_(lol)
mass update trundle -> trundle_(lol)
mass update thresh -> thresh_(lol)
mass update ziggs -> ziggs_(lol)
remove implication volibear (747) -> league_of_legends (31281)
remove implication soraka (1330) -> league_of_legends (31281)
remove implication veigar (994) -> league_of_legends (31281)

Reason: Updates the current (old) names to the new ones with suffixes.

The suffix is for ambiguous names, a couple are not ambiguous and there are no other tags using/containing them:
*shyvana*
*volibear*

The rest seem okay, but your first BUR is gonna get blocked since the marked antecedent tags have implications

Updated

snpthecat said:
The suffix is for ambiguous names, a couple are not ambiguous and there are no other tags using/containing them:
*shyvana*
*volibear*

Not entirely sure I understand, there are plenty of names in league that would be considered non-ambiguous that still has the suffix (on e621).
Examples:
vel'koz_(lol)
vex_(lol)

snpthecat said:
The rest seem okay, but your first BUR is gonna get blocked since the marked antecedent tags have implications

I assume we could append unimply(s)? Or is it more complicated than that?

Updated

Watsit

Privileged

rakustrike said:
Not entirely sure I understand, there are plenty of names in league that would be considered non-ambiguous that still has the suffix (on e621).
Examples:
vel'koz_(lol)
vex_(lol)

Vex isn't unique to League of Legends. Some names can be debated on whether they're unique enough, and others may have a suffix just because people started tagging it with a suffix and no one bothered to remove it. But generally, a name that's unique enough shouldn't get one.

watsit said:
Vex isn't unique to League of Legends. Some names can be debated on whether they're unique enough, and others may have a suffix just because people started tagging it with a suffix and no one bothered to remove it. But generally, a name that's unique enough shouldn't get one.

Fair point about vex, made a quick assumption - I got no problem removing shyvana/volibear (or other names that are unique/non-ambiguous) mind you, but given that they would be the outlier means then we should either clean all unique league names up (which is fine) or keep up with adding suffix to every league character essentially.

rakustrike said:

I assume we could append unimply(s)? Or is it more complicated than that?

Put the unimplications in the second BUR, which should be accepted before the first

snpthecat said:
Put the unimplications in the second BUR, which should be accepted before the first

I'll try and do that later in the day, sleep calls!
Also just for future precaution should update BURs come before or after alias+imply BURS?

rakustrike said:
I'll try and do that later in the day, sleep calls!
Also just for future precaution should update BURs come before or after alias+imply BURS?

Update before alias if the destinations are to different tags, if it's to the same tag, update is unnecessary

  • 1