Litah

They posted an announcement about 10min ago on Dragonblight's Discord regarding better bot detection.

This may or may not be related, they claim this was discussed, agreed on and possibly acted on last Saturday during GM meeting.

I mean it's Dragonblight. They're one mess away from shutting down, so we'll see.

Is anyone able to shed any light to this error? I cannot run bot on my other character (Paladin), it works fine on Rogue, though.

I won't get even an error anymore, bot straight up closes when trying to run a profile. However it does still work with Rogue just fine.

Same server, just different characters. I tried on broken bot different profiles and fightclasses, still the same end result.

Have tried rebooting system and all the steps Droidz listed in Repair/Install topic

Again, the thing that throws me off most, is that it works just fine on one character, but not on the other.

So obviously I can run the bot, just not on Paladin. I tried disabling all plugins, still same error.

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.

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