- summary: The server refusing your InteractiveUseRequest: names the element it will not let you use. Nothing started.
- area: Game.Interactive
The server refusing your InteractiveUseRequest: names the element it will not let you use. Nothing started.
Kind event · Area Game.Interactive
The server's NO to your InteractiveUseRequest: it will not perform that use.
Exactly one of this message or InteractiveUsedEvent answers a use request.
WHAT TO DO WHEN YOU RECEIVE IT
1. MATCH IT BY element_id - the element you asked to use. That is the only
member the official client reads.
2. THE REQUEST IS ANSWERED. Clear your "requested" mark for that element: you
may ask again later. The official client does exactly this - it drops its
record of the unanswered request when the refusal names that element.
3. NOTHING HAPPENED. No interaction started, nothing is timed, you are not
busy. The official client prints the localized ui.popup.impossible_action
line in chat and, in its movement service, releases the "use in flight"
state so the character may walk again. Its queue of pending interactions,
if any, drops the refused one and moves on to the next.
4. DO NOT RETRY BLINDLY. The message does not say why. Likely causes: you were
out of range, the action is not currently offered, the element is in use,
or it is not on your map. Re-check InteractiveUseRequest's procedure
before asking again.
skill_instance_uid echoes which offer was refused. The official client never
reads it, so it carries no client-side meaning; use element_id. Some builds pad
this message with another int32 the client does not read either; where the two
cannot be told apart, skill_instance_uid stays unnamed.
The current build declares nothing else.
When you may send it
- Requires
roleplay_contextinferred
Related messages
- Arrives after
InteractiveUseRequest
Fields
| # | Field | Type | Meaning | You set it |
|---|---|---|---|---|
| 2 | element_id | int32 | The element whose use the server refused. (interactive element id) The element_id you sent in InteractiveUseRequest. Match the refusal to your request with it.The only member the official client reads: it compares it with the element it is waiting on and clears that wait when they are equal. | never |
| 3 | skill_instance_uid | int32 | Which offer of that element was refused - the skill_instance_uid of the request. (skill instance uid) No official client code reads it on any dumped build; rely on element_id. Left unnamed on builds that pad the message with another unread int32, where the two cannot be told apart. | never |