Open jetrotal opened 9 months ago
This one is near completion.
Just need to revamp @raw 2050, "SetFlying", targetIsVar,target, flyingIsvar, flying
Once Ghabry have time, he will help refactoring the vehicles code, to allow any event entities to fly or land like airships.
I wonder if we could also have an extra parameter called forceLanding
to detect if a terrain is appropiate for landing or not.
About the semantics of Wait for Single Movement:
I understand this ones:
But about the output variable:
The variable is set to 0 when the move route was aborted.
The variable is set to 1 when the move route did not exist or ended successfully.
Is this correct and the intention?
Here's a bunch of stuff that was already requested in different places.
Call Movement Action:
A collection of new move commands that can be called as:
Wait for Single Movement:
Waits for the end of a Single Event's Movements.
While waiting for the Move Route to complete, you can save the outcome of the motion (success or failure) to a targetVariable. Additionally, you can set the number of failed attempts allowed before triggering a failure condition. If the failuresAmount is set to 0, this command will simply wait for the motion to finish without considering failures.
old commits comments: Update Feature - Support Detecting when Move Route Fails Thanks @MackValentine Mack for solving some Core Issues