Difference between revisions of "UseFieldObject"
Jump to navigation
Jump to search
| (2 intermediate revisions by 2 users not shown) | |||
| Line 6: | Line 6: | ||
See Also: [[Event_Instruction_54|{54} {{IE_54}}]] ― [[Event_Instruction_57|{57} {{IE_57}}]] | See Also: [[Event_Instruction_54|{54} {{IE_54}}]] ― [[Event_Instruction_57|{57} {{IE_57}}]] | ||
| + | |||
| + | A (partial) list of documented Field Objects can be found [[Field_Object_List|here]]. | ||
| Line 11: | Line 13: | ||
Most maps do not have objects that have many states, and there is no easy way to know which are. | Most maps do not have objects that have many states, and there is no easy way to know which are. | ||
| + | In some cases (perhaps all cases, as this is untested thoroughly), the ID references a Textured Animation ID as defined in a [[Maps/Mesh#Texture_animation_instructions|Mesh Resource]]. | ||
{{x00}} | {{x00}} | ||
Latest revision as of 15:27, 23 April 2021
{55} UseFieldObject
UseFieldObject(xID,x00)
Changes the state of an object on the map.
See Also: {54} Use3DObject ― {57} WaitFieldObject
A (partial) list of documented Field Objects can be found here.
State Change ID : Byte (hex)
Most maps do not have objects that have many states, and there is no easy way to know which are.
In some cases (perhaps all cases, as this is untested thoroughly), the ID references a Textured Animation ID as defined in a Mesh Resource.
x00 : Byte (hex)
This value is always set to x00 in the original game; it probably doesn't have a function.
