hey,
thanks for asking. sadly no. I do prefer to have only one version on one platform. as Moderator of an Arma unit I know the pains of automatic updates my self...

to elaborate on apl-sa and the comment at the bottom to not reupload.
this is due to steams user license agreement. when uploading to steam you do accept that agreement and it kind of gets added to the mod, effectively overwriting and adding to the existing license.
in case of steams license you must be the owner of the thing you are uploading.
I have given permission in goodwill to people for some of my other mods before, but that most of the time ended up rather abused, thus I have stopped giving out permission to reupload and bundle on steam.

Hey Diwako, I'm using the apl-sa license to re-engineer your mod to work with a mod I'm working on. I'm totally gutting the code and using custom assets, but I am using DUI as a base to write the scripts, editing lines and removing what isn't needed.

I do have you in the credits, but I was curious if this would cause an issue with you when I upload it. There isn't much left of your mod, I've reduce it to two addons and a few scripts (with most being consolidated together) running along side a bunch of my own additions, but going through your code did teach me how to do all of this and there are still aspects of your original code left (which is why I have you in the credits).

Also, I am curious to some of the methods you used in your code, wondering if it's best for me to keep most of these files separate. You understand your own code better than I do, so if you're available I'd love to have another coder on the team as well.

Let me know if you're ok with me using parts of your mod in this way, if you aren't I'll find another way to implement a motion tracker.

Hey,
Reverse engineering is completely fine, learning from the code is as well. Giving credits to someone is mostly a curtesy thing, and a well regarded one on top of that.

However when you do use external code directly your project, as in having said code inside your project and not as an external source will put you into another ballpark.

APL-SA allows this, which is my full intention behind it. There are however rules people do need to follow.
For the code that is being reused, the license is not allowed to be changed. It must stay APL-SA, even if you change it a little. It is not even allowed to be changed to other APL derivatives.
Does that mean your whole project needs to be APL-SA? No, only the code that is licensed under it must stay under it.
It has happened quite a few times people take other peoples code as it is allowed via license, but then use it in a way that violates the original license.
As example: You use parts of DUI's code in your project. Your project however wrongfully claims to be endorsed by the original author or the project is being used in any commercial / monetized way. This would violate the APL-SA license and you are not allowed to use it that way.

That is what I mean with "another ballpark". Just to put that out there.

Yup, mod is APL-SA (and actually was before I came across yours), is totally free, and you are listed in the additional credits section as "Original author for the Radar and Nameplate scripts."

It does use some copy-pasted sections, with different object names of course, but everything is going on github when it's done so you can see exactly what bits of your code I used. I like to keep (especially free) things open source so various people with various expertise can pitch in and create something far better than a single person could. Plus, it does sort of immortalize the work. Even if at some point there isn't any of your code left, you will forever be in the credits as the original writer of those features.

hello a friend of mine got permission a while ago to bundle this with a few other mods to reduce the number of mods in the modlist. I was wondering if I could get permission from you to make use of this, It would be unlisted so that just anyone can't use it and obviously a like would be provided to your mod for anyone who isn't one of us to come here and use the main mod since they can't get the bundle to work on a server without us.
I sincerely hope we can get your support to shrink our modlist a bit please and thank you

Originally posted by dra90nslay3r:

hello a friend of mine got permission a while ago to bundle this with a few other mods to reduce the number of mods in the modlist. I was wondering if I could get permission from you to make use of this, It would be unlisted so that just anyone can't use it and obviously a like would be provided to your mod for anyone who isn't one of us to come here and use the main mod since they can't get the bundle to work on a server without us.
I sincerely hope we can get your support to shrink our modlist a bit please and thank you

Not sure who your friend it, but i do not give out permission to bundle this mod. They probably lied or meant another mod.

Originally posted by diwako:

hey,
thanks for asking. sadly no. I do prefer to have only one version on one platform. as Moderator of an Arma unit I know the pains of automatic updates my self...

to elaborate on apl-sa and the comment at the bottom to not reupload.
this is due to steams user license agreement. when uploading to steam you do accept that agreement and it kind of gets added to the mod, effectively overwriting and adding to the existing license.
in case of steams license you must be the owner of the thing you are uploading.
I have given permission in goodwill to people for some of my other mods before, but that most of the time ended up rather abused, thus I have stopped giving out permission to reupload and bundle on steam.

So, out of curiosity, I went over the Steam Subscriber Agreement and the APL-SA. Upon inspection, Section 6.B of the Steam Subscriber Agreement basically just says that Valve is not obligated to use, distribute, or continue to distribute copies of Workshop items and reserves the right, but not the obligation, to remove workshop items for any reason.

Section B then goes on to specify that certain workshop-enabled games/apps may contain special terms that supplement or change the terms set out in Section 6 of the STEAM Subscriber Agreement.

Authors of Workshop Contributions can choose to remove a workshop contribution from applicable workshop pages, but the section also stipulates that the removal must not affect the rights of affected individuals (for example, if there is a license attached to the material. In this case, the APL-SA)


Section 2.a of the APL-SA grants permission of all recipients of the Licensed Material to exercise the rights listed within the terms and conditions of the license; Section 2.a.1 explicitly grants permission to reproduce and share material licensed under the APL-SA (for NonCommercial and ArmaOnly purposes).

Section 2.a.5.c of the APL-SA specifies that you may not impose additional or different terms to the Licensed Material if doing so restricts exercise of the aforementioned Licensed Rights.

Section 3.a of the APL-SA lays out steps that must be followed for sharing the licensed material (such as identification of the creator of the licensed material, copyright notice, notice that refers to the public license, disclaimer of warranties, and a URL to the original licensed material, among other things.)


Basically, in the example of including the mod in say a modpack bundle, that is allowed by the SSA and the APL-SA license as long as the attribution rules outlined in 3.a of the APL-SA are followed


I've seen some pretty long winded licenses filled with all sorts of legalese, but the Steam Subscriber Agreement and the APL-SA are fairly straightforward in these regards.

Although the terms of the SSA and APL-SA would allow a person to redistribute in this case, generally, it's good conduct to respect the wishes of a mod author