0x0F — nop

Immediate return 0; no handler-side behavior.

proven— handler traced, and exercised by at least one shipped script.

At a glance

Opcode	`0x0F` (15)
Handler	`CRadiScript::Command_0f`
Signature	`CRadiScript::Command_0f(int,SCR_DATA*,unsigned int,unsigned int)`
Translation unit	`r_script_run0.cpp`
Address	— debug build, the only one that confirms it Not placed in the ENG or JPN maps. Those maps are derived, and neither a byte match nor a porting rule has pinned this handler down there — it is still installed in that build's dispatch table.
Handler size	`0x8` (8 bytes)
Family	Script control, flags and values
Command size	`4 + extra_words * 4` bytes

Handler behaviour

Immediate return 0; no handler-side behavior.

Encoding

The command header is one 32-bit word, as described in §3 Instruction encoding:

 31            24 23            16 15             8 7              0
+----------------+----------------+----------------+----------------+
|  flags         |  argument byte |  extra words   |  0x0F          |
+----------------+----------------+----------------+----------------+

Bits 8–15 give the number of 32-bit operand words that follow. Bits 16–23 are handed to the handler as a bitfield; on character commands bit 0 normally says whether a character selector word is present. Bit 31 is the keep-going bit.

Operand fields

1 documented field. input fields are read from the command's operand words; derived fields are computed from other fields rather than stored separately.

Field	Role	Meaning
`flags`	input	Command header flag byte. Bit 0x80 is the keep-going bit: set (the hidden default), the next command runs in the same frame; clear (printed as `yield=1`), the script pauses until the next game update. Other bits are rare and stay as an explicit flags= byte.