Scripting Discussion (dev branch)

So, lifting\towing and all that can be more realistic now? Nice.

Would be nice to know if new commands use local / global argument and if the effect is local / global

I really like Killzone's suggestion here: http://killzonekid.com/arma-scripting-tutorials-syncing-map-clock-with-itemwatch/

Improving the watch item thanks to the Put and Take eventhandler fix by Japapatramtara :icon_twisted:

Nice one KK.

SetObjectTexture still needs a Global equivalent.

http://feedback.arma3.com/view.php?id=13032

Tricky bug:

whenever you want to pick enemy infantrymen near some unit, you may code:

_enemies = _unit nearEntities ["Man", _radius];

Then you may filter enemy units via getFriend ...

However, the above code will pick (at least) any snakes around.

Yes, snakes are kind of "Man" in Arma3 ...

And by the way, they're always enemy too.

So using the above piece of code you'll end up processing more units than needed (as well as wrong ones).

You may write instead:

_enemies = (_unit nearEntities ["Man", _radius]) - (_unit nearEntities ["Animal", _radius]);

Cumbersome, but looks like it may overcome the problem.

BIS please fix this!

just use CAManBase

;2537967']just use CAManBase

Yes, easier ;)

SetObjectTexture still needs a Global equivalent.

http://feedback.arma3.com/view.php?id=13032

Agreed and voted up.

SetObjectTexture still needs a Global equivalent.

http://feedback.arma3.com/view.php?id=13032

indeed, manually syncing this to players and JIP clients using scripts inside the mission is a bit of a drag, and uses unnecessary resources..

I think suppressFor is broken... or how do I know it's working as intended?

I think suppressFor is broken... or how do I know it's working as intended?

Try issuing the order to a machinegunner.

I saw close to no effect for riflemen.

The script which makes the offroad randomized is not synced between players or JIP compatible: http://feedback.arma3.com/view.php?id=15618

This has bugged me since day 1 of the Alpha.

whats the script that makes helicopters land very quickly and smoothly?

those who played campaign will know what im on about.

whats the script that makes helicopters land very quickly and smoothly?

those who played campaign will know what im on about.

http://forums.bistudio.com/showthread.php?167405-Campaign-Episode-1-SURVIVE-Feedback-thread-**-SPOILER-WARNING!-**&p=2542427&viewfull=1#post2542427 :)

It's not a magic script, it's BIS_fnc_unitCapture/unitPlay. It lets you record a path and then play it back on the unit. Basically, while recording, you pilot the chopper yourself and make it land how you want, then 'play' it on an AI unit.

thanks buddy

We could use a Physx based rope object for things like towing, having a vehicle tied down, and lifting: http://feedback.arma3.com/view.php?id=15658

There is a fix of script command removeAllActions in today's dev branch update. This fix is changing syntax of this command. If you are working with this command, you need to fix your scripts. This fix won't be a part of tomorrow's stable branch update!

Old syntax: unit removeAllActions index

New syntax: removeAllActions unit

Ticket on Feedback Tracker: http://feedback.arma3.com/view.php?id=5317

• ctrlAddEventHandler and displayAddEventHandler now accept game code as well as strings
  

Thanks, much appreciated :)

Linking in case anyone misses it: Stacked Event Handlers.

- addItemToBackpack

- addItemToVest

- addItemToUniform

Hello,

Any chance for these commands to receive an array version? Like this command.

So it can work this way _x addItemToUniform ["Chemlight_red",2].

Lead programmer Ondřej Martinák changed behaviour of event handler HandleDamage. This change is a part of today's update of dev branch.

Old behaviour:

Code provided must return a value what should be the damage of given selection after processing. No return value or return value 0 will make the unit invulnerable if damage is not scripted in other ways. If you want default processing to be done, be sure to return _this select 2.

New behaviour:

Code provided can return a value what should be the damage of given selection after processing. Return value 0 will make the unit invulnerable if damage is not scripted in other ways. No return value means that event handler won't affect damage given to unit.

Motivation:

Working with these event handlers should be easier now. If there is more event handlers of same type, then damage from the last one is used. But it is difficult to find out which of them is the last one in many situations. Now you can add event handler with no return value. This event handler won't affect damage modified by event handler. This modification won't be affected even in case it was made before the start of event handler with no return value.

Any chance of having the same behaviour for HandleHeal? It's quite complicated to handle healing right now.

Any chance of having the same behaviour for HandleHeal? It's quite complicated to handle healing right now.

Also, while we're at healing, also make self-healing fire the HandleHeal handler ?

Thanks BIS :D