Greasy Fork is available in English.
Hides scripts for popular browser games and social networks as well as scripts that use "foreign" characters in descriptions. Applies to posts in Forum too.
< Feedback on GreasyFork Bullshit Filter
The option you're referring to is to modify the value of line const DEBUGGING = 0 to 1.
Doing that the script works fine for me, in both Tampermonkey and Violentmonkey, both logged in or not. Greasyfork is NOT supported.
Screenshot examples:
https://greasyfork.org/en/users/2160-darkred
https://greasyfork.org/en/users/302389-oliwang
https://i.imgur.com/e3WR51u.jpg
https://i.imgur.com/fLliPig.jpg
Please give details (browser, script manager, URL example) so that I can help you.
And, update your rating to: "No rating - just a question, comment, or feature request".
After some experimentation, I've figured out that the modifying const DEBUGGING = 0 to 1 did not work as intended because the script was clashing with two other Greasyfork scripts I have: Greasyfork Search with Sleazyfork Results include and Greasy Fork+. When I disable those two, your script works properly.
Is it possible to address the conflict that's causing this bug?
Unfortunately there's nothing I can do about it. These two scripts are meant to work similarly to this one. I don't think there's a way to make them all work ok simultaneously, sorry.
In fact all three scripts try to filter matching scripts, but:
document-end, i.e. they may conflict with each other, document-start, i.e. it gets injected as fast as possible and so it filters matching scripts first, therefore afterwards the other two scripts have no unhidden scripts left to match against.I'm just describing how they work.
The option to simply highlight the filtered scripts in yellow instead of hiding them does not work.