Hi people since a lot of time I work on kyofu no saku
a new kind of xas edition
I work a lot but I hesite a little
I give credit to Xiderowng
but ALSO moghunter for rgss3 reference
now the dillemma is I work on the event and player sensor part ..but I love Moghunter XAS sensor
so I decide to get inspiration of his code because I love how its work
so
as long I credit moghunter is not considerate like plagiarism ? (well I hope)
because the lattest things I want is get banned for plagiarism due the fact I use the same structure of moghunter
and some part are is orginal code
thanks if people can answer me D:
Script Creditation
● ARCHIVED · READ-ONLY
-
-
Well you have to be careful. A coder named Soulpour777 had some misunderstandings and resolved the issue with Moghunter. So you'd have to contact him first.
-
I doubt very seriously you need to credit someone if your structure is similar to theirs, that would be extremely weird.
-
Some part are from XAS Hero Edition so normally I need to credit MoghunterI doubt very seriously you need to credit someone if your structure is similar to theirs, that would be extremely weird.
Yep I will contact Moghunter-sempai as soon possible if I can use is system like a base for my systemWell you have to be careful. A coder named Soulpour777 had some misunderstandings and resolved the issue with Moghunter. So you'd have to contact him first. -
It's plagiarism when you lift others' work and then try to pass it off as your own.
-
I said and I resaid I credit moghunter for the base and the referency so I assume in the script some part are from moghunterIt's plagiarism when you lift others' work and then try to pass it off as your own.
so I don't know why it will be plagiarism... -
Someone else was just banned for the same reason today - they did put a bit more effort into making the script their own (they changed variable names and method names) but it was still clearly a copy of the other person's. Both of these people had the audacity to charge money for their "stolen" scripts.
You can use someone's script for inspiration. You can look at someone's script to see how they did something. But when you implement it into your own script YOU MUST NOT COPY IT OR RETYPE IT. Copying it and changing variable names is still copying. Copying it and adding extra line breaks and extra comments is still copying.
Giving credit doesn't make it okay if it's still more or less a copy. But it does indicate that you're not trying to pass someone else's work off as your own. It all depends on how different or similar your script is to theirs. -
hum okai it answer my question D:
I was not sure
thanks for your proper answer -
Hmmm, for me, you really have to ask the original scripter what he / she can say about it. Sometimes it could be a backthrow if you did a rework, add on and stuff, and if they're okay with it, I guess get a copy of the permission so you won't get busted in no time.
-
the problem is Xiderowng is a Japanese user xD..Hmmm, for me, you really have to ask the original scripter what he / she can say about it. Sometimes it could be a backthrow if you did a rework, add on and stuff, and if they're okay with it, I guess get a copy of the permission so you won't get busted in no time.
and I never really saw is original Code
just moghunter code so
I ask to moghunter because I literreally follow the structure of moghunter coding -
If you want to do something, and someone did exactly what you want to do, what's the point if you're not allowed to do what they did? Should I try to find another way to do the same thing because someone else already took that approach?Someone else was just banned for the same reason today - they did put a bit more effort into making the script their own (they changed variable names and method names) but it was still clearly a copy of the other person's. Both of these people had the audacity to charge money for their "stolen" scripts.
You can use someone's script for inspiration. You can look at someone's script to see how they did something. But when you implement it into your own script YOU MUST NOT COPY IT OR RETYPE IT. Copying it and changing variable names is still copying. Copying it and adding extra line breaks and extra comments is still copying.
Giving credit doesn't make it okay if it's still more or less a copy. But it does indicate that you're not trying to pass someone else's work off as your own. It all depends on how different or similar your script is to theirs.
It's also entirely possible that two people arrived at a very similar solution. At one point I had written a script that allowed you to create popup balloons with item icons instead (to show that you received an item, for example), and then someone posted a link accusing me of plagiarising a japanese scripter that I've never heard of. When I looked at the script, it was almost identical: same methods being aliased, same classes being modified, different variable names but basically the same thing. A different way to actually call the balloons, but otherwise the same logic for handling the balloons themselves. -
yes, he is. I think he understands English, you can contact him on his website.the problem is Xiderowng is a Japanese user xD..
and I never really saw is original Code
just moghunter code so
I ask to moghunter because I literreally follow the structure of moghunter coding -
I will try to contact himyes, he is. I think he understands English, you can contact him on his website.
it is why I open this topic it is a really big contreversal SubjectIf you want to do something, and someone did exactly what you want to do, what's the point if you're not allowed to do what they did? Should I try to find another way to do the same thing because someone else already took that approach?
It's also entirely possible that two people arrived at a very similar solution. At one point I had written a script that allowed you to create popup balloons with item icons instead (to show that you received an item, for example), and then someone posted a link accusing me of plagiarising a japanese scripter that I've never heard of. When I looked at the script, it was almost identical: same methods being aliased, same classes being modified, different variable names but basically the same thing. A different way to actually call the balloons, but otherwise the same logic for handling the balloons themselves.
I was really not sure of the limit of how I can use people script for basis normally when I use other script part I addapt the script part and say this part is made from who and I don't change anything (unless alias for advoid Compatibility issue ) and add my part but it seem it is not legal of doing this so I will stop doing this -
Blatant plagiarism asides(like just changing the author name and terms of use and nothing else), I think it depends on individual's script's terms of use.
One 1 side, some let you edit the codes and publish your edit as long as you still give proper credit. Some even let you copy blatantly as long as you don't claim those codes aren't their original authors' works.
On another side, some just don't let you edit from their codes. Some don't even let you redistribute the original codes without their permission.
It's extremely important to clearly comprehend all of their terms of use before using any of their script codes to do anything or you can be putting yourself in danger.
Using myself as an example, I'd made bug fix, compatibility fix and some addons to Yami's ATB script. I interpreted their terms of use as strictly as I could, and I even asked Yami for permission before I post my edits.
Even then, I still won't ask users to credit me for using any of my edits to Yami's ATB. I even disallow them to credit me without crediting Yami as well if they're to use any of those edits.
All these are to ensure that I'm not violating the rights nor wills of the original authors. After all, I'm just editing from their scripts but not writing all these things myself. My edits won't even exist if the original scripts didn't.
Going back to your case, I think you may want to contact him even though he did write the terms of use in this website, like what you said. Better safe than sorry :D
P.S.: I think Tsukihime's case's really tough. It seems to me that it's extremely hard for either side to have almost 100% concrete and decisive evidences to support their claims in general :)
(Also giving the benefit of doubt to either side might lead to serious exploits that put the other side into unfair situations) -
How big was this script? How complicated was it?At one point I had written a script that allowed you to create popup balloons with item icons instead (to show that you received an item, for example), and then someone posted a link accusing me of plagiarising a japanese scripter that I've never heard of. When I looked at the script, it was almost identical: same methods being aliased, same classes being modified, different variable names but basically the same thing. A different way to actually call the balloons, but otherwise the same logic for handling the balloons themselves.
The script we saw today would not have been created so similarly by two different scripters. We did look to see how complex the script was and how they both went about approaching that complexity. Also the size of the script - how many classes, how many methods.
And if you DIDN'T copy it and are accused of doing so, you can always plead your case. -
Yes, it is possible to arrive at similiar solutions, especially with short scripts. But the word is "similiar", not "identical".If you want to do something, and someone did exactly what you want to do, what's the point if you're not allowed to do what they did? Should I try to find another way to do the same thing because someone else already took that approach?
It's also entirely possible that two people arrived at a very similar solution.
Let's just say that in both cases where the user was banned, we talked about it internally to make sure we didn't go wrong (in one case for days until we could find clear proof). And even in those cases we send them messages that they would be unbanned if they can send proof of their innocence.
And also, the action was taken because the copy scripter claimed the work as their own, having specifically removed all indications of the true origin (but done so in a very obvious way in one case). And we're not talking about simple scripts that could accidentally look the same... -
I think we can close this now. Really, we don't go around looking for reasons to ban people.