Skip to content

0xD4 — battle_volty_distance

Resolves character abstractions, calls CbtlEtc::Script_CalcVoltyDistance and CRadiApp::ProcessTaskReady.

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

At a glance

Opcode0xD4 (212)
HandlerCRadiScript::Command_d4
SignatureCRadiScript::Command_d4(int,SCR_DATA*,unsigned int,unsigned int)
Translation unitr_script_rund.cpp
Address— debug build; click for all 3
Handler size0x22C (556 bytes)
Engine namebattle_volty_distance
FamilyPerson, battle and effects
Command size4 + extra_words * 4 bytes

Handler behaviour

Resolves character abstractions, calls CbtlEtc::Script_CalcVoltyDistance and CRadiApp::ProcessTaskReady.

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

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

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

FieldRoleMeaning
character_ainputOperand field character_a.
character_binputOperand field character_b.
distanceinputOperand field distance.

Engine calls

Engine functions this handler was observed calling:

  • CCharacterManager::GetCharacterClass2 (×2)
  • CRadiApp::ProcessTaskReady
  • dword_405E30