[pyrodex]

UPDATE: I was curious if the SAME machine with the same KODI settings as mentioned above would exhibit the problem with an NFS source and LOCALDB so I was able to try it out and not reproduce the issue. This led me to thinking maybe it was something with MySQL so I attempted Kodi to use a new MySQL name instead of the default and basically have a new Database. I then tested the same test case with a new MySQL DB of a custom name and didn't have the problem. Reverted back to my MySQL DB and had the problem, so I wiped the DB from the MySQL server and had Kodi recreate it with no issues. I didn't lose much since I purge my watched shows but not sure if this was just something maybe carried over recently but I am still at a loss for words.

Sounds like a corrupt database, or incorrect metadata - did you check the runtime for S01E04 to make sure it was correct and not ridiculously short? Maybe Kodi is calculating 90% of the runtime metadata field and if that field is massively incorrect then Kodi might think that 10 minutes is 90% of the run time and bump the playcount. If you are using NFOs with embedded streamdetails then check them to make sure the calculated runtime is correct.

I've just checked with 1008 and a MySQL db and Kodi is spot on when setting the playcount - an episode that is 1:01:43 (3703 seconds) long bumps the playcount when stopping after 00:55:32 (3332 seconds), which is 90%, and not before.

Not to beat a dead horse but I think I found the cause of this and it wasn't a corrupt DB issue. On a few select clients I have video cache settings to help with skipping video when background disk IO is heavy on the NAS or even on remote VPN clients (for when I travel). I used http://kodi.wiki/view/HOW-TO%3AModify_the_video_cache as the model and have Example 1 on my MAC Laptop for when I travel and Example 4 on my main RPI3s.

I think Kodi is caching the entire file, which is expected behavior, but once the cache is there it is causing a playcount to be incremented even though the show isn't over. I can reproduce this behavior on a system with a fresh Kodi directory with advanced settings for the MySQL AND caching, without caching I can't reproduce this issue.