[Bug]: Quickstart overwrites Rotten Tomatoes rating operation sources

[santastabber]

Describe the bug

Quickstart appears to overwrite or regenerate Rotten Tomatoes rating operation sources when revisiting the Library/Overlay configuration UI.

I configured a ratings-only overlay setup where the poster badges are:

• IMDb rating badge
• Rotten Tomatoes critic/tomato badge
• Rotten Tomatoes audience/popcorn badge

My Plex movie library already uses Rotten Tomatoes as its rating source, so the desired operation sources are Plex-backed:

operations:
  mass_critic_rating_update:
  - plex_tomatoes
  mass_audience_rating_update:
  - plex_tomatoesaudience
  mass_user_rating_update:
  - imdb

However, after revisiting the Quickstart Library/Overlay section, the generated config is changed back to MDBList-backed Rotten Tomatoes sources:

operations:
  mass_critic_rating_update:
  - mdb_tomatoes
  mass_audience_rating_update:
  - mdb_tomatoesaudience
  mass_user_rating_update:
  - imdb

This causes incorrect overlays in my setup because MDBList is not returning RT audience scores for these items. Kometa logs show:

No mdb_tomatoesaudience Audience Rating Found

Because the audience field is not updated, the overlay can retain stale values from a previous run. In practice, the RT critic and RT audience badges end up showing the same number on posters.

The config itself is valid, and Kometa supports both source families:

• mdb_tomatoes
• mdb_tomatoesaudience
• plex_tomatoes
• plex_tomatoesaudience

The issue seems to be that Quickstart assumes RT tomato/popcorn badge images should use MDBList sources, rather than preserving the user's selected/imported operation source.

Relevant source pointer from Quickstart:

const RATING_SOURCE_MAP = {
  rt_tomato: { critic: 'mdb_tomatoes', audience: 'mdb_tomatoesaudience', user: 'mdb_tomatoes' },
  rt_popcorn: { any: 'mdb_tomatoesaudience' }
}

This is in:

static/local-js/overlayHandler.js

Expected behavior: Quickstart should preserve manually selected/imported operation sources such as plex_tomatoes and plex_tomatoesaudience, or expose source selectors separately from badge image selectors.

---

Quickstart should preserve the Plex-backed operation sources:

operations:
  mass_critic_rating_update:
  - plex_tomatoes
  mass_audience_rating_update:
  - plex_tomatoesaudience
  mass_user_rating_update:
  - imdb

The RT badge image selection should not force MDBList as the rating source.

Steps to reproduce

1. In Plex, use a movie library with Ratings Source set to Rotten Tomatoes.
2. In Quickstart, configure a movie library with rating overlays enabled.
3. Configure the rating overlay badges as:

   overlay_files:
   - default: ratings
     template_variables:
       rating1: user
       rating1_image: imdb
       rating2: critic
       rating2_image: rt_tomato
       rating3: audience
       rating3_image: rt_popcorn
   

4. Configure or manually edit the generated config so operations use Plex-backed Rotten Tomatoes sources:

   operations:
     mass_critic_rating_update:
     - plex_tomatoes
     mass_audience_rating_update:
     - plex_tomatoesaudience
     mass_user_rating_update:
     - imdb
   

5. Go back into the Quickstart Library/Overlay section.
6. Save/regenerate/run the config from Quickstart.
7. Inspect the generated config.

Actual result:

Quickstart changes/regenerates the RT operation sources to MDBList-backed values:

operations:
  mass_critic_rating_update:
  - mdb_tomatoes
  mass_audience_rating_update:
  - mdb_tomatoesaudience
  mass_user_rating_update:
  - imdb

Kometa then logs missing MDBList RT audience values:

No mdb_tomatoesaudience Audience Rating Found

The audience field is not updated, and the RT critic/audience overlays can display identical or stale values.

Expected result:

Config source

Fresh walkthrough (Quickstart)

How are you running Quickstart?

Unraid

Support Info Output

N/A

Relevant logs (optional)

Checklist

• I have searched existing issues and this bug has not already been reported
• I can reproduce this issue consistently
• I included the full Support Info output

[bullmoose20]

Thanks for reporting. We will investigate