Page MenuHomeFeedback Tracker

Re-insert MergeConfig script command
Closed, ResolvedPublic


We wish to have back the mergeConfig script function, that function is used to merge a file that contain a configuration class of the object with the engine object, that make model maker able to work more fast because up to now any model modification require to restart ArmA.

That command open a lot of new possibilities for model makers and scripters, some of them are: create custom animations, modify speed, maxheight (aircraft), make models able to do or to don't do something, and a lot of other things that can increase ArmA flexibility.

Script usage (wished):

object mergeConfig "file.clss"; (please note, extension is for represent class file).

object mergeConfig object; (class can be stored in an object)

object mergeConfig variable; (could be modify only one variable)

mergeConfig "file.clss"; (can create custom classes)

object>>object2>>objectN mergeConfig "file.clss"; (can load/create class in trees)

I avioded to repeat the combinations of that commands for not be useless repetitive.


Legacy ID
Additional Information

mergeConfig was avaiable for some times in ArmA 2 OA, it could be improved and insert in ArmA 3

Event Timeline

FlorianGeyer edited Additional Information. (Show Details)
FlorianGeyer set Category to Scripting.
FlorianGeyer set Reproducibility to N/A.
FlorianGeyer set Severity to None.
FlorianGeyer set Resolution to Fixed.
FlorianGeyer set Legacy ID to 548422147.May 7 2016, 3:09 PM

Would cause a hackfest.

Couldn't you protect it by making it only executed by the mission?

MergeConfig load the configuration only for current session, new join in another server restore default configs.

in today's dev branch changelog:

Added: arma3diag.exe (includes diagnostic tools, excludes MP)

This command is a part of the new arma3diag.exe. Marking as fixed.

MadDogX added a subscriber: MadDogX.May 7 2016, 3:09 PM

Mass closing tickets marked as resolved more than 1 month ago.

If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.