But this method also doesn't have a play count parameter. The value is read from the DB and always incremented. How can I know if a MI is unwatched (or set it as unwatched) as the play count is every time increased.the play count is handled server side here.
I can understand that a play count attribute can be useful in some cases, but if it's never gets reseted it can't be used to know the watched state.
Not that I know, could you please point me to an example? I see that each time I restart the client the play count is the "real" one.My guess is you are not reloading the user data after changing the play count?
Yes, I noticed. Does reloading the user data have such a performance impact? Or are they other reasons why it' can't be reloaded each time the watched action is called?As you can see there is a little "cheat" for KEY_PLAY_PERCENTAGE to avoid reloading the user data by just changing the values in the already loaded user data.