Kavita+ Paused/Dropped Scrobbling

[majora2007]

Currently Kavita+ only scrobbles reading/completed events. However, Kavita has a knowledge of when the last time a Series was read.

The idea is for each scrobble eligible user to configure 2 different months and for a scrobble status to be applied from it. This feature is optional per user. Each field may be configured or not.

The first is the number of months since last reading activity on a series for which Kavita should scrobble "PAUSED".

The second is the number of months since last reading activity on a series for which Kavita should scrobble "DROPPED".

Kavita+ will check (with AniList) before saving if the series' last progress is different than what Kavita is reporting.

[scare376]

I would say 3-4 months for paused would probably be fine. That should account for the series that release every other month. I'd rather have dropped as a toggle though. I have series I haven't touched for over a year but haven't dropped it. Just waiting for chapters to build up.
Also how would this affect releasing series. I have a novel series that releases at a rate of about a volume per year.

Edit: I just realized you mentioned this would be customizable x.x . That would be perfect imo. Still not sure about automating dropped status though

[majora2007]

This is quite tricky. The idea is to let the user a) opt-into it and b) configure the dates themselves.

I could see how some series could have this issue, especially if they are releasing yearly. I have a few that release every 8 months for example.

I'm honestly not sure how to handle this use case. For me personally, I wouldn't mind it moving to Paused then back to Active when I read it next, because if I don't, then it's either Paused or Dropped. The user could also do only for Paused and nothing for Dropped, thus not having to worry about that.

[Roshri]

this could be useful as an opt-in
I have series on my "Reading" list that I havent touched in years, but because that's how I can keep track of stuff I have to get back to.

[majora2007]

Updated the description based a bit on comments to make it clear that it's opt-in per user on the server and each field can be configured independently.