Anyone still having problems please try this update.
I have found within windows update for May 2017 Preview of Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 for windows 7
Works perfectly again
Anyone still having problems please try this update.
I have found within windows update for May 2017 Preview of Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 for windows 7
Works perfectly again
I have found a solution to the issue. I have found within windows update for May 2017 Preview of Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 for windows 7.
Ive been using the bot since January and now all of a sudden it will not enter run mode. If I click the "play" sign but it doesn't turn on and doesn't change to allow you to stop it. Any ideas? I have checked framework repair tool and restarted pc serveral times. Reinstalled Bot as well. Logs are attached
9 May 2017 20H34.log.html
awesome thanks! it looks perfect based on description, not sure how I didn't see that one earlier.
I figured the form thing out, it works fine in fightclass with the skill on the actionbar, still doesnt explain why my macro doesn't work but it doesn't matter anymore
when did you say this was available? :p
This is not extremely relevant, but I've noticed there isn't much in the fightclass section either for vanilla. Ive got some OK ones started for warlock and druid but need some major refining.
I can't get shapeshift to work on druid for anything. Getting out of shapeshift is simple w/ an out of combat macro on the bot but the fightclass does not recognize the form spell names as I have them, anyone here have a solution?
Druid.xml
lock2.xml
I cant get the bot to shapeshift into any forms for the life of me any tips or possibly an example? I am actually on vanilla but figure it shouldnt differ much
I've also been experiencing a similar issue, my char's click to move frequency seems to be too high causing the bot to basically inch around for lack of a better term.
I restarted my computer once and it seemed to fix it. But since then it has occured again, and restarting the PC/wow/wrobot did not correct the problem.