Repository navigation
v2.3.0 — keywords as a preference, and a tag threshold you can set
Three changes to what a keyword-tagged library writes, from a merging anime library in
use. Upgrading is a pull.
useKeywords is a preference now, not an ultimatum
It meant keywords instead of genres, and nothing at all when the source had no keyword
for that title. AniList counts only the tags its community agrees on strongly enough,
and a great many TMDB entries carry no keyword, so each source went quiet on a large
share of titles. Where both did, the title was tagged with nothing and recorded as a
failure under backoff.
It now reads as a preference: the finer vocabulary where a source has one, that
source's own genres where it does not. A merging library writes something for every
title again, from both of its sources.
AniList's tag threshold is yours to set
AniList shows a tag with the share of its community that agreed with it. Only tags at
70% or more were written, a figure hard-coded with nothing anywhere to say so — which is
why a tag plainly visible on AniList's own page could fail to reach Plex.
ANILIST_TAG_RANK="20" # default 70Lower it to take much more of what AniList knows, and accept the noise that comes with
it. It joins the settings fingerprint when it is not the default, so changing it re-tags
the libraries that read AniList.
A failure message that pointed at the wrong thing
"returned no usable genres (all filtered by your ignore rules?)" was shown even when the
rules were innocent. When they really are the cause it now says so as a fact, with how
many names they dropped. To see what a source returns for one title without running a
pass:
plex-auto-genres query "<title>" --type anime --keywordsAlso
The example config and several docstrings use invented names for their examples. Two
genre posters nothing referred to are gone; a collection with no poster file is
reported as missing and skipped, as always.