The bulk update request #45854 (forum #377345) has been approved by @nonamethanks.
Posted under Tags
The bulk update request #45854 (forum #377345) has been approved by @nonamethanks.
The bulk update request #45863 (forum #377362) has been approved by @nonamethanks.
Ahwii said:
1. recently LeBlanc underwent a visual update, and her new design (post #9047971) is now pretty much the same as her Arcane version, Arcane LeBlanc. since this is her default design now, is there still a need for the arcane leblanc tag?
How recently? If 99% of the posts have that design there's no point in an extra tag for it. But if it's more like half, or even less, then yes, it should be tagged. Given that leblanc_(legacy) is about half of the tag, I'd say it's fine to have the other tag as well. But it should probably not be called Arcane LeBlanc anymore, unless that's what it's called in-game as well.
2. also related to leblanc, i went ahead and tagged the posts with her old design (pic) as LeBlanc (legacy), similar to Akali (legacy) and Viktor (legacy) (post #1628319). however, her design in Legends of Runeterra (pic 1, pic 2) is a bit different from her legacy design, namely her clothes and hair. does this warrant a separate tag? some posts such as post #6680767 and post #6115363 are closer to her runeterra design than her legacy one
Sure.
3. usually skin chromas (alternate color versions) don't have separate splash arts from their base skin, but certain chromas have special splash arts only obtainable on the chinese server (example: post #9452910, post #8812362, post #7683227). should they be separate from the base skins (just like ahriversary k/da ahri is currently) or tagged under them?
We already have multiple k/da skins of the same character, like Prestige K/Da Ahri or K/Da All Out Ahri, so these can just be under the parent too.
The bulk update request #45967 (forum #377781) has been approved by @nonamethanks.
The bulk update request #46095 (forum #378400) has been approved by @nonamethanks.
BUR #46303 has been approved by @evazion.
create implication ahri_(fox) -> ahri_(league_of_legends)
create implication spirit_blossom_springs_ahri -> ahri_(league_of_legends)
create implication prestige_k/da_akali -> akali
create implication inkshadow_aurelion_sol -> aurelion_sol_(league_of_legends)
create implication storm_dragon_aurelion_sol -> aurelion_sol_(league_of_legends)
create implication prestige_select_crystal_rose_caitlyn -> caitlyn_(league_of_legends)
create implication arcana_camille -> camille_(league_of_legends)
create implication coven_camille -> camille_(league_of_legends)
create implication prestige_winterblessed_camille -> camille_(league_of_legends)
create implication winterblessed_camille -> camille_(league_of_legends)
create implication masque_of_the_black_rose_elise -> elise_(league_of_legends)
create implication lovestruck_ekko -> ekko_(league_of_legends)
create implication nightbringer_evelynn -> evelynn_(league_of_legends)
create implication winterblessed_hwei -> hwei_(league_of_legends)
create implication crystal_rose_jarvan_iv -> jarvan_iv_(league_of_legends)
create implication arcane_fractured_jinx -> jinx_(league_of_legends)
create implication lovestruck_jinx -> jinx_(league_of_legends)
create implication crystal_rose_kai'sa -> kai'sa
create implication heavenscale_kai'sa -> kai'sa
create implication prestige_k/da_kai'sa -> kai'sa
create implication soul_fighter_kalista -> kalista
create implication spirit_blossom_kayle -> kayle_(league_of_legends)
create implication snow_moon_kayn -> kayn_(league_of_legends)
create implication prestige_porcelain_kindred -> kindred_(league_of_legends)
create implication debonair_leblanc -> leblanc_(league_of_legends)
create implication shan_hai_scrolls_lillia -> lillia_(league_of_legends)
create implication prestige_spirit_blossom_lux -> lux_(league_of_legends)
create implication pool_party_malphite -> malphite
create implication shamrock_malphite -> malphite
create implication debonair_malzahar -> malzahar
create implication faerie_court_milio -> milio_(league_of_legends)
create implication prestige_star_guardian_neeko -> neeko_(league_of_legends)
create implication redeemed_star_guardian_rakan -> rakan_(league_of_legends)
create implication battle_dove_seraphine -> seraphine_(league_of_legends)
create implication supreme_cell_sett -> sett_(league_of_legends)
create implication heavenscale_smolder -> smolder_(league_of_legends)
create implication victorious_sona -> sona_(league_of_legends)
create implication prestige_chosen_of_the_wolf_swain -> swain_(league_of_legends)
create implication winterblessed_sylas -> sylas_(league_of_legends)
create implication snow_moon_varus -> varus
create implication crystal_rose_vayne -> vayne_(league_of_legends)
create implication arcane_savior_viktor -> viktor_(league_of_legends)
create implication viktor_(legacy) -> viktor_(league_of_legends)
create implication redeemed_star_guardian_xayah -> xayah
create implication battle_academia_yone -> yone_(league_of_legends)
create implication high_noon_yone -> yone_(league_of_legends)
create implication cyber_cat_yuumi -> yuumi_(league_of_legends)
create implication supreme_cell_zed -> zed_(league_of_legends)
create implication chromacrash_zeri -> zeri_(league_of_legends)
create implication odyssey_ziggs -> ziggs
create implication prestige_arcanist_zoe -> zoe_(league_of_legends)
i hope it's okay to use this thread as a general league bur thread since it might clog the forum if i make a bunch of mini threads for non-skin stuff
pretty sure these are all the non-implied league skin tags remaining (+ some alt forms like ahri_(fox) and viktor_(legacy)), might've missed a couple
i haven't actually watched arcane so i need someone that's watched it to pitch in here: how should the arcane_fractured_jinx tag be handled? the skin has 3 forms in game (image video). most of the posts i see are the form with the hood. one of the forms (rightmost in the image) should be powder_(alternate_timeline)_(arcane) but i'm not sure how to go about the other two forms since, again, i haven't watched the show
for arcane_savior_viktor, the skin in game is post #8658327, but there are some posts like post #8900586 and post #8900987 tagged under it that are of viktor but not the savior form. not sure how to handle these
For the Jinx part, in the image you linked, the third form is the Alternate Universe one, the second form is the real universe one, the first one is neither.
Personally, I think the granularity isn't that important, and it would be fine to put all three versions under one skin. People wouldn't know the names of each of the forms, only the name of the skin itself, so they would have to google the names of the forms.
In an ideal world, every form would get it's own tag, since they are visually distinct, but I think that's not realistic.
It could also depend on how skins like Dj Sona and spirit_guard_udyr, Elementalist Lux are treated, since they have separate, very distinct forms too.
For the Viktor part, post #8900586 should either be tagged with just Viktor (his new in-game look, which is post #8545017), or with some new tag, since that's what Viktor looks like in the astral plane/magic plane, when he captures Jayce (though I think a separate tag is not needed, and we could just keep both forms under one tag).
post #8900987 is neither form, if anything, it's closer to his still-human form, a tag that we don't have, and could use for a few posts, like post #9727602 (his face is still normal, but his body already has hextech influence on it, in various stages).
BUR #47759 has been approved by @evazion.
create alias ambessa_medarda -> ambessa_(league_of_legends)
create alias mel_medarda -> mel_(league_of_legends)
Only these two characters have both their first and last names in their tags. I think very few people know their last names, especially if they haven’t watched Arcane.
The bulk update request #46303 (forum #379342) has been approved by @evazion.
The bulk update request #47759 (forum #387696) has been approved by @evazion.
BUR #52322 has been approved by @nonamethanks.
create implication drx_akali -> akali
create implication arcana_aurora -> aurora_(league_of_legends)
create implication prestige_spirit_blossom_springs_aphelios -> aphelios
create implication high_noon_evelynn -> evelynn_(league_of_legends)
create implication lovestruck_ezreal -> ezreal
create implication battle_queen_gwen -> gwen_(league_of_legends)
create implication rain_shepherd_gwen -> gwen_(league_of_legends)
create implication high_noon_irelia -> irelia
create implication spirit_blossom_irelia -> irelia
create implication empyrean_lux -> lux_(league_of_legends)
create implication faerie_court_lux -> lux_(league_of_legends)
create implication panda_pal_lux -> lux_(league_of_legends)
create implication lovestruck_lux -> lux_(league_of_legends)
create implication cosmic_exile_riven -> riven_(league_of_legends)
create implication dumpling_darlings_seraphine -> seraphine_(league_of_legends)
create implication spirit_blossom_springs_sona -> sona_(league_of_legends)
create implication flora_fatalis_soraka -> soraka_(league_of_legends)
create implication battle_sheep_soraka -> soraka_(league_of_legends)
create implication dumpling_darlings_syndra -> syndra
create implication crystalis_motus_taliyah -> taliyah
create implication battle_academia_xayah -> xayah
create implication calligraphia_xayah -> xayah
create implication spirit_blossom_springs_yunara -> yunara_(league_of_legends)
it's been a while
is there a way to automate these implication requests, like hsr, umamusume and other copyrights with a lot of skins? there's new league skins coming out every patch, and there's still a lot that haven't been implied or don't have posts, it's a bit hard to keep up with. i understand if not though
Updated by user 881800
League of Legends skins follow a different schema from the rest of our skin tags (skin_character instead of character_skin_(copyright)), so no, it can't be automated in the same way as the other series.
Basically, there's no way to search for all of the random character skins in a simple way, so there's no way for the bot to know which tags are missing implications.
The bulk update request #52322 (forum #405536) has been approved by @nonamethanks.
BUR #53212 has been approved by @evazion.
create implication blood_moon_diana -> diana_(league_of_legends)
create implication winterblessed_diana -> diana_(league_of_legends)
create implication sentinel_diana -> diana_(league_of_legends)
create implication battle_queen_diana -> diana_(league_of_legends)
create implication firecracker_diana -> diana_(league_of_legends)
Missing Diana implications.
Updated by LuxuryRay
BUR #53213 has been approved by @evazion.
create implication championship_ashe -> ashe_(league_of_legends)
create implication spirit_blossom_ashe -> ashe_(league_of_legends)
create implication crystalis_motus_ashe -> ashe_(league_of_legends)
create implication drx_ashe -> ashe_(league_of_legends)
Missing Ashe implications.
BUR #53214 has been approved by @evazion.
create implication prestige_immortal_journey_sona -> sona_(league_of_legends)
Missing Sona implication.
BUR #53217 has been approved by @evazion.
create implication lunar_eclipse_aatrox -> aatrox
create implication drx_aatrox -> aatrox
create implication k/da_unbound_ahri -> ahri_(league_of_legends)
create implication project:_ahri -> ahri_(league_of_legends)
create implication heartseeker_ahri -> ahri_(league_of_legends)
create implication project:_akali -> akali
create implication headhunter_akali -> akali
create implication street_demons_briar -> briar_(league_of_legends)
create implication sacred_sword_janna -> janna_(league_of_legends)
create implication heavenscale_janna -> janna_(league_of_legends)
create implication prestige_masque_of_the_black_rose_katarina -> katarina_(league_of_legends)
create implication faerie_court_katarina -> katarina_(league_of_legends)
create implication dawnbringer_karma -> karma_(league_of_legends)
Missing Aatrox, Ahri, Akali, Briar, Janna, Katarina, Karma implications.
The bulk update request #53212 (forum #412655) has been approved by @evazion.
The bulk update request #53213 (forum #412656) has been approved by @evazion.
The bulk update request #53214 (forum #412657) has been approved by @evazion.
