Repository navigation
Home
Here I am just going to detail the specific project I was working on when I decided to make Pathlog, and how I ended up applying it to the project. 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 or list 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, 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 to round Y axis down and use .000 because atPoint() gets 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:
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: