Bug #2809

[Dedicated]Setting mission parameters in server.cfg not working

Added by Whisper about 1 year ago. Updated 11 days ago.

Status:Closed Start:2009-07-13
Priority:High Due date:
Assigned to:- % Done:

90%
Category:Server
Target version:1.54.72888
Operating system: Mainboard chipset:
Graphics card: System RAM size:
Graphics card driver version: GPU VRAM size:
Affected ArmA II version:1.52.71816 server Audio card:Please specify!
Maxmem parameter:Not set Size of OS swap file:Please specify!
Difficulty:Not set I am using some Mods:No
Reproduced by another DH user:Yes I am using:
CPU:Please specify! Reproducible for you:Yes
Votes: 13

Description

Trying to force mission parameters in the missions list part of the server.cfg doesn't work, the server always use the default setting as set in description.ext, not the one asked in mission entry
syntax used in server.cfg:

class Missions
{
   class Mission01
   {
     ....
     param1 =xx;
     param2 =yy;
   }
}

Related issues

related to ArmA2 Community Issue Tracker - Feature #12427: server.cfg default multiple mission parameters for chosen missions Assigned 2010-07-28

History

Updated by Fireball 12 months ago

  • Due date set to 2009-10-13
  • Status changed from New to Feedback
  • Difficulty set to Not set

Still the case with 1.03 server?

Updated by Whisper 12 months ago

Still no go in 1.03, not tested yet in 1.04
BTW, how does the new parameter system in 1.04 fits in the config file?

Updated by kju 11 months ago

  • Affected ArmA II version changed from 1.02.58055 server to 1.04 BETA server
  • Reproduced by another DH user set to No

Not possible I guess..

Updated by Fireball 11 months ago

  • Due date changed from 2009-10-13 to 2009-11-13
  • Status changed from Feedback to Assigned
  • Affected ArmA II version changed from 1.04 BETA server to 1.04.59026
  • CPU set to Please specify!

Updated by Fireball 11 months ago

  • Tracker changed from Bug to Feature

Updated by kju 11 months ago

  • Tracker changed from Feature to Bug

Updated by kju 11 months ago

  • Affected ArmA II version changed from 1.04.59026 to 1.04 BETA server

Lets keep it a bug Fireball.
It was working for a1..

Updated by Fireball 11 months ago

  • Category changed from 174 to Server
  • Affected ArmA II version changed from 1.04 BETA server to 1.04.59026 server

Updated by Whisper 10 months ago

No change on this issue, even using the new paramters system.
I tried the settings indicated in the 1.03 beta Biki entry for the new parameters system:
http://community.bistudio.com/wiki/Arma_2:_Patch_v1.03.58899_Beta
I tried 2 settings :

1 class misionName
2   {
3      template = misionName.Chernarus;
4      difficulty = "recruit";
5      paramsArray = [1,0,5,40,10];
6   };

and

1 class misionName
2   {
3      template = misionName.Chernarus;
4      difficulty = "recruit";
5      paramsArray[] = {1,0,5,40,10};
6   };

Never got the mission starting with the settings I had asked for

Updated by Fireball 10 months ago

Are you sure that this is no typo in the Biki:

1 class misionName
2   {
3 ...

mision? mission?

Updated by Whisper 10 months ago

It's just a name, and the typo has no impact :)

the missions were rotating fine, just without the asked parameters

Updated by Fireball 10 months ago

  • Due date changed from 2009-11-13 to 2009-12-13

Ah, so the "misionName" was then the name of the mission you started? If yes, then I'm happy.

Updated by Whisper 10 months ago

Errr, what?
It has nothing to do with actual mission name, this name can be anything (as specified in Biki entry for server.cfg : http://community.bistudio.com/wiki/server.cfg )
The mission name is specified in the template = "..."; entry
I could put class tototutu { ...}; for any mission ;)

Updated by zGuba 9 months ago

  • Due date changed from 2009-12-13 to 2010-01-15

Updated by kju 6 months ago

  • Due date changed from 2010-01-15 to 2010-03-25
  • Affected ArmA II version changed from 1.04.59026 server to 1.05.62014 server

Updated by Dwarden 3 months ago

  • Assigned to set to Dwarden

Updated by kju 3 months ago

Example mission: MP_WarWelcome.utes

class Params 
{
    //Victory Conditions
    class VictoryTime
    {
        title = $STRWFMISSIONENDTIME;
        values[] = {-1,30,45,60,90,120,180,300};
        texts[] = {$STRWFNA,"30","45","60","90","120","180","300"};
        default = -1;
    };
    ...

Note the default -1 for class VictoryTime.

DS server.cfg

class Missions
{
    class MP_WarWelcome
    {
        template = "MP_WarWelcome.utes";
        difficulty = "mercenary";
        param1 = 300;
        param3 = 300;
        params1 = 300;
        params3 = 300;
        paramsArray = [300,300,300,-1,-1,-1,0,0,0,0,0,-1,-1,0,0];
//        paramsArray[] = {300,300,300,-1,-1,-1,0,0,0,0,0,-1,-1,0,0};
        templateparameter = [300,300,300,-1,-1,-1,0,0,0,0,0,-1,-1,0,0];
        parameter = [300,300,300,-1,-1,-1,0,0,0,0,0,-1,-1,0,0];
    };
};
Repro
  1. Launch DS with the given server.cfg
  2. Connect with client
  3. Notice the mission is automatically selected
  4. Log in as admin
  5. Go to parameters
  6. Notice no parameter has been changed via server.cfg

Updated by kju 2 months ago

  • Due date changed from 2010-03-25 to 2010-07-14
  • Status changed from Assigned to Feedback
  • Audio card set to Please specify!
  • Size of OS swap file set to Please specify!

Still valid in 1.07 / OA?

Updated by Whisper 2 months ago

Need Linux installed 1st, answer will come later :)

Updated by Dwarden about 1 month ago

  • Priority changed from Normal to High
  • Affected ArmA II version deleted (1.05.62014 server)
  • I am using some Mods set to No
  • Reproducible for you set to No

still issue?

Updated by kju about 1 month ago

  • Due date changed from 2010-07-14 to 2010-08-01
  • Status changed from Feedback to Assigned
  • Affected ArmA II version set to 1.52.71816 server

yes. Killswitch just tested this recently.
Also see my nice repro from above. :)

Updated by Dwarden about 1 month ago

  • Target version set to Upcoming version
  • % Done changed from 0 to 10

Updated by Dwarden about 1 month ago

  • Status changed from Assigned to Resolved
  • % Done changed from 10 to 90
  • Reproduced by another DH user changed from No to Yes
  • Reproducible for you changed from No to Yes

Updated by kju about 1 month ago

  • Due date deleted (2010-08-01)
  • Assigned to deleted (Dwarden)

great news!

Updated by CarlGustaffa about 1 month ago

Works for us with latest beta. Only Domination in the mission list though, so far, only to test the feature.

Updated by kju about 1 month ago

  • Status changed from Resolved to Closed
  • Target version changed from Upcoming version to 1.53 BETA

ty

Updated by ade about 1 month ago

Work only for missions started while entering into a empty server, mission start automatically with server.cfg parameters.

Starting the same mission from Missions menu, does not set parameters defined into server.cfg, but switched back to mission defaults.

Updated by kju about 1 month ago

Which is to be expected. You define them for class missions only not for missions globally.
Best to edit the default in the mission for you desire.

Updated by Whisper about 1 month ago

I realise I've not added my big "thank you" here :) Good to see this annoyance solved \o/

Updated by mr.g-c about 1 month ago

Yes awesome thank you!
Seems like Dwarden@BIS is a really big win for the community!

Updated by kju 11 days ago

  • Target version changed from 1.53 BETA to 1.54.72888

Also available in: Atom PDF