Feature #15192

Bring back mergeConfig with OK state to use MP.

Added by kju almost 5 years ago. Updated almost 3 years ago.

Status:Assigned Start date:11/16/2010
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:Scripting: Problem
Target version:-
Affected ArmA II version:Please select... First affected ArmA II version:
Reproduced by another DH user:No Single / Multi Player?:
I am using some Mods:No BIForumURL:
I am using: NGUrl:
Reproducible for you:No WIKIurl:
Related to content of DLC:

Description

http://forums.bistudio.com/showthread.php?p=1789446#post1789446

Maruk:

Until proper system to handle its multiplayer effects is in place, the only way to use it is to "downgrade" to the last beta that had it.

Topic about mergeConfig with all pros and cons.

In short it would be a very powerful and useful to for mission designers.


Related issues

related to ARMA2 Community Issue Tracker - Feature #21591: Per mission config space modification. Assigned 06/30/2011
related to ARMA2 Community Issue Tracker - Feature #13449: [Development] Speed up game loading time for config work Feedback 09/02/2010
related to ARMA2 Community Issue Tracker - Feature #25606: Public availabile developer/debug version Assigned 10/18/2011

History

Updated by kju almost 5 years ago

  • Subject changed from Bring back mergeConfig with OK to use MP. to Bring back mergeConfig with OK state to use MP.

Updated by Whisper over 4 years ago

Do we need a script command for this functionality? Script can be abused.

Another way could be to enable config statements inside description.ext file. This would restrict new class creation to mission makers, not scripters (ie, potentially hacker)

Which doesn't resolve the fact you cannot unload the classes, unless you can mark their scope for mission use only inside the description.ext (defining something in between "private" and "public", reserved for current mission only?)

Updated by kju over 4 years ago

Good idea!

Updated by Sickboy over 4 years ago

As an addon maker I resent the idea of only being able to use it from description.ext :D
Also it's a workaround for a problem that only really exists on pub-servers, while the application of the command is imo more broad.
If it would only be available from desc.ext, I wouldn't mind a server-config flag to have scripting command :D

Updated by Xeno over 4 years ago

There is another problem with description.ext.

It's beeing read every time when the server "reads" the missions, trying to get the mission name from desc.ext.
And, when you start the server it gets read four times before the mission finally starts :P

Updated by kju over 4 years ago

Good points as well.

I guess making it only ext only is not worth the trouble,
as long as cheaters can still abuse all other commands.

Updated by Whisper over 4 years ago

Mmmh, I must admit I didn't think about usage of this command in an addon :)
Is there a real benefit in using a mergeConfig command in addon over using hard defined configurations inside addon?

I'm only seeing this command through the point of view of being able to add/tweak the game on public, addonless servers, which is a big step forward (public server shouldn't be overlooked)

Updated by Sickboy over 4 years ago

Sure; different config loading depending on different conditions, may it be user settings/preferences, or a dynamic/random config etc.
What about changing the walking speed by adjusting animations on the fly, based on Stamina? :)

Also available in: Atom PDF