Converting a waypoint file to use teleport functions

[Boris-The-Blade]

Creating a waypoint file :

First, open micromacro and run "rom/createpath". This will set you on your path creation ways. I'll skip this part for now, as most should probably be fairly familiar with it. For this to work, you'll need to fully read Rock5's teleport function, which is located here on the subforums "waypoints", installed, and installed correctly. Secondly, be careful not to use this in open areas.

Secondly :

Opening up your finished waypoint path :

First located and open your waypoint path you've created and would like to convert to a teleport path. Opening with notepad should work fine. Now, let's say you have a entire waypoint file, inside a particular instance, and it's ok to turn on teleporting for the entire waypoint file. Note, as mentioned by Rock5, it's pretty important not to teleport around in public, so play with this inside a instance until you get used to it. Now that you've opened up your waypoint file, let's go ahead and add this, exactly, on the onload portion at the top of the waypoint file.

before :

Code: Select all

<?xml version="1.0" encoding="utf-8"?><waypoints>
	<!-- #  1 --><waypoint x="-1456" z="2190" y="-380">	</waypoint>
	<!-- #  2 --><waypoint x="-1505" z="2146" y="-380">	</waypoint>
	<!-- #  5 --><waypoint x="-1504" z="2190" y="-380">	</waypoint>
	<!-- #  6 --><waypoint x="-1721" z="2197" y="-479">	</waypoint>

and after :

Code: Select all

<?xml version="1.0" encoding="utf-8"?><waypoints>

<onLoad>
    function portToNextWP()
        local nextWP = __WPL.Waypoints[__WPL.CurrentWaypoint]
        teleport( nextWP.X, nextWP.Z, nextWP.Y)
    end
</onLoad>

	<!-- #  1 --><waypoint x="-1456" z="2190" y="-380">	</waypoint>
	<!-- #  2 --><waypoint x="-1505" z="2146" y="-380">	</waypoint>
	<!-- #  5 --><waypoint x="-1504" z="2190" y="-380">	</waypoint>
	<!-- #  6 --><waypoint x="-1721" z="2197" y="-479">	</waypoint>

Now, you have the beginning of your teleport file. Now, for the next part, you'll want to start marking exactly which teleport waypoints within your file you'll want to be using. On each waypoint you'd like to use a teleport, you'll need a specific line of code on :

Code: Select all

portToNextWP()

This line of code will instruct RoMbot to teleport to your next chronological waypoint. As of the userfunction now, onload is no longer a requirement and need not be put in the header of your waypoint file. If you encounter problems for whatever reason, you can include it on the header as a backup method for calling it.. It has a few functions, and can be used as :

portToNextWP() ---> Will teleport the user to the next chronological waypoint in the list
teleportToIndex() ---> Will teleport user to the next chronological waypoint, without need of the onload section
portToNextWP(numberhere) ---> Will teleport user to the specified waypoint.

Code: Select all

	<!-- #  9 --><waypoint x="1334" z="2911" y="318">	portToNextWP() </waypoint>

Now, RoMbot will recognize waypoint 9, and after having successully run to it, teleport to waypoint 10. Remember to add the function portToNextWP() for each waypoint you'd like to teleport to, which can actually be used in different ways as instructed on Rock5's page. It's a little tricky to get down in the beginning, but after some practice it will serve you well.

[rock5]

Nice, but there is already a "teleportToWP(index)" in the userfunction file. If you leave out "index" it will default to the next wp. So no need for the onLoad function and just use

Code: Select all

teleportToIndex()

instead of

Code: Select all

portToNextWP()

[Boris-The-Blade]

Thanks rock, I never had a lot of luck getting that setup right after hours of learning the teleport function last night and making waypoint files. I think your teleport function thread actually has it as "teleporttonextWP(index)", which I could never get to work. Thanks for the info though, I'll stick teleporttoindex in there and see what happens. Still learning myself, but glad to have it going now

Also, I will add it here, once I understand it exactly. But how while creating a waypoint inside an instance, can you invoke the swim hack? Wanting to add that to future tp waypoints myself, but focusing on staying on teleporting until i get the ropes down. Thanks for the help, I changed the original post.

[lisa]

if using create path when you want to add code press numpad 0 and then type the code you want, for fly you want fly() and then flyoff() to turn off flying.

You can also just edit the code in after you have finished using createpath.

[rock5]

I think he meant how do you invoke fly so you can mark waypoints in the air while creating the waypoint. Just start the commandline in another instance of micromacro and type fly() or flyoff() when needed.

[Boris-The-Blade]

Oh man, that's super helpful. Thanks guys.

Lisa that's perfect. I've been going back and manually editing lowbie instance waypoint files to include teleport over the last week, and attempting to make about 5 different instance runs for lower characters to put on the waypoint sub-forum. This will help immensely.

Rock5 your right on, I was hoping to start it up to make fly waypoints as I go, which should help a lot in FA at least. I'll try that here in the next few minutes and see how it does, but that should help out a lot and speed things up.

Appreciate the help thus far guys, hopefully I can give back a little and upload some dependable lower instance waypoint files in the subforum this week from it, as I didn't see a lot of them there.

[MiesterMan]

This is funny, I created an addon like this that would toggle between regular walking and all teleporting. How it worked was you would use a toggle to tell when you're safely in a dungeon then it replaced the moveto function with a modified version that teleported to the next waypoint. The addon also made it so looting was done by teleporting so you could remove the second attempt to loot and the time needed past looting the corpse.

There was also a toggle to be used before exiting a dungeon so everything would be set back to normal. The reason I never posted the addon is that there were some glitches I never worked out before quitting this game entirely. First, if you move along too quickly, you'll get rubber banded back to a prior waypoint. I needed to add a check using a timer to see if the next waypoint actuall got substantially further away and goto the nearest waypoint if it did. Second, this required waypoint files to have the y coordinated recorded and most of the ones I was using for dungeons did not. You can't teleport up inclines up your bot doesn't know it's going up, ..