Shared watched status with independent resume — supported plugin API?

[daddystorm 0]

Separate normal/extended items need shared watched status but independent resume positions.

Is there a supported atomic update of Played only, or a conditional save that detects concurrent changes?

In isolated tests on 4.10.0.40 and 4.11.0.6, posting only {"Played":true} to /Users/{UserId}/Items/{ItemId}/UserData reset the position from 20 minutes to zero. SDK saves write the full history record, and UserDataSaved fires after persistence.

This is an API guidance question, not a claim of an Emby bug. We want to avoid private hooks or direct database writes.

[ebr 16933]

21 hours ago, daddystorm said:

Separate normal/extended items need shared watched status but independent resume positions

Hi.  That doesn't really make sense... but what are you calling "separate normal/extended items"?

Both these values are stored in the user data which is keyed by provider ID if there.

[daddystorm 0]

Thanks. I mean separate normal and Extended/Superfan cuts of the same episode.

The desired behaviour is:

• Finishing either cut marks both as watched, because they represent the same episode.
• Each cut retains its own resume position, because added scenes make the timestamps different.

We understand that sharing the user-data key shares both values. That is precisely what we want to avoid.

Is there a supported plugin API to update only Played on the other item, without overwriting its resume position or other user-data fields—even if Emby saves playback progress concurrently?

[HawkXP71 133]

Its not just an episodes issue.

I have seen the same issue Director's cut versions.  The resume location is different per version of the media,

[ebr 16933]

On 10/12/2026 at 8:22 AM, daddystorm said:

Is there a supported plugin API to update only Played on the other item, without overwriting its resume position or other user-data fields—even if Emby saves playback progress concurrently?

No, as there is only one record.