sumodima

Thanks, seems to be fixed.

I tried changing a bunch, nothing worked. Ended up just disabling going to town which kinda sucks.

This issue is caused by the server, they have a bug that bugs your character out when you dismount from a fly mount.

Well then there's an issue with the builtin whitelist of crafting materials.

I don't know how Wrobot works on 3.3.5a but on Retail and Mop it doesn't sell herbs or ore even if sell whites/greens is selected and the whitelist is empty.

Yeah, Lordaeron is very overcrowded and the node spawn rates are pretty low especially for BC ones.

You want this 5.4.2 support for Warmane correct ? If that's the case then Droidz shouldn't bother as that realm is going to be updated to 5.4.8 on 26th of January.

If you have leveled up and learned smite while the bot was still active, you need to reboot the bot in order to get the new spells to show up.

Well there's even a specific warning asking you to exclude SotA and IoC due to issues the bot is having in those bg's.

1. 2. Set your potion of luck to your keybind 9. It's going to be used every 20 minutes (12000 seconds)

The drop down menu only shows the spells that are available in your spell book, not all of the class spells by default.

You could try deleting/moving WTF folder, that would remove all of the settings and addon presets - basically would make your wow feel as a freshly installed copy.

Could be memory corruption too but that's pretty unlikely for RAM to randomly go faulty. You could try clearing your game cache by deleting Cache folder in your WoW installation folder eg "X:\World of Warcraft\Cache"

I have not experienced as single game crash. Could you post your logs from the crashes and tell us what product were you using so we can attempt to reproduce the crash case and hopefully identify what is causing it.

1. Good suggestion, profile creator could do some work to allow easier editing of the path after the recording process. 2. Not a bug, its an intentional feature, when the bot doesn't exit properly it leaves behind traces of itself, and to avoid further issues with the bot it requires a restart of the game to work properly. 3. Black list the area for now since the log you attached isn't showing any information other than the one that was gathered at launch ( you likely uploaded a wrong log file ).

You could use LUA same as Auctioneer does with its easy buy out - Shift+Click

Have you tried manually adding them ? Like writing them in the field by hand.

I think you misunderstood what I meant. The wait time needs to be set before looting and not after looting. Currently it is: Cast fishing > Caught Something > Loot > Wait x > Recast And it needs to be: Cast fishing > Caught something > Wait X > Loot > Recast And the wait x needs to be a random number in between xxx-xxxx.

Thanks, I thought it works of the active buff. It's not a huge issue just noticed that it does that.

I'm aware of the fact that wrobot doesn't work when the game is minimized and that's why its trying to automatically bring the game out of the minimized state. The report is not about that. Report is about the game glitching out when both bot and the user attempts to maximize the game at the same time.