Rewatches

Preserve separate watch events for repeated plays.

Rewatches keep repeated plays as separate history events.

Normal history stores watched state and the latest watched time. Rewatches preserve every individual play.

For example, three plays of one movie remain three history events.

Supported providers

Rewatches currently work with:

1. Trakt
2. SIMKL
3. PublicMetaDB
4. Floppy
5. MDBList
6. Scrob
7. CW Tracker

Each side of the connection must support the required capability.

For a one-way connection, the source must read rewatch events. The target must read and write them.

For a two-way connection, both providers must read and write rewatch events.

Normal history synchronization remains available without this support.

Enable Rewatches

Configure Rewatches for each connection.

1. Open the connection.
2. Select History.
3. Enable History.
4. Enable Rewatches.
5. Save the connection.

CrossWatch then compares individual watch events. It no longer treats all plays as one history entry.

Each play keeps its own watched timestamp. Supported providers preserve repeated watches during synchronization.

SIMKL requirements

SIMKL supports Rewatches with Pro and VIP accounts.

Without either account level, SIMKL cannot synchronize Rewatches.

When to enable it

Enable Rewatches when repeated watches should remain in your tracker history.

Use normal History when watched state alone is enough.

Rewatches affect History only. They do not affect Watchlist, Ratings, or Playback Progress.