New Commands: 2050 - Call Movement Action | 2051 - Wait for Single Movement (can Detect fail cases) #3111
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jetrotal
force-pushed
the
CallMovement+WaitForMovement
branch
from
feeed6f
to
b58c8af
Compare
jetrotal
force-pushed
the
CallMovement+WaitForMovement
branch
from
248a21f
to
e5c2381
Compare
|
This one is near completion. 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 |
Call Movement Action: `@raw 2050, "SetMoveSpeed", 0, 10001, 1, 3` @2050("typeOfAction",[targetIsVar,target, parameterIsvar, parameter]) ```js @raw 2051, "", 0, 10001 //Wait for Single Movement @raw 20140, "Fails to move x times", 8 // start fail branch @raw 10 //empty space for more cmds @raw 20141 // end of fail branch ``` ------------------------------- old commits comments: Update Feature - Support Detecting when Move Route Fails Thanks @MackValentine Mack for solving some Core Issues
```js @raw 2050, "FaceTowards", eventAIsVar,eventA, eventBisVar, eventB ``` ```js @raw 2050, "FaceAway", eventAIsVar,eventA, eventBisVar, eventB ```
It now uses a single command instead of a chain of commands. ```cpp CommandWaitForMovement(useVarID, ID, useVarTargetVariable, targetVariable, useVarFailuresAmount, failuresAmount) ``` You'll store if a Move Route failed or succeed on a target variable. Then use that variable to define an outcome.
jetrotal
force-pushed
the
CallMovement+WaitForMovement
branch
from
e5c2381
to
1d9597e
Compare
jetrotal
force-pushed
the
CallMovement+WaitForMovement
branch
from
1d9597e
to
ee8b2ad
Compare
|
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? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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