At Ease License Agreement Important: read license_agreement.rtf for information about the atease.exe license. It's distributed as freeware under the terms set in the license_agreement.rtf file accompanying the installation. Generally, the license is given to you as long as you use the tool to create Operation Flashpoint Add-ons for non-commercial use apart from some other conditions as described in the EULA and you're not going to publicely release any addon created using this utility unless it's at ease compliant (see below).
At Ease! Compliance Requirements Also, your Operation Flashpoint Add-on should respect following requirements to be At Ease compliant:
I) It is a single MSI file created using the official AtEase tool. Name of the Addon should start with unique TAG of the creator (see http://www.ofpec.com/tags_about.php for more information about the TAG system).
II) It includes at least one single player mission in the package. Name of any mission installed should start with TAG.
III) All included addons should be created in compliance with the TAG system.
IV) The included sample mission(s) should not require any other addons beside of the addons being installed as part of the At Ease package and official BIS content included in Operation Flashpoint version 1.91.
V) If the addons itself requires other addons to work properly, it has to:
i) include such addons in requiredAddons[] list
ii) provide exact instructions where to get the addon in the readme file
iii) the addons in question has to be At Ease compliant addons as well
VI) All addons and missions should be compatible with Operation Flashpoint version 1.91
VII) A readme file giving the user the exact information about content being installed and end user agreement must be present in readme.txt and eula.rtf files packed into the msi with the addon.
How to create your msi file
You need to copy your content to folders Addons, Res\Addons, Missions or MPMission in the same folder where you have atease.exe.
Write your readme to readme.txt file, name of the addon beginning with your TAG to name.txt file and also the end user license agreement to eula.rtf file (a sample readme and eula are included in doc folder but you may create your own readme and eula if you want).
atease.exe will automatically create an msi file with all content ready for distribution (you may not need to compress it to zip file as msi file is compressed quite well already).
It also creates a msi-info.bin file. It's recommended to archive this file when you created the release version of your addon for future use.
