Jump to content
This site uses cookies! Learn More

This site uses cookies!

By continuing to use this site, you agree to allow us to store cookies on your computer. :)

Litah

WRobot user
  • Content Count

    4
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. So apparently, it is not possible to ress at Spirit Healer currently in WotLK when using wRobot. I made a topic about this here: More details, including reproduction steps and logs can be found in the topic above. I'm not sure if you are aware of the bug, but apparently it's been like that for a while now. A fix would be most appreciated. Cheers.
  2. Thanks for the reply. Yeah, after I posted this I troubleshooted it with my friend and came to the conclusion that for reason XYZ ressing at spirit healer just doesn't work currently. So I've disabled it since. Hopefully it can get fixed in nearby future.
  3. I have been using the bot for a few days now. Since yesterday, I haven't been able to resurrect in The Barrens nor Thousand Needles. It gets stuck on talking with Spirit Healer, the confirmation window about Ress Sickness pops up and the bot closes it and initiates the talk with Spirit Healer again. Multiple graveyards, not just a certain one. This loops goes on and on. It doesn't even try to corpse run. Even after session's first death, it tries to ress at Spirit Healer. I don't want this behavior. I only want it to try ress if it has died like 5 times in 15 minutes. Attached is two screenshots on wRobot settings and one of Human Master Plugin settings. Nothing else control Spirit Healer behavior AFAIK on my end currently. Maybe there's something in the log? I can't find the culprit in my settings. EDIT: I'm playing on Dragonblight EU, WotLK 3.3.5a. 12 Jun 2019 22H05.log.html
  4. Nah, I just got Cheap Shot and it happens on my end as well, using English client on WotLK 3.3.5a. Attached is the log where it occurs. First time it happened, I took manual control and disabled its Stealth it was on. Second time I killed the bot. 11 Jun 2019 17H16.log.html
×
×
  • Create New...