Difference between revisions of "FF7/Field/Script/Opcodes/02 REQSW"
From Final Fantasy Inside
my_wiki>BukTop m (2 revisions imported) |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
* Opcode: '''0x02''' | * Opcode: '''0x02''' | ||
* Short name: '''REQSW''' | * Short name: '''REQSW''' | ||
| − | * Long name: Request | + | * Long name: Request send wait (asynchronous execution, guaranteed) |
==== Memory layout ==== | ==== Memory layout ==== | ||
| Line 11: | Line 11: | ||
==== Arguments ==== | ==== Arguments ==== | ||
| − | * '''const UByte''' ''E'': The ID of the target [[FF7/Field/Script/ | + | * '''const UByte''' ''E'': The ID of the target [[FF7/Field/Script/Actor|actor]]. |
* '''const Bit[3]''' ''P'': The [[FF7/Field/Script/Priorities|priority]] at which we want to execute the remote script (high 3 bits of byte). | * '''const Bit[3]''' ''P'': The [[FF7/Field/Script/Priorities|priority]] at which we want to execute the remote script (high 3 bits of byte). | ||
| − | * '''const Bit[5]''' ''F'': The ID of the specific | + | * '''const Bit[5]''' ''F'': The ID of the specific actors event to be executed (low 5 bits of byte). |
==== Description ==== | ==== Description ==== | ||
| − | Requests that a remote | + | Requests that a remote actor executes one of its events at a specified priority. If the specified priority is already busy with some other event (higher priority may be executing), the request will block until it becomes available and only then return. The remote execution is still carried out asynchronously, with no notification of completion. |
Latest revision as of 12:13, 21 September 2025
- Opcode: 0x02
- Short name: REQSW
- Long name: Request send wait (asynchronous execution, guaranteed)
Memory layout
| 0x02 | E | P / F |
|---|
Arguments
Description
Requests that a remote actor executes one of its events at a specified priority. If the specified priority is already busy with some other event (higher priority may be executing), the request will block until it becomes available and only then return. The remote execution is still carried out asynchronously, with no notification of completion.
