FNV316

Can confirm that this still happens from time to time, even after ->

Authentication server crashed, but it's back running again by now. Please give it another try

wManager.Wow.Forms.UserControlTabGeneralSettings.ReloadGeneralSettings(); Call this function once after modifying settings. Updates the wRobot UI

Uncheck "Ninja": Enter advanced Settings -> Looting and Farming options -> Ninja

Use a tool like NvidiaInspector, set Frame Rate Limiter to ~60 and V-Sync to Force On

KeyExample.xml Add the Custom Script part of the attached file to the "Custom Script" part of your quester profile. Then use it as custom complete condition for that quest (part) and call it like this: return Key.haveKey(KeyId); Returns true, if the key is on your key chain. The only thing you have to change is KeyId

That's why I said, use quest name (-> quest title) instead of id. Calling that Lua function returns (in Vanilla) 7 different values, so you need a variable for the very first value. You then check, if the value (string) of the quest title variable is the same (string.match / string.find) as your quest name string. Please read the documentation. There is an example of how to use these variables right at the bottom. http://classic-wow.wikia.com/wiki/API_GetQuestLogTitle#questTag

Use quest name instead of id: http://classic-wow.wikia.com/wiki/API_GetQuestLogTitle

You can achieve that by de compiling the dll with a tool like dotPeak. Avvi explained this in a thread: This allows you to take a look at the code, but not applying changes to the source dll

General communication about such stuff could by improved a lot and some issues take an eternity to be dealt with, but I agree. The latest update is a step in the right direction. Also, due to the bot being fully customable with C#, you can create your own fixes / workarounds, if you are fine with putting the effort in

Instead of creating one different grinder profile for each step of the grind, you have one core profile that executes the following grind steps one after another. It also grants you easy access to all the fancy C# stuff and other quest types (f.e. FollowPath for custom routes), in case you need that for more advanced profiles. It's pretty straight forward. You create a KillAndLoot quest without an quest id, scroll to the bottom and check "Grind". You then set the level of that KillAndLoot quest to one below the level you want the bot to grind to and change "Not Required in Quest log" to true. The only thing left (besides adding Hotspots and unit ids to attack) is to add a "Pulse" step for that created quest and run it with quester.

Took an unskilled programmer like me around four hours to fully automate entering Thorium Point, reach any NPC at Thorium Point and leaving Thorium Point, without my bot breaking his nose every other minute. Might be a dirty solution, but it works. Why exactly is this still a thing? Thorium Point - Default Path Finder VS Custom Path Plugin.mp4

I don't buy that. Even if it is impossible to make that with the path finder, why not hard code paths at these locations? Pathfinder is looking for a path to coordinate XYZ within range of area ABC? Use one of the pre made paths that is closest to that coordinate and use path finder to move to the starting location of that pre made path. Need to leave the place? Well, use the closest pre made path leading out again. Need to run to another NPC at the same location? Then join a follow path loop leading to any NPC / object, until players position is closest to his original destination. Similar to how battlegrounds are set up. I mean c'mon. How long does wRobot exist now? Still no solution for this? Not even a workaround? Who cares about bot trains and inefficient routes, if the alternative is the bot slamming his head into a wall for ten minutes straight. That's why I'm asking what needs to be done. But I refuse to write and support a whole logic for this crap, to allow my other code running as intended. I already did this for the broken taxi system. I don't expect any random location in the world to be fixed, but at least major hubs have to work properly.