KAZESUI'S PROFILE

if it's the variable you use for giving the event ID, you should set it to the ID of the animator event in an autostart event.
if it's the variable for giving the page, then there's an error somewhere in the code I guess, as this one should be set when direction keys are being hit. You might want to just set it to 1 or something as an initial value as well though, just for the sake of not getting an error if there's a parallel process event in the background triggering prematurely

This is fixed by having a branch catch if the key input = 0. If so, then the animation frame variable is set to 1, i.e. the first image.
This is shown in the sample project under the common event "Movement 3"

Remember, there are 4 states of movement, so just checking for animation frame 4 isn't sufficient, since frame 2 should show a walking image as well

Easy way of doing this:

Make a footprint event like this:


Now you can copy an arbitrarily large amount of these events without making any changes to the code.

Have an Auto start event like this:


After the auto start event has executed, let a parallel process run with code like this


This will make footprints last as long as you stay on the map, and as long as you don't make too many steps. If you spend too many steps, the last footprints will disappear and appear as new ones instead. Only bad thing about it is that you'll need a lot of events, but there's no real way around that with conventional event coding anyway.

To make the footprints not visible before used, I'd recommend having an inaccessible tile on the map, with the graphic covering the entire tile above hero, and with a simple loop, change the location of all the foot print events to this tile with help of the call event command.

A fairly good question. I guess I might have forgotten to add that there's (probably) an autostart event with a show picture command at the start before calling erase event. Even if there weren't a picture, this doesn't result in an error message or anything in rm2k3, as it then just ignores the command, meaning that this would only cause a bug in terms of there being no sprite the second you start the game, but everything working as normal the second you move.

This is actual a reason why I tend to include sample projects, as I might forget to explain something which seems obvious to me (or which just gets lost of the sheer amount of stuff I try to explain), such that it's possible to look up on ones own for the details which might seem unclear.

But yes, thanks for pointing it out. I guess I'll have to reread a bit and try to find a fitting spot to include that detail

edit: seeing your new edit, I guess you might have seen something, I didn't while quickly skimming through my own tutorial?

author=PepsiOtaku
Thanks Kaz! This is very helpful. The biggest pain will be going through the sound effects in the battle animations though. Do you think you could send me the source so I could mess around with it?

source
This won't help you in terms of controlling the battle animation sound effects though, no matter how much you mess with it.
As far as I see, the SDK gives no control over the battle animations in any way, meaning you'll most likely have to simply do those the manual way.
Still, wish you fun with the source

As for the problems you mentioned with conflicting data for different savefiles, this can be remedied by using the onLoad and onSave callbacks. This way you can store savefile specific data (like the battle speed), and reload it upon loading.