Where to begin?

I've merged Enemy with Player. Now you have to specify that a Player is an enemy and then it lets you set all the Enemy properties right there. It automatically keeps up the "don't save" option, although you can turn that off for enemies that can change over the course of the game. Existing projects should load fine in the editor, but you'll have to edit the Enemy properties for the Players again (under Player this time).

The weapon animations from before are in. They took the old Enemy slot in the database. This simply lets you assign animations to sprites, and then you can assign the set to weapon items. It automatically loads the "right" and "left" animations for right and left handed swings (it uses this to correctly flip the sprite in the opposite direction but to keep the correct weapon hand). The name you give to the animations is important. These can be played on events outside battle, of course. You'll need to add another animation to the set so that it uses Normal Character Sprites too.

Most majorly, the pixel movement system is in. This upgrades the engine so that it has two event modes (character and a bunch of tiles) and two movement modes (step on tile and pixel). All types of events and all movement modes can collide cleanly with one another. The engine saves the pixel movement setting on the Player so you only need to do it once if you plan on the player moving smoothly the entire game. You only need to call the move function once (it has a Go and a Stop option). This is known as locomotion in the engine- the force that the event uses to move itself.

For external forces..

You can use the Force command to shove events around. This will often be done for when you knockback events after they got hit in an action RPG. You can also set a positive value for Z in the Force command to launch the events into the air. You only need to call the command once, if you do it multiple times in a row the effects add up.. if you aren't paying attention and you accidentally have a knockback Force command in a parallel event, the event will shoot off. If the event lands on the ground, it slows down based on a friction setting you can change.

Character physics like this is not as simple as it looks. You can easily lag out any game engine with collision detection. I have tested and adjusted the character physics, but it might still be quite unstable. If you play with the Ray command, but it isn't working at all like you wanted, press F9 when testing the game to see where the ray ended up.

There you go. Pixel movement. A lot of the previous commands and features do work in pixel movement, including all the commands that make a custom battle system easy. Not sure if a complete action RPG is possible, but you can give it a try. Don't go too nuts with the Ray command and try to keep them as short as possible- longer Rays are more intense on the computation.

The download up there should be updated.