New Commands: 2050 - Call Movement Action

[jetrotal]

Here's a bunch of stuff that was already requested in different places.

Call Movement Action:

@2050("typeOfAction",[targetIsVar,target, parameterIsvar, parameter])

A collection of new move commands that can be called as:

@raw 2050, "SetMoveSpeed", targetIsVar,target, speedIsvar, speed

@raw 2050, "SetMoveFrequency", targetIsVar,target, frequencyIsvar, frequency

@raw 2050, "SetTransparency", targetIsVar,target, transparencyIsvar, transparency

@raw 2050, "SetAnimationType", targetIsVar,target, animationTypeIsvar, animationType

@raw 2050, "SetFacingLocked", targetIsVar,target, lockedIsvar, locked

@raw 2050, "SetLayer", targetIsVar,target, layerIsvar, layer

@raw 2050, "SetFlying", targetIsVar,target, charsetIndexIsVar, charsetIndex

@raw 2050, "StopMovement", targetIsVar,target

@raw 2050, "ChangeCharset/actor1", targetIsVar,target

@raw 2050, "Event2Event", eventAIsVar,eventA, eventBisVar, eventB 
//teleports an eventA over eventB, putting EventA to look at same direction as EventB too.

@raw 2050, "FaceTowards", eventAIsVar,eventA, eventBisVar, eventB 

@raw 2050, "FaceAway", eventAIsVar,eventA, eventBisVar, eventB 

---

Wait for Single Movement:

Waits for the end of a Single Event's Movements.
Already Implement on another PR.

Details

```js @raw 2051, "WaitForMovement", 0, 10001, 0, 35, 0, 8 ```

@raw 2051, "WaitForMovement", useVarID, ID, useVarTargetVariable, targetVariable, useVarFailuresAmount, failuresAmount

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

[jetrotal]

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.

[Ghabry]

About the semantics of Wait for Single Movement:

I understand this ones:

• Event ID is obviously the event that is checked
• Failures Amount is a threshold to prevent soft locks: 0 = wait infinitely, >=1 abort move route and continue when failure threshold is reached

---

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?

[florianessl]

Small draft proposal for providing extended functionality of "StopMovement" with a new command:
florianessl@07a5b5c
(Not yet tested - could break)

Minimum parameter size: 3

• param[0]: Mode
  • 0: Cancel routes of given events
  • 1: Cancel all active routes except those of the given events
• param[1]: ValueOrVariable modifier (Single value - I see no need to mix modifiers for the subsequent span of parameters)
• param[2 - x]: event ids

Side note:
Cancelling move routes for single events is actually possible in Vanilla RPG_RT by just calling "Set Move Route" without providing a list of move_commands. But I'm sure a lot of people aren't aware of this detail.

[jetrotal]

@florianessl I like this idea a lot!

Maybe extending it a bit more with
Pause, Resume, Restart Move Route (and maybe goto(lineN)? ) options could help making it more independent from the blank move route approach.

---

On other subject, We just discovered that this command I made is a bit similar to Maniacs "Add Move Route", with 2 differences:

• Maniacs Command needs an set move route happening right before it being called.
• Our command call move route actions instantly, instead of waiting for the next frame, as it is done in call move route (some people liked this a lot)

[Ghabry]

Yeah I was thinking about this PR here again after seeing "Add Move Route" and imo this command is quite bad. Especially the requirement to have an existing move route (would be also more useful if it would create a new route instead of silently failing).

At least everything that finishes immediately is imo for this command here. Stuff that takes longer to execute needs testing (or is better suited in a move route).