0x1E — packing_file_load_or_release

Arg bit 0 clear: reads a halfword id and calls CRadiDataCenter::LoadPackingFile. Bit 0 set: calls CFileObject::ReleaseFile on data-center slot arg>>4 when below 8.

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

At a glance

Opcode	`0x1E` (30)
Handler	`CRadiScript::Command_1e`
Signature	`CRadiScript::Command_1e(int,SCR_DATA*,unsigned int,unsigned int)`
Translation unit	`r_script_run0.cpp`
Address	— debug build; click for all 3
Handler size	`0x60` (96 bytes)
Engine name	`packing_file_load_or_release`
Family	Script control, flags and values
Command size	`4 + extra_words * 4` bytes

Handler behaviour

Arg bit 0 clear: reads a halfword id and calls CRadiDataCenter::LoadPackingFile. Bit 0 set: calls CFileObject::ReleaseFile on data-center slot arg>>4 when below 8.

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   |  0x1E          |
+----------------+----------------+----------------+----------------+

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

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

Field	Role	Meaning
`file`	input	Operand field `file`.
`raw_high`	input	Operand field `raw_high`.
`release`	input	Operand field `release`.
`slot`	input	Operand field `slot`.

Engine calls

Engine functions this handler was observed calling:

CFileObject::ReleaseFile
CRadiDataCenter::LoadPackingFile