Moveset optimize

[mylafter]

Is there a way to make an events' move route move 'up,down,left,right' more than once?
For example, a normal looking move route would look like:

Spoiler

> Move Up
> Move Up
> Move Up
> Move Right
> Move Right
>

Instead I'd like something like:

Spoiler

> Move Up (x3)
> Move Right (x2)
>

I know I can just use a path finding script but it doesn't work with most of my other scripts. (I'm using a pixel movement script)
The Pixel movement script counts each move as 8 pixels. Therefore, in the moveset I have to make it 'move up' 8 times in order to make an event move one whole tile.

As an alternate solution, maybe the wiser decision is to make a pathfinding script compatible with the pixel movement script?

 

[gstv87]

add a script block and try X.times{move_straight(direction)}
where X is the number and direction is 2, 4, 6 or 8.

 

[mylafter]

add a script block and try X.times{move_straight(direction)}
where X is the number and direction is 2, 4, 6 or 8.

It works but the event sort of jumps to the next destination. No matter how I change the frequency or speed, making the event move more than 1 time makes it move instantly.

 

[gstv87]

confirmed.
then it needs a rework of the move route, because that's not sending 3 entries to the move route, but 1 that is 3 times as long.
I don't think there's a way of doing it without changing anything from the move route object.

 

[mylafter]

Yeah, the only way to make the movement look fluid is if you make it move one pixel at a time like: '1.times{move_straight(2)} '

But even that, the event moves at a very choppy pace. It also pretty much defeats the whole purpose.

 

[A-Moonless-Night]

I remember there being a script that had convenience methods for that, but I couldn't find it when I just searched. I think perhaps it was an old HimeWorks script that they stopped supporting. Anyway, I decided to make something. I haven't tested it thoroughly, but give it a go if you want.

 

[mylafter]

I remember there being a script that had convenience methods for that, but I couldn't find it when I just searched. I think perhaps it was an old HimeWorks script that they stopped supporting. Anyway, I decided to make something. I haven't tested it thoroughly, but give it a go if you want.

I get this error popup when I load into the game. I tested to see if it was just my project but even on a blank new project, this still occurs.

Spoiler

 

[A-Moonless-Night]

Are you putting the script call into the move route?

 

[mylafter]

Are you putting the script call into the move route?

Okay, I figured out what was causing the crash.
I thought I had to keep it uppercased like <move MU 3> when it had to be lowercase.

It works perfectly! Thank you so much Moonless!

 

[A-Moonless-Night]

Oops, forgot to make it so codes can be upcase or downcase. Updated the code now.