Usually caused by a bad mesh. Try the one's in my repo.
@Medicman -
Sorry you're still experiencing difficulty. When building this macro, I divided the zones it has to travel to into clusters/regions (always starting and ending in PoK), and then determined the order to execute those regional routes based on class. I did this so that I wouldn't waste users time running through 40 zones only at have them hit their class event zone, fail the event, and have to re-run the quest for ~2 hours to try again. I tried to have them perform the route with their class event zone first. As such, Shaman does them in the following order (taken directly from the code):
Code:
/call subRouteKunark
/call subRouteFaydark
/call subRouteLuclin
/call subRouteNWAntonica
/call subRoutePlanes
/call subRouteSWAntonica
/call subRouteVelious
Those in turn break down the individual zones orders:
Code:
Sub subRouteKunark
|- General Route = Pok(0) > OT(0) > Tim Deep > PoK(1) > OT(1) > Warslick > FoB (0) > EJ > FoB (1) > East Cab > P0K (2) > Fironia Vi (0) > LoiO > FM > Burning Woods > Dreadlands > FV (1) > PoK(3)
...
Sub subRouteFaydark
|- General = PoK (0) > Butherblock > GFay (0) > LFay(0) > Mistmoore > LFay(1) > GFay(1) > PoK(1)
...
Sub subRouteLuclin
|- General Route = PoK(0) > Shadeweaver's Thicket (0) > Shar Vhal (0) > Hollowshade Moors (0) > Grimling Forest (0) > Acrylia Caverns > Grimling (1) > Hollowshade(1) > Shar Vhal(1) > Shadeweaver(1) > PoK(1)
...
Sub subRouteNWAntonica
|- General Route = PoK (0) > Guild Lobby > Nedaria's Landing > Jaggedpine Forest > Black Burrow > Everfrost Peaks > PoK (1)
And so forth for the rest...
For Shaman, the class event is in EJ. So, the macro will run to just short of the event (navLoc -132 -2126 -338) and is generally left facing where the event takes place. Non-Shaman would then proceed to navLoc 303 -2114 -335 for their update. Shaman end the macro at that point so you can advance to the event and perform it without interferce from the macro. Further, I end the macro so you are free to run other combat-oriented macros if you so desire/need for your class event. It sets flags that it will read back in once you restart the macro after completing your event, allowing the macro to continue without resetting the quest.
The macro was written before we had TLO's to read the status tasks/quests in the window, so the macro (at time of writing) was unable to determine which steps you had or had not completed. It presumes to clear any old versions of the quest and start fresh (unless started in your class-event zone and certain flags were set to let it know it's a class-event continuation). Even with the addition of being able to read task step status, it would still require you to visit all the zones on a given route as there is not a reasonable way to programmatically perform dynamic route finding. (Without going into technical specifics, doing such would require a macro 10x the size of Explore.mac or KissAssist, and would need code development that would price this macro beyond affordability and hit issues of feasibility.) As for being unable to start your class event, that would be an Everquest issue, and beyond the scope of my supporting this macro itself. The macro stops for your class event as performing it zones you to a dynamically created zone instance.
All of these are explained on the Overview tab of the macro in the "Information and Recommendations" section:
As for meshes, over 50% of the meshes in the Updater were originally mine. They have since been replaced piecemeal by other's (Wired420 maintains that repo) and so I began offering mine for download separately as the replacements didn't maintain functionality. But installing my meshes should only overwrite certain meshes from the Updater. Are you wholesale deleting all of the Updater meshes and then downloading mine? No need to do that. Just overwrite the ones you need.
Hope this helps clear up some confusion.