Talk:Arma 3: Event Handlers

Dammaged

Appears to only trigger if the damage is greater than 0.5

Repro:

• Add to player init

player addEventHandler ["Dammaged", { hint format ["Damage: %1", _this select 2]; }];

• Set elevation to 5 metres.
• Preview.
• Exit.
• Set elevation to 4.5 meters.
• Preview.

You may need to fiddle with those figures a bit, but it's a quick and dirty method to test.

Observe: Only damage above 0.5 is hinted.

Am I wrong, or should this be noted in the documentation?

Fred Gandt (talk) 06:54, 3 March 2014 (CET)

-- Yes, Dammaged EH is less sensitive than HandleDamage, not sure if there is a defined threshold.

So we should add a note to the documentation? I'm pretty sure a threshold of 0.5 exists, but that obviously needs testing of verification from bistudio to justify an absolute statement. I'd consider any verifiable fact that affects returns to be important to note, even if the fact is imprecise. A note to the effect that "Dammage will not necessarily trigger for < 0.5 damage", would at least save some folk the trouble I had trying to figure out WTF was going on. Fred Gandt (talk) 04:30, 4 March 2014 (CET)

-- I wouldn't put any definite numbers if I were you. It needs to be tested not only with units and as far as I remember for vehicles you can get EH triggered for damages < 0.5. I personally think copy paste from "Hit" EH where it explains sensitivity would be sufficient.

I'm not seeing Dammage EH triggering for less than 0.5 on Pawnees, Hunters and others, but sure, without confirmation (it'll be in the code somewhere), figures are tough to justify. I agree; a copy-paste of the note in Hit EH would be a start (I noticed that after my last comment here). At least it gives a clue to expect less than obvious behaviour. Fred Gandt (talk) 13:42, 4 March 2014 (CET)

Curator handler locality

"Curator Event Handlers are also added with addEventHandler command and are supposed to be added to curator object (not player object) and where curator object is local and will be executed only where curator is local (i.e., on computer of player who's in control of it)."

Assuming there can be more than one possible curator (user not object and perhaps not simultaneously), and a handler is added during the curation by Player 1, will the EH be local to Player 2 if they take over the curator role?

Also, I suggest this grammatical structure and wording

"Curator Event Handlers are also added with the addEventHandler command, are supposed to be added to the curator object (not the player object), where the curator object is local, and will be executed only where the curator is local (i.e. on the computer of the player who's in control of it)."

Although I'm not sure yet if curator should be "a curator" or "the curator". I assume there can be only one (object), even if there are multiple possible users of it? -- Fred Gandt (talk/contribs) 13:23, 22 April 2014 (CEST)