Using Arma/Arma2/OA content in A3 via AIA arma 3 mod. Views from players and modders.

[chrisb 196]

With ‘AIA’ mod now in A3 Alpha and the possibility to put series content over into A3 (those that work o.k.) without breaking any EULA, i.e. arma/arma2/OA and TOH, simple drag and drop mod and activate via ‘AIA’.

I think this is as important as ‘caa1’ was to bring over arma content into A2, allowing players to get the best from mod/addons in the series (renewing perhaps).

I like seeing mod/addons made a while back re-used in-game wherever possible, but understand the SWS issue, this is not what this is about.

Just thoughts on taking content over, as said with nothing altered or changed just drag-drop and use, obviously with the help of ‘AIA’

Will we see a devide in the series whereas "this content is for Arma 2 use only", or will mod/addon makers embrace the possibility of this injecting new life into older, but still great, mod/addons..

I don't want this to break into a Steam Workshop issue/conversation, just the thoughts about using this as it is, completely outside of Steam itself 'mod wise'..

My personal view as above is, kju is doing really important and great work, to enhance the series and outside this series (BIS TOH) experience..

______

I have not seen a thread in the Arma 2/OA thread here, sorry if this has already been listed..

Edited April 15, 2013 by ChrisB

[NoRailgunner 0]

Imo if the author/creator doesn't want his work "just be ported" over A3 by anyone this should be respected even by the most impatient player/fan. Guess some addon/mod makers will be pissed off if they see their work beeing ported over and flying around in (many) bugged, "tweaked" or "customized" A3 variants. Better wait until addon/mod "...is done" - for A3. Keep in mind A3 is Alpha not final (!) and things, features etc might change through time. Btw would be interesting to know if AIA break or circumvent the IP rights of the author/creator? IIRC there were some legal troubles using certain tools....

[Binkowski 26]

Imo if the author/creator doesn't want his work "just be ported" over A3 by anyone this should be respected even by the most impatient player/fan. Guess some addon/mod makers will be pissed off if they see their work beeing ported over and flying around in (many) bugged, "tweaked" or "customized" A3 variants. Better wait until addon/mod "...is done" - for A3. Keep in mind A3 is Alpha not final (!) and things, features etc might change through time. Btw would be interesting to know if AIA break or circumvent the IP rights of the author/creator? IIRC there were some legal troubles using certain tools....

I agree with this.

I know if someone tried to port my characters I would be very mad if they didn't ask for my permission before porting them over. Luckily, as far as I know you can't just straight port characters over to ArmA3 (to my knowledge..). But for Island makers, vehicles, etc. it's much easier. While it's good that people are putting forth the work to get BI content from the other games into the Alpha to have more content; I am hoping that the people in the community don't just port someone's work without their permission. I'm sure we won't have many more issues now. But there were a few when the Alpha was first released, that were quickly resolved.

[Dwarden 1125]

on the SWS line: there is no SWS until we confirm it , so any discussion over it is moot, and even if in theory there is then nothing preventing the content maker to not use it and release via other means

on the backward compatibility and e.g. AiA alike solution,

think about analogy in way of x86 program released for WindowsXP ... now user updated to Windows 7,8,8.1 yet the program still runs

unless it's EULA/TOS/LA/ or w/e license agreement clearly defines what OS the program can be used only on or what is maximal build or else

then there should be no restriction on the usage for user (as long as there is no alteration)

we encourage possibility of backward compability for years and it gets improved each iteration (A2: CO, TOH: Rearmed etc.)