Jump to content
Sign in to follow this  
a_blunt_rifle

Secop help!

Recommended Posts

Hello does anyone know of a way to increase the secop time between missions? such as once you complete a secop mission, instead of there being a 1-2minute wait time for the next one to come, is there a way to increase the time between to about 20min?

Share this post


Link to post
Share on other sites
Hello does anyone know of a way to increase the secop time between missions? such as once you complete a secop mission, instead of there being a 1-2minute wait time for the next one to come, is there a way to increase the time between to about 20min?

Yes, good question. Is there something that can just be put in the unit init box?

Share this post


Link to post
Share on other sites

you just put this line in the init line of the SOM module (named itself 'som1'):

som1 setVariable ["settings", [["ambush","attack_location","defend_location","destroy"], true, ["Razor", ["Razor"], "H.Q.", ["HQ"]], 60, false, 10, 1, [400, 700]]];

the last numbers are:

- 60 seconds = initial delay before the FIRST mission come out

- autoReinforce (if a unit/s in your squad die, then HQ will send you another one unit/s) = false

- 10 seconds = delay between SecOp missions

- 1: random chance to spawn a SecOp mission (1 = 100%)

- [400, 700]: min and MAX distance a mission will spawn from the player

Share this post


Link to post
Share on other sites
you just put this line in the init line of the SOM module (named itself 'som1'):

the last numbers are:

- 60 seconds = initial delay before the FIRST mission come out

- autoReinforce (if a unit/s in your squad die, then HQ will send you another one unit/s) = false

- 10 seconds = delay between SecOp missions

- 1: random chance to spawn a SecOp mission (1 = 100%)

- [400, 700]: min and MAX distance a mission will spawn from the player

(I edited your code line.)

[b]som1[/b] setVariable ["settings", [["ambush", "attack_location", "defend_location", [color="Red"]"destroy"[/color]], true, ["[b]Razor[/b]", ["[b]Razor[/b]"], "H.Q.", ["HQ"]], 60, false, 10, 1, [400, 700]]];

I thought where 'your' 1 is, was for the chance of WHICH mission would be spawned? I have to go research.

Also, Blunt, the som1 is what goliath named his SOM (SecOp module). I just name mine SOM. But the line has to match the name of the module. You can just use the word... this ... in the place of a SOM name in the code line.

Where Razor is, you can change that to a dif call sign, like Alpha, or Beta. I guess by now you have read the wiki, right? :)

(EDIT: Typo.)

Edited by CyOp

Share this post


Link to post
Share on other sites
(I edited your code line.)

[b]som1[/b] setVariable ["settings", [["ambush", "attack_location", "defend_location", [color="Red"]"destroy"[/color]], true, ["[b]Razor[/b]", ["[b]Razor[/b]"], "H.Q.", ["HQ"]], 60, false, 10, 1, [400, 700]]];

I thought where 'your' 1 is, was for the chance of WHICH mission would be spawned? I have to go research.

Also, Blunt, the som1 is what goliath named his SOM (SecOp module). I just name mine SOM. But the line has to match the name of the module. You can just use the word... this ... in the place of a SOM name in the code line.

Where Razor is, you can change that to a dif call sign, like Alpha, or Beta. I guess by now you have read the wiki, right? :)

(EDIT: Typo.)

thanks for the correction CyOp! ;)

Share this post


Link to post
Share on other sites

Yeah, I have a bad habit of doing that. ;)

What about the - 1 - . I have not researched that yet. Which mission, or if it will spawn a mission?

Share this post


Link to post
Share on other sites
Yeah, I have a bad habit of doing that. ;)

What about the - 1 - . I have not researched that yet. Which mission, or if it will spawn a mission?

It's the probability to spawn a mission. Missions are always random.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×