Rail scripts that do things are not easy to get right. Start smaller. Go to the documentation tab on easyuo.com and read about the move and the event pathfinder commands. Make a small snippet of code that does something like this:
Event pathfind X Y Z
Halt
Then look at your charposition information, walk around and try using the code snippet to move. You can evolve it by adding more moves, waits, and checks to see if you moved to the right spot. Now when you try to use someone else's more complete rail and movement code to build your script you will have some experience to help you troubleshoot when it doesn't work well.
Get comfortable with how the movement options work, plan what you want the script to do, preferably by practicing the routine in the game yourself. In this case I would go to the place you want to run the rail and actually do it live six or eight times so that you can anticipate potential failure points. Make a plan for the rail that you think will work that accounts for how the move commands work and what your environment will be like.
Now go look at some of the rail and movement code out there and try to build the script to run in a safe environment first. Don't introduce anything else until you have your rail working -- and don't run it live until you can run it consistently somewhere safe. No sense dying while you try to get it working.
