Skip to main content

Ability to Build Playlist Templates That Can Be Added Like the Auto_Generated Child Playlists

šŸ“‹ Summary

Add the ability to create reusable Playlist Templates that can be applied when adding a new Playlist or when generating Auto-Generated Child Playlists. These templates would define preset values (e.g., Name patterns, Sort Title rules, Auto-Populate filters) and allow dynamic variables like parent Platform to be used automatically.


šŸŽÆ Feature Overview

This feature introduces a Playlist Template System enabling users to define templates that can later be instantiated across Platforms, Categories, or Playlists.

A template could include:

  • Name format (e.g., ā€œWant to Play – {Platform}ā€)

  • Sort Title format

  • Auto-Populate Rules, including:

    • Platform = Parent platform

    • Progress = specific status

    • Date added rules

    • Missing media rules

    • Broken status

  • Optional default artwork for playlists

  • Optional placement rules (e.g., always create under the platform node)

Templates would appear as selectable options in:

  • Add New Playlist

  • Auto-Generate Child Playlists

  • Right-click Platform → Add Auto-Generated Playlist

This mirrors how LaunchBox already creates auto-generated playlists such as Favorites, but expands it so users can define their own reusable structures.


šŸ›  Example Use Cases

āœ”ļø Platform-wide Progress Playlists

A user defines two templates:

  • Want to Play

    • Auto-Populate: Progress = Want to Play

    • Platform = Parent Platform

  • In Progress

    • Auto-Populate: Progress = In Progress

    • Platform = Parent Platform

Instead of manually creating these under every platform, the user can generate them instantly using templates.


āœ”ļø Maintenance Templates

Users could create templates for:

  • Recently Added

    • Auto-Populate: Added within last 30 days

  • Missing Media

    • Auto-Populate: Missing Box Front OR Missing Video

  • Broken Games

    • Auto-Populate: Broken = True


āœ”ļø Collection Expansion

When adding a new Platform, the user can instantly generate:

  • Want to Play

  • In Progress

  • Favorites by Genre

  • Recently Played

  • Series Playlists

All based on their personal template collection.


šŸ“¦ Benefits

  • Huge time-saver for users who organize their collection with consistent structures.

  • Reduces repetitive manual setup when adding new Platforms.

  • Makes Auto-Generated Playlists far more customizable and powerful.

  • Provides a scalable system that grows with large collections.

  • Ideal for workflows that rely heavily on Progress, Metadata cleanliness, or Playlist curation.

Status: Open To Community3 comments

Log in to comment and vote

Comments3

  • AstroBob

    Team•

    Dec 11, 2025

    Hi there, I’ve fleshed this out, but that said I just thought, do you think the following request would also solve this?

    Dynamic ā€œCurrent Platform/Categoryā€ Filter for Auto-Populated Playlists

    With that implemented, you could create a single platform and then have it show up under every platform.

    If you agree, i’ll probably merge this request into that one, since the Current filter would enable this

    • VodkaParalyzer

      •

      Dec 12, 2025

      Possibly. As long as you can have an easy way to view curated collections of games, in different locations, without having to create each playlist manually. I like having the abillity to quickly navigate my way through BigBox to what I feel like playing that day. Arcade games that I’ve flagged that I want to try? No problem. N64 games that I’m in the middle of playing? Easy. C64 games that I recently added? Simple. A couple clicks on the controller, and you’re there. And you can have a custom video or theme kick in to make everything flashy and pretty like :)

  • VodkaParalyzer

    •

    Dec 11, 2025

    Ability to Build Playlist Templates That Can Be Added Like the Auto_Generated Child Playlists

    Add ability to define Playlist Templates that can then be created as part of the Add Playlist or the Auto-Generated Child Playlists dialogs. Envisioning defining a set of values for things like Name, Sort Title, and Auto-Populate rules. Having the ability to use values that come from the parent node the Playlist is being added to, like the Platform. Similar to how you can already auto-generate a ā€œFavoriteā€ Playlist.

    I like having ā€œWant to Playā€ and ā€œIn Progressā€ as two Playlists under each Platform. Having the ability to quickly generate these via a template, that has rules for Platform and where Progress is this value or that value, would have been a great time saver while setting these up. But in the future, I could see wanting to have new Playlists under each Platform for things like ā€œRecently Addedā€, ā€œBrokenā€, ā€œMissing Mediaā€, etc.