MCCodes v2.0.4 Released & Security Doc

[HauntedDawg]

but there are also licensing issues associated with that even if the mods are released as "free".

Licensing issues? The link's i provided are directly to modification's i submitted awhile ago. In other term's I'm saying: 'You may use these as you wish'.

By the way. Is the engine itself copyrighted yet? If not, then no "licensing issues" would be encountered am i correct?

[Dabomstew]

Licensing issues? The link's i provided are directly to modification's i submitted awhile ago. In other term's I'm saying: 'You may use these as you wish'.

By the way. Is the engine itself copyrighted yet? If not, then no "licensing issues" would be encountered am i correct?

I understand that the mods that you linked to would have been absolutely fine to include in the patch. However, the process by which I compiled the patch did not include looking for topics on the forum containing mods that could improve the base engine. I was simply aiming to discover the bugs and security flaws in the script and correct them, whilst doing some other minor touchups such as standardizing the code style. I decided that the best way to patch the issues I found was simply to correct the code, as most of them were not complex problems. Whether you agree or not with this approach regarding this patch doesn't really matter as it has already been released, and does the job it is intended to (to our knowledge, at least). Again, we may release another patch in the future that *does* go down the route you suggest.

Copyright and licensing are two different issues, really. As far as copyright goes, where MCCodes is created (the country I live in), there is *no* copyright registration process whatsoever. Additionally, the codes are still protected under copyright from the date of their creation according to the copyright laws of a large amount of countries. Whether it would be prudent to register our copyright in certain other prominent countries where such registration is possible & helpful is another matter.

As far as licensing goes? If you were to release some code under a GPL license, and I was to include it in a product I was selling without asking you to relicense it, you could take action against me regardless of the copyright status or license of my for sale product. That is where licensing issues could arise.

[Dominion]

We will consider stuff like "improved" mods being integrated if there is another patch release, but there are also licensing issues associated with that even if the mods are released as "free".

Not really a good idea to use mods created by other. Take ideas by all means, but create it yourself, and avoid all problems you listed above.

Btw - nice to see yet more updates.

[Mystical]

I understand that the mods that you linked to would have been absolutely fine to include in the patch. However, the process by which I compiled the patch did not include looking for topics on the forum containing mods that could improve the base engine. I was simply aiming to discover the bugs and security flaws in the script and correct them, whilst doing some other minor touchups such as standardizing the code style. I decided that the best way to patch the issues I found was simply to correct the code, as most of them were not complex problems. Whether you agree or not with this approach regarding this patch doesn't really matter as it has already been released, and does the job it is intended to (to our knowledge, at least). Again, we may release another patch in the future that *does* go down the route you suggest.

Copyright and licensing are two different issues, really. As far as copyright goes, where MCCodes is created (the country I live in), there is *no* copyright registration process whatsoever. Additionally, the codes are still protected under copyright from the date of their creation according to the copyright laws of a large amount of countries. Whether it would be prudent to register our copyright in certain other prominent countries where such registration is possible & helpful is another matter.

As far as licensing goes? If you were to release some code under a GPL license, and I was to include it in a product I was selling without asking you to relicense it, you could take action against me regardless of the copyright status or license of my for sale product. That is where licensing issues could arise.

No to be a wise guy but you might want to explain all that licensing info to this guy http://ravan.info/ who is still selling your codes and has been for a long time. Years.