Difference between revisions of "Game Opcodes:SetPushEventConditionWithCircle"

Revision as of 21:44, 26 June 2019

Sets a push event trigger to this actor. "Push" events are collision tested events, this one specifically setting a trigger circle around the actor.

Offset	Data Type	Length	Variable	Description
0x00	float	4 Bytes	radius	How far the trigger circle extends from the actor.
0x04	float	4 Bytes	unknown
0x08	float	4 Bytes	unknown
0x0C	float	4 Bytes	unknown
0x10	byte	1 Bytes	direction	Changes behavior of the push circle. If 0x11; triggers when player leaves the circle. If 0x1, triggers when player enters the circle.
0x11	byte	1 Bytes	unknown	Gets shifted around to make 3 booleans.
0x12	byte	1 Bytes	isSilent	If 0x1, does not cause the UI and player to lockup.
0x13	string	32 Bytes	eventName	The name of the event that will be sent when a Start/End event is fired.

Generic events are usually named "pushDefault". Certain scripts require specific event names; ie: PushCommands need a "pushCommandIn" and "pushCommandOut" trigger.

If the eventName starts with _! the circle will block and "push back" a mounted player informing them that you cannot proceed on Chocoback. If it starts with _@ a generic "you cannot proceed" is shown, regardless of mount status.

@@ Line 34: / Line 34: @@
 == Notes ==
-Generic events are usually named "pushDefault". Certain scripts require specific event names; ie: PushCommands need a "pushCommandIn" and "pushCommandOut" trigger.
+* Generic events are usually named "pushDefault". Certain scripts require specific event names; ie: PushCommands need a "pushCommandIn" and "pushCommandOut" trigger.
+* If the eventName starts with <code>_!</code> the circle will block and "push back" a mounted player informing them that you cannot proceed on Chocoback. If it starts with <code>_@</code> a generic "you cannot proceed" is shown, regardless of mount status.
 == Visual Layout ==