Hey TMDB Devs,

I'm running into a problem where my API is throwing errors because TMDB's episode numbering doesn't match other platforms. This makes it hard to sync data with other APIs like AniDB, TheTVDB, and others. A lot of people are having the same issue, as seen here.

The Issue:

• Some anime get all episodes crammed into one season, while others split them properly.

• Because of this, apps like Emby and Jellyfin can't match files correctly, leading to missing episodes or broken metadata.

• Right now, there's no way to fix this automatically. I either have to rename files manually or patch the API response myself.

• When using TMDB's episode detail api, i get error when i request season/2/episode/1 because the correct episode according to the api is season 1 episode 13

Suggested Feature (Up to You How to Implement It!):

1. Alternate Season Mapping:

-   Add an `alternate` field in the API response so a series can have multiple season mappings based on different platforms. something like this

    ```
    {
      ...current data,
      "seasons", [...],
      "alternate_seasons": [
        {
          "platform": "AniDB",
          "seasons": [{ 
             number:2, 
             episodes:[{
                  number: 1,
                  mapTo: {season:1, episode: 13}
            },...]
           }]
        }
      ]
    }
    ```

1. Make the API Smarter:

-   If I request `season/2/episode/1`, the API should recognize this and return `season/1/episode/13` based on TMDB's numbering.

-   Similar to how [this API endpoint](https://developer.themoviedb.org/reference/tv-episode-details) works, but with built-in remapping.

Why This Helps:

• Fixes API mismatches and prevents errors when syncing data.

• Makes it easier for apps to use TMDB without hacking together custom fixes.

• Keeps everyone happy without breaking existing TMDB rules.

Would love to see something like this added! Appreciate all the hard work you guys do. Thanks!