Results 1 to 6 of 6

Thread: Need less missions.

  1. #1

    Need less missions.

    I am currently making a mission where I use the SOM to call in support. The one issue I have with the SOM is it is creating missions for me every 10 seconds. Is there a way to disable the SOMs mission giving request and make it work only on the support items?

  2. #2
    Here ya go, try this

    You can override certain SOM settings by setting a "settings" variable in a SOM (do this during the first 2 seconds of a mission!). In this Array you can send the SOM your custom pool of SecOps for this mission, you can disable the standard H.Q. radio communications, you can set different callsigns and set an initial delay (default is 30 seconds). If you do not want to set all settings, you may pass nil for those that you wish to leave on their default values. A typical settings Array can look like this:

    Code:
    private ["_pool", "_hq", "_callsigns", "initialDelay", "_autoReinforce", "_settings"];
    _pool =
    [
    	"ambush"
    ];
      
    _hq = false;
      
    //Team text, team speech, H.Q. text, H.Q. speech.
    _callsigns = ["Razor", ["Razor"], "Frostbite", ["Frostbite"]];
      
    //Delay in seconds before starting random SecOps selection.
    _initialDelay = 60;
      
    //Should an automatic Reinforce be triggered when there are casualties?
    //Default is true.
    _autoReinforce = false;
      
    _settings =
    [
    	_pool,
    	_hq, 
            _callsigns, 
            _initialDelay, 
            _autoReinforce
    ];
      
    _som setVariable ["settings", _settings];

  3. #3
    Try putting this in the init of your Secondary Ops Game Logic.

    Code:
    this setVariable ["settings", [[], true, nil, nil, false]];
    Removes the missions, but retains the support functions. You can still add your own missions via script (pretty sure).

  4. #4
    Quote Originally Posted by beita View Post
    Try putting this in the init of your Secondary Ops Game Logic.

    Code:
    this setVariable ["settings", [[], true, nil, nil, false]];
    Removes the missions, but retains the support functions. You can still add your own missions via script (pretty sure).
    Wow, much simpler than the top said method =P

    Actually, it seems like it also disabled the support from artillery actually. Looks like im going with the top method.
    Last edited by Kocrachon; Jun 11 2009 at 21:25.

  5. #5
    Well, the top method is in fact the same as that line of code. It is simply written to be easier to read/understand.

    How are you calling the artillery? I have had no trouble getting AI fire missions with this setting on the SOM.

  6. #6
    Quote Originally Posted by beita View Post
    Well, the top method is in fact the same as that line of code. It is simply written to be easier to read/understand.

    How are you calling the artillery? I have had no trouble getting AI fire missions with this setting on the SOM.
    I have a radio trigger, which when I radio it gives me the option through the SOM to call artillery. Its a M119 team sitting on the hill. Once i put that script in, the artillery support doesnt show up anymore.

    never mind It works now, Im not sure what I was doing wrong before hand.
    Last edited by Kocrachon; Jun 11 2009 at 21:34.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •