Is it possible to add options to the script that the user can activate and deactivate and thus change the script execution?

Some user might not like some features of a script and thus they would be able to deactivate them.

If it is not possible now, are there any plans to add such a feature?

Re: @freeos:

... add options ...

Take a gander at https://openuserjs.org/garage/Making_a_blocklist_user-friendly

Re: @Marti:

thanks!

Re: @Marti:

GM_config lacks the following features, a regular user might want:

• Ability to open and change the options without reloading the page.
• Do not show the options every time when the page is loaded (refreshed), only when the user explicitly decides to.

I think a better alternative solution would be if the options could be accessed through the Violentmonkey extenesion popup. Then they will be always active, and when the user decide to change them he can do so.

Re: @freeos:

You should only call GM_config.open() when the user wants to open it or you need the user to decide something.

I think a better alternative solution would be if the options could be accessed through the Violentmonkey extenesion popup.

You can add one or more menu commands to appear below the name of your script for users to call up the settings dialog, but the dialog would need to launch from the script in the web page, for example, in an overlay or popup window.

The code to allow real-time settings changes to take effect immediately can be laborious to write. As an example -- by someone without a programming background, so surely it's not very efficient -- you could look at:

https://www.jeffersonscher.com/gm/google-hit-hider/

Re: @freeos:

Taking the less subtle approach, unlike jscher2000's gently mentioned open advice, to prevent blatant misinformation:

GM_config lacks the following features, a regular user might want:

• Ability to open and change the options without reloading the page.

This is absolutely incorrect. You have clearly ignored bothering to check out how to use GM_config with the .open command.

GM_config lacks the following features, a regular user might want:
...

• Do not show the options every time when the page is loaded (refreshed), only when the user explicitly decides to.

Again incomplete research on your part with poor assumptions on the GM_config Unit Test.

The wiki is referenced on the library homepage and should have been your first visit before assuming incorrectly.

Please try, try again.