Event Handlers – Arma Reforger

Script Invokers

• An Event Handler can be created using a ScriptInvoker class.
• Any Script Invoker signature can be created using typedef - see ScriptInvoker Usage - Signature Declaration.
• Using the ScriptInvoker class itself is considered bad practice and must be avoided.
• As Script Invokers are big objects and can be numerous, it is good practice to not instanciate them by default but to rather create them on request, using their getter - saving memory.

ⓘ

See ScriptInvoker Usage and its Signature Declaration section for tutorials on how to use Script Invokers.

Event Handler Manager Component Events

The EventHandlerManagerComponent groups the following events under its category:

Event	Class	Description
OnADSChanged	CharacterControllerComponent
OnConsciousnessChanged
OnInspectionModeChanged		on player character which switches in/out of inspection mode
OnMagazineCountChanged	InventoryStorageManagerComponent
OnDestroyed	DamageManagerComponent	when the default hit zone is set to destroyed
OnCompartmentEntering	BaseCompartmentManagerComponent
OnCompartmentEntered
OnCompartmentLeft
OnCompartmentLeaving
OnLightStateChanged	BaseLightManagerComponent
OnTurretReload	TurretControllerComponent	isFinished is true when reload is done and false when it started
OnADSChanged		on player character which switches to ADS TurretControllerComponent can also trigger this event
OnWeaponChanged	BaseWeaponManagerComponent
OnMuzzleChanged	BaseWeaponComponent
OnAmmoCountChanged	BaseMuzzleComponent	Both weapon and character can raise this event (see BaseWeaponManagerComponent)
OnMagazineChanged
OnProjectileShot
OnFiremodeChanged
OnWeaponAttachmentChanged	WeaponComponent	isAttached is true if attachmentEntity was attached to the weapon, and false if it was detached
OnZeroingChanged		currently does not carry currentMuzzle
OnGrenadeThrown	WeaponSlotComponent
HHMMSS	TimeAndWeatherManagerEntity	Triggers based on TimeAndWeatherManagerEntity's TIME_EVENT_PERIODICITY value: 0: never 1: every hour 2: every minute 3: every second
OnDayStart
OnNightStart

Entity Event Handlers

ⓘ

See also Entity Lifecycle.

The following events are present and available in the IEntity class - read the code documentation to learn more about them and how to use them.

ⓘ

E in e.g EOnInit stands for Event (not Entity).

Event	Description
EOnInit	Event after the entity is allocated and initialised.
EOnVisible	This event triggers when the entity is made visible (versus being invisible).
EOnFrame	This event, as its name suggests, triggers on each simulation frame.
EOnPostFrame	Triggers after physics update.
EOnFixedFrame	⚠ This event can be called on another thread than the main thread. This means that you must avoid any modifications on other entities during this event!
EOnFixedPostFrame
EOnAnimEvent	Event from the animation system
EOnPhysicsActive	Triggers on (de)activation of the RigidBody's physics.
EOnPhysicsMove	Triggers when the physics engine moves this entity.
EOnSimulate	Happens before physics engine iteration - called from sub-iterations.
EOnPostSimulate	Happens after physics engine iteration. Happens once per frame.
EOnJointBreak	Triggers when a joint attached to this entity's RigidBody is broken.
EOnTouch	Event when touched by another entity. It requires the entity to have TouchComponent.
EOnContact	Triggers when contact with another RigidBody has been registered.
EOnDiag	Happens every frame after EOnFrame when "Entity Diag" is enabled in the Diag Menu (e.g Workbench).
EOnUser0
EOnUser1
EOnUser2
EOnUser3
EOnUser4