Another plug-in I created recently which is proving useful to me is: saturation_h_m_l.py
It creates three layers with masks for high, medium and low saturation to allow independent adjustment of the three regions.

Now at Version 5 29/05/2023

Edit: I have removed the file. I have now found a problem with it!!!
Edit2: Hopefully I have corrected the plug-in. If there had been previous processing of the original image it tried to work on the top layer. This became very obvious when I had a layer in overlay mode! It now creates a New-from_Visible as a first step.

I hope others will test it and highlight any problems.

Can't you people create a Github of some sorts where people can find the latest version of things instead of posting them at random? Just a suggestion...

@MareroQ,

Apologies! The morning after I put saturation_h_m_l.py in this thread (#84) I discovered a problem. If an image had a number of layers from previous processing, the plug-in only worked on the top layer. This became obvious when the top layer of an image was in overlay mode!

I have modified the plug-in so that it initially creates a new-from-visible layer.

I have updated the file at #84 to Version 5, dated 29/05/2023.

@David
I have to update The OLD Archive: 'GimpLearn archive'. whether to post as new threads?

@Ofnuts
There is already such a possibility (and it's very simple)::

It just doesn't work that way.
Unfortunately, there are few people willing to publish their plugins on this site (95% of posts and plugins are chosen by the moderators themselves).

@Trandoductin
... I guess that's the end of GIMPlearn!...

I hope you come back someday with your new website.

Or maybe some weird questions (probably little known to users): planting how many trees has GIMPLearn sponsored?
How many trees will not be "born"?

Many thanks to you and may you miss what you lost.

Ofnuts is probably right, maybe gimpscripts.net isn't the right way to go about this. I only offered to do this so there would be a place to "at least" host newly updated scripts. It was never intended to be the final solution.

The problem with these single-owner sites is that they can disappear overnight. My code on SourceForge or GitHub will certainly outlive me, while my ghost will continue to farm kharma on StackOverflow and Reddit.

Do you have to "own" the code in order to upload it on SourceForge or GitHub? Anyone wanting to create their own is up to them, but to take what we have, even with the updated code, would be nice to transition them away to a more permanent place.

As long as the source code is FOSS (GPL or else), which is the case of very many scripts, you can put it in a GitHub or SF project. PatDavid copies the whol Gimp registry to GitHub.

But if the code has a maintainer, let the maintainer keep it, and avoid having obsolete versions floating around.

At least if you had a backup, you buried our efforts, I tried so hard, if you're worried, I have offered to help you many times. I would work for free. I was happy while making GL Banners. My old name gimpturkey in Gimp Learn site

Not sure how much can be gleaned using the Wayback Machine. I have managed to get quite a few of my older scripts that way.

I don't have backup. sorry. didn't pay for automatic back up either.

can always rebuild on gimpchat and gimp-forum.net, stronger and better.

Will it be as you say?

I guess I misunderstood, is our previous work still on wayback machine?
Dear Mahvin, you are a very constructive and positive person.Thank you
I decided to redo everything.

If you talk about GL, sadly there is only 9 pages (if I recall) on the wayback machine
BTW, nice to see you here GT

... and none of the scripts ....
What I can't understand in this case is: how can one throw one's work away just like that?