rswac

Coordinates 17.90, 44 gets stuck for 30+ seconds trying to run up this huge curve I've seen this 3+ times. My settings are on to run the reverse track I'm going to disable that for now to see if it fixes, just thought you should know.

4 hours ago, Hapiguy said:

Is someone else mining the node, or just leaving after mining the node?

Depending on your settings, this could be part of the issue.

Also, if someone has mined the node over 10-15 seconds before you get to it, sometimes it will simply despawn prior to your dismount, and the bot will take off.

Pay attention to the steps that your bot is on when this happens, if you can.

Either way, it's definitely a great profile.

No one else on the node, but I'll look more into it.

Repairs with mammoth are working now and I'm dying a lot less frequently. Only thing I would have to add at this moment is at some instances when babysitting I will see the script approach a node and before capturing it, it will just take off. I'm not too sure how common this is, but I can recount at least 10-15 times over a span of hours this happening. I'm paying attention to the chat to make sure I didn't miss anything, but I'm not sure if this is a possible fix you may look into, thanks for everything anyway keep it up!

Working really well thank you. If you can fix the instance when it's in combat and for instance uses "Fireball, fireball, combustion, rune of power, etc." To have rune of power be dropped prior to combustion that would make this amazing.

If you could also prioritize ice block at a certain hitpoint % rather than casting fireball at that low percentage that would work well as well (yes I did enable ice block in the UI).

Going to run this for awhile see how it goes. PVP server as Horde starting as a level 40 druid, shouldn't be a problem.