I'll use code tags, but it might add random spaces. I'll also paste in a line without code tags (as long as it doesn't make the thread scroll far right) to hopefully clarify where spaces are and aren't).
Code:
<Icon IconStyle="MOB" IconType="map" Location="191,196" Name="MOBviciousbadgers" pathfindlocation="947, 0, -352" ScrollExtent="10,10" Size="10,10" Tooltip="Vicious Badgers" TreatAsButton="true" OnHoverIn="Parent.Parent.Parent.Parent.WC_Titlebar.QM_LocEntry.QM_LocText.LocalText=pathfindlocation Parent.Parent.Parent.Parent.WC_Titlebar.QM_LocEntry.QM_LocPath.pathfindlocation=pathfindlocation"/>
<Icon IconStyle="MOB" IconType="map" Location="191,196" Name="MOBviciousbadgers" pathfindlocation="947, 0, -352" ScrollExtent="10,10" Size="10,10" Tooltip="Vicious Badgers" TreatAsButton="true" OnHoverIn="Parent.Parent.Parent.Parent.WC_Titlebar.QM_LocEntry.QM_LocText.LocalT ext=pathfindlocation Parent.Parent.Parent.Parent.WC_Titlebar.QM_LocEntry.QM_LocPath.pathfindlocation= pathfindlocation"/>
That's a good example of what a complete icon line looks like. IconStyle is what it looks like, IconType is so pahfindlocation will draw a find trail, pathfindlocation is standardized as "###.##, ###.##, ###.##" where the commas and spaces are important for uniformity. Notice there's a Tooltip but no LocalTooltip to cut down on file size bloating. The OnHoverIn passes the pathfindlocation to the Path Finder.
Quib