Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Mission Condition assigngear factions. #674

Open
Khaosmatic opened this issue Aug 30, 2015 · 5 comments
Open

[Feature Request] Mission Condition assigngear factions. #674

Khaosmatic opened this issue Aug 30, 2015 · 5 comments

Comments

@Khaosmatic
Copy link

Currently the system in place means we can dictate a set of gear per faction, e.g. NATO, OPFOR and INDEP. By faction I mean you set up the assigngear to have US Marines gear, etc. Wouldn't it be feasible to be able to create a folder wherein it has for example:

'f_assignGear_faction1.sqf'
'f_assignGear_faction2.sqf'

And then in the mission conditions you could just have 'Use faction: 1, 2 or 3' just like weather or time? Given I don't have extensive knowledge in this but you are executing an .sqf for weather and time presets so surely this is possible? Also I guess it doesn't really apply as F3 is built for vanilla ARMA where there is only one OPFOR or INDEPENDANT faction however for people using mods it means replay-ability could be added to missions very easily.

@Pasrules
Copy link
Contributor

For B|Tac we have 3 factions which we keep the same NATO, CSAT, FIA with their custom gear. Then we have multiple spare AAF loadouts which we just drag and drop into F3 if we want to use them. This could be made a param but alot of script would have to be changed over.

@Khaosmatic
Copy link
Author

Indeed, I too have set up multiple custom gear profiles which can be dropped in, its just when PBO'd or on a dedicated server it means either you shut down and upload the new mission or bog down the server with multiple types.

@ferstaberinde ferstaberinde added this to the The Future milestone Oct 21, 2015
@ferstaberinde
Copy link
Owner

This may constitute bloat, but am going to assign to the 'future' milestone for now (it will not be in scope for v3-4-0).

@rainhardtgabriel
Copy link

Did you mean something like this....
// F3 - LoadoutSelector

// This Parameter will select the Loadouts that are chosen for each Side

class f_param_uniforms
{
        title = "$STR_f_param_uniforms";
        values[] = {0,1,2,3};
        texts[] = {"Vanilla","RHS Woodland","RHS Desert","CUP Woodland"};
        default = 1;
        code = "f_param_uniforms = %1";

If you want I can start a PR without the other changes we made.

@Khaosmatic
Copy link
Author

Yes that is exactly it! I apologize I only received the notification for this today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants