Page MenuHomeFeedback Tracker

Extend configfile per mission
Closed, ResolvedPublic

Description

It would be great if Mission Creators could extend the existing configfile with configs defined in the mission
I have 2 ideas how this could be done:

  1. Allow config.cpp file in the mission root
  1. Allow scriptcommands that use classnames to also use configpaths

This way we could define the classes in description.ext and call it like:

player addWeapon (missionConfigFile >> "cfgWeapons" >> "myCusomWeapon")

It would also be helpful if we could inherit inside the missionconfigfile from classes from the configfile
Example Description.ext:

class cfgVehicles
{
class my_Hummingbird : B_Heli_Light_01_F
{
weapons[] = {"CMFlareLauncher"};
};
};

I'm sure that it isn't that easy and I dont know if it would be vulnerable for hacking or something like that but I think every missionmaker would benefit from this

Details

Legacy ID
182767497
Severity
None
Resolution
Open
Reproducibility
N/A
Category
Feature Request
Additional Information

There is a ticket on the Arma 2 Community Issue Tracker from kju discussing the first idea:
https://dev-heaven.net/issues/21591

Event Timeline

trnapster edited Additional Information. (Show Details)
trnapster set Category to Feature Request.
trnapster set Reproducibility to N/A.
trnapster set Severity to None.
trnapster set Resolution to Open.
trnapster set Legacy ID to 182767497.May 7 2016, 5:24 PM