You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of SetMesh does not reflect vanilla behavior correctly.
As seen in trigger editor, the parameters are:
arg1: TriggerObjectIDs;
arg2: visibility;
arg3: StartDelay - the delay before starting action;
arg4: Interval - the delay between setting each object;
arg5: AlphaDuration - the duration of the fade
Arguments 1 and 2 are implemented correctly, however, argument 3 is currently implemented as if it were argument 5, treating it as fade.
Instead, it is the duration of how long it should wait before starting the action at all. A good example of this is the patterns in Spring Beach, with how blocks will disappear in waves.
Argument 4 is the interval between the setting of each TriggerObject, in the order they are defined.
A good example is Tiares Desert (02010084), with how the water blocks will disappear in a circle pattern, due to the interval and how their IDs are assigned in a specific pattern. <action name="메쉬를설정한다" arg1="3001-3063" arg2="0" arg3="0" arg4="30" arg5="2" />
Other good examples are numerous patterns in Spring Beach.
Argument 5 is the duration of the fade away/in of the visibility. There may however be an unknown default value for this argument, as the fade animation exists even when the argument isn't defined, as seen in Surnurny's Dream (80000007). <action name="메쉬를설정한다" arg1="401,402,403,404,405,406,407,408,409" arg2="0"/>
The text was updated successfully, but these errors were encountered:
The current implementation of SetMesh does not reflect vanilla behavior correctly.
As seen in trigger editor, the parameters are:
Arguments 1 and 2 are implemented correctly, however, argument 3 is currently implemented as if it were argument 5, treating it as fade.
Instead, it is the duration of how long it should wait before starting the action at all. A good example of this is the patterns in Spring Beach, with how blocks will disappear in waves.
Argument 4 is the interval between the setting of each TriggerObject, in the order they are defined.
A good example is Tiares Desert (02010084), with how the water blocks will disappear in a circle pattern, due to the interval and how their IDs are assigned in a specific pattern.
<action name="메쉬를설정한다" arg1="3001-3063" arg2="0" arg3="0" arg4="30" arg5="2" />
Other good examples are numerous patterns in Spring Beach.
Argument 5 is the duration of the fade away/in of the visibility. There may however be an unknown default value for this argument, as the fade animation exists even when the argument isn't defined, as seen in Surnurny's Dream (80000007).
<action name="메쉬를설정한다" arg1="401,402,403,404,405,406,407,408,409" arg2="0"/>
The text was updated successfully, but these errors were encountered: