POI Mistake Finder too

[TreeMos]

The script that I use to generate the XML for my POI Finder mod also logs when it has issues parsing certain POI's from the original Map files. Typos in the descriptions I can't do much about, but I did keep it fairly picky about the format of pathfindlocation coordinates. So it reported a few that someone should go and investigate to get correct values for. Here are the 7 issues it found from the latest map files: (I'll color the likely mistakes in red)


Failed to parse pathfindlocation
Could not parse the values out of this icon tag text:
<Icon IconStyle="Skinnable_Styles.POI.QST" IconType="map" Location="190,343" Name="secondsouthernsigilofundeath" OnHoverIn="Parent.Parent.Parent.Parent.Parent.QM_LocEntry.QM_LocText.LocalText=p athfindlocation" pathfindlocation="-1147.09, n25.86, 647.58" ScrollExtent="12,12" Size="12,12" Tooltip="UID: 21667
Second southern sigil of undeath " TreatAsButton="true"/>

Failed to parse pathfindlocation
Could not parse the values out of this icon tag text:
<Icon IconStyle="Skinnable_Styles.POI.LOC" IconType="map" Location="41,307" Name="boatdeck" OnHoverIn="Parent.Parent.Parent.Parent.Parent.QM_LocEntry.QM_LocText.LocalText=p athfindlocation" pathfindlocation="1416.00, -16.56, 274.98`" ScrollExtent="12,12" Size="12,12" Tooltip="UID: 1073
Boat Deck: Dervish Cutthroat Camp The Boat Deck looks like something a Captian would stand on " TreatAsButton="true"/>

Failed to parse pathfindlocation
Could not parse the values out of this icon tag text:
<Icon IconStyle="Skinnable_Styles.POI.NPC" IconType="map" Location="261,299" Name="bailangrovetheelder" OnHoverIn="Parent.Parent.Parent.Parent.Parent.QM_LocEntry.QM_LocText.LocalText=p athfindlocation" pathfindlocation="-68, -4, =94" ScrollExtent="12,12" Size="12,12" Tooltip="UID: 20597
Bailan Grove the Elder: He tells you not to disturb the waters. Word of warning dont... " TreatAsButton="true"/>

Failed to parse pathfindlocation
Could not parse the values out of this icon tag text:
<Icon IconStyle="Skinnable_Styles.POI.ZONE" IconType="map" Location="1259,-539" Name="toantonica" OnHoverIn="Parent.Parent.Parent.Parent.Parent.QM_LocEntry.QM_LocText.LocalText=p athfindlocation" pathfindlocation="" ScrollExtent="14,14" Size="14,14" Tooltip="UID: 466
To Antonica " TreatAsButton="true"/>

Failed to parse pathfindlocation
Could not parse the values out of this icon tag text:
<Icon IconStyle="Skinnable_Styles.POI.QST" IconType="map" Location="1003,214" Name="thecachepathofthecrusader" OnHoverIn="Parent.Parent.Parent.Parent.Parent.QM_LocEntry.QM_LocText.LocalText=p athfindlocation" pathfindlocation="(+791, -20.5, -30" ScrollExtent="12,12" Size="12,12" Tooltip="UID: 17843
The Cache - Path of the Crusader: Instanced zone for Path of the Crusader quest " TreatAsButton="true"/>

Failed to parse pathfindlocation
Could not parse the values out of this icon tag text:
<Icon IconStyle="Skinnable_Styles.POI.NAME" IconType="map" Location="313,306" Name="oakmatriarch" OnHoverIn="Parent.Parent.Parent.Parent.Parent.QM_LocEntry.QM_LocText.LocalText=p athfindlocation" pathfindlocation="-750, ??, 26" ScrollExtent="12,12" Size="12,12" Tooltip="UID: 21612
Oak Matriarch: Named 44^^ Dryad with 6 minions. Also part of Peacemaker quest " TreatAsButton="true"/>

Failed to parse pathfindlocation
Could not parse the values out of this icon tag text:
<Icon IconStyle="Skinnable_Styles.POI.NAME" IconType="map" Location="57,300" Name="captainduranas" OnHoverIn="Parent.Parent.Parent.Parent.Parent.QM_LocEntry.QM_LocText.LocalText=p athfindlocation" pathfindlocation="1193.63, o.74, 576.67" ScrollExtent="12,12" Size="12,12" Tooltip="UID: 17579
Captain Duranas " TreatAsButton="true"/>

[Dolby]

As long as you have the ID of the POI you can easy submit the corrections.

http://maps.eq2interface.com/index.php?action=reportbad



BTW new POI's shouldn't have invalid charaters in /loc's as the webpage makes sure its valid. Looks like this are all ones submitted before the new webpage.

[Dolby]

I had some time and fixed them.

[TreeMos]

Great! I just grabbed the latest updates and re-ran the script. My error log file came up empty this time