Event Handlers – Arma 3
Introduction
An event handler (abbreviated to EH) allows you to automatically monitor and then execute custom code upon particular events being triggered.
These event handlers relate to commands such as: addEventHandler, removeEventHandler, removeAllEventHandlers.
General MP Note
As opposed to OFP event handlers, a respawned unit retains the EHs it had before, so it is no longer required to re-add EHs after respawning.
The MP event handlers "MPHit", "MPKilled" and "MPRespawn" have to be assigned to the object by using addMPEventHandler.
Event Scripts
See also: Event Scripts for special event triggered scripts.
Lists
addEventHandler
Object event handler, always executed on the computer where it was added.
Example:
mySoldier addEventHandler ["Killed",{hint format ["%1 was killed by %2",name (_this select 0),name (_this select 1)];}]
Class | Description | Arguments | Effects | Since |
---|---|---|---|---|
AnimChanged |
Triggered every time a new animation is started. It can be assigned to a remote unit but will only fire on the PC where the actual addEventHandler command was executed. |
|||
AnimDone |
Triggered every time an animation is finished. It can be assigned to a remote unit but will only fire on the PC where the actual addEventHandler command was executed. |
|||
AnimStateChanged |
Triggered every time an animation state changes. Unlike AnimChanged and AnimDone, it is triggered for all animation states in a sequence. It can be assigned to a remote unit but will only fire on the PC where the actual addEventHandler command was executed. |
|||
ControlsShifted |
Triggers when controls of vehicle are shifted (pilot->co-pilot, co-pilot->pilot). Works for both, "Take" and "Release" controls actions. Event only triggers on PC where vehicle is local and EH was added. NOTE: If helicopter is local to the server and co-pilot takes controls, the helicopter changes locality to co-pilot PC. This means that if "ControlsShifted" EH was added on both server and client, "Take Controls" action will trigger EH on the server PC, but subsequent co-pilot "Release Controls" action will trigger it on co-pilot's PC. |
|||
CuratorFeedbackMessage |
Triggered when curator attempts invalid action in curator interface. Each error has its own unique ID, recognized values are:
|
|||
CuratorGroupDeleted |
Triggered when a group is deleted in curator interface. |
|||
CuratorGroupDoubleClicked |
Triggered when a group is double-clicked on in curator interface. |
|||
CuratorGroupEdited |
Triggered when a group is moved or rotated in curator interface. |
|||
CuratorGroupPlaced |
Triggered when new group is placed in curator interface. |
|||
CuratorGroupSelectionChanged |
Triggered when a group is selected in curator interface. |
|||
CuratorMarkerDeleted |
Triggered when a marker is deleted in curator interface. |
|||
CuratorMarkerDoubleClicked |
Triggered when a marker is double-clicked on in curator interface. |
|||
CuratorMarkerEdited |
Triggered when a marker is moved in curator interface. |
|||
CuratorMarkerPlaced |
Triggered when new marker is placed in curator interface. |
|||
CuratorMarkerSelectionChanged |
Triggered when a marker is selected in curator interface. |
|||
CuratorObjectDeleted |
Triggered when an object is deleted in curator interface. |
|||
CuratorObjectDoubleClicked |
Triggered when an object is double-clicked on in curator interface. |
|||
CuratorObjectEdited |
Triggered when an object is moved or rotated in curator interface. |
|||
CuratorObjectPlaced |
Triggered when new object is placed in curator interface. |
|||
CuratorObjectRegistered |
Assign curator cost to every object in the game. This is the primary way how mission designer can limit what can curator placed. Expected returned value is an Array of Arrays with the same number of items as the input array. Example:
Cost of every object is defined by an array with following arguments:
Altrnatively, you can use scripting functions which will simplify cost settings:
|
|||
CuratorObjectSelectionChanged |
Triggered when an object is selected in curator interface. |
|||
CuratorPinged |
Triggered when a player pings his curator(s) by pressing Zeus key. To add player to specific curator, use addCuratorEditableObjects command. |
|||
CuratorWaypointDeleted |
Triggered when a waypoint is deleted in curator interface. |
|||
CuratorWaypointDoubleClicked |
Triggered when a waypoint is double-clicked on in curator interface. |
|||
CuratorWaypointEdited |
Triggered when a waypoint is moved in curator interface. |
|||
CuratorWaypointPlaced |
Triggered when new waypoint is placed in curator interface. |
|||
CuratorWaypointSelectionChanged |
Triggered when a waypoint is selected in curator interface. |
|||
Dammaged |
Triggered when the unit is damaged. In ArmA works with all vehicles not only men like in OFP. It can be assigned to a remote vehicle but will only fire on the PC where the actual addEventHandler command was executed. (If simultaneous damage occured (e.g. via grenade) EH might be triggered several times.) |
|||
Engine |
Triggered when the engine of the unit is turned on/off. |
|||
EpeContact |
Triggered when object collision (PhysX) is in progress. It can be assigned to a remote vehicle but will only fire on the PC where the actual addEventHandler command was executed. |
|
||
EpeContactEnd |
Triggered when object collision (PhysX) ends. It can be assigned to a remote vehicle but will only fire on the PC where the actual addEventHandler command was executed. |
|
||
EpeContactStart |
Triggered when object collision (PhysX) starts. It can be assigned to a remote vehicle but will only fire on the PC where the actual addEventHandler command was executed. |
|
||
Explosion |
Triggered when a vehicle or unit is damaged by a nearby explosion. It can be assigned to a remote vehicle but will only fire on the PC where the actual addEventHandler command was executed. |
|||
Fired |
Triggered when the unit fires a weapon. |
|
||
FiredNear |
Triggered when a weapon is fired somewhere near the unit or vehicle. It is also triggered if the unit itself is firing. (Exception(s): the Throw weapon wont broadcast the FiredNear event) |
|
||
Fuel |
Triggered when the unit's fuel status changes between completely empty / not empty (only useful if the event handler is assigned to a vehicle). |
|||
Gear |
Triggered when the unit lowers/retracts the landing gear (only useful if the event handler is assigned to is a member of the class "Plane"). |
|||
GetIn |
Triggers when a unit enters a vehicle. It can be assigned to a remote vehicle but will only fire on the PC where the actual addEventHandler command was executed. This EH is neither triggered upon a change of positions within the same vehicle nor by the moveInXXXX commands. However it is triggered by a "GetInXXXX" action. In vehicles with multi-turret setup, entering any turret will show "gunner" for position. |
|||
GetOut |
Triggers when a unit gets out from a vehicle. It can be assigned to a remote vehicle but will only fire on the PC where the actual addEventHandler command was executed. This EH is triggered by both the moveOut command and by "GetOut" action. |
|||
HandleDamage |
Triggers when the unit is damaged and fires for each damaged selection separately. Works with all vehicles. This EH can accept a remote unit as argument however it will only fire when the unit is local to the PC this event handler was added on. For example, you can add this event handler to one particular vehicle on every PC. When this vehicle gets hit, only EH on PC where the vehicle is currently local will fire. If code provided returns a numeric value, this value will overwrite the default damage of given selection after processing. Return value of 0 will make the unit invulnerable if damage is not scripted in other ways (i.e using setDamage and/or setHit for additional damage handling). If no value is returned, the default damage processing will be done. This allows for safe stacking of this event handler. Only the return value of the last added "HandleDamage" EH is considered. Notes:
Additional Celery's explanation. |
|
||
HandleHeal |
Triggered when unit starts to heal (player using heal action or AI heals after being ordered). Triggers only on PC where EH is added and unit is local. If code returns false, engine side healing follows. Return true if you handle healing in script, use AISFinishHeal to tell engine that script side healing is done. See also lifeState and setUnconscious commands. |
|||
Hit |
Triggered when the unit is hit/damaged. Is not always triggered when unit is killed by a hit. |
|||
HitPart |
Runs when the object, it was added to, gets injured/damaged. It returns the position and component that was hit on the object within a nested array, this is because the model may have more than selection name for the hit component. While you can add "HitPart" handler to a remote unit, the respectful addEventHandler command must be executed on the shooter's PC and will only fire on shooter's PC as well. Additionally, if the unit gets damaged by any means other than shooter's shooting, "HitPart" will not fire. Because of this, this event handler is most suitable for when the shooter needs feedback on his shooting, such as target practicing or hitmarker creation. |
|
||
Init |
Triggered on mission start or when a vehicle is created on the fly using createVehicle. |
|
||
IncomingMissile |
Triggered when a guided missile locked on the target or unguided missile or rocket aimed by AI at the target was fired. |
|||
Killed |
Triggered when the unit is killed. Be careful when the killer has been a vehicle. For most cases the reference of the vehicle is the same as the effectiveCommander, but not always. |
|||
LandedTouchDown |
Triggered when a plane (AI or player) touches the ground. |
|||
LandedStopped |
Triggered when an AI pilot would get out usually. Not executed for player. |
|||
Local |
Triggered when locality of object in MP is changed. |
|||
Respawn |
Triggered when a unit respawns. |
|||
Put |
Triggers when a unit puts an item in a container. |
|||
Take |
Triggers when a unit takes an item from a container. |
|||
SoundPlayed |
Triggered when player is making noises when injured or fatigued. |
|||
WeaponAssembled |
Triggers when weapon gets assembled. |
|||
WeaponDisassembled |
Triggers when weapon gets disassembled. |
addMPEventHandler
Global object event handler, executed on every connected machine.
Example:
mySoldier addMPEventHandler ["MPKilled",{hint format ["%1 was killed by %2",name (_this select 0),name (_this select 1)];}]
Class | Description | Arguments | Effects | Since |
---|---|---|---|---|
MPHit |
Triggered when the unit is hit/damaged. EH can be added on any machine and EH code will trigger globally on every connected client and server. Add it only on server because if you have 10 machines on network and add this EH to every machine, when triggered the EH code will be executed 10 x 10 = 100 times. Is not always triggered when unit is killed by a hit. Most of the time only the Killed event handler is triggered when a unit dies from a hit. The hit EH will not necessarily fire if only minor damage occurred (e.g. firing a bullet at a tank), even though the damage increased. Can also trigger several times for an explosion (direct and indirect damage). Does not fire when a unit is set to allowDamage false. However it will fire with "HandleDamage" EH added alongside stopping unit from taking damage addEventHandler ["HandleDamage",{0}]; Will not trigger when unit is dead. This EH must be used in conjunction with the addMPEventHandler command. Note: Call a function from the MPHit EH code space, rather to define the full code in there directly. The reason is the code space will be transferred over network on each event activation - so keep the data as small as possible! |
|||
MPKilled |
Triggered when the unit is killed. EH can be added on any machine and EH code will trigger globally on every connected client and server. Add it only on server because if you have 10 machines on network and add this EH to every machine, when triggered the EH code will be executed 10 x 10 = 100 times. |
|||
MPRespawn |
Triggered when a unit respawns. Notes:
|
addMissionEventHandler
Mission event handler, always executed on the computer where it was added.
Example: addMissionEventHandler ["Loaded",{playMusic "EventTrack03_F_EPB";}]
Class | Description | Arguments | Since |
---|---|---|---|
Ended |
Triggered when mission ends, either using trigger of type "End", endMission command, BIS_fnc_endMission function or ENDMISSION cheat. |
|
|
Loaded |
Triggered when mission is loaded. |
addMusicEventHandler
Music event handler, always executed on the computer where it was added.
Example: addMusicEventHandler ["MusicStop",{playMusic (_this select 0);}]
Class | Description | Arguments | Since |
---|---|---|---|
MusicStart |
Triggers when CfgMusic sound starts playing, after being executed with playMusic command. This event handler needs to be added with addMusicEventHandler command and removed with removeMusicEventHandler. |
|
|
MusicStop |
Triggers when CfgMusic sound finished playing, after being executed with playMusic command. Note that EH will not be triggered if you force stop the music with playMusic "". This event handler needs to be added with addMusicEventHandler command and removed with removeMusicEventHandler. |
|