Just tried using BRL - Round Bevel 1 on the design.
Here is the result.

Now its perfect !

Also thanks for explaining the code. This knowledge might come handy in some future project.

This is what I get when trying out the plugin:


Is that what it's supposed to do? I used the latest update in post 50.

@mackenzieh
Yes - the mini version is just paths.

Ver. 0.6.
-add Vertical Text (experimental)
-add Drop Shadow (on request P1937)

Love the Vertical Text in v0.6, very well done!

Thank you MareroQ for the drop shadow. Works beautifully.
Appreciate the time and effort spent on this Plug-in.

Here's my result:

Ver. 0.7 (take a breath - there probably this is the last version)

Only add for interactive call scripts:
- 3D-Extrusion.scm by GnuTux,
- Bevel-Reflect-Logo.scm by GnuTux,
- Chisel.scm by Rob Antonishen,
- Double-Bump-Map.scm by Tin Tran,
- Gradient-Bevel-Logo.scm by Brian McFee,
- GT-Bevel.scm by GnuTux.

You will never check all possible combinations - so when you are bored you can try to change the possible parameters - especially in those called interactively
(but that it is difficult to predict all possible combinations so some may end up with an error - sorry, but don't shout at me).

For convenience, I have collected all the required plugins in one BIG_package:

- Scroll bar for scripts (script-fu.exe for Gimp 2.10.14_64bit) and python (gimpfu.py) - you need to replace the original so make a copy for possible restoration;
- plug-ins: ofn-bend-path.py, layerfx.py, bump-map.exe ("repair" for Gimp 2.10.14_64bit coming from Gimp-2.8.22);
- scripts: 3D-Extrusion.scm, Bevel-Reflect-Logo.scm, Chisel.scm, Double_Bump_Map.scm, Gradient Bevel.scm (glossy bevelly), GT-bevel.scm.

Watch out for duplicates - maybe you already have them installed (if you're not sure - don't install add-ons).

If you distribute my script (bad idea IMHO, because I could update it), at least distribute it with its documentation...

@Ofnuts.

Your reaction surprised me (not for the first time anyway).
This thread begins with information - where you can download your plugin (i.e. also documentation - for those interested).
When a part of the puzzle changes, sometimes everything stops working - and it's good to know: why and in what version it worked (and be able to access as quickly as possible).
If you think that I violated your copyrights (which are not GPL - unfortunately, I checked it too late because only today), I ask the administrator to completely remove the thread (no regrets -I had a great time for 7 days).

@Wallace.

I hope you will act according to Ofnuts decision.
For me, this thread is closed.
Thank you to everyone who took part in my game.

As far as i can tell, ofnuts is asking you to not redistribute his plug-in, so he maintains control over it.
He also says, if you absolutely must, then at least include the documentation, so it doesnt take away from the work he invested in his plug-in.

If you redistribute his plug-in in a bundle, instead of linking to ofnuts's github, you help spreading code that may be outdated in the future.

People tend to not read whole threads from bginning to end or will jump right to the part that was linked to.
Some people arent even capable of reading the information that was on the same page, three post higher, as it has been proven in this very thread.

@Konstantin

I was not to speak in this thread anymore but I will answer (because unlike some you are always nice).
I don't need anything - in my opinion "all in one" is just a convenience for users.
All the time I emphasized that my attempts are just a small addition to the original plugin (the title of the thread and the header of the plugin indicates this).

Ofnuts reserves only:
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.
This very file is the complete source code to the program.
If you make and redistribute changes to this code, please mark it
in reasonable ways as different from the original version.

Nothing about documentation.
I didn't change anything in the code - I wanted to popularize it.

In the GPL case, I don't know which is more binding:

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
The GPL v3 licence is available at: https://www.gnu.org/licenses/gpl-3.0.en.html

or information Copyright?

As I wrote: the decision belongs to Ofnuts.

@MareroQ

I think you are overreacting a bit.
ofnuts said nothing about copyright in his post.

He asks you to not include his plug-in in a bundle, but instead always link to his github.

As far as i can tell, all you have to do is delete the bundle and then we can all continue to enjoy this thread.

There is absolutely no doubt that you had the best intentions.

I never asked for this thread to be closed, and my code is GPL, all my scripts state this in their header.

My point is not about redistribution but about abandon. I'm just warning that code put in a zip in a forum is rarely updated. If it's throw-away code it"s not a problem, but if it contains otherwise maintained code this may have moved forward when the zip is discovered by people in a couple of years from now. I made the remark initially for my own code but the bundle also contains code that replaces standard Gimp code.

OK - knowledge is never too much.