Greasy Fork

Hello, I don't understand the Auto Restart Live Stream function.
Do I need to have more than one stream open to ensure it continues if the in focus tab ends stream?
Otherwise this is a fantastic script, thanks! :)

You don’t need to keep multiple streams open.
As long as you have a Drops progress running and the inventory page open, the script checks if progress updates.
If there’s no update for a while, it will assume the stream needs to restart and try to reopen it.

However, since Twitch often changes their page structure, these functions sometimes stop working. I usually only notice when someone lets me know, so thanks for pointing it out!

Oh, I didn't realise it was broken, I'm new to this script :)

Just to update, this is now cycling between "inventory" and "campaigns" but not reliably. I've downgraded to v2025.08.06

Thanks for the update! Could you share a bit more detail about what you mean by "not reliably"? For example:
– What exactly happens when it switches between "inventory" and "campaigns"?
– Does it stop responding, get stuck, or show unexpected results?
– How often does it occur, or under what conditions?

Any extra details would help us better understand the issue.

- I must have been distracted when I wrote that sorry. It tends to get stuck on the campaign page more often than not.
- As above.
- I don't monitor it 24/7 but multiple times a day at least.

Thanks for the update! What you’re seeing is expected to some extent — when the page is running in the background, browsers may throttle timers and background tasks. That’s why the cycling between “inventory” and “campaigns” can sometimes get stuck.

The good news is that this doesn’t break the process: if you just leave it running, the next scheduled cycle will continue correctly, and in my testing everything still completes successfully in the end. It’s not perfectly smooth, but it does recover on its own.

It works perfectly with v2025.08.06. What is the purpose of switching between "inventory" and "campaigns" in the latest version?

It might recover after a decent amount of time, but by then the drop may have expired.

In the older version, the whole page would reload, but some users complained that when you had a lot running, it caused noticeable lag.
So in the new version, I switched to refreshing by page switching instead of reloading everything, which makes it more efficient.

That said, I didn’t add strict checks for the refresh state — it just waits a fixed time before switching back to inventory. Combined with browser background execution limits, this sometimes causes it to get stuck or not switch back properly.
I’ll be fixing this to make the refresh handling more stable.