Affect whole side

[Pr0ph3t]

strange.. This really doesn't make sense I'm going to try again

[Pr0ph3t]

I get an unknown operator error msg.. It detects " and halts the command I think its my ver hee hee

[Planck]

You know you really are crippling yourself sticking with version 1.0

Why don't you download the FREE patches to take you to version 1.46?

There are a lot of extra commands and official vehicles added in the updates that you can't use.

In the long run it makes sense to update.


Planck

[Pr0ph3t]

I know its free. I know there's lots of goodies.
And I will get all the bells and whistles for the sequel. But for now its 1.0 all the way. I've been working on this campaign for about a year. Now near the end suddenly I'm gonna overhaul? Forget it it's going to add another 6 months to production time. Now, if this meant I was going to distribute something of quality of something not then yes I would upgrade. But I've put a lot of quality in this campaign, and I only need the odd command that is not avaliable. 9/10 times there's a work around and when there isn't usually its not necessary or I find a better way around it.

[Planck]

Let me see now, you have been using the command allowFleeing.......correct?

EDIT: I got the command wrong, but you know what I mean....I meant allowDammage.

When you release your campaign, if you do that is, everone who does not have version 1.0 will not be able to use that command because it has been removed in later versions.

I don't know about any other older commands that you have used that might have a similar effect.

I'll try to 'think' of a way around it.


Planck

[Pr0ph3t]

Oh don't worry about that.. Its only 1 or 2 missions out of 50 that use it.. And besides.. Why don't I just remove the original campaign and just leave the raw game with my campaign and distribute it that way ...

Look I know it sounds piratish, but everyone here has OFP and besides.. I don't really see pushing OFP 1.0 with the original campaign deleted as piracy compared to the distance OFP has come. Anyway, I'm sure this is going to raise all type of controversy but understand. I just like to create, and I like to pass on to other people. So don't see it as a warez statement, rather as just an error free way of distributing my campaign

[Planck]

You could try making the trigger as usual, but put:

[] exec "nameofscript.sqs"

in the On Activation field.

Then make the script with the contents:

"_x setcombatmode ""red""" foreach list XXX
exit

Don't forget to name the trigger and replace the XXX with the name you use.

Put this script in your mission folder.


Planck

[Pr0ph3t]

Yah.. Sounds good I'm gonna try it in 30mins. Thanks for all the quick responses btw!

So a command that isn't recognized inside the editor may sometimes be recognized if read from a sqs file?

[Planck]

Sometimes   ;D


Planck

[Peter_Bullet]

You mean {} don't work with YOUR version?

Why not setting a variable: VariableName="red" (type somewhere) then after that "_x setCombatMode VariableName" forEach list xxx

(VariableName="red"; "_x setCombatMode VariableName" forEach list xxx)

[Pr0ph3t]

YOU BASTARD!

That's great! I can do the same with the inflame for the unlit campfire detection. I can't believe I didn't think of that. Great thinking bud.. I'm gonna test it soon and let you guys know

[Pr0ph3t]

bleh. A great though my friend but it simply doesn't work.

I don't understand why setcombatmode "red" can't affect every unit on the map. and when I do it the variablename way the command passes.. But the soldiers don't react.

[Blanco]

euh...is your trigger activated by a side?

[Pr0ph3t]

of course d00d

[Peter_Bullet]

Maybe not putting them in a same trigger? I hope you know that the setCombatMode affects wether the unit will fire or not. It doesn't make him put his gun on his back or his hand.

Maybe trying a script. (I'm sure you know how to do it but I write it anyway)

_i=0
_array = list trigger
_count = count _array

#Loop
(_array select _i) setCombatMode "red"
_i = _i + 1
?_i < _count: goto "Loop"
exit