InteractiveUsedEvent

Announces the BEGINNING of an interaction - chopping a tree, mining an ore, opening a door, taking a zaap - not its result. Nothing here says whether the harvest succeeded or what it yielded.

IT IS BOTH AN ANSWER AND A BROADCAST. When the actor is you, it is the server accepting your InteractiveUseRequest (a refusal comes as InteractiveUseErrorEvent instead, and this event is then never sent). It is also broadcast for every other character, monster and NPC that starts an interaction, so most arrivals are about someone else.

HOW TO RECOGNISE THE ANSWER TO YOUR OWN REQUEST - it does not echo the request:

- entity_id is your character's id; - element_id is the element you sent in the request; - skill_id is the skill_id of the action you picked - the request carried that action's skill_instance_uid, which never comes back.

WHAT TO DO WHEN IT NAMES YOU

1. Consider the request answered: you may use that element again later. 2. If duration is above zero, the use is TIMED and you are busy: it lasts duration x 100 ms (duration is in TENTHS OF A SECOND - 30 is three seconds). Send no further InteractiveUseRequest, for any element, until InteractiveUseEndedEvent for this element closes the interaction. The official client does exactly this. 3. If can_move is false - absent on the wire, which is how false arrives - the character is locked in place for the use: send no movement request until it is over.

A script that fires its next action immediately is acting during an interaction the server still considers in progress.

element_id joins this to InteractiveElement and to StatedElement, so it is how you tell WHICH node someone just started on.

LIVE CAPTURE (3.6.12.16): duration 30, element_id 537803, entity_id 676609130790, skill_id 68, can_move absent (false) - a three-second use during which the character could not move. Fields at their default value (0, false) are simply absent from the wire, as here.