This is a major feature release that adds adaptive sorting to Tag Autocomplete.
In simple terms, the more you use a tag, the higher it will rank, meaning it gets pushed to the top of the list over time. You will have to type less to reach your favorite tags, even if their post count is much lower than other matches for your search term. It also works for all other completion types TAC supports, such as Loras, embeddings and wildcards.
This is a big change in how Tag Autocomplete shows its results, which is why it was "in beta" for quite a while. While I have used it for months already without issue, there might still be some oversights, so if you happen to encounter any problems with it, feel free to open an issue.
🖼️ Some example images of the feature in use (click to expand)
A tag sorted higher due to frequency will be marked with the ✨ symbol. It can also be reset at any time:
"solo" ranks higher than "sole_female"/"1girl":
"standing" ranks first despite a much lower post count:
Also works for embeddings:
And for lora:
New settings:
New settings:
As usual, the feature is very customizable through a number of settings (also shown in the example images):
Locally record tag usage and sort frequent tags higher- Turns the feature on/off
Function to use for frequency sorting- This determines how strong the influence of usage count on the sort order should be.
Minimum number of uses for a tag to be considered frequent- As the name suggests, usages lower than this will just be ignored.
Maximum days since last use for a tag to be considered frequent- This will not consider tags you haven't used for a long time to prevent having to manually reset them. It will continue as normal from the old count after you first use it again.
Maximum number of recommended tags- Caps the maximum number of recommendations at the set value to prevent them from completely displacing normal results (especially relevant for Extra Networks, as they have no inherent post count).
Frequency sorting matches aliases for frequent tags- Normally, aliases are ignored during frequency sorting since they would often get in the way of the wanted result (due to the main tag the alias links to ranking higher again, e.g. with the "solo" example).