Greasy Fork

Nice script. It works well except videos are always playing in 4K even though I changed storage value to,

{
"targetRes": "hd1080"
}

I'm using it in Violentmonkey in Brave browser with the latest version of the script released 1 Hour ago at the time of me writing this. Is it a bug or am I doing something wrong?

Hey, the value of "overwriteStoredSettings" is set to false by default so I don't wipe your saved settings after each update. Changing that to true should allow you to modify your settings from code again. It's really an unnatural leftover artifact from adisib that I might remedy soon.

The artifact has been remedied. An UI has been added for quality selection that bypasses the need to edit the script directly.

Hello again, after your previous changes I never had an issue with your script. But currently I'm running the script in AdGuard for desktop and the way to store userscript settings seems to be a bit different in this product.
This is how it looks in AdGuard for Desktop's storage option by default once I visit YouTube.

{"scriptInfo":"[O;{\"version\":null}"}

If I copy-paste this Violentmonkey settings into AdGuard,

{

"scriptInfo": {

"version": "2025.02.11"

},

"settings": {

"targetResolution": "hd1080",

"expandMenu": false,

"debug": false

}

}


Then I'm getting this error in AdGuard saying,
"cannot deserialized edited GM properties."

What can I do about this? Can you please help?

I tried to look into this but could neither find a way to run nor to debug the script through adguard. What is your current browser and system that you use? If I can't replicate your issue then I unfortunately cannot provide compatibility with AdGuard as I can't get AdGuard to recognize its own browser extension.

Alright I've pushed an updated that may or may not solve your problem. Try that first.

Alright I've pushed an updated that may or may not solve your problem. Try that first.

Thank you. Now it's working. Settings are now stored properly, and I am able to change the resolution to my preferred 1080p.
"AdGuard for Desktop" is a separate product that doesn't require extension to function. It's a paid product but they provide a 15 day trial period.
This is how it looks in AdGuard for Desktop.
https://postimg.cc/YhtkGSk7
In the userscript's Compatibility Status section here in greasyfork, you may add AdGuard for Desktop as a program that is compatible with your script. You could also check it out in a VM to see if there's any other compatibility issue that I might have missed.

I am aware what "AdGuard for Desktop" but it wouldn't execute any scripts for me so I thought to try it with their assistant extension that they recommend. Never ended up working. Regardless, thank you for reporting the working status.

The new update (2025.09.05) probably fixes this issue completely. If you are able to give feedback on this it would be great.

Hi! It seems the last update actually broke it for AdGuard for Windows. Since your previous fix in February, I never had any issues with the extension again but now it's loading 4K video again by default even though my setting is 1080p. This is how the setting look like, {"settings":"[O;{\"targetResolution\":\"hd1080\",\"expandMenu\":false,\"debug\":false}"}

The new version moved the script's settings menu into YouTube's existing quality selection menu. It no longer saves anything into AdGuard so settings written there would no longer have any effect.

The new update uses the default 4k value as it no longer reads from your previous saved stuff from the older versions. Can you try to see if you can find the new menu and see if that works for you?

Ok, I see. Yeah, I see the menu and it seems to be working as expected.

Nice to hear that it's working. Thanks for checking.

Hello again! On negative thing about the new approach is that it seems to be cookie dependent. In browser's private/incognito window it doesn't respect my quality settings. It plays videos in the default 4K.

I have noticed the same thing, but this new approach was taken for compatibility reasons. I'll look into whether a hybrid approach is possible without breaking compatibility. My initial guess is leaning pessimistic however.

I think I got the hybrid approach to work. Try the new (v2025.09.27) version, it should hopefully solve you issue.

Thanks for the update. The hybrid approach now works perfectly.