Difference between revisions of "Use3DObject"

From Final Fantasy Hacktics Wiki
Jump to navigation Jump to search
m (Xifanie moved page Event Instruction 54 to Use3DObject)
 
Line 5: Line 5:
  
  
See also: [[Event_Instruction_55|{55} {{IE_55}}]] ― [[Event_Instruction_56|{56} {{IE_56}}]]
+
See also: [[Event_Instruction_55|{55} {{IE_55}}]] ― [[Event_Instruction_56|{56} {{IE_56}}]] ― [[Event_Instruction_27|{27} {{IE_27}}]]  
  
  
Line 32: Line 32:
 
*x01: Ring (DO NOT USE [[Event_Instruction_56|{56} {{IE_56}}]]; they animate forever)
 
*x01: Ring (DO NOT USE [[Event_Instruction_56|{56} {{IE_56}}]]; they animate forever)
 
*x02: Freezes movement
 
*x02: Freezes movement
 +
 +
== Note ==
 +
 +
Resetting a 3D Object for good is difficult - even after closing it, the map might still not register it correctly. The issue seems to be that the first pass of ReloadMapState or anything similar (preparing the encounter through ChangeMap/jumping into the random battle event?) gets some value set by Use3DObject *before* it resets it, requiring at least one extra run of that code to re-close it for good. The easiest way to accomplish this is just to use ReloadMapState.

Latest revision as of 03:08, 6 September 2025

{54} Use3DObject

Use3DObject(xID,xST)

Use an object that has a 3D animation.


See also: {55} UseFieldObject{56} Wait3DObject{27} ReloadMapState


Object ID

006 Riovanes Castle

  • x01: Right Door (3D)
  • x02: Left Door (3D)


002 Back Gate of Lesalia

  • x01: Door (2D)


036 Church Outside of Town

  • x01: Western-most Bell (3D)
  • x02: Eastern-most Bell (3D)


State

For doors:

  • x01: Open
  • x02: Close


For bells:

Note

Resetting a 3D Object for good is difficult - even after closing it, the map might still not register it correctly. The issue seems to be that the first pass of ReloadMapState or anything similar (preparing the encounter through ChangeMap/jumping into the random battle event?) gets some value set by Use3DObject *before* it resets it, requiring at least one extra run of that code to re-close it for good. The easiest way to accomplish this is just to use ReloadMapState.