[Feature Request] Export Presets as Tags eg "[FM] My Preset"

[bonanza465]

I think this would unlock huge value in this add-on.

The interface right now is very powerful, but not very "comfy" for everyday use. This reflects good goals for the add-on! It's a waste to reinvent the wheel by creating a new version of Playnite's already great library interface.

I have had this add-on installed for years, but almost never use it unfortunately, because for me the comfy interface is what I prefer day-to-day.

But - if you created the ability to export a tag into to games based on their preset, that would change everything for me. Now I can filter by a tag in the main Playnite interface, like "[FM] My Preset". I can create a preset in Filter Master named "Dark RPGs", put together a very specific filtering config in Filter Master, and then in filter by that tag in the library.

Suddenly I have access to all the other powerful functions in the library: details vs grid vs list view, sorting, grouping, the basic filters... AND I can create library quick filters using the "[FM] Dark RPGs" tag that I can access in Fullscreen Mode.

Finally, I think for large libraries filtering with a tag in the library UI may perform faster than filtering with a preset in the Filter Master tab.

This could be a checkbox available on each preset: "Export preset to tag across matching games"
I would imagine tag export happening when the Playnite UI moves to another tab (away from the Filter Master tab), so that tag export doesn't happen each time a preset is changed
Depending on how long the tag export takes, a progress bar element would be useful
It would also be ideal to update all preset exports at the end of each library update or batch metadata update
Not sure what to do about single metadata updates, ie making a change to metadata for one game... it probably depends on how long tag export process takes, how many presets are configured to export, etc
Maybe it's possible to monitor which games have been changed by a recent Playnite action, and run tag export for that game/those games only?

I have ~1500 games, and my biggest gripe with Playnite's library system is that I can't negative match. This would fully fix that issue, allowing me to use negative matching in my preset and while still using the main library UI day-to-day.

[bonanza465]

It just occurred to me - this would also allow for "meta-presets". So I can make three presets:

Dark RGPs (based on tags)
Family Friendly (based on tags)
Installed Locally (based on Install Drive)

When all three are exported, I can then create these new "meta-presets" using the tags that were exported:

Dark RPGs - Local Install ([FM] Dark RPGs AND [FM] Installed Locally tags)
Family Friendly - Local Install ([FM] Family Friendly AND [FM] Installed Locally tags)

In this way I can re-use complex presets that I have created as building blocks for other presets, and they will stay up to date as I make changes to the dependencies eg "Installed Locally".

This does introduce potential issues:

In what order are the presets processed for exporting tags so that dependencies work well?
Would there be any potential recursion issues? eg the user accidentally makes "Dark RPGs - Local Install" a required tag within "Dark RPGs" which is its dependency
Right now presets can have duplicate names, that would need to be fixed

[Gerren]

Hi there,

that is a sound idea. Since there is a list of games shown already, it would be easy to mark every game with a tag.

The UI/UX is really rough, especially with the groupings, I know. But that is another topic entirely... I might have an idea... #10

As for the meta filtering, there is no way to stop you, because the resulting tag is basically just another tag. If the user decides to use these for further filtering, that's on them. :)

The only important thing is to communicate the order. As for that, the easy way out would be an alphabetical order. [FM] 01 Dark, [FM] 02 Local, [FM] 03 Dark & Local.

The other way about it would be to let the user establish their own order in the UI, and keep to that. But that brings another layer of confusion.

Or it could be entirely manual, so the order the user runs it, the order it will get evaluated. Absolute control, but no way to automate. Aside from "recording" the order as the user does it and do it the same way...

The scripting (on demand/menu, on import, on start), might be worth looking into.

[bonanza465]

I like the alphabetical order option because it's simple to implement and can still be automated. My initial thought was that adding 01 in front of a tag would make your tag organization ugly, but these tags will all be sorted by [FM] into their own block - so I think actually this is totally fine.

I think the only req from a user perspective would be some short explanation in the interface, eg: "Presets that export tags execute in alphabetical order starting with numbers. If you would like for Preset A to export a tag which is then used as part of Preset B to export its own tag, you can prepend numbers to your preset names to ensure they execute in the correct order ie 01 Preset A and 02 Preset B"