Most questions are answered faster by the built-in tool than by guessing. Open the extension popup and click Diagnostics, then pick your YouTube tab. It reports which layers are working on that page.
chrome://extensions and then reload
your YouTube tab with Ctrl+Shift+R.
Run Diagnostics and look at these three lines:
budama kaydı or ytInitialPlayerResponse. If it
says couldn't find a player response, reload the page.Open Settings → Anti-detection and turn it on, then reload the page. This option is off by default — we prefer to show you what we do rather than hide it.
Note: after changing this setting you must reload the page. Hooks that are already installed cannot be reliably removed.
Settings has seven independent cleanup groups. Turn off the one hiding what you need — for example Shorts — home page if Shorts shelves disappeared from the home feed.
Session counters reset when the browser closes. Also, after reloading the extension you must reload your YouTube tab — the old content scripts become detached and can no longer report anything. Diagnostics has a "Counter consistency" card that flags exactly this.
YouTube stitches some advertisements directly into the video stream on the server. No browser extension can block these, because the ad and the video are the same bytes. Most in-video ads are still client-side and are blocked here; some never will be.
In Diagnostics, Run test disables the network rules, re-enables them, and compares. A row is counted as proof only when the request fails while rules are on and succeeds while rules are off.
The robots.txt row is a control: it must always succeed. If it
ever fails, the whole test is invalid and the result is discarded rather
than reported — a control that fails is treated as "no measurement", not as
"something is broken".
Alt+Shift+Y opens the extension menu.
Please include:
chrome://versionYou can reach the developer directly at ferhatdogan55@gmail.com.