Excellent find and totally reproducible ... thank you for reporting this - I had not seen this. 👍🏻
Now comes the not so great part; RMTV takes exactly what the TVDB API provides.
So these "season" and episode number are 100% copy of what the API provides.
Note: oddly enough, API and website are not always in sync. Like they use different databases (which would make sense, considering how the database are used).
Now ... Maybe the new API (v4) does not have that problem, but there are a few reasons why I haven't implemented this;
- this will take quite a bit of work on my end,
- all users will have to get a subscription API,
- I, as the developer, will have to get a subscription as well,
- TVDB's track record hasn't been the greatest in the last few years since they keeps changing things (this would be the 4th time now for me), unreliable, inconsistent, etc.
I wish I could show this with the old testing environment, but TVDB seems to have removed the v3 test environment in favor of v4. I just tried going there, couldn't find it with Google either. And ... I cannot even test v4 unless I pay a subscription fee.
The subscription is not insanely expensive ($12/yr), but these days we all have to watch how we spend money, I will not get the subscription until I'm 100% convinced I want to implement v4 for RMTV.
I'll pin this one on my desktop - maybe even dig in a little deeper this week.
Again: thanks for reporting!