Your "own" plugin would be code you wrote; not a bunch of copied code, not a modified version of another.
Your "own" plugin would be code you wrote; not a bunch of copied code, not a modified version of another.
https://github.com/Nogrod/OxidePlugins/blob/master/Rust/GUIShop.cs
https://github.com/strykes/Oxide2Plugins/blob/master/CSharp/GUIShop.cs
The first link is NogRod. Second is a contributor named Strykes. You allowed this "GUIShop plugin" as it is to be uploaded. Despite there already being gethib repositories. Based on this code ^ and what has been uploaded I'd say it violates your polices. No?
Merged postkhan
Okay so basically unless I either become the new maintainer of this plugin. Or send the current maintainer of this plugin my version that I completely re-write as my own, and hope they choose to upload as a new update. Then I cannot upload it at all to your site?
As mentioned previously, you can either contribute to the existing (we have a Patch function for existing plugin developers, else a code block with just the changed lines, or a PM with modified version) you can or write your own original works (your code, not a modified version). We accept submissions of plugins created or managed by the person submitting them, not modified versions of existing.
It's more than just some changed config lines that had to be done... I literally had to re-write parts of the #Csharp code for certain aspects to even function.
I have no idea what this patch function is your talking about? I don't see anything called a patch function on the site under the listed plugin?
Am I expected to create a new thread entirely under the plugins help section? And call it Khan's re-worked fork with add on's. Or am I supposed to make "extension plugins that work with this "Shop plugin" At least those would be my own plugin add-ons.
khan
Okay, so how would I get that tag? And why is it not like the default when I made an account?
The tag is assigned when a plugin has been accepted on the site. Not all users here are developers.
So what your saying is that it's a closed community and if I wanted to even contribute to an existing plugin using the patch function. I'd first half to up-load an "accepted plugin" to the site.
That's my understanding of it right?
khan
So what your saying is that it's a closed community and if I wanted to even contribute to an existing plugin using the patch function. I'd first half to up-load an "accepted plugin" to the site.
That's my understanding of it right?
No, I am saying that the Patch functionality is available once a user has submitted some of their own work and been granted the tag of Plugin Developer; literally that. As I stated previously, you can send a PM to the maintainer or show the changed portions that you'd like to request changed in the plugin, the Patch functionality is WIP and there for those shown to have some experience, not all users.
What do I do when the maintainer doesn't accept private messages? And how long would it take for review acceptance if I uploaded a plugin?
Would I post 1,000+ lines of code under a new thread? The current version has under 200 lines of code... Or would I just post a new thread with a link attachment download from like GetHub? When I'm finished...