Aae addons/missions

[andersgrim]

For an addon to follow the AAE standard properly, a mission for the addon should be made...
Now, will it be necessary to include two .msi's for the addon; one for the addon itself and one for the mission, or would it be best to make a zip containing the .msi packed addon and just a .pbo mission?

[Maruk]

For an addon to follow the AAE standard properly, a mission for the addon should be made...
Now, will it be necessary to include two .msi's for the addon; one for the addon itself and one for the mission, or would it be best to make a zip containing the .msi packed addon and just a .pbo mission?

It all shall be on single msi file containing everything. Theoretically, you can create msi file containt a mission only and it still would be AAE compliant but unless the mission is really superb quality (with notable musical score, storyline, voice overs) I doubt anyone would be really interested in such addon.

On the other hand, if you addon packed into msi doesn't contain a single mission, it's not aae compliant.

[andersgrim]

Ok, I understand.
I thought the installer was like the beta where you browsed for your \addons folder. Now as you just browse to your \Flashpoint directory, i get the point
Do any other game developer publish that much help and tools for it's community?

[Nagual]

So what is the bis stance on music in aae missions?
Are we allowed to use custom music, or will that bring about such serious legal issues that bis cant dare list them on the aae page?

And IF anyone from bis read my posts in the last aae thread, you will know i think the addon only mission restriction is flawed when dealing wither a bigger mod/team that make inter-related, but not interdependant addons.
I would seriously prefer to not make missions at all than make missions i have zero interest in, or to work backwards, hacking up old demos so they are worse off for the "update".

[PSC]

Quote from the AAE guidelines:

Quote[/b] ]
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

PSC

[Nagual]

Those lines are in relation to addon dependencies PSC, not missions.

[Nagual]

So what is the bis stance on music in aae missions?
Are we allowed to use custom music, or will that bring about such serious legal issues that bis cant dare list them on the aae page?

I got some info from the AvonLady that is relevant to this:

Quote[/b] ]
If this will turn out to be a problem, there's always AMORE.

AMORE makes music optional - not required. So, you can produce an AAE mission that uses AMORE and is AAE compliant, since technically, AMORE music files are optional.

[PSC]

Oh, but wasn't that what you were asking for?

Quote[/b] ]Or, for example a delta ranger specific mission, are we meant to insert them with BIS blackhawks, when there are nice littlebirds available? From my perspective, that defeats the greater scope of what BAS make, and doesn't provide BAS fans with what they enjoy.

Maybe I didn't get your point right though?

Regards, PSC

[Nagual]

I was thinking more along the lines of 2 addons in a mission when the two addons do not use the requiredAddons[].

For example, the delta's and MH6 dont use requiredAddons[] because they dont need to, neither addon uses the config or textures/resources of the other.
But ingame, they are a pair. So even though the delta's are not technically required to play a mh6 demo mission, it is common sense to use the delta's in that mission for gameplay, enjoyment, and technical reasons (such as goggles/rotorwash).

Another small example, the mh47e missions use KLR 250 bikes, not because they are required, but because using them in combination with the Mh47 is one of the addons features, so they are there to give the player chance to check out the options of the addon.

But if making the mission using an addon that is not required in the [] config makes the package non-AAE compliant, its seems silly when the mission would be better of for it, and the players first experience of the addon would be more enjoyable.

Another example, say the nomad mod, with their big island download. If they later release some soviet / afghan units to fight on the island, as a seperate download, the mission for the units would techincally not be allowed to be on the island, unless the requiredaddons[] is needlesly used, or they are packed in one even bigger download. ***

I think using just the addon being installed is a good idea, most of the time,especially for standalone addons (not part of bigger project), its even the bas policy. But there is only 2 (released) bas demos that stick to that policy, because of gameplay or practicality. And one of those, the MH6 demo, is already converted to use Deltas, as it makes sense.

[PSC]

Oh well, I always understood it like this: If you need another addon for a) the addon itself or b) the mission, write a note into the requiredAddons[] part of a) the addons config, or b) the mission.sqm (there is such a part in the mission.sqm, isn't it?).
Plus the rest (instruction in the readme where to get, etc...).

Regard, PSC