-
Notifications
You must be signed in to change notification settings - Fork 2
Home
Here I am just going to detail the specific project(s) I was working on when I decided to make Pathlog, and how I ended up applying it to the project(s). I have been working on Assaults, and have previously meticulously created pathing nodes one by one using a GM command. This addon will allow developers to easily record path points and patrols with a few simple commands.
- Using either the
target
orlist
mode, I went in to retail and obtained the logs for each Giant Orobon's patrols.
- For the hiding spots, I knew I would want each point to be a table, so I used the //pl tablepoints(tp) command.
- Using the
/pl point
command, I ran around the map on my local server standing in the Qiqirn Diver hiding spots and giving a brief description. - For example, the first hiding spot was recorded by walking to the point on my local server and typing the command
//pl point SW half, starting area
.
- First by npcID - offset (effectively ordering the Giant Orobons 1 through 7).
- Then, index table by each "leg" of the patrol.
- Using the timestamps, I was able to see when the Giant Orobons would pause for approximately 5 seconds and split into a leg here.
- I went in to retail and compared timestamps to estimate which leg the Giant Orobons would spawn at.
- Next, I changed the first and last points of each leg to round the Y axis down and use
.000
(because on our repoatPoint()
seems to get confused otherwise). - I also copied the last point of each leg and pasted it to be the first point of the next leg.
- Using a simple timer, I was able to recreate the 5 second pause we see from retail just like the timetamped logs.
Here is the logic for the Giant Orobons, calling the structured table above.
- I copied these points from the raw data and structured them in a table by SW half of the map and the NE half of the map.
- Funny things happen when you tell them to
pathTo()
one of these points, so I just added some logic for them to go to the other half of the map prior to pathing to their target point in the event that they are in the wrong half of the map.
- Using
list
mode//pl mode list
, I used the//pl list add 17006664
command for Lamia ID 17006664 through 17006678. - If/when I felt like I had obtained enough information for any specific Lamia (such as the first one encountered that has a very short patrol, basically guarding the entrance only), I removed them from the list by targeting and using the command
//pl list r
. - I went in to retail 3 or 4 times solely for the purpose of running around, hiding, and soaking up as much information as possible.
I knew there would be a lot of information so I tried to come up with a plan to quickly parse through the information and get an idea of each Lamia's patrol and pause points. I ended up with a simple GM command that would port me around to the various points.
- Step 1: Paste the pathlog data from the target mob in the table for the command.
- Step 2: Number every 5th point e.g. 5, 10, 15, 20, etc...
- Step 3: Using the command above, step through each point in the logs and mark resets or breaks in the path.
- Step 4: Evaluate the time stamps and mark pause points.
- Step 5: Compile the path, noting any gaps that will be targeted for later capture.
This part of the project is on-going, but I will post the structured data and Lamia logic here when it is complete:
- Using
list
mode//pl mode list
, I used the//pl list add 17006664
command for Lamia ID 17006664 through 17006678. - If/when I felt like I had obtained enough information for any specific Lamia (such as the first one encountered that has a very short patrol, basically guarding the entrance only), I removed them from the list by targeting and using the command
//pl list r
. - I went in to retail 3 or 4 times solely for the purpose of running around, hiding, and soaking up as much information as possible.
- Immediately we notice a few things:
- The Lamia pathlegs are not standard because they rotate in place once they get to their pause point.
- These path legs are easy to spot, because the point is exactly the same 3 times with a different rot.
- The Lamia seem to rotate to N, S, E, W when they pause.
- The turns appear to be about a second apart, 3 times, then the Lamia continues the patrol.